Blog

How to Choose ERP for Custom Manufacturing

Choose ERP for custom manufacturing by testing real order workflows, BOM changes, costing, integrations, and implementation fit.

By ITHENA ITHENA Insights 8 min read

TL;DR

The right ERP for custom manufacturing keeps a customer order connected from requirements and estimates through engineering, purchasing, production, delivery, and financial close. Compare vendors by giving each the same realistic order and change request. Watch how the system handles revisions, material shortages, production progress, and job costs, then record what was demonstrated, what needs configuration, and where manual work remains.

PanelOps is built on ITHENA iERP, connecting quoting, BOMs, purchasing, inventory, scheduling, production visibility, and project financials in one industrial ERP workflow.

Key Takeaways

  1. Start with real order workflows and exceptions, not a feature checklist.
  2. Map each product family to its production model and required controls.
  3. Test a BOM revision after purchasing starts and trace its impact through the job.
  4. Compare estimated, committed, actual, and forecast costs.
  5. Score implementation, integration, security, support, and user adoption alongside product fit.

Quick Q&A

What should a custom manufacturer look for in ERP?

Look for connected workflows across customer requirements, estimates, BOMs and revisions, purchasing, inventory, production, delivery records, and job costing. The right fit depends on your products, order variation, industry needs, and current systems.

Can custom ERP support a quote before the final BOM is ready?

Some workflows begin with an estimate based on confirmed requirements, assumptions, allowances, and supplier input before engineering completes the BOM. Ask vendors to demonstrate how those details are reviewed and carried into the order. For a practical walkthrough, read how to quote custom machines before the parts list is ready.

How should I compare ERP vendors?

Give each vendor the same order scenario, change request, and scorecard. Compare demonstrated workflow fit, revision control, costing, integrations, implementation, security, and usability. Mark standard features, configuration, custom development, and manual work separately.

How do I test BOM change control?

Change a component after a purchase order has been placed. Check approvals, current revision, open orders, received inventory, reservations, shop floor work, schedule, and project cost.

What costs belong in an ERP implementation estimate?

Include licensing, configuration, custom work, migration, integrations, testing, training, support, internal staff time, and ongoing maintenance. Ask who owns each task and how completion will be measured.

What is the relationship between PanelOps and ITHENA iERP?

PanelOps is built on ITHENA iERP. It connects the workflows custom manufacturers, OEMs, and system integrators use from quote to production and financial close. Explore iERP / PanelOps.

Production model What is known when demand arrives What the ERP should demonstrate
Make to stock Product is defined before a customer order. Forecasting, replenishment, inventory accuracy, and production planning.
Make to order Product is largely defined; the order triggers production or purchasing. Order linked materials, promised dates, and job cost visibility.
Configure to order Product platform and permitted options are defined. Configuration rules, pricing, option compatibility, and approved order transfer.
Engineer to order Significant design work is specific to the customer. Project control, order specific BOMs, revision approval, purchasing impact, and cost tracking.
Table 1: Order scenario for each ERP demonstration

Choosing the Right ERP for Custom Manufacturing

Compare ERP approaches with a real order

A purpose-built industrial ERP may fit common workflows in its target industries. Test its fit for your production models, integrations, upgrades, and support needs.

A general manufacturing ERP can cover a broad range of processes. Check how much configuration, partner software, or process change your workflows require

A highly custom ERP can support distinctive workflows. Weigh that fit against the ownership, testing, documentation, and ongoing maintenance of custom code and integrations.

Use the same order scenario for each option. Compare the product and delivery plan, not the category label.

End-to-end ERP workflow connecting custom quotes to BOM, procurement, production, delivery, and financials

One custom order stays traceable from quote to financial close.

Follow one job from quote to financial close

Use a real request for quotation (RFQ) as the backbone of each vendor demonstration. Include enough variation to expose how information moves between sales, engineering, purchasing, production, and finance.

1. Start with the quote and order handoff

Ask the vendor to show how customer requirements become an estimate and approved order, including how assumptions, early quantities, labor, supplier input, exclusions, approvals, and expected margin are recorded. Then follow the approved information into the next workflow without reentering it.

A quote may begin before the final BOM is ready. Keep the demonstration focused on the ERP handoff and use the dedicated custom machine quoting guide for the estimating process itself.

2. Release and revise the BOM

Ask the vendor to release an initial BOM, then change one component after purchasing has begun. The demonstration should show who requested and approved the revision, which version is current, and when it takes effect.

Trace the change through open purchase orders, received inventory, material reservations, production work, schedule, and job cost. Ask what happens if the old component is already on the shop floor or a supplier cannot cancel an order. A useful workflow makes the exception visible and gives each team a clear next action.

3. Connect purchasing and production

Follow a long lead item from the job requirement to the supplier order and receipt. Check whether the buyer can see the quantity required, date needed, supplier lead time, order status, partial receipts, and shortage risk. Ask whether available inventory can be distinguished from stock reserved for another job.

Then ask a production user to find the released job information, record labor or progress, and report a delay. Check whether production status updates the schedule and whether authorized users can tell planned work from work in progress. If shop floor or quality systems provide key data, ask where it is owned and how the ERP receives it.

4. Close delivery and project costs

Check how the system records the final configuration, serial or lot details where required, customer documents, and outstanding work. Ask finance to reconcile the original estimate, purchase commitments, labor and material actuals, billing, and forecast cost to complete.

Use the same sequence with every vendor: Quote → BOM → Purchasing → Production → Delivery → Financial close. Record every manual handoff and every point where staff must leave the ERP to find the current answer.

Score the evidence, not the presentation

Score each category from 1 to 5 and calculate weighted points as (rating ÷ 5) × category points. A low score means the workflow needs substantial manual work. A middle score means it depends on configuration or a documented workaround. A high score means the vendor demonstrated it and explained how it is maintained.

For each requirement, record whether it is standard, configured, custom-built, supplied by another product, or outside the ERP. Note the evidence type: demonstration, documentation, reference, or future commitment. Keep critical workflow, security, and integration gaps visible even when the total score is high.

Evaluation area Points Evidence to request
Quote to order workflow and production model fit 25 Run the RFQ, estimate, approval, and handoff.
BOM revisions and change impact 15 Trace a component change through purchasing, inventory, schedule, production, and cost.
Project costing and margin 15 Compare estimate, commitments, actuals, and forecast for one job.
Purchasing and inventory 10 Show lead times, allocations, partial receipts, substitutions, and shortages.
Planning, production, and delivery 10 Show constraints, status, labor capture, and completion records.
Integration, access, and security 10 Review data ownership, exception handling, access, audit history, and export.
Implementation and support 10 Review migration, testing, training, ownership, support, and total cost.
Usability and adoption 5 Have sales, engineering, purchasing, production, and finance users complete common tasks.
Total 100  
Table 2: ERP Evaluation Scorecard: Evidence-Based Selection Criteria

Plan implementation and integration

ERP selection also sets the direction for process change and delivery. List the systems that must connect and identify which system owns each important record. Ask vendors to show how a duplicate, changed record, or failed transfer is detected and resolved. Review the integration design, then test an exception in a realistic workflow.

Build a total cost view that includes licenses, configuration, custom development, migration, integrations, testing, training, support, internal staff time, and ongoing maintenance. Ask who owns each task, what needs to be ready first, and how progress will be measured. Treat estimates and timelines as planning inputs to validate.

Involve future users before selection. Have sales prepare a quote, engineering revise a BOM, purchasing handle a shortage, production report progress, and finance review project cost. Their experience can reveal friction that a polished presentation will not.

Where ITHENA fits

PanelOps connects customer quoting and approvals with project execution, BOMs, purchasing, inventory, scheduling, shop floor progress, and financials. Explore iERP / PanelOps.

For the quote and CPQ workflow before the ERP handoff, see ITHENA iCRM. Use iCRM consistently as the product name throughout this article.

Conclusion

The right ERP for custom manufacturing is the system that keeps requirements, quote assumptions, BOM revisions, material decisions, production progress, delivery records, and job costs connected in the way your business works. Demonstrate one realistic order with every vendor and use the same scorecard to compare evidence, gaps, implementation effort, and total cost. That gives your team a practical basis for choosing a system that can support the work from first quote to financial close.

Use a real order scenario to explore the workflow and identify where your team needs better continuity or visibility.

Sources

  1. SAP Help Portal: Sales order processing with engineer-to-order production: Example of customer-specific engineering requirements before final production details are available.
  2. ITHENA PanelOps industrial ERP: Product workflows and reported customer results.
  3. ITHENA iCRM: CRM, configuration, pricing, quoting, and order workflows.

Next Step

Read the guide to quoting custom machines before the parts list is ready to see how the estimate can prepare for the ERP handoff.

Get started.

Connect every order from quote to production and financial close.

Streamline quoting, BOM, purchasing, production, and job costing into a single workflow