A single export order passes through several kinds of business system before it ships. An ERP system usually controls commercial and financial transactions. A PLM system usually controls product specifications and their revisions. A workflow tool usually controls tasks, approvals and hand-offs between people. A spreadsheet usually fills a gap none of the others cover yet. Merchandisers, planners, technical staff and buyers all touch these tools, but few of them stop to ask which tool is actually meant to hold which fact.
Without that question, the same order quantity, specification version or approval status can exist in an ERP screen, a PLM record, a workflow ticket and three spreadsheets at once, each one slightly different. This lesson gives you a working test for deciding what each of the four tool types is meant to control, so your own factory, buying office or brand stops duplicating facts that already have a proper home.
You need: a basic understanding of an order, a purchase order, a tech pack and the main factory departments. Course 1 of this track (data ownership and data quality) is useful preparation.
By the end of this lesson you can:
Not covered here: installing, configuring or comparing named software products, database administration, or a full systems-selection process. This lesson stays vendor-neutral and focuses on the business rule, not a specific product.
| Term | Meaning |
|---|---|
| ERP system | A business system that usually controls commercial transactions such as purchase orders, inventory, invoices and financial postings. |
| PLM system | A system that usually controls product specifications, bills of materials and their approved revisions. |
| Workflow tool | A system that usually controls tasks, approvals and hand-offs between people, without being the approved source for the underlying fact. |
| Spreadsheet gap-filler | A spreadsheet used only for information that no controlled system currently holds. |
| System of record | The one system that is the approved, authoritative source for a given type of information. |
| Duplicate entry | Typing the same fact into a second tool that already has, or should have, its own controlled copy. |
An ERP system's core job is commercial and financial: the confirmed order, the inventory movement, the invoice, the payment posting. A PLM system's core job is technical: the current approved specification, its bill of materials, and the history of revisions. A workflow tool's core job is procedural: which task is open, who owns it, what stage an approval has reached. None of the three is meant to be the master record for what the other two already control.
A spreadsheet has no fixed job of its own. It is useful exactly where no controlled system yet exists for a fact, and it becomes a problem exactly where it starts holding a second, competing copy of a fact that an ERP or PLM system already owns.
| What can differ | The shapes you will meet | Why it matters |
|---|---|---|
| Export order, Make to Order | An ERP system holds the confirmed export PO and shipment invoice; a PLM system holds the buyer's approved tech pack; a workflow tool tracks sample approval stages. | Nothing here should be re-typed into a private spreadsheet as a second "true" copy. |
| Domestic order, Make to Stock | A smaller domestic brand may run its replenishment orders and stock counts entirely inside one ERP module, with no separate PLM system yet. | Where no PLM exists, the approved spec must still live in one controlled place, even if that place is a well-managed spreadsheet or document, not a scattered set of copies. |
| Small factory with no PLM system | Specifications and revisions are kept in a shared, version-controlled spreadsheet or document because no PLM system has been bought yet. | A spreadsheet can be a legitimate temporary system of record if it is controlled the way Course 1 describes; the risk is several uncontrolled copies, not the spreadsheet itself. |
| Agent or buying office coordinating several factories | A workflow tool tracks which factory has approved which stage for which order, while each factory's own ERP still owns its own commercial data. | The workflow tool coordinates status across companies; it should not try to replace any factory's own commercial or technical system. |
| Different product families | Socks and hosiery, knit-to-garment, terry towels and home-textiles orders use the same four tool types, with different fields inside the PLM specification and ERP transaction records. | The fields change by product family; which tool type controls which kind of fact does not change. |
Northline Apparel confirms Order A with Delta Garments: 15,000 T-shirts, single jersey fabric at 180 GSM and Ne 30/1, agreed price USD 3.20 per piece FOB. Mona, the merchandiser, works across an ERP system, a PLM system, a workflow tool and a small set of spreadsheets every day.
The confirmed quantity, the FOB price and the shipment invoice belong in Delta Garments' ERP system, because those are commercial and financial facts. The approved construction, the bill of materials and the size ratio 1:2:2:1 belong in the PLM system, because those are technical specification facts that need a controlled revision history. The stages of sample approval — lab dip sent, buyer comment received, bulk approval given — belong in the workflow tool, because those are tasks and hand-offs, not the specification itself or the commercial value. Mona still keeps one small spreadsheet, but only for a genuine gap: a personal daily checklist of which task is due today, not a second copy of the specification or the PO.
The worked numberOrder A's confirmed quantity and FOB price are commercial facts; the derived fabric requirement is a planning calculation built from a PLM-controlled input.
The USD 48,000 order value and the 3,075 kg fabric requirement look similar in shape — both are single numbers calculated for the same order — but their approved inputs live in different systems. The quantity and price are ERP-controlled commercial facts. The 0.205 kg consumption figure is a PLM-controlled technical fact. Planning combines both to produce the derived fabric requirement, but planning does not own either input; it only owns the calculation.
A merchandiser under time pressure often builds a personal tracking sheet with the order quantity, price and specification copied in for convenience. That sheet is fast to open and easy to edit, so it starts being trusted more than the ERP or PLM screen it copied from. When the buyer later changes the quantity, the ERP system is updated, but the personal spreadsheet is not, and the two numbers quietly disagree. The cost is not the spreadsheet itself; the cost is treating a convenience copy as if it were a system of record.
Think of four tools with four separate jobs. One tool keeps track of money and quantities that were agreed. One tool keeps track of what the product must be, and how that changed over time. One tool keeps track of who still needs to do something and whether it is done. A spreadsheet is a helper you use only when none of the other three yet cover something you need to record.
The mistake most people make is copying a fact from one of the first three tools into a spreadsheet "to keep an eye on it," and then trusting the spreadsheet more than the tool that actually controls the fact. Once you know which of the four tools is meant to hold a fact, you stop needing a private copy of it.
Mona built a personal spreadsheet early in Order A to keep a daily view of tasks and figures in one place. The approved amendment changing a downstream planning figure was entered into Delta Garments' ERP system on the day it was confirmed. Mona's personal spreadsheet, however, still shows the earlier value, because she has been busy and has not opened that tab in several days. A colleague in planning asks her which number is correct before finalising a material booking.
Which figure should Mona tell her colleague to use, and what should she do with her personal spreadsheet? Decide before opening the answer.
The ERP system's current record is correct; Mona's personal spreadsheet must be corrected or retired, not treated as a second source.
1. Mona confirms the current approved figure directly from the ERP system, since that is the system of record for a confirmed commercial change. 2. She tells her colleague to use the ERP figure for the material booking, not the older figure sitting in her personal sheet. 3. She updates or deletes the stale line in her personal spreadsheet so it cannot mislead her or anyone else again, and reminds herself the sheet is a convenience view, not an approved source. 4. If she needs a daily task view, she rebuilds it to pull the current figure from the ERP system each time, rather than typing a number once and letting it go stale.
The material booking should never be based on a spreadsheet that copied a figure from the system of record and then fell out of date.
Order A's confirmed value is directly derived from its fixed quantity and price:
If planning had booked material against Mona's stale spreadsheet figure instead of the ERP system's current record, the fabric requirement calculated from it would not match the order actually confirmed with Northline Apparel. Re-ordering, re-booking or holding excess material wastes time and, depending on the size of the gap, real money against an order worth USD 48,000. The cost of checking the system of record before finalising a booking is a few minutes; the cost of not checking is measured in wasted material, wasted time, or a late shipment.
Use the T17-C02 Business-system role map workbook. For each important fact on an order, record what kind of information it is, which tool type is meant to control it, whether a controlled system currently exists for it in your company, and whether any spreadsheet copy of it should be retired. Start with Order A, then repeat the exercise for one order you handle yourself.
[Download the Business-system role map workbook](../../templates/T17-C02-business-system-role-map.xlsx)
1. For Order A, which tool type should normally control the confirmed quantity and agreed FOB price?
2. A small factory has no PLM system yet and keeps its approved specifications in a shared, version-controlled document. Is this acceptable?
3. Why should a workflow tool tracking sample-approval stages not also be treated as the source of the approved specification?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| ERP system | نظام تخطيط موارد المؤسسة | Système ERP | ERP sistemi | A business system that usually controls commercial transactions such as purchase orders, inventory, invoices and financial postings. |
| PLM system | نظام إدارة دورة حياة المنتج | Système PLM | PLM sistemi | A system that usually controls product specifications, bills of materials and their approved revisions. |
| Workflow tool | أداة سير العمل | Outil de workflow | İş akışı aracı | A system that usually controls tasks, approvals and hand-offs between people, without being the approved source for the underlying fact. |
| Spreadsheet gap-filler | جدول بيانات لسد فجوة | Feuille de calcul de complément | Boşluk dolduran e-tablo | A spreadsheet used only for information that no controlled system currently holds. |
| 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. |
| 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. |
Next you will learn where a tech pack, its bill of materials and its revisions should live once several people rely on the current version. Back to the course map