Lot Traceability

Traceability has two directions and both matter. Backward traceability answers: this shirt has a shade problem — which fabric roll was it cut from, which dye lot was that roll dyed in, which yarn lot went into it, and which supplier sold us that yarn? Forward traceability answers the more urgent question: that dye lot was defective — which other rolls came from it, which orders were they cut into, which cartons shipped, and to whom?

A factory with only backward traceability can explain a complaint. A factory with forward traceability can contain one. The difference is measured in how many cartons you have to recall.

The textile traceability chain

The chain in a vertically integrated textile business is longer than in most industries, because the material physically transforms at every stage and each transformation creates a new lot identity while destroying the old one's physical distinctness.

Note what happens at the dyeing stage. Several greige rolls, possibly woven from different yarn lots, go into a single dye batch and come out as one dye lot. That is a many-to-one transformation. At the cutting lay, one roll is cut into many bundles across several sizes, and a lay may consume several rolls — many-to-many. Any traceability system that models only one-to-one parent-child links will break at both points, which is why bolt-on lot tracking so often ends at the fabric store and never reaches the shipped carton.

Shade continuity: the everyday use case

Most traceability discussion is about recalls and audits, but the daily reason a mill tracks lots is duller and more expensive: shade. Two dye lots of the same colour will differ slightly, and the difference is invisible in isolation and obvious when the sleeve and the body of one shirt are cut from different lots.

This means lot traceability is not merely a record kept after the fact — it is an *allocation constraint applied before the fact*. The cutting room needs to know, at lay planning time, which rolls belong to which lot and which lots fall within an acceptable [shade band](/glossary/shade-matching), so that a lay is either built from a single lot or deliberately segregated so that lot boundaries fall between garments rather than within one. A system that records lot history but cannot enforce lot allocation is documenting the problem instead of preventing it.

Tracing a complaint backwards

Suppose a buyer rejects a carton for shade variation. With lot traceability, the sequence is mechanical: the carton's packing list gives the bundles, the bundles give the roll IDs consumed in their lay, the roll IDs give the dye lot and the finishing batch, the batch gives the recipe, the vat, the operator, the date and the shade readings taken at inspection.

That chain answers three questions at once. Was the batch itself out of tolerance, or was it in tolerance and mixed with another lot at the lay? Which other rolls from that batch are still in stock — and can be blocked before they are cut? And which other orders already shipped from that batch — the list you would otherwise assemble by memory and prayer.

Without the chain, all three questions become an investigation, and the investigation happens while the buyer waits.

Compliance and the export evidence file

Traceability has become a regulatory requirement as much as a quality one. Origin-based import rules and forced-labour enforcement — see [UFLPA](/glossary/uflpa) and the [yarn-forward rule](/glossary/yarn-forward) — turn on your ability to prove, with documents, where the material at each stage came from.

The evidence that gets asked for is specific: purchase orders and invoices for the raw fibre, the spinner's yarn lot records, the mill's production records linking those yarn lots to specific greige rolls, dye batch records, and finally the packing list linking finished goods back to those rolls. What customs is testing is whether that chain is complete and internally consistent, not whether it is well presented.

A factory that maintains lot traceability as a byproduct of its normal transactions can produce that file quickly, because it already exists. A factory that keeps lot records in a separate spreadsheet has to reconstruct the chain under time pressure with a shipment detained, and every gap it finds is a gap it now has to explain.

What makes traceability actually work

Three things, all unglamorous. Lot identity must be captured at the moment of physical transformation, not entered later from memory — which in practice means [barcode scanning](/glossary/barcode-rfid) at doff, at batch load, at roll close, at lay and at pack. The system must model many-to-many consumption, because dye batches and cutting lays both are. And lot must be a first-class dimension of inventory, so that stock, allocation and [MRP](/glossary/mrp) netting all happen at lot level rather than at SKU level.

Vastra ERP carries lot identity as a dimension of inventory rather than as a note on it: yarn lot, dye lot, roll, bundle and carton are linked through each transformation, so a shade complaint on a carton resolves back to a batch and forward to every other roll from it, and the [quality](/features/quality-control) and [inventory](/features/inventory-management) records that make up an audit file are generated by the transactions themselves.