Make to Order (MTO): Definition, Process & MES Role 2026

What is Make to Order (MTO)?

Make to Order (MTO) — German Auftragsfertigung or auftragsbezogene Fertigung — is a production strategy in which manufacturing only starts after a confirmed customer order. Nothing is built for stock, so finished-goods inventory is near zero and each order can carry customer-specific configuration. MTO is planned at ISA-95 Level 4 (ERP) and executed at Level 3 (MES).

MTO sounds simple on a slide and is difficult in reality. The real question is not "do we build to order?" but "how quickly and how accurately can we translate an incoming order into a shop-floor reality — with the right material, the right capacity, the promised date, and a cost that still carries margin?" That is where most MTO environments struggle, and where the gap between ERP and the shop floor becomes painfully visible. After 30+ years building MES for discrete manufacturers, I have seen this same gap in every tier of industry.

Make to Order vs. Make to Stock vs. Engineer to Order

MTO is most often confused with its neighbours on the production-strategy spectrum. The differences matter because they drive lead time, pricing, and the entire planning logic.

A fourth strategy, Assemble to Order (ATO), sits between MTS and MTO: modules are produced to forecast, final assembly happens against the order. Many real factories run a mix — MTS for runners, MTO for exotic variants, ETO for strategic projects — in the same plant. The MES must handle all three without forcing one logic onto the others.

How an MTO order flows through ERP and MES

In a mature MTO operation the order flow is tight and bidirectional. The ERP owns the commercial order, the bill of materials, and the promised date. The MES owns what actually happens on the shop floor — cycle times, stoppages, scrap, operator and machine assignment, and order confirmation back to the ERP.

1. Order entry & configuration — ERP receives the customer order, expands the configuration into a production-ready BOM, and reserves material.
2. Capacity check & scheduling — either ERP or an APS validates available capacity against the promised date. Without real-time shop-floor data this check is an estimate, not a commitment.
3. Release to MES — the work order, routing, and operations are pushed to the MES. Operators see the order on shop-floor clients; machines receive the correct program or setup parameters.
4. Execution & feedback — cycle counts, stops, reasons, and quality events are captured in real time. Deviations (scrap, rework, overruns) are visible within seconds, not at end-of-shift.
5. Confirmation to ERP — completed quantities, times, and cost-relevant events flow back automatically. The ERP sees the order status without manual re-entry.

Why MTO is harder to plan than it looks

MTS forgives planning errors — the warehouse absorbs them. MTO does not. Every forecasting miss, every unannounced micro-stop, every late material delivery hits the promised date directly and visibly. Three failure modes show up in almost every MTO operation:

• Capacity promises based on paper numbers. If the planning system assumes 85 % availability but the real figure is 68 %, every promised date is already at risk the moment it is quoted. Until OEE is measured automatically, nobody in the plant can distinguish the two.
• One-way ERP-to-MES integration. Orders flow down, nothing flows back. Planners replan against stale data, customers get late surprises, post-calculation is done manually in Excel.
• Setup time treated as a constant. In real MTO the setup is the job — especially in forging, stamping, injection moulding. Treating it as a fixed average destroys the plan on the first changeover.

None of these are software problems. They are measurement problems. Fix the measurement and the planning logic starts to work.

What MES adds on top of ERP in an MTO environment

Every MTO company already has an ERP — SAP, Microsoft Dynamics, proAlpha, Infor, InforCOM, Navision, or similar. The MES does not replace it. The MES closes the gap between the order as the ERP sees it and the order as the machine actually runs it.

Concretely, the MES delivers four things the ERP cannot: real-time order status at the machine (not at end-of-shift), automatic mapping of machine cycles to the correct work order, capture of unplanned stops and scrap with reason codes while they are happening, and bidirectional confirmation so the ERP sees reality instead of a manual estimate. The result is that the promised date stops being a hope and becomes a planned number with a measurable confidence interval.

Hard-earned lesson from 30+ years in discrete MTO manufacturing: a mid-sized forging and machining supplier was quoting lead times of six weeks against a reported machine availability of 82 %. On-time delivery sat around 71 % and nobody could fully explain why. When we connected the presses and machining centres and started capturing stops automatically, real availability was 64 %. The planning logic had been building every promise on a number that was 18 points too high. The fix was not a faster plan — it was an honest one. Once the new baseline was quoted to customers, on-time delivery climbed above 90 % within a quarter, the sales team stopped firefighting, and margin on the order book improved because rushed overtime disappeared. Lesson: in MTO, planning accuracy is a function of measurement accuracy. You cannot out-plan a wrong number.

What MTO looks like in the SYMESTIC deployment pattern

Several companies in our customer base run exactly this pattern. Schmiedetechnik Plettenberg operates a classic MTO profile — variable order sizes, demanding setups, high quality requirements on forged and machined parts — integrated bidirectionally with InforCOM as the ERP: work orders, routings and master data flow into SYMESTIC, while quantities, stops and status flow back automatically. Axicom runs enterprise MES across two plants with a brownfield mix of CNC, injection moulding and potting, all order-driven. Meleghy, across six plants in Germany, the Czech Republic and Hungary, is bidirectionally integrated with SAP R/3 via ABAP IDoc for its automotive body-in-white programmes — 10 % less downtime, 7 % more output, 5 % availability gain in six months.

What these deployments share is not the ERP, not the industry, and not the machine park. It is the order of operations: measure the shop floor first, connect it to the ERP second, let planning accuracy catch up third. Across 15,000+ connected machines in 18 countries, that sequence holds.

FAQ

What is Make to Order in simple terms?
Make to Order (MTO) means a product is only manufactured after a specific customer order has been confirmed. Finished-goods inventory is near zero, each order can be configured to the customer's specification, and planning revolves around promised dates rather than stock replenishment. Typical industries are forging and metal processing, automotive Tier-n suppliers, furniture, and electronics.

What is the difference between MTO and MTS?
Make to Stock (MTS) produces to forecast and ships from inventory — lead time to the customer is hours or days. Make to Order (MTO) produces against a confirmed order — lead time is weeks. MTS optimises for availability and scale, MTO optimises for flexibility and working capital. Many plants run both in parallel: MTS for runners, MTO for variants.

How does MTO differ from ATO and ETO?
Assemble to Order (ATO) produces modules to forecast and assembles them against the order — a middle ground between MTS and MTO. Engineer to Order (ETO) starts each order with an engineering phase, producing a one-off item; lead times run in months. MTO itself assumes the product design exists; only the specific configuration and timing come with the order.

What lead time is realistic for MTO manufacturing?
It depends on complexity, material availability, and the number of production steps. Configured components with standard material and one-to-three operations typically run two to four weeks. More complex MTO parts with heat treatment, surface finishing, and multiple machining steps run four to eight weeks. Material procurement is usually the long pole, not production itself.

Why do MTO delivery dates slip?
Three recurring reasons. Capacity was promised against an optimistic availability figure that the real shop floor cannot hit. Material arrives late because supplier integration is manual. Setup and changeover times are treated as averages when they are in fact highly variable. All three are invisible without automatic shop-floor data, and all three disappear once the data exists.

Does MTO need an MES, or is ERP enough?
ERP alone works when order volume is low and the shop floor is stable. As soon as order mix, changeover frequency, or machine count grows, the ERP cannot see reality fast enough — confirmations arrive hours late, replanning runs on stale data, and post-calculation is done in Excel. An MES closes that gap by feeding real-time execution data back into the ERP, which is exactly what MTO planning depends on.

Which industries are the strongest fit for MTO?
Forging and metal processing, automotive Tier-1/2/n suppliers producing customer-specific body or interior parts, electronics assembly, furniture manufacturing, building products, and special-component suppliers across plastics and metals. The common pattern is high configuration, moderate-to-high changeover frequency, and a business model where inventory risk is too expensive to carry.

How does SYMESTIC support a Make-to-Order environment?
SYMESTIC integrates bidirectionally with the ERP — SAP R/3 via ABAP IDoc, proAlpha, Infor/InforCOM, Microsoft Dynamics/Navision, and others via REST or file interface. Work orders and master data flow from the ERP; quantities, stops, reasons and order status flow back automatically. Setup, cycle time and scrap are captured in real time. See production planning, production control, and the ISA-95 reference model for the integration pattern (ISA-95).

Related: MES: Definition, functions & benefits · OEE: Definition, calculation & practice · Make to Stock · Advanced Planning & Scheduling (APS) · ISA-95 · Production planning module · Production control module · Metal processing industry.

About the author

Uwe Kobbert

Founder and CEO of SYMESTIC GmbH. 30+ years in manufacturing — Consultant at SAS, Head of Industry at STERIA responsible for process control and MES in food & beverage, founded SYMESTIC in 1995 in Dossenheim near Heidelberg. Led the mid-2010s rebuild from on-premise to cloud-native. Today: 15,000+ connected machines in 18 countries, 5,000+ users, 0% customer churn 2024, ~150% SaaS growth 2024, fully self-financed. Dipl.-Ing. Nachrichtentechnik/Elektronik. Nominated for the Großer Preis des Mittelstandes (Oscar-Patzelt-Stiftung). · LinkedIn