ERP for Machinery and Plant Engineering — what really matters in engineer-to-order, variant and make-to-order manufacturing.
In machinery and plant engineering, the ERP system determines whether projects with long lead times, evolving bills of materials and a demanding after-sales business remain manageable. Standard manufacturing functionality is typically not enough when engineering, production and service need to work from the same data. This page outlines which requirements tend to be decisive in this setting and how commonly evaluated systems relate to them.
Typical core requirements in machinery and plant engineering
- Make-to-order and engineer-to-order with a growing bill of materials: in machine building, the complete BOM often does not exist when the order starts. The ERP must handle incomplete structures that change during engineering without blocking procurement and production.
- Project business with milestone logic: down payments, partial acceptances and milestone-based invoicing shape order processing. What matters is that project structure, scheduling and commercial processing are connected end to end in the system — not managed in spreadsheets alongside it.
- Separation of engineering and manufacturing BOM: E-BOM and M-BOM follow different logics. The system should maintain both views and transfer changes in a controlled way; otherwise, experience shows that what is engineered and what is built start to diverge.
- CAD/PLM integration: item creation, BOM transfer and change management from the CAD or PLM system are a continuous process in machine building, not a one-time import. The quality of this interface largely determines the daily workload in production planning.
- After-sales, service and spare parts: delivered machines often live for decades. The ERP must represent the installed base with as-built structures, serial numbers and service history, so that spare-part identification and service calls do not depend on individual employees' knowledge.
- Export processing and compliance: shipments to third countries require export control checks, preference calculation and properly maintained proofs of origin. Retrofitting these processes is typically more expensive than testing them during selection from the outset.
What really changes in the selection.
ERP selection in machinery and plant engineering differs structurally from selection in repetitive manufacturing or trade: the individual order is the dominant object, not the item master. Costing, procurement, production and assembly all hang off a project structure that keeps changing over months. Systems designed primarily for repeatable processes with stable master data tend to reach their limits quickly in this setting — regardless of how extensive their manufacturing modules look on paper.
A second difference lies in the role of engineering. While the ERP is the leading data source in many industries, a large share of order-relevant data in machine building originates in the CAD and PLM environment. The selection question is therefore not whether a CAD interface exists, but how changes flow through the system after production has started: who sees them, who approves them, and what happens to material that has already been ordered. In DACH selection projects, it frequently takes a demo with your own engineering data to see how robust this process really is.
Third, the service business shifts the weighting. Many machine builders earn a relevant share of their results from spare parts, maintenance and retrofits — processes that are often examined late in classic ERP selection projects. Including the installed base, service orders and spare-parts logic early in the requirements profile avoids the common outcome where the new ERP covers production well while the service business keeps running on isolated tools.
Systems typically evaluated in this setting
SAP S/4HANA
Typically evaluated when deep manufacturing, complex project structures and international group requirements come together; established partner industry solutions exist for machine building, but implementation requires a correspondingly capable project organization.
Dynamics 365 Business Central
A frequent choice in SME machine building when an industry app closes the standard product's gaps in project manufacturing, growing BOMs and service; in practice, choosing the industry solution and the partner tends to matter at least as much as the platform itself.
Dynamics 365 Finance & Operations
Typically enters the picture in the upper mid-market with complex, multi-level manufacturing and several legal entities — when Business Central appears structurally too small and SAP too heavyweight as an overall package.
Odoo
Evaluated by smaller machine-building companies prepared to cover industry requirements such as E-BOM/M-BOM separation or milestone billing through customization and modules; this presupposes internal or external development capability and disciplined release management.
What to verify concretely in your selection project.
- In the demo, have a real order created with an incomplete BOM and apply an engineering change after production start — including the effect on material already ordered.
- Test the CAD/PLM integration with your own engineering data: new item creation, BOM transfer and a change run, not just the vendor's standard demo dataset.
- Walk through a project with down payment, milestone invoicing and partial acceptance — all the way into financial accounting, not just to the order screen.
- Test the service process on a delivered machine: open the as-built structure, identify a spare part, and bill a service order with material and time.
- Test export processing on a third-country case: export control check, supplier declarations and preference calculation working together.
The mistakes we see most often in this constellation.
- Narrowing the selection to manufacturing functionality and looking at engineering, service and export only during implementation — corrections are significantly more expensive there.
- Evaluating demos on vendor sample data: machinery-specific challenges such as growing BOMs only reveal their pitfalls with your own, unfinished real data.
- Equating a partner's industry solution with the standard product without separately assessing maintenance, upgradeability and the long-term viability of the industry extension.
- Treating the spare-parts and service business as a side topic, even though it is often the most stable long-term profit source and requires its own data structures.
Neutral editorial assessment — no ranking, no recommendation, no paid placements. Our approach is documented in the methodology.
Which system fits your constellation?
Our structured selection advisory captures your situation systematically and shows which systems realistically belong on your shortlist.