How to Trace Garment Origin with QR Codes: A Factory-Side Guide

When a buyer asks "can you prove where this garment came from?", they are rarely asking about a single shirt. They are asking whether your factory can connect a carton on a truck back to a fabric lot, a cutting date, and the people and machines that made it, with records that were captured at the time rather than reconstructed for the audit.

QR codes on bundles are the cheapest way I know to build that connection. We run this in my own CMT factory in Nepal, so what follows is the mechanics as they actually work, including the part most vendors skip: where the trace honestly stops.

What a Bundle QR Encodes

The unit of tracing in a sewing factory is not the garment; it is the bundle, the stack of cut pieces that travels the floor together. Each bundle gets a QR label at cutting, printed on a TSC thermal printer in the cutting room, and the code carries six things: lot, article, colour, size, component, and quantity.

That is deliberately minimal. The QR is an identity, not a database. Everything else about the bundle lives in the system and is looked up when the code is scanned, which means a label printed in week one stays valid no matter what happens to the bundle afterwards. The mechanics of running production on bundles are covered in our bundle system guide.

What Each Scan Appends

A QR label by itself proves nothing. The trace is built by scans. Every time a bundle is scanned at a station, the record appends who scanned it (the operator), on which machine, for which operation, and when. Operators scan with their own Android phones; there is no scanner hardware at the sewing stations.

Accumulated over a lot, those scans become a searchable history. Our bundle forensic search takes any bundle and shows its full journey: every operation performed, the operators and machines involved, the timestamps, the earnings paid against it, and where it currently sits. That search is the difference between traceability as a brochure word and traceability as something you can demonstrate to an auditor in under a minute.

The Traceability Chain, End to End

Two structural details make the chain auditable rather than merely recorded. First, assembly is gated: marriage tracking will not treat a garment as assembled until all its components have converged, so a front from one lot cannot quietly marry a back from another without the system objecting. Second, the lot pipeline ledger balances CUT against RECEIVED against DISPATCHED per lot and article, so a gap between what was cut and what was dispatched is visible as a number, not a suspicion.

The Honest Boundary: Identity Ends at Folding

Here is the part to be straight about, because vendors routinely are not. In a bundle-based system, identity is piece-group level, and it holds from cutting through finishing: this stack of twenty size-M red fronts, this lot, these scans. At folding and packing, the bundle structure dissolves. The pieces become finished goods, and from there the trace runs at lot-and-article level: the SAC receipt records what was received and its A/B grade, and the challan records what left, but no record connects one specific packed shirt to one specific sewing machine.

In practice this boundary matches what buyers ask for. An origin declaration or audit wants to know that the goods in challan number so-and-so came from lot so-and-so, cut on these dates, sewn in this factory, and the ledger plus the scan history answers that fully. If a buyer genuinely needs per-piece identity into the carton, that requires serialised piece-level labels, which is a different and considerably more expensive system.

Why Buyers Are Asking

Two pressures are driving the questions. Audits first: a scan trail captured at production time is much stronger evidence than a register written up afterwards, and buyers know it. Regulation second: the EU's Digital Product Passport will require product-level data that brands can only publish if their suppliers capture it, and brands are asking about data capture well ahead of the deadlines. I have written a separate factory-side guide to the Digital Product Passport and what it will actually demand from a CMT factory.

QR vs RFID for Origin Tracing

The short version: RFID reads without line of sight and in bulk, but tags cost money per piece, readers cost more, and a CMT factory does not own the garments it sews, which makes per-piece tag spend hard to justify. QR labels cost a strip of thermal paper, are printed in-house, and are read by the phones your operators already carry. For bundle-level origin tracing, QR does the job. The full comparison, including where RFID genuinely wins, is in our RFID vs QR code guide.

Implementing QR Traceability in an Existing Factory

1. Start at cutting. Put the label printer in the cutting room and print a QR per bundle as batches are entered. Nothing downstream works until bundles are born labelled.
2. Add scan points in production order. First the sewing operations, then finishing receipt, then dispatch. Each new scan point extends the chain; you do not need all of them on day one.
3. Use phones before buying hardware. Operators' own Android phones scan QR perfectly well. Prove the process before spending on dedicated stations.
4. Reconcile early. Once cutting and finishing both scan, the CUT versus RECEIVED balance starts exposing losses and missed scans. Chase those gaps in the first weeks; that is where the discipline is built.
5. Run one live lot end to end before declaring the system operational, and do a forensic pull on a few of its bundles to check the story the data tells is the story the floor lived. The broader scanning setup is described in our QR production tracking guide.

Frequently Asked Questions

How do you trace garment origin using QR codes?

Print a QR label for every bundle at cutting that identifies lot, article, colour, size, component, and quantity, then scan that QR at every station the bundle passes. Each scan appends the operator, machine, operation, and timestamp. The result is a chain from the fabric lot through the cutting batch, every sewing operation, finishing, and graded receipt to the dispatch challan, so any bundle can be traced back to its origin and any dispatch traced back to the bundles behind it.

Can a QR system trace every individual garment to the customer?

Honestly, no, not in a bundle-based system. Identity is piece-group level: pieces travel in bundles of known lot, article, colour, size, and quantity, and that identity holds from cutting through finishing. At folding and packing the bundle structure dissolves, and from there tracing is at lot-and-article level, meaning you know which lot and article a carton contains, not which sewing machine touched one specific shirt inside it. For most buyer audits and origin declarations, lot-level tracing at dispatch is what is actually asked for.

Do you need special hardware to scan bundle QR codes?

No. In our factory operators scan with their own Android phones, and the QR labels are printed on a TSC thermal label printer at the cutting room. The label printer is the only dedicated hardware the basic system needs. Dedicated scanner stations can be added later where phones are impractical, but they are an optimisation, not a requirement.

Why are buyers asking factories about garment traceability now?

Two pressures. First, audits: buyers increasingly want evidence that the goods in a shipment were made in the declared factory from the declared materials, and a scan trail is far stronger evidence than a paper register. Second, EU regulation: the Digital Product Passport under the ESPR will require product-level data that brands can only supply if their factories capture it, so brands are starting to ask suppliers about data capture years before the rules bite.

The test I would set any traceability system, including ours: pick a challan from last month, and ask for the lots behind it, the cutting dates, and the scan history of three bundles from those lots. If the answer takes a minute, you have traceability. If it takes a meeting, you have paperwork.

Santosh Rijal is the founder of Scan ERP, a garment manufacturing ERP system designed for factory floor operations. He works directly with sewing lines, cutting rooms, and production supervisors across Nepal's garment manufacturing sector.