An export order record holds commercial facts, technical specifications, planning numbers and status updates that several people touch every week. Without a clear rule for who may view a field and who may change it, anyone with access to the file can edit a price, a quantity or a specification, whether or not that change has been approved. A wrong edit made in good faith can travel just as far as one made by mistake.
This lesson gives you a working method for setting data responsibility, access rights and change control on a shared order record, so the people who need to see information can see it, the people who may change it are named, and every change follows an approved path before it takes effect. Without this, the file itself becomes the least controlled part of the order, even when every department around it is well run.
You need: a basic understanding of an order record, a purchase order and the main factory departments. Track 17, Course 1 on data ownership is useful preparation.
By the end of this lesson you can:
Not covered here: software configuration, database administration, or a specific ERP or PLM product. Lesson 5.2 covers the audit trail that proves who changed what and when; this lesson 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. |
| Access right | Permission that allows a specific role to view, enter or change a specific piece of business information. |
| Permission level | The specific set of actions, such as view, enter, or approve, a role is allowed to perform on a record. |
| Change control | The agreed process for approving, recording and communicating a change to controlled business information before it takes effect. |
| Version history | The ordered record of every saved version of a file or record, showing what changed and when. |
A shared order record is not one block of information; it is several groups of fields, each created or approved by a different part of the business. Commercial fields such as price and quantity, technical fields such as specification and construction, and status fields such as production or shipment progress each need their own accountable owner. Once an owner is named, that owner decides which roles may only view the field and which roles may change it, and every change to a controlled field passes through an approval step before it takes effect.
Without this structure, access tends to default to "everyone can edit everything," because that is the easiest setting to leave in place. That default feels convenient until the day someone changes a field they were never meant to control.
| What can differ | The shapes you will meet | Why it matters to you |
|---|---|---|
| Export order under Make to Order | An export buyer's confirmed price and quantity are set once per order and rarely change after confirmation; access to change them is usually kept very narrow. | A narrow change list makes an unapproved edit easier to notice and easier to trace back to one person. |
| Domestic replenishment under Make to Stock | A domestic brand's own standing forecast is updated on a routine cycle by a small planning team, not by every person who reads it. | Frequent, routine updates need a clear owner just as much as a rare one does, or the file drifts quietly over many small edits. |
| Hybrid order handled through an agent | An agent working on a hybrid mix of order types for more than one buyer often needs to view several buyers' records but should not hold change rights on any buyer's confirmed commercial fields. | Wide visibility across buyers is common in this role; wide change rights across buyers is a real risk if the agent's own access is not kept narrower than its visibility. |
| Production and quality status fields | Production reports what has been made; quality records inspection results. Each department should hold change rights only on the status field its own work creates. | A field changed by someone outside the department that created the fact can no longer be trusted as that department's own record. |
| Different product families | Socks add gauge and reinforcement fields; knit-to-garment adds yarn count and shaping; terry adds pile-height and border fields; bedding adds set-component fields. | The fields change by product family, but every field still needs one named owner and a defined access right. |
Northline Apparel has confirmed Order A with Delta Garments: 15,000 T-shirts, single jersey 180 GSM, Ne 30/1, agreed FOB USD 3.20 per piece, total order value USD 48,000. Mona, the factory merchandiser, is setting up the shared order record before the sewing line begins work under it.
Mona does not give every person who touches the order full edit access to every field. She groups the record's fields by owner: the confirmed price and quantity, owned by merchandising against the approved purchase order; the approved specification, owned by the technical team; the production-output field, owned by the sewing line supervisor; the inspection-result field, owned by quality. For each group, she names which roles may only view it and which single role may change it, and she sets the shared file so that a change to price or quantity requires her own approval before it is saved as current.
Karim, the production manager, can view the confirmed quantity and the approved specification at any time, because his team needs both to plan the line. He cannot change either field, because neither fact is created by production.
The worked numberSuppose a data-entry error changes Order A's recorded FOB from the agreed USD 3.20 to USD 3.10 per piece in the shared file, and the wrong figure is used in an internal costing check before anyone catches it.
USD 1,500 is a real distortion against Order A's own fixed profit of USD 0.26 per piece, or USD 3,900 total profit on the order (15,000 × 0.26). A change-control step that required approval before the price field could be saved would have caught the wrong entry before it reached a costing check, at no cost beyond the few minutes the approval step takes.
That choice feels efficient in the first busy week of an order, because nobody has to ask anyone else for a right they might need later. It becomes expensive the first time an unapproved change reaches a costing sheet, a production plan or a shipment document before anyone checks it, because there is no way to see who made the change or to have stopped it before it was saved.
The better rule is simple: give the narrowest access right that lets a role do its own job, and add a change-control step to every field whose wrong value would cost money or time to correct.
Think of a shared order record as a filing cabinet with several drawers. One drawer holds the price and quantity the buyer confirmed. Another holds the approved product specification. Another holds what production and quality have actually done. Not everyone who can open the cabinet should be able to write in every drawer, and writing in the price drawer should need someone's sign-off before the new figure is filed.
Set an owner for each drawer, decide who may only look and who may write, and require approval before a write to an important drawer is saved. When you do that, a mistaken or unapproved change is caught before it can travel through the rest of the order.
A planning assistant, added to Delta Garments' team this week, takes a phone call from someone at Northline Apparel who mentions a possible quantity change for Order A. Before Mona sees the call notes, the assistant opens the shared order file and edits the confirmed quantity field directly, intending to save time.
Should the assistant's edit be accepted as the new confirmed quantity? Decide before opening the answer.
No. The edit is not accepted; the field is restored to 15,000 pieces until a written, approved change is received.
1. The commercial field group's approval step requires a written confirmation or amendment from Northline Apparel, not a verbal mention during a phone call, before the confirmed quantity can change. 2. The assistant's permission level is view-only on this field group. A gap in the file's own lock setting let the save happen, but the assistant was never the accountable role for this field. 3. Fabric already requested against 15,000 pieces would be wrong if the unconfirmed number had been accepted, so restoring the approved value avoids a second, larger correction later.
The cost of accepting the unapproved edit is not only the risk of a wrong fabric request; it is that the shared record would show a number nobody can actually prove, which is worse than showing the last approved number while the real change is confirmed in writing.
Order A's fixed total order value is directly derived from its quantity and agreed price:
An unapproved change to a controlled field rarely destroys the whole order value at once. Its real cost is smaller and easier to miss: a wrong fabric quantity requested, a costing sheet built on a wrong price, or a production plan built on an unconfirmed quantity. Each of these can cost hours of rework or a real cash difference, such as the USD 1,500 shown earlier against Order A's own fixed figures, well before anyone notices the original access gap that let it happen.
The cheapest point to prevent that cost is the access setting itself: a narrow permission level and a required approval step, set once, before the order's shared record is opened to the wider team.
Use the T17-C05 Data governance decision tool workbook. In the Access and responsibility sheet, list each field group in the shared order record, its accountable owner, the roles that may view it, the roles that may change it, and whether a change to it needs approval. Start with Order A's own field groups, then repeat the exercise for a shared record you use at work.
[Download the Data governance decision tool workbook](../../templates/T17-C05-data-governance-decision-tool.xlsx)
1. Why does Mona give Karim view-only access to Order A's confirmed quantity and approved specification instead of full edit access?
2. Order B (3,000 jeans, agreed target FOB USD 9.80 per piece) is entered in a shared file with a data-entry error of USD 9.70. Before anyone corrects it, the wrong figure is used once in an internal costing check. What is the value affected on the whole order?
| 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. |
| Access right | حق الوصول | Droit d'accès | Erişim hakkı | Permission that allows a specific role to view, enter or change a specific piece of business information. |
| Permission level | مستوى الصلاحية | Niveau d'autorisation | Yetki seviyesi | The specific set of actions, such as view, enter or approve, a role is allowed to perform on a record. |
| Change control | ضبط التغيير | Contrôle des changements | Değişiklik kontrolü | The agreed process for approving, recording and communicating a change to controlled business information before it takes effect. |
| Version history | سجل الإصدارات | Historique des versions | Sürüm geçmişi | The ordered record of every saved version of a file or record, showing what changed and when. |
Next you will learn how a permission level and an audit trail work together so a buyer and a factory can both trust who changed a shared record, and when. Back to the course map