This page teaches how to connect three digital records that are usually built separately, a CAD pattern file, a 3D sample file, and a body-scan fit record, into one order's own single digital record, so that anyone checking the order sees the same current version of each. This is mainly an information-flow skill, done once per order rather than for every version of every record. An agent working from three separate, disconnected records can approve a 3D sample built against an outdated CAD pattern version without knowing it; an agent working from one connected digital record sees immediately when one record is newer than another.
An agent that assumes three separate records are automatically consistent can pass an approval on to a buyer that turns out to reference an old pattern version. An agent that insists on rebuilding every record from scratch for every check gives up the speed a connected digital record is meant to provide.
You need: the order's own CAD pattern file, 3D sample file and body-scan fit record, each with its own version and date.
By the end of this lesson you can:
Not covered here: deciding whether to collect scan data (Lesson 4.1), building the virtual fit block itself (Lesson 4.2), deciding which stages still need a human check (Lesson 4.3), and building the complete decision tool covering this whole course (Lesson 4.5).
| Term | Meaning |
|---|---|
| Digital record | The single, current file or entry that holds one order's own version of a specific piece of information. |
| Digital record version mismatch | When two or more of an order's own digital records reference different versions of the same underlying pattern or fit decision. |
| Record owner | The person or role responsible for updating a specific digital record whenever its underlying information changes. |
| Connected record | One order's own single digital record that holds the CAD, 3D sampling and body-scan fit information together, each dated and versioned. |
| Stale reference | A record that still points to an earlier version of another record after that other record has since been updated. |
A digital record built correctly on its own day can still become a stale reference once another connected record is updated afterwards. A CAD pattern file, a 3D sample file, and a body-scan fit record are usually built by different record owners, at different times, for different purposes; nothing about building each one correctly guarantees the three stay in step with each other. The only way to know whether a version mismatch exists is to check each record's own version number and date against the others before approving anything based on all three together.
| What can differ | The shapes you meet | Why it matters |
|---|---|---|
| Export vs. domestic order | An export order passing through an agent such as Meridian Sourcing usually has records held by the factory, the agent and the buyer in three separate places; a domestic order held entirely inside one brand's own systems has fewer parties to reconcile | More parties holding separate copies of the same record raises the chance of a version mismatch going unnoticed |
| Make to order vs. make to stock | A make-to-order order's records are usually finalised once against one confirmed order and rarely revisited; a make-to-stock order's records may be revised across several forecast cycles, each revision needing the same version check repeated | A make-to-stock order needs the connection check repeated more often across its own life than a make-to-order order does |
| An agent role vs. a direct buyer-factory relationship | An agent such as Meridian Sourcing often acts as the record owner reconciling records from both the factory and the buyer's own design team; a direct buyer-factory relationship without an agent has one fewer party's own copy to reconcile | An agent's own role includes catching a version mismatch neither the factory nor the buyer alone would notice |
| A single style vs. several styles sharing one fit block | A single style's records are simpler to keep in step; several styles sharing one base fit block multiply the number of record combinations that must each be checked separately | Assuming one style's records are in step tells nothing about whether a second style sharing the same fit block is also in step |
| Product families | The same three-record connection method applies whether the style is apparel, socks and hosiery, knit-to-garment, terry and towels, or home textiles and bedding, since every product family's tech pack combines a pattern record, a sample record and a fit record in the same way | An agent new to this method applies the same version-check regardless of product family |
Meridian Sourcing acts as agent between Delta Garments and two European buyers, earning a 5% commission on Order A, 15,000 pieces of the T-shirt made to order, and Order B, 3,000 pieces of the jeans made against Delta Garments' own forecast run, together forming one hybrid pair of business models under Meridian Sourcing's own oversight. Each order has its own CAD pattern file, updated by Delta Garments' pattern room; its own 3D sample file, updated by the buyer's own design team after a virtual review; and its own body-scan fit record, updated after Lesson 4.1's decision on each order.
Meridian Sourcing's own record shows Order A's CAD pattern file was updated eight days ago to reflect the sleeve-width correction from Lesson 4.2, but Order A's 3D sample file was built eleven days ago, three days before that correction, meaning it still shows the uncorrected sleeve width.
The worked numberThe 3D sample file is three days out of step with the CAD pattern file's own latest sleeve-width correction, a stale reference that would carry the uncorrected measurement into the buyer's own approval if it is not caught first. Reconciling the two records before approval costs Meridian Sourcing about USD 30 of its own time, against the USD 570 the correction was meant to save in the first place if the stale reference goes unnoticed.
A common mistake is trusting whichever record happens to be open on screen, rather than checking its own date and version against the order's other records first. A record can be entirely correct on its own and still be the oldest of the three, carrying a stale reference to a decision one of the other two records has since corrected. The fix is checking every record's own date and version before any approval, not assuming the first record opened is the most current one.
An order usually has three separate digital records built by different people at different times: a pattern file, a 3D sample file, and a body-scan fit record. Each one can be correct on the day it was built and still fall out of step with the others once one of them is updated afterwards. Meridian Sourcing found that Order A's 3D sample file was built three days before a sleeve-width correction was made to the pattern file, meaning the sample file still showed the old, uncorrected measurement. Checking and reconciling the two records cost about USD 30 of the agent's own time, protecting the USD 570 the original correction was meant to save.
While reconciling Order B's own records ahead of a buyer review, Meridian Sourcing finds that the body-scan fit record was updated four days ago to reflect a new denim batch's slightly different stretch recovery, but the CAD pattern file, which sets the waistband curve, still reflects the previous batch's own figures. The facts in front of the agent:
The note relayed to the agent:
Should Meridian Sourcing send the buyer the current records as they are, or hold the review? Decide before you open the decision.
Hold the review until the CAD pattern file is checked against the new denim batch's own stretch recovery; sending the current records as they are risks the exact stale-reference problem this lesson warns against.
Two facts decide this. First, the body-scan fit record's own update is more recent than the CAD pattern file's, which by this lesson's method means the CAD pattern file may now be the stale reference, specifically on the waistband curve, a measurement point directly affected by the denim's own stretch recovery. Second, a two-day gap before the buyer's review is enough time to check whether the waistband curve needs a digital adjustment against the new batch, following the same method as Lesson 4.2, rather than approving on an unreconciled record set.
Sending the buyer the current records without checking is the same mistake as approving on whichever record was opened first; the fix this lesson gives is checking every record's own date before approval, and a two-day window is enough time to do that check properly rather than skip it under time pressure.
Holding the review by one day to check the pattern file costs about USD 60 of Meridian Sourcing's own time, against an estimated USD 1,800 in returns if a waistband-fit problem reaches Order B's full 3,000 jeans pieces. This is the same reconciliation principle as the sleeve-width example earlier, applied to a different, denim order.
Use the T25-C04 Digital workflow decision tool. On the RecordConnect sheet, enter each record's own version number and date for the CAD pattern file, the 3D sample file and the body-scan fit record; the sheet flags the most recently updated record and any other record that has become a stale reference against it, ready for Meridian Sourcing or any agent to reconcile before an approval.
[Download the Digital workflow decision tool](../../templates/T25-C04-digital-workflow-decision-tool.xlsx)
1. Why can the 3D sample file be entirely correct on the day it was built and still be a stale reference eight days later?
2. In the workplace scenario, why is the CAD pattern file treated as the possible stale reference, not the body-scan fit record?
3. Two records were updated on the same date; a third has not been touched in six months. What should happen next?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Digital record | السجل الرقمي | Dossier numérique | Dijital kayıt | The single, current file or entry that holds one order's own version of a specific piece of information. |
| Digital record version mismatch | تعارض الإصدارات | Incohérence de version | Sürüm uyuşmazlığı | When two or more of an order's own digital records reference different versions of the same underlying pattern or fit decision. |
| Record owner | مالك السجل | Propriétaire du dossier | Kayıt sahibi | The person or role responsible for updating a specific digital record whenever its underlying information changes. |
| Connected record | السجل المترابط | Dossier connecté | Bağlantılı kayıt | One order's own single digital record that holds the CAD, 3D sampling and body-scan fit information together, each dated and versioned. |
| Stale reference | إشارة قديمة | Référence obsolète | Güncelliğini yitirmiş referans | A record that still points to an earlier version of another record after that other record has since been updated. |
You now know how to connect separate digital records into one order's own record. The final lesson of this course builds a complete decision tool covering every step from this course in one place. Back to the course map