Industry Observation: MTO and MTS Are Not Just “Produce After Receiving an Order”

Many wrong MTO/MTS decisions come from mixing business language with system-level planning concepts.

MTO and MTS are old concepts, but they still cause wrong decisions in ERP projects. The problem is not that the words are difficult. The problem is that many teams understand them only from a business phrase: produce after receiving a customer order.

That definition is not completely wrong, but it is incomplete. In SAP implementation, the real question is often not whether production is triggered by demand. MRP always creates supply from demand. The real question is the dimension of supply-demand balancing, cost collection, traceability, and special stock.

Why companies still struggle with this basic decision

Some companies switch from MTS to MTO years after go-live because they want better traceability. Others switch from MTO back to MTS because they want fewer adjustments and less operational friction. Both directions can be reasonable in a specific context, but both can also be wrong if the basic concept is misunderstood.

The decision touches sales and operations coordination, finance, inventory ownership, production planning, and system configuration. It is not a simple label attached to a finished product.

Business “make to order” and system MTO are different things

From a business perspective, people often say a material is purchased or produced only after there is demand. But from a system perspective, that does not automatically mean MTO.

For example, a finished product can be configured as MTS. If there is no forecast and a sales order is created, production may still be driven by the sales order quantity. This looks like “make after order” in business language, but it is still MTS in the system.

Another common case is that forecast prepares semi-finished goods or raw materials, while the sales order drives final production. This can still be an MTS planning design. The sales order is involved, but the system-level meaning is not the same as MTO.

The key point: business language describes why supply is needed; system language decides at which dimension supply and demand are balanced.

A more useful way to judge MTO and MTS

The first dimension is supply-demand balancing. Should supply be separated by sales order, shared across demand, or controlled through another dimension? This is often the most important planning question.

The second dimension is cost collection. MTO can make cost analysis more detailed, but it also brings management consequences. Traceability, special stock, changes, substitutions, and execution adjustments all need to be considered together.

A typical misunderstanding

A business team may say, “Raw materials are purchased by order,” meaning they purchase only when production creates demand. A consultant may then conclude, “Use MTO for raw materials.” These two statements are not on the same level.

The first statement describes business discipline. The second changes system planning logic. If these two levels are confused, the project may introduce unnecessary complexity while still not solving the real traceability or planning problem.

So MTO/MTS should not be decided by a slogan. It should be decided after clarifying the business objective, the system planning dimension, the cost impact, and the later change cost.

Product Update: A Business Suite with SAP-inspired Architecture
A suite that brings Lean ERP logistics, SRM, MES, WMS, B2B, planning, records, actions, and insights into one architecture.