Lessons 4.1 to 4.4 gave you the rule for telling Make to Order (MTO) from Make to Stock (MTS), and showed how each one changes lead time, forecast risk and warehousing. This page is for anyone who now has to apply that rule to a document sitting in front of them: a purchase order, a company description, or a factory's internal production instruction. Without this skill, a merchandiser judges a document by how it looks, a mistake that costs real decisions upstream. A well-formatted internal stock order can look exactly like a confirmed export purchase order. This lesson does not add a new rule. It gives you practice reading real, sometimes similar-looking documents with the same three questions you already know, until you can do it fluently.
You need: the three-question method from lesson 4.1, and the difference between MTO and MTS from lessons 4.1 to 4.4.
By the end of this lesson you can:
Not covered here: how MTO changes lead time and cash flow (lesson 4.2), how MTS changes forecasting and markdown risk (lesson 4.3), and how a hybrid company is recognised at the company level rather than the document level (lesson 4.4).
| Term | Meaning |
|---|---|
| Make to Order (MTO) | Production starts only after a specific buyer has confirmed a specific order, with quantity, price and delivery date agreed. |
| Make to Stock (MTS) | Producing against the seller's own sales forecast, rather than a single confirmed buyer order. |
| Hybrid production model | A company that runs Make to Order and Make to Stock lines side by side, usually split by customer, product line or channel. |
| Purchase order | A document from a buyer confirming quantity, price and delivery date, which commits the buyer to pay for the goods it orders. |
| Forecast | A company's own estimate of what it expects to sell, used to decide how much to produce before any specific sale exists. |
| Stock code | An internal reference number a company gives a product it plans to hold as its own stock. |
| Production instruction | A factory's internal document that authorises a specific production run, whatever triggered it. |
A document is MTO if a specific, already-agreed sale stands behind it, and MTS if a forecast stands behind it instead. This is the whole test. It has nothing to do with whether the document is called a purchase order, whether it has a price and a quantity, or how professional it looks. Two documents can share every visible field, buyer name, reference number, price, delivery date, and still belong to different classifications, because what stands behind them is different. Reading a document correctly means asking what triggered it, never judging it by its shape.
| What can differ | The shapes you will meet | Why it matters |
|---|---|---|
| A clean MTO document | A purchase order with a fixed quantity, price and delivery date, referencing a named external buyer and a signed contract, such as Northline Apparel's Order A purchase order, NA-2291. | The easiest case: the confirmed sale is named on the document itself, so the trigger is visible. |
| A clean MTS document | An internal production instruction referencing a stock code and a forecast quantity, with no external buyer named on it, such as Cedar & Co.'s internal orders to Delta Garments. | No confirmed sale exists yet; the goods are made against Cedar & Co.'s own estimate of what its shops will sell. |
| An ambiguous document | A document with a quantity and a price, issued by a brand's own buying office against its own forecast, not a confirmed retail sale. | The giveaway is who the issuer is selling to next, not the document's formatting; a forecast order can carry every field a purchase order has. |
| A hybrid company's mixed order book | A factory's full order book, with several purchase orders side by side, some tied to a specific external buyer and some tied to an internal stock code. | Reading the whole book means classifying each line separately, per lesson 4.4, never giving the whole factory one label. |
None of these four shapes needs a new rule. Each one is answered by asking what triggered the document, then checking whether the same company runs a different pattern on a different line.
The case we followThis course's practical exercise reuses documents already established earlier in the course. Northline Apparel's Order A purchase order, reference NA-2291, states a fixed quantity of 15,000 pieces, an agreed FOB price, and a delivery date, and names Northline Apparel as the confirmed buyer. Cedar & Co.'s internal order has the same fields filled in, a "buyer" name (Cedar & Co. itself), a reference number, an agreed price and a delivery date, issued against Cedar & Co.'s own stock forecast rather than a confirmed sale to a shop customer. Delta Garments' order book shows a third shape: several purchase orders side by side, some like Northline Apparel's and some like Cedar & Co.'s, on the same page.
| Document | Fields present | What actually triggered it | Classification |
|---|---|---|---|
| Northline Apparel's Order A, NA-2291 | Buyer name, reference number, price, quantity, delivery date | Northline Apparel's own already-secured sale plan for its own shops | MTO |
| Cedar & Co.'s internal stock-code order | Same field types: "buyer" name, reference number, price, quantity, delivery date | Cedar & Co.'s forecast of what its 12 shops might sell | MTS |
| Delta Garments' combined order book | Several lines, mixing both field patterns above | Different triggers on different lines, from different customers | Hybrid order book (classify each line) |
This exercise counts correct classifications, not a cost. Given four sample documents shown in the workplace scenario and the working template, a learner applies the same three-question method to each one and names it MTO, MTS, or hybrid-context, with no new figures introduced.
A common mistake is deciding a document's classification from whether it "looks like" a normal purchase order, rather than from what actually triggered it. A well-formatted, professional-looking internal MTS production order can carry the same layout as an MTO purchase order: a buyer field, a price, a quantity, a delivery date. The real test is always the trigger, a confirmed external sale, or a forecast, never the paperwork's format. A learner who stops at "it has a price and a quantity, so it must be MTO" will misclassify Cedar & Co.'s own forecast orders every time.
This lesson does not teach a new rule. It gives you practice reading real documents with the rule you already know: a document is MTO if a confirmed sale stands behind it, and MTS if a forecast stands behind it. Two documents can look identical, same buyer field, same price, same quantity, same date, and still be different, because what stands behind them is different. A factory's whole order book can mix both, so classify each line on its own, never the whole factory at once. Never judge a document by how professional or complete it looks.
A learner is shown two documents side by side, deliberately similar in format. One is Northline Apparel's Order A purchase order: a buyer name, reference number NA-2291, an agreed FOB price, and a delivery date. The other is a document from Cedar & Co. with the same fields filled in, a "buyer" name (Cedar & Co. itself), a reference number, an agreed price, and a delivery date, but issued against Cedar & Co.'s own stock forecast, not a confirmed sale to a shop customer.
Does having the same fields filled in, buyer, price, quantity, date, make both documents MTO? Decide before opening the answer.
No — matching fields do not decide the classification; what matters is what stands behind the order. Northline Apparel's order is confirmed against Northline Apparel's own already-secured sale plan: its own shops will sell these specific T-shirts. Cedar & Co.'s order, despite looking identical in format, is triggered by Cedar & Co.'s own forecast of what its 12 shops might sell, not a confirmed sale, so it remains MTS from Cedar & Co.'s side.
Two facts decide this together: what triggered each document (a confirmed sale for Northline Apparel, a forecast for Cedar & Co.), and whose risk sits behind that trigger (Northline Apparel already has the sale secured; Cedar & Co. is still guessing at its own future sales). Neither document's fields alone would have told you this.
From Delta Garments' point of view, both are equally firm production orders it will fulfil under agreed terms, exactly lesson 4.1's own point. The classification difference matters upstream of Delta Garments, not to Delta Garments' own commitment to produce.
Misreading a forecast-driven MTS order as MTO, or the reverse, does not change what a factory is paid; Delta Garments is committed to produce and be paid either way, once a purchase order is placed. What it changes is who is misled upstream. A bank or an investor assessing Cedar & Co.'s inventory risk would reach the wrong conclusion if Cedar & Co.'s MTS commitments were mistaken for pre-sold, MTO-style orders with no forecast risk behind them.
This is framed qualitatively rather than in cost, because the loss from a misread document falls on whoever relies on the classification, not on the factory's own payment.
The workbook's "Decide" sheet already shows Order A and Cedar & Co.'s order worked through three questions, trigger, forecast owner, and whether the company also runs the other pattern, with a formula that outputs MTO, MTS, or Hybrid. Run each sample document through the same sheet, in the "Your order or company" column, and check your answer against the formula.
| Sample document | Trigger | Forecast owner | Other pattern too? | Formula result |
|---|---|---|---|---|
| Northline Apparel's Order A, NA-2291 | Confirmed sale | Not applicable | Yes (Cedar & Co.'s line) | |
| Cedar & Co.'s internal stock-code order | Forecast | The brand itself | Yes (Order A) | |
| The ambiguous buying-office document | Forecast | The brand itself | Depends on its other lines | |
| Delta Garments' combined order book, per line | Mixed, per line | Mixed, per line | Yes, by definition |
1. What is the one reliable test for classifying a production document as MTO or MTS?
2. Two purchase-order-style documents have identical fields: buyer name, price, quantity, delivery date. Does that guarantee they are the same classification?
3. When reading a factory's whole order book with several different orders on it, should a learner assign one classification to the whole factory?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Make to Order (MTO) | الإنتاج حسب الطلب | Fabrication sur commande (MTO) | Siparişe göre üretim (MTO) | Production starts only after a specific buyer has confirmed a specific order, with quantity, price and delivery date agreed. |
| Make to Stock (MTS) | إنتاج حسب المخزون | Fabrication sur stock | Stoğa üretim | Producing against the seller's own sales forecast, rather than a single confirmed buyer order. |
| Hybrid production model | نموذج إنتاج مختلط | Modèle de production hybride | Hibrit üretim modeli | A company that runs Make to Order and Make to Stock lines side by side, usually split by customer, product line or channel. |
| Purchase order | أمر الشراء (طلبية الشراء) | Bon de commande | Satın alma siparişi | A document from a buyer confirming quantity, price and delivery date, which commits the buyer to pay for the goods it orders. |
| Forecast | التوقع (توقع المبيعات) | Prévision (prévision des ventes) | Tahmin (satış tahmini) | A company's own estimate of what it expects to sell, used to decide how much to produce before any specific sale exists. |
| Stock code | رمز صنف المخزون | Code article de stock | Stok kodu | An internal reference number a company gives a product it plans to hold as its own stock. |
| Production instruction | أمر إنتاج داخلي | Instruction de production | Üretim talimatı | A factory's internal document that authorises a specific production run, whatever triggered it. |
You can now read any document and say whether it is MTO, MTS, or part of a hybrid order book. The next course follows one order's whole life, from the first enquiry a buyer sends to the day the goods are shipped. Back to the course map