Engineer-to-Order (ETO)
Engineer-to-Order (ETO) describes production where each customer order requires substantial engineering before manufacturing can start. ETO contrasts with Make-to-Order (standard products produced after order) and configure-to-order (assembly from pre-engineered options). ETO is the dominant production strategy for one-off industrial installations, custom machinery, large industrial plants, complex tooling and project-based engineering services — all heavily represented in DACH machinery and industrial-equipment industries.
Defining characteristics
- Per-order engineering — design effort for each order rather than reusable designs
- Long lead times — typically 3-24 months from order to delivery
- Project structure — orders managed as multi-phase projects with milestones, earned-value accounting, progress billing
- Customer involvement — ongoing dialogue and design reviews through the project
- Engineering changes during production — changes after start of manufacturing are common
- Project-specific BOMs and routings — created per project rather than from master templates
- Specialised resources — skilled engineers, specific machine capabilities
- Risk concentration — large projects with significant project-specific risk
ETO-specific ERP requirements
ETO ERP must integrate project management with production. Critical capabilities. Project structure: multi-level WBS with phases, milestones, deliverables. Project accounting: per-project P&L with percent-of-completion revenue recognition. Project BOM management: per-project BOMs that evolve through the engineering phase. Capacity planning: skilled-engineer capacity alongside machine capacity. Procurement: project-specific purchases with extended lead times. Change management: engineering changes during the project lifecycle without disrupting production execution. Progress billing: milestone or percentage-based invoicing to customer with retentions. Document management: project-specific drawings, specifications, customer correspondence with audit-trail. Service integration: post-installation service, spare parts, maintenance contracts.
Top ERP vendors for ETO
Specialist ETO: IFS Cloud — particularly strong in engineer-to-order, with deep project-business capabilities; abas ERP — DACH-built mid-market with native project structures; proALPHA — project-business overlay with APS for scheduling; Microsoft Dynamics 365 F&O with Project Operations — strong project capabilities; Infor LN — classical ETO and industrial-equipment strength. Enterprise: SAP S/4HANA with Project System, Oracle Cloud ERP with Project Portfolio Management. DACH mid-market specialist: PSI Penta, godesys, ams.erp, APplus. For DACH machinery and industrial-equipment ETO operations, IFS Cloud, abas, proALPHA and SAP S/4HANA are the most-commonly evaluated; choice depends on scale and specific industry sub-segment.
Practical considerations
Three patterns. (1) Phase the engineering-to-production handoff: rigid phase boundaries (complete engineering before production starts) rarely match operational reality. Modern ETO operations use concurrent engineering — production starts on early-completed components while later engineering continues. ERP must support this overlap. (2) Manage variant proliferation: every project creates unique master data. Without discipline, ten years of ETO accumulates thousands of project-specific items that nobody uses again. Periodic master-data review identifies reusable patterns. (3) Capture lessons-learned: each project provides feedback on engineering accuracy, lead-time predictability, customer-specific patterns. ETO operations that systematically capture and apply these lessons outperform peers measurably on project margins and customer satisfaction.