Batch Traceability Software: From Weigh-Step to Mock Recall in Minutes

A batch traceability record is not the batch record. The batch record is the manufacturing instruction plus its execution evidence. The batch traceability record is the genealogy graph that surrounds it — every raw lot consumed (with quantity at the gram), every piece of equipment used, every operator who signed each step, every in-process check and result, every deviation opened against the batch, every sample drawn, every finished lot produced, and every customer shipment those finished lots fed. The data points are simple. The discipline is in capturing them at the moment they happen, not reconstructing them at end of week from paper. A traceability system that captures the genealogy at the kiosk during execution always wins against one that reconciles afterward.

21 CFR 211.188 (drug cGMP) requires batch production and control records to include 'identification of each major piece of equipment, identification of each weight, measure, or quantity used' — verbatim, the genealogy. 21 CFR 211.184 requires component records linking lot to batch. 21 CFR 111.260 (supplement cGMP) requires the same for dietary supplements. 21 CFR 110 / 117 (food cGMP) requires batch records with lot identification. EU GMP Chapter 4 (Annex I-V) mirrors the drug expectation. FSMA 204 adds Critical Tracking Events at receiving, transformation and shipping for foods on the Food Traceability List. ISO 22005 defines the general principles of feed/food chain traceability. The common thread: every input lot, every transformation, every output lot, recorded electronically, retrievable on demand.

ERPs assume a clean batch graph — raw lots in, one finished lot out. The shop floor rarely cooperates. A batch falls short on a target weight and a partial top-off is added from a second blend. A finished lot fails an in-process check and is reworked into the next compatible batch at 20%. A bulk tote is broken down into retail packs across three days, each pack inheriting the bulk lot — but each pack is also a new lot with its own expiry. ERPs that record these as inventory adjustments lose the genealogy link. A real batch traceability system records each event as a parent-child lot transaction with proportions, dates, signatures and reasons — so the mock recall still works after three rework loops and a re-blend.

Sample draws and retains are the most-forgotten traceability event in batch manufacturing. A QC sample is pulled, sent to the lab, consumed in testing — and the parent batch loses 50g it can't account for. Retain samples sit in the retain room for shelf life plus one year, then get destroyed — and the destruction record is missing. Inspectors look for both. A batch traceability system records sample draws as outbound lot transactions (quantity, purpose, destination, operator, signature) and retain disposal as a closed-loop record. Without this, the genealogy doesn't close — and an inspector who asks 'where did the missing 50g go?' gets the wrong silence.

The lot-level mock recall is one question — 'which finished lots used raw lot X?'. The batch-level mock recall is harder: 'this finished batch failed end-of-shelf-life stability testing — which raw lots, which equipment, which operator, which deviation, and which customers received this batch?'. A modern batch traceability system answers both in seconds. The trick is the underlying data model: raw lots, equipment usage, operator signatures, deviations and customer shipments must all link to the batch record as first-class relationships, not as text fields in a comment box. Buyers should ask the vendor to demonstrate a batch-level mock recall on real data during evaluation — not a slide deck.