Make-to-Order (MTO) Production
Make-to-Order (MTO) describes a production strategy where manufacturing of a product begins only after a customer order is confirmed. MTO contrasts with Make-to-Stock (MTS), where finished goods are produced into inventory ahead of demand. Between these poles sit Configure-to-Order (CTO) (assembly of pre-built modules per order configuration) and Engineer-to-Order (ETO) (custom engineering per order). The choice of production strategy fundamentally drives ERP requirements: variant management, BOM resolution, capacity planning, customer lead-time commitments and inventory carrying costs all hinge on the dominant strategy.
Production-strategy spectrum
Make-to-Stock (MTS): finished goods produced from forecast, held in inventory, shipped from stock. Typical for consumer goods, commodity industrial products. High inventory carrying cost, fast delivery, exposure to forecast error. Make-to-Order (MTO): standard products produced after order confirmation, often from pre-stocked raw materials. Typical for industrial equipment with limited variants. Lower inventory, longer lead time, lower forecast risk. Configure-to-Order (CTO) / Assemble-to-Order (ATO): modular products assembled per customer configuration from pre-built sub-assemblies. Typical for machinery, automotive, electronics. Engineer-to-Order (ETO): custom design per order, with engineering effort as part of the project. Typical for one-off industrial equipment, custom installations. Lowest inventory, longest lead time, highest engineering complexity. Many companies operate across multiple strategies depending on product line.
ERP implications
Each strategy drives different ERP capability emphasis. MTS requires strong demand-forecasting, S&OP processes, inventory optimisation and replenishment logic. MTO requires accurate available-to-promise (ATP) calculations, capacity-constrained planning, customer lead-time visibility. CTO/ATO requires variant configuration (rule-based BOM resolution), modular bill-of-material structures, late-customisation planning. ETO requires project management integrated with ERP, engineering-change management, earned-value accounting, custom-pricing for one-off products. Mid-market ERPs vary in their strength across these areas: abas and proALPHA traditionally excel at CTO and ETO; Sage X3 and Business Central cover MTS-MTO well; SAP S/4HANA and Oracle Cloud ERP credibly handle all four with industry-specific add-ons.
DACH context
The DACH mid-market manufacturing landscape skews heavily toward CTO and ETO. The classical German Mid-Market manufacturer makes variant-rich industrial machinery, specialty equipment or customised industrial components — rarely simple high-volume MTS products. This drives the regional dominance of ERP vendors with strong variant-configuration and project-business capabilities (abas, proALPHA, IFS, Tacton CPQ on top of various ERPs). Cloud-native ERPs (Microsoft Dynamics 365 Business Central, NetSuite, weclapp) have been gradually closing the variant-configuration gap; SAP S/4HANA covers it natively with Variant Configuration. For DACH ERP selection, the production-strategy fit is one of the most predictive single factors of long-term project success.
Hybrid strategies
Most real-world manufacturers operate mixed strategies. Postponement: pre-build sub-assemblies to stock, complete final configuration only on customer order. Combines MTS volume advantages with MTO variant flexibility. Catalogue plus custom: standard product catalogue under MTS plus engineered solutions under ETO — common in specialty industrial supply. Configure-to-stock for popular variants: forecast-driven stocking of the most-common configurations, MTO production for long-tail variants. ERP must support such hybrids without forcing the organisation into single-strategy thinking. Most modern ERPs handle hybrid strategies; the implementation discipline is in correctly classifying each product family and applying the matching production logic.