An apparel order creates a large amount of information. The buyer confirms commercial facts. Technical teams control approved product specifications. Planning and procurement calculate requirements. Production reports what has actually been made. Quality records inspection and test results. Logistics records shipment milestones and documents. Merchandising connects these groups, but that does not make the merchandiser the factual owner of every field.
This lesson gives you a simple rule: every important data item needs a clearly named data owner, an approved source, and a clear path for updating everyone who depends on it. When those three things are missing, the same order can show different quantities, dates, specifications or statuses in different departments. When they are clear, people know which value to trust and who must correct it.
You need: a basic understanding of an order, a purchase order, a tech pack and the main factory departments. Track 1, Course 9 is useful preparation.
By the end of this lesson you can:
Not covered here: software configuration, database administration, legal ownership of information, or a specific ERP or PLM product. This course stays vendor-neutral and focuses on the business rule first.
| Term | Meaning |
|---|---|
| Data owner | The role accountable for confirming that a specific business data item is current and correct. |
| Approved source | The document, approval or controlled record that proves the value currently in force. |
| Source of truth | The agreed place people use as the authoritative current record for a data item. |
| Derived data | A value calculated from other approved inputs, such as total fabric requirement from quantity and consumption. |
| Data hand-off | The point where one person or department passes information to another person or department that needs it. |
| Downstream user | A person or team that depends on an earlier data item to do its own work correctly. |
Many people can use the same information, and several people may contribute to it, but accountability should not be vague. If a buyer changes a confirmed quantity, the factory needs to know which document proves the new quantity, who updates the accepted internal order record, which derived values must be recalculated, and which departments must be told before they continue working.
Data ownership here is an operational responsibility. It does not mean that a factory employee legally owns the buyer's information. It means someone is accountable for saying, "This is the current approved value, this is where it came from, and these are the people who must receive the change."
| What can differ | The shapes you will meet | Why it matters to you |
|---|---|---|
| Buyer-confirmed commercial data | Order quantity, required ship date and agreed price normally come from the confirmed purchase order or a formal amendment. | The buyer confirms the commercial commitment; factory merchandising controls the accepted internal order record and must escalate contradictions. |
| Technical product data | Construction, measurements, bill of materials and approved material specifications come from the current approved tech pack or controlled technical record. | Technical/product teams control the approved revision. Production should not build from an old copy kept in someone's inbox. |
| Derived planning and procurement data | Fabric requirement, material need and planned dates are calculated from approved commercial and technical inputs. | The team making the calculation owns the derived value and must recalculate it when an input changes. |
| Execution status and results | Production output, inspection result, test status and shipment status are facts created by the department doing the work. | Merchandising can coordinate the full order view, but it should not invent a production, quality or logistics result. |
| Different product families | Socks add yarn, gauge and reinforcement data; knit-to-garment adds yarn count, gauge and shaping; terry adds GSM, size and pile-related data; bedding adds set components, dimensions and fabric consumption. | The data fields change, but every field still needs an owner, an approved source and an update path. |
Northline Apparel confirms Order A with Delta Garments. The order is for 15,000 T-shirts, using single jersey fabric at 180 GSM and Ne 30/1, with the approved size ratio 1:2:2:1. The agreed price is USD 3.20 per piece on FOB terms. Mona is the factory merchandiser coordinating the order.
Mona does not copy every value into a spreadsheet and then call herself the owner of everything. Instead, she identifies the accountable source and owner for each kind of information. The buyer-confirmed quantity comes from the approved purchase order. The approved product specification comes from the controlled technical record. Planning and procurement own the derived material requirement they calculate from the confirmed quantity and approved consumption. Production, quality and logistics each own the factual status or result created by their own work.
That separation gives Mona a reliable order view without pretending that one person can personally verify every fact in the factory.
The worked numberOrder A uses the approved consumption of 0.205 kg per piece, including the fixed 7% marker waste. The confirmed quantity is 15,000 pieces.
The three values do not have exactly the same owner.
This matters because a calculated value can be mathematically correct and still be wrong for the live order if one of its inputs is old. Data quality therefore depends on both calculation accuracy and source control.
That feels convenient, but it hides responsibility. A merchandiser may coordinate the order and chase updates, yet cannot personally create a valid production output result, approve a technical revision, issue a quality inspection result or confirm a shipment event that has not happened. If every field is marked "owned by merchandising," departments stop being accountable for the facts they create, and the merchandiser becomes a manual messenger between systems and spreadsheets rather than the coordinator of an accountable process.
The better rule is simple: the department that creates or approves the fact owns that fact; merchandising owns the coordinated order record it is responsible for and the communication that connects the facts.
Think of an order as a chain of promises and facts. The buyer promises a quantity, price and required date. Technical people approve what the product must be. Planning works out what material is needed. Production says what has actually been made. Quality says whether it passed. Logistics says what has actually shipped. One person may see all of those answers, but that does not mean that person should invent or approve them all.
For every important number, date, specification or status, identify three things: the role accountable for the value, the approved source that proves it, and the people who need the change. When those three answers are clear, your order information is much easier to trust.
Mona has the approved Northline Apparel PO for Order A showing 15,000 pieces. A planner opens an older internal sheet that contains a different quantity. The material requirement in that planning file was calculated from the old internal value. No material has been ordered yet.
What should happen before procurement uses the planning sheet? Decide before opening the answer.
Use the approved PO as the controlling source for the buyer-confirmed quantity, then repair the downstream data before material is ordered.
1. Merchandising confirms the approved commercial source — the current PO or formal amendment — and corrects the factory's accepted internal order record to match it. 2. Planning or procurement recalculates the derived material requirement from the confirmed quantity and the approved consumption of 0.205 kg per piece. For Order A, that gives 3,075 kg. 3. The old internal copy is not treated as a competing source of truth. It is corrected, archived or clearly marked as superseded according to the company's control method. 4. Downstream users are notified before they act, especially anyone booking or buying fabric, planning capacity or using the old quantity in another calculation.
The key point is that Mona coordinates the correction, but planning still owns the recalculated requirement. One person does not take ownership of every field merely because they found the conflict.
Order A's agreed FOB value is directly derived from its fixed quantity and price:
A wrong live quantity can therefore affect more than one place at once: the commercial order value, material requirement, capacity plan, packing quantities and shipment preparation can all be built from the same bad input. The lesson is not that every data mistake loses the whole order value. The lesson is that an uncontrolled source can spread into several downstream decisions before anyone notices.
The cheapest point to stop that spread is at the ownership hand-off: confirm the approved source, correct the current record, recalculate derived data, and notify the people who depend on it.
Use the T17-C01 Data ownership and data quality workbook. For each important data item, record what it is, who creates or approves it, which document or controlled record proves it, who updates the current order view, and which downstream users must be notified after a change. Start with Order A, then repeat the exercise for one product family you work with.
[Download the Data ownership and data quality workbook](../../templates/T17-C01-data-ownership-data-quality.xlsx)
1. Why is Mona, the merchandiser, not automatically the owner of every Order A data item?
2. For Order A, which statement correctly separates the confirmed quantity from the derived fabric requirement?
3. What three controls should every important order data item have?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Data owner | مسؤول البيانات | Responsable de la donnée | Veri sorumlusu | The role accountable for confirming that a specific business data item is current and correct. |
| Approved source | المصدر المعتمد | Source approuvée | Onaylı kaynak | The document, approval or controlled record that proves the value currently in force. |
| Source of truth | المرجع المعتمد | Source de référence | Ana referans | The agreed authoritative current record for a data item. |
| Derived data | بيانات مشتقة | Donnée dérivée | Türetilmiş veri | A value calculated from other approved inputs. |
| Data hand-off | تسليم البيانات | Transmission de données | Veri devri | The point where one person or department passes information to another that needs it. |
| Downstream user | مستخدم لاحق للبيانات | Utilisateur en aval | Sonraki kullanıcı | A person or team that depends on an earlier data item to do its own work correctly. |
Next you will learn how to stop several copies of the same order data becoming competing versions, and how to keep one approved current record. Back to the course map