Most factories already know where their fabric is. The problem is that they know it the way a good supervisor knows it: from memory, from a register at the store, from a phone call to the cutting section. When that supervisor is on leave, when a buyer asks which rolls went into a particular carton, or when two registers disagree, the answer takes hours or days. A QR-based tracking system does not make the factory smarter. It makes what the factory already knows visible, consistent and quick to retrieve.
This article looks at what actually changes when a floor moves from paper to scanning, what it takes to get there, and where projects usually go wrong.
What "traceability" means on a garment floor
In practice, traceability is a chain of links between physical things. For a typical woven or knit garment operation, the chain looks like this:
- Roll: fabric received against a purchase order, with supplier, lot, shade and width.
- Lay and cut: rolls consumed into a marker, producing bundles of cut panels.
- Bundle: a numbered group of pieces with size, colour and quantity, moving through sewing lines.
- Garment and carton: finished pieces checked, packed and assigned to a carton and a shipment.
On paper, every link exists, but it lives in a different book. The store has a roll register. Cutting has a lay report. Sewing has bundle tickets. Finishing has a packing list. Joining them back together means people reading and matching records by hand.
With QR codes, each roll, bundle and carton gets a label at the point it is created. Every time it crosses a defined point, someone scans it. The links are recorded as they happen, not reconstructed afterwards.
What really changes
1. Questions get answered in minutes, not days
"Which rolls went into carton 214?" "How many bundles of size M are still in line 3?" "Has this lot been inspected?" These are routine questions, and on paper each one needs a person to go and look. When the scan history is in one place, the answer is a search. The time saved is not only the clerk's; it is the merchandiser's, the planner's and, eventually, the buyer's.
2. Gates replace good intentions
A gate is a point where an item cannot move forward without a scan. Fabric cannot be issued to cutting until the roll has been inspected. A carton cannot be loaded unless its contents match the packing list. Gates are where tracking stops being a report and starts being a control.
The useful question is not "where can we scan?" but "where does a mistake cost us most?". Good first gates are usually:
- Fabric receiving and inspection (wrong lot or shade causes the costliest rework).
- Issue from store to cutting (prevents uninspected or wrong rolls being cut).
- Bundle entry to and exit from a sewing line (gives real work-in-progress, not estimated).
- Carton close and shipment loading (protects against short or mixed shipments).
3. Work-in-progress becomes a number you can trust
Most WIP figures on a factory floor are calculated: input minus output, adjusted by someone who knows better. Scanned bundle movement gives WIP by line, by style and by size, as it stands now. Planners stop arguing about the figure and start acting on it.
4. Problems become traceable backwards
When a shade issue or a measurement problem appears in finishing, the scan history lets you go back from the garment to the bundle, the lay and the original roll. That is the difference between holding one lot and holding a whole order.
A scan is only valuable if it is taken at the moment the thing actually moves. Everything else in the design follows from that.
Adoption on the floor: the part that decides success
The technology for QR tracking is mature and inexpensive. Labels, printers, handheld scanners and phones are all readily available. Projects rarely fail because of hardware. They fail because the scanning step does not fit the way people work.
Design for the person holding the scanner
- One scan, one action. If an operator has to scan, then choose from a menu, then type a quantity, the step will be skipped when the line is busy. Default as much as possible from context.
- Clear feedback. A distinct sound and colour for success and for error. People on a noisy floor do not read small text.
- Local language. Screens and error messages in Bangla where the operators are more comfortable in Bangla.
- Work offline. Network coverage inside a factory is rarely perfect. Scans should queue on the device and sync when the connection returns.
- Labels that survive. Test label stock and placement against handling, folding and washing where relevant. A label that peels off at sewing breaks the chain.
Start small and prove it
Choose one flow and one section first, typically fabric receiving to cutting. Run it alongside the paper process for a short, defined period. Compare results each day. When supervisors find that the screen answers their questions faster than the register does, they will ask for the next section themselves.
Make the supervisor the owner
Floor adoption follows supervisors. Give them a simple view of their own section: what came in, what is pending, what is stuck. If the system helps them run their shift, scanning becomes part of the job rather than an extra duty.
Common mistakes to avoid
- Scanning everything on day one. More scan points mean more chances for skipped scans and bad data. Begin with the gates that matter.
- Printing labels away from the point of creation. If bundle labels are printed in an office and walked to cutting, they will be mixed up. Print where the item is born.
- No plan for exceptions. Damaged labels, split bundles, re-cut pieces and partial cartons happen every day. The system needs a clear, permitted way to handle each one, or people will invent their own.
- Treating it as an IT project. Production, quality, store and commercial teams all need to agree on what each scan means. That agreement is more important than the software.
- Keeping the paper as the "real" record. A parallel run is sensible; a permanent one is not. Set a date when the scanned record becomes the official one.
A short readiness checklist
- Can you draw your material flow from receiving to shipment on one page, with every hand-off marked?
- Have you agreed which three or four points will be gates, and what happens when a scan fails?
- Do you have a named owner in production, not only in IT?
- Have you tested label stock and scanners in the real environment, not in an office?
- Do you know which existing systems (ERP, accounts, buyer portals) the data needs to reach?
- Have you set a date to stop maintaining the parallel paper record?
If most of these have a clear answer, a pilot can usually start quickly. If not, the gaps are worth closing first; they are cheaper to solve on a whiteboard than on the floor.
Where RAED fits
We build tracking and production systems that start from the floor: we walk the flow, agree the gates with the people who will scan, and pilot one section before extending. Where a factory already has an ERP or other systems, we integrate rather than replace.
