ERP for Engineer-to-Order Machine Builders: What to Require and What to Skip

Project-Centric BOMs and Engineering Release

In ETO, the bill of materials is not finished when the order is entered. Mechanical design releases assemblies in waves, the electrical designer adds panel components later, and purchasing needs long-lead items such as servo motors, robots, and PLCs before the design is complete. The ERP must accept a partial BOM, let purchasing buy against it, and track what has been released versus planned.

Check whether it can link to your CAD or PDM, SolidWorks PDM, Inventor Vault, or Teamcenter, to import BOMs with revision, and whether part numbers can be created on the fly with controlled numbering.

• Partial and phased BOM release by project
• CAD or PDM BOM import with revision awareness
• Phantom and subassembly handling for repeat modules
• Long-lead purchasing before design freeze

Job and Project Costing That Matches How You Quote

Your quote lists engineering, controls, fabrication, purchased parts, and outside services. The ERP should let you set up a project budget on those same lines and show committed cost, actual cost, and estimate to complete by line. Look for work breakdown structure or task levels, labor booked by discipline, purchase order commitments visible before receipt, and WIP reporting.

Infor SyteLine and CloudSuite Industrial have project accounting, Epicor Kinetic has project management, and NetSuite uses its project modules. Verify with each vendor how engineering time gets captured, since this is the weak spot.

Engineering Change Control and Change Orders

After release, a change in a drawing must flow to purchasing, the shop floor, and the customer commercial record. The ERP should log the change, show affected parts and open purchase orders, and let you attach a cost and schedule impact. If it only edits the BOM without history, you lose the evidence for charging the customer.

Ask how the system handles rework of already-purchased or machined parts and how change orders attach to the project budget, so the original baseline stays visible next to the revised budget.

Scheduling, Billing, and Revenue Recognition

ETO scheduling is project milestone scheduling with shared resources: a few designers, a controls programmer, a fabrication cell, and a test floor. Few mid-market ERPs finite-schedule engineering well, so many builders use project scheduling alongside ERP. For billing, confirm milestone and progress billing with retention, and percent-complete revenue recognition under ASC 606 where you recognize over time.

Your accountant should sign off on the method and the reports before you buy, because rework of WIP schedules at year-end is painful.

When Not to Replace Your ERP

If your current system handles purchasing, inventory, and financials acceptably and the pain is in quoting and project reporting, replacement is the expensive answer. Often a project costing layer, better time capture, and a read-only analytics or AI layer over the existing ERP gets most of the value for a fraction of the cost and risk. Replace when the BOM, costing, and billing model fundamentally cannot represent your projects, not when users merely dislike the screens.