Batch Traceability System for Zipper Production Lines

Symptom

The symptom of poor traceability is a question that cannot be answered. A customer reports a defect on a garment lot, and the factory cannot say which tape roll, which dye bath or which plating batch produced it. The recall scope becomes either dangerously narrow or commercially impossible, and the corrective action cannot be verified because the affected population is unknown.

Traceability failures are usually discovered during an audit or a complaint, which is the worst possible time. The system either exists before the event or it does not; it cannot be assembled retrospectively from memory and paper travellers.

• Carton label that cannot be linked to a production date or shift.
• Two batches merged in a warehouse without a merge record.
• Dye lot or plating bath number absent from the finished goods record.
• Traceability exercise taking more than four hours to complete.
• No link between incoming tape roll and finished zipper lot.

Root Causes

Traceability breaks at handover points: receiving, issue to line, changeover, rework, and packing. Each handover is an opportunity for a batch number to be dropped, and paper systems drop them silently.

• No unique batch identifier at receiving. Tape, filament and hardware arrive with supplier lot numbers that are not converted into an internal batch number.
• Bulk issue without recording. Material issued to the line by weight or by pallet, with no record of which rolls were consumed on which order.
• Changeover without a cut point. Two lots run on one line and the finished goods record shows only the later one.
• Rework without a new identifier. Reworked material re-enters production with its original identity lost.
• Manual transcription. Handwritten travellers are transcribed into a spreadsheet at the end of the shift, introducing errors and delays.
• Warehouse merging. Partial cartons consolidated for shipping without recording which source batches were combined.

Troubleshooting Sequence

Test the system with a live exercise before an auditor does. Pick a shipped carton and try to walk backwards, then pick a raw material batch and walk forwards.

• Select a carton at random from finished goods and record the time taken to identify its production order, date and shift.
• Continue backwards to tape roll, filament lot, dye bath and plating bath, noting every missing link.
• Select a tape roll and walk forward to every carton that contains material from it.
• Identify the time taken for both directions and compare against the customer requirement, often four hours.
• Review records at each handover point for completeness and legibility.
• Check that rework and second-quality material carry a distinct identifier.
• Confirm that the warehouse merge record links every consolidated carton to its sources.

Corrective Actions

Assign an internal batch number at receiving and print it on every roll label. Record issue and return at the line by scanning, not by writing, and create a hard cut point at every changeover: the finished goods record must state the batch that was running at the start and end of the order.

Give rework its own identifier and its own route, and require a merge record whenever cartons are consolidated. If a full ERP link is not feasible, a barcode plus a daily reconciliation is sufficient, provided the reconciliation is done daily rather than at month end, because a month-end reconciliation cannot recover a lost link.

Prevention

Design the identifier once and use it everywhere: one number that appears on the roll label, the line traveller, the finished goods record and the carton label. Systems fail when each department invents its own reference, and the reconciliation between references is where traceability dies.

Donglong Zipper runs a traceability exercise every quarter, selecting a shipped carton and requiring a complete forward and backward walk within two hours. YCC audits should ask for the last exercise record rather than the procedure document, because the record shows whether the system works and the document only shows that someone wrote it.

Finally, keep the data long enough. A traceability system that is complete but deleted after 90 days fails the first claim that arrives in month five, and apparel claims routinely arrive after the season, not during it.

Run the exercise as a drill, with a clock and a named owner. Announce a mock recall once a quarter, choose a carton at random, and require the team to produce the full chain within the target time using only the records available that day. Record where the chain broke and fix that handover before the next drill. The exercise costs two hours and reveals more than any audit checklist, because it tests the system under the condition that matters: someone needs an answer quickly and the person who created the record is not available to explain it.

Extend the same discipline to suppliers. A zipper factory that can trace its own tape but cannot obtain a lot history from its yarn supplier has a chain with a known weak link. Write the traceability requirement into the purchase agreement, require a batch number on every delivery note, and test one supplier per quarter with the same drill.

Protect the data as carefully as the product. Traceability records that exist only on one server, or only in a spreadsheet on one laptop, fail at exactly the moment they are needed. Back up the batch records on the same schedule as the financial data, restrict editing rights so that a record cannot be altered after release, and test a restore once a year. A perfect trace that cannot be retrieved is not a traceability system.