Cover: AI-generated conceptual illustration for WEFTSIGNAL, not documentary photography.
What a lot identity has to survive
A lot number is only worth having if it still means something at the end of the journey. Between the dye house and the delivery, a lot is split across machines, merged onto pallets with other lots, substituted when a roll runs short, and reworked after an inspection failure. Each is a legitimate production decision and each is a chance to lose the link. Lot traceability is the record of what happened to that identity, not a property of the number.
What a retrieval test actually proves
A retrieval test is a question asked backwards: take one garment, one carton or one delivery and ask what went into it, from which lot, through which processes, at whose hands. It proves that a chain of records connects the item to its inputs — not that the chain is complete, and not that the product was any good. The GS1 Global Traceability Standard is explicit that traceability is a shared responsibility, and that each party should at minimum trace back to its direct suppliers and forward to its direct recipients.
Where the chain breaks: splits
Splitting is ordinary: one roll goes to two markers, one cutting lay feeds several sewing lines. The link survives only if outputs are recorded as children of the input with quantities that reconcile. A split recorded as a fresh lot number with no parent reference is invisible in a retrieval test — nothing in the system says the two identities were ever the same cloth.
Where the chain breaks: merges
Merging is harder, because it compresses several identities into one and asks a single carton to carry them all. The GS1 Logistic Label Guideline is direct about the limit: only one batch or lot number can be placed on a logistic label, and where a unit contains products with different batch numbers at its highest level of packaging, those numbers cannot be shown. The composition of a mixed unit therefore has to live in the electronic record, not on the carton.
Substitution and rework are changes too
Substitution — a trim from a second source, a lining from another lot — creates a new combination without creating a new lot. Rework runs the other way: a rejected unit re-enters the line. Both change the honest answer to what is in this garment and who touched it, while leaving the lot number untouched. Recorded only as a purchase decision or a rework ticket, they stay outside the trace, which remains internally consistent and factually wrong.
Choosing the level of identification
The Global Traceability Standard separates two dimensions that set the precision of any trace: the level at which objects are identified, and the granularity at which data is recorded. A GTIN identifies a class of trade item; adding a batch or lot number identifies a group; adding a serial number identifies one piece. The standard notes that a serialised object can exist in only one place at a time, giving it a single unambiguous path. Lot-level tracing is a deliberate compromise below that, and should be a stated choice rather than an accident.
What has to be recorded at each step
Each business process step generates critical tracking events, for which the standard says key data elements need to be recorded. Its worked illustration shows the shape: a transformation process records inputs and outputs at batch or lot level, a warehouse records the link between product identifiers and pallet identifiers, and receiving scans the pallet identifier against pre-registered information. The pattern worth copying is inputs and outputs, plus the link between old identity and new.
An illustrative example
Suppose, illustratively, that one fabric lot is split across two cutting lays, one lay feeds two sewing lines, and a trim is substituted part-way through the order. A customer later reports a shade variation and asks for everything made from the affected fabric. Retrieval walks the delivery back to the fabric lot and stops at the substitution, because the replacement trim was recorded against a purchase order and never against the garments that consumed it. The chain is not absent; it ends where a change was not treated as an event.
Questions to settle before the next retrieval test
- Identity: at what level is each object identified — class, lot or serial — and where is the number printed?
- Splits: is every output recorded against its input, with quantities that reconcile?
- Merges: when identities are combined, where is the resulting composition held if it cannot go on the label?
- Substitution: are replacement materials linked to the orders that consumed them?
- Rework: does a failed and re-entered unit carry its earlier history with it?
- Direction: does the record resolve both ways, from delivery back to lot and from lot forward to delivery?
- Retention: how long must the record outlive the season, and who can retrieve it afterwards?
- Test: when was a real retrieval last run, and what did it fail to reach?
Source and further reading
Sources consulted 16 October 2026: GS1 — Global Traceability Standard, Release 2.0 (ratified August 2017); GS1 — Logistic Label Guideline, Release 1.3 (ratified July 2019). Both are cited by official designation and source page only, and the questions here are WEFTSIGNAL editorial material rather than requirements issued by GS1. For the wider record set, see supply-chain traceability records; mapping work sits in supply chain mapping. Continue exploring fashion supply chain coverage and our editorial standards.
