Meridian Sourcing acts as the agent in Egypt for two European buyers, earning a 5% commission on orders it places with factories such as Delta Garments. Every order Meridian handles crosses a company boundary at least twice: the buyer's specification and commercial approval must reach the factory, and the factory's production status, quality result and shipment information must reach the buyer. Neither side's ERP or PLM system is visible to the other, so Meridian's own hand-off is the connection between them.
If Meridian re-types figures by hand at each hand-off, or keeps its own private spreadsheet as a shadow copy of both sides' data, this course's earlier warnings about duplicate entry and version conflict apply directly to the agent's own desk. This lesson gives you a working rule for passing information across a company boundary without creating a new, uncontrolled copy of a fact that already has an owner on one side or the other.
You need: this course's earlier lessons on what an ERP system, a PLM system and a workflow tool are each meant to control, and where specifications and commercial facts should live.
By the end of this lesson you can:
Not covered here: electronic data interchange standards, API integration design, or a specific software product's import/export feature. This lesson stays vendor-neutral and focuses on the business rule.
| Term | Meaning |
|---|---|
| Hand-off | The point where information passes from one company's system or person to another's. |
| Single point of entry | Entering a fact into a system only once, at its source, rather than re-keying it at every hand-off. |
| Shadow copy | An unofficial copy of a fact kept outside the systems that actually own it, usually for convenience. |
| Company boundary | The point where information stops being controlled by one company's own systems and passes to another company's. |
| Pass-through | Forwarding a fact unchanged from its source to its destination, without retyping or reinterpreting it. |
| Two-way traceability | The ability to trace a fact back to its original source, and forward to everywhere it was sent, in either direction. |
A hand-off should move a fact from where it is controlled to where it is needed, unchanged. It should never become an opportunity to create a second, independent version of that fact. If the buyer's approved quantity is confirmed in Northline Apparel's own system, Meridian's job is to carry that exact figure to Delta Garments, not to recall it from memory or re-confirm it informally and then treat its own recollection as equally valid.
The same applies in the other direction: production status, quality results and shipment dates are the factory's own facts, and Meridian's job is to carry them to the buyer accurately, not to summarise them from a partial understanding and let that summary become the buyer's working version.
| What can differ | The shapes you will meet | Why it matters |
|---|---|---|
| Agent between one buyer and one factory | Meridian passes the buyer's confirmed specification and commercial approval to the factory, and the factory's production and shipment facts back to the buyer. | Each fact still has one owning side; the agent's role is transmission, not ownership. |
| Agent coordinating several factories for one buyer | The same buyer specification is passed to more than one factory; production status comes back from each factory separately. | Every factory must receive the identical pass-through, and the agent must not merge or average separate factories' own facts into one figure. |
| Trading company buying and reselling in its own name | A trading company's own purchase order to the factory and its own resale invoice to a retailer are genuinely two separate commercial transactions, not one fact passed through. | Unlike a pure pass-through, each of the trading company's own transactions needs its own controlled record in its own ERP system. |
| Hybrid order combining an export specification with a domestic production slot | A factory may produce part of an order against an export buyer's specification and part against a domestic brand's own standing order, on the same production line. | Even where two different scenario sides share a production resource, each order's own commercial and technical facts still belong to their own owning side. |
| Different product families | Terry towels, home-textiles, socks and hosiery orders passing through an agent or buying office carry different technical fields, but the pass-through discipline is identical. | The content of what is passed changes by product family; the rule that a hand-off should not create a new, independent copy does not. |
Northline Apparel confirms Order A with Delta Garments through Meridian Sourcing: 15,000 T-shirts, single jersey fabric at 180 GSM and Ne 30/1, agreed price USD 3.20 per piece FOB, with Meridian earning its 5% commission on the transaction. Northline's own commercial approval and Delta Garments' own production status never sit inside the same company's system; Meridian sits at the hand-off between them.
When Northline approves the tech pack, Meridian forwards the approved file to Delta Garments' technical team without retyping the measurements into its own separate specification sheet. When Delta Garments reports a production milestone or a quality result, Meridian forwards that fact to Northline without rounding it off from memory or waiting to batch several updates into one vague summary. Meridian's own systems track which hand-offs have happened and when, but they are not a second, competing copy of either side's specification or commercial figures.
The worked numberMeridian's commission is calculated from Order A's confirmed commercial value, which is itself a pass-through fact from Northline Apparel's own approval.
The USD 48,000 order value is a pass-through fact: Meridian did not create it and must not adjust it while forwarding it. The USD 2,400 commission is Meridian's own derived fact, calculated from the pass-through value using Meridian's own agreed rate. Confusing the two — for example, letting a rounded or re-estimated order value creep into the commission calculation — would make Meridian's own invoice disagree with the commercial fact both the buyer and the factory already agreed.
An agent handling several orders for several factories and buyers may build a personal summary sheet to keep track of where each order stands. That sheet is convenient, but if a buyer or factory starts reading figures from the agent's summary instead of confirming them against their own system, the summary has quietly become an uncontrolled second version — exactly the shadow copy this course has warned against throughout. The fix is not to stop summarising for personal tracking; it is to make sure nobody treats that summary as the source of truth in place of the system that actually owns the fact.
Think of an agent as a careful messenger standing between two companies that cannot see each other's systems. The messenger's job is to carry each fact across accurately, not to remember it approximately or improve it along the way. A confirmed quantity, price or specification belongs to whichever side approved it; the messenger's job is to deliver it unchanged.
Where the messenger has their own job to do — like calculating a commission — that calculation should be built freshly from the delivered fact, not from a private recollection of it. Keep personal notes for your own tracking if you need them, but never let those notes quietly become the answer other people rely on instead of the real source.
Sara at Northline Apparel asks Meridian for Order A's current production status ahead of a planning call. Meridian's own tracking sheet shows a note from a factory update received two weeks ago, but no confirmed update since then. A team member is tempted to describe that old note as "on track, no issues" so the call can proceed smoothly.
What should Meridian tell Sara before the planning call? Decide before opening the answer.
Confirm the current status with Delta Garments before reporting anything to Northline, rather than reusing an old note as if it were current.
1. Meridian contacts Delta Garments' own production team to get today's actual status, since a two-week-old note is not a reliable pass-through of the current fact. 2. Meridian reports the confirmed current status to Sara, clearly dated, rather than an assumption dressed up as an update. 3. If a confirmed current status cannot be obtained before the call, Meridian tells Sara honestly that the last confirmed update is two weeks old and a fresh check is in progress, rather than inventing reassurance. 4. Meridian records when each status update was received, so a future gap like this one is visible rather than hidden inside a vague summary.
Passing along an assumption as if it were a confirmed fact is exactly the kind of uncontrolled version this course has warned against — it just happens to originate from the agent's own convenience rather than from either company's system.
Order A's agreed value and Meridian's own commission are directly derived from the confirmed figures:
If Northline Apparel makes a planning decision based on a status Meridian invented or assumed, and the real situation at Delta Garments turns out to be different, the resulting confusion, delay or corrective action can affect far more than the USD 2,400 commission Meridian earns on the order. An agent's value depends entirely on being a reliable pass-through; a single invented status update, once discovered, can cost the agent future business worth many times one order's commission.
Use the T17-C02 Business-system role map workbook. For each fact that crosses a company boundary on an order, record which side owns it, the date it was last confirmed, and whether the current hand-off is a fresh pass-through or a stale note being reused. Start with Order A, then repeat the exercise for an order you coordinate between two companies yourself.
[Download the Business-system role map workbook](../../templates/T17-C02-business-system-role-map.xlsx)
1. When Northline Apparel's approved tech pack for Order A needs to reach Delta Garments through Meridian Sourcing, what should Meridian do with the measurements it contains?
2. Why should Meridian's 5% commission be calculated from the confirmed order value each time, rather than reusing a previously remembered commission figure?
3. Delta Garments is simultaneously producing part of an order against Northline Apparel's export specification and part against Cedar & Co.'s own domestic standing order on the same line. What is true about the two orders' commercial facts?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Hand-off | نقطة تسليم بين الشركات | Transfert entre entreprises | Şirketler arası devir | The point where goods, and ownership of them, pass from one separate company to another. |
| Single point of entry | نقطة إدخال واحدة | Point de saisie unique | Tek giriş noktası | Entering a fact into a system only once, at its source, rather than re-keying it at every hand-off. |
| Shadow copy | نسخة ظل | Copie parallèle non officielle | Gölge kopya | An unofficial copy of a fact kept outside the systems that actually own it, usually for convenience. |
| Company boundary | حدود الشركة | Limite entre entreprises | Şirket sınırı | The point where information stops being controlled by one company's own systems and passes to another company's. |
| Pass-through | التمرير المباشر | Transmission directe | Doğrudan aktarım | Forwarding a fact unchanged from its source to its destination, without retyping or reinterpreting it. |
| Two-way traceability | إمكانية التتبع في الاتجاهين | Traçabilité bidirectionnelle | İki yönlü izlenebilirlik | The ability to trace a fact back to its original source, and forward to everywhere it was sent, in either direction. |
Next you will build a single working tool that decides, for any piece of information, which system should own it. Back to the course map