Cedar & Co. is a domestic brand that mostly runs Make to Stock replenishment for its 12 shops, but occasionally accepts a one-off Make to Order trial for a special range, produced alongside its standing orders. Across both lines, Cedar & Co.'s team touches an ERP system, a PLM system, a workflow tool and, inevitably, a few spreadsheets. By now you know what each of those four is meant to control, where a specification and its revisions live, where commercial and financial facts live, and how to hand off information across a company boundary without creating duplicate entry or conflicting versions.
This final lesson does not introduce a new rule. It gives you one decision tool that applies everything already taught, so that for any new piece of information on any order — Make to Order or Make to Stock, export or domestic — you can quickly decide which system should own it.
You need: all four earlier lessons of this course: what each tool type controls, where specifications live, where commercial and financial facts live, and how to hand off information without creating duplicate entry.
By the end of this lesson you can:
Not covered here: selecting, buying or configuring any specific software product. This lesson stays vendor-neutral and closes out the course's business rules.
| Term | Meaning |
|---|---|
| System of record | The one system that is the approved, authoritative source for a given type of information. |
| Pass-through | Forwarding a fact unchanged from its source to its destination, without retyping or reinterpreting it. |
| Revision | One numbered version of a document, such as a tech pack, produced when a change is made and approved. |
| Purchase order | A document from a buyer confirming quantity, price and delivery date, which commits the buyer to pay for the goods it orders. |
| Hand-off | The point where goods, and ownership of them, pass from one separate company to another. |
| Duplicate entry | Typing the same fact into a second tool that already has, or should have, its own controlled copy. |
Every fact in this course has fallen into one of a small number of categories: a commercial or financial fact, a technical specification fact, a task or approval status, or a fact that genuinely has no controlled home yet. The system that should own a fact follows directly from which category it belongs to, regardless of whether the order is Make to Order or Make to Stock, export or domestic.
The decision should never be made by habit ("we always put this in a spreadsheet") or convenience ("this screen is faster to open"). It should be made by asking what the fact actually is, then matching it to the tool type this course has already shown is meant to control that kind of fact.
| What can differ | The shapes you will meet | Why it matters |
|---|---|---|
| Make to Order export order | Buyer-confirmed quantity and price go to the ERP system; buyer-approved specification and revisions go to the PLM system; sample approval stages go to the workflow tool. | The four-question test gives the same answers this course's earlier lessons already worked through for Order A. |
| Make to Stock domestic replenishment | Replenishment order, receipt, stock movement and invoice all go to the ERP system; the standing product specification goes to the PLM system or its controlled equivalent. | Frequency of transactions increases; which system owns each fact does not change. |
| Hybrid brand running both lines on shared production capacity | The same factory floor produces against two different orders' own specifications and commercial terms at once. | Sharing a resource never merges two orders' facts; each order's own commercial and technical facts stay with their own owning system. |
| Agent or buying office hand-off between companies | A pass-through fact should never be retyped into a private spreadsheet at the hand-off point. | The decision test applies to the receiving side of a hand-off exactly as it applies to the side that created the fact. |
| Different product families | Socks and hosiery, knit-to-garment, terry towels and home-textiles orders each have their own specification fields and commercial figures. | The fields differ by product family; the four-question test that decides which system owns them does not. |
Cedar & Co. runs its usual Make to Stock replenishment for its 12 shops, and separately accepts a one-off Make to Order trial order for a special range, produced on the same production line as the standing replenishment work. For the Make to Stock line, the replenishment quantities, receipts and invoices belong in the ERP system, exactly as this course's third lesson established. For the Make to Order trial, the buyer-approved specification belongs in the PLM system or its controlled equivalent, exactly as the second lesson established, and the trial's own confirmed quantity and price belong in the ERP system as a separate commercial transaction from the standing replenishment orders.
Sharing a production line does not blur the two lines' own facts together. Cedar & Co.'s team applies the same four-question test to every fact on both lines, and gets a consistent answer each time regardless of which line the fact belongs to.
The worked numberOrder A's confirmed facts pass the four-question test cleanly, and the derived fabric requirement follows directly from them.
None of these five figures needed a private spreadsheet to exist correctly. The ERP system owns the confirmed quantity and price and produces the order value. The PLM system owns the approved consumption. Planning combines both owned facts to produce the derived fabric requirement, and that calculation itself belongs wherever the company's own controlled planning process lives — but the two input facts it depends on are never in doubt about which system owns them.
A team may complete the course workbook once, feel satisfied that "we have sorted out our systems," and then slip back into old habits the next time a new kind of fact appears — a new report, a new field, a new type of order. The four-question test is not a project with an end date; it is a habit to apply every time a new piece of information needs a home. The moment a team stops asking the question and starts guessing again, the same duplicate entry and version conflicts this course opened with will return.
This course taught four separate things, and this lesson turns them into one tool you can use every day. Ask what kind of fact you are looking at: money and quantities, product description, task and approval, or a genuine gap nothing yet covers. That answer tells you which system should own it. It does not matter whether the order is a big export shipment or a small domestic top-up, or whether an agent is standing in the middle — the same four questions give the same kind of answer every time.
Use this test whenever a new fact needs a home, not just once at the end of a course. Keeping that habit is what actually stops duplicate entry and conflicting versions from creeping back into your work.
A shop assistant records a customer's size-exchange request for the first time. No existing field in the ERP system, the PLM system or the workflow tool obviously fits this new kind of information, and a well-meaning team member proposes tracking it in a personal notebook "until we figure out where it belongs."
How should the team decide where this new fact belongs? Decide before opening the answer.
Apply the same four-question test used throughout this course, rather than defaulting to an uncontrolled personal notebook.
1. Ask whether this is a commercial or financial fact. A size exchange affects stock and possibly a refund or replacement sale, so its stock and financial consequences belong in the ERP system as a transaction, even if the request itself is new. 2. Ask whether it is a specification fact. It is not; it does not describe the product, only an event involving a customer and a specific unit. 3. Ask whether it is a task or approval status. If shop staff need to track whether the exchange has been approved, processed and closed, that status belongs in the workflow tool, or a simple controlled process the ERP system already supports. 4. If, after asking all three questions, a genuine gap remains — for example, no current system captures the specific reason for size exchanges — record that gap clearly and propose it as a new controlled field, rather than letting a personal notebook quietly become the answer.
A new kind of fact does not excuse skipping the test; it is exactly when the test is most useful.
Order A's confirmed value is a reminder of the scale that a single order's commercial facts can reach:
A single uncontrolled notebook tracking a new kind of fact may look harmless at first, especially if it starts on a small, unfamiliar case like a size exchange. But the pattern this course opened with — an uncontrolled copy quietly becoming the version people trust — applies to any new fact just as much as it applied to Order A's quantity, specification or commission. The cost of skipping the four-question test is not paid immediately; it is paid later, when someone discovers two disagreeing answers to the same simple question.
Use the T17-C02 Business-system role map workbook one last time, but treat it as a living reference rather than a finished exercise. Whenever a new kind of business information appears on any order — Make to Order or Make to Stock, export or domestic — run it through the four-question test and record the decision, so your team applies the same rule consistently over time.
[Download the Business-system role map workbook](../../templates/T17-C02-business-system-role-map.xlsx)
1. A confirmed quantity, a bill of materials, and a sample-approval task all appear on the same order. Which system should own each, applying this course's four-question test?
2. Cedar & Co. shares one production line between its Make to Stock replenishment work and a one-off Make to Order trial order. What is true about the two orders' own commercial facts?
3. A completely new kind of information appears on an order for the first time, and no existing field seems to fit it. What should the team do?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| System of record | نظام السجل المرجعي | Système de référence | Referans sistemi | The one place a piece of information is considered authoritative, when it might otherwise exist in several documents. |
| Pass-through | التمرير المباشر | Transmission directe | Doğrudan aktarım | Forwarding a fact unchanged from its source to its destination, without retyping or reinterpreting it. |
| Revision | نسخة معدّلة | Révision | Revizyon | One numbered version of a document, such as a tech pack, produced when a change is made and approved. |
| 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. |
| Hand-off | نقطة تسليم بين الشركات | Transfert entre entreprises | Şirketler arası devir | The point where goods, and ownership of them, pass from one separate company to another. |
| Duplicate entry | إدخال مكرر | Saisie en double | Yinelenen kayıt | Typing the same fact into a second tool that already has, or should have, its own controlled copy. |
You have completed Course 2: ERP, PLM and Business-System Roles. You can now decide which system should own any type of business information on any order, in any market or business model. Continue with the next course in Track 17, Systems and Data, when it becomes available, and keep applying the four-question decision test from this course as a daily habit on every order you handle. Back to the course map