Lot Traceability: Answer a Recall in Minutes
Lot traceability is the question every packaging and automotive supplier eventually gets: which finished units used material lot X? A customer found a defect and names a roll, a batch, a drum. A regulator asks for your recall scope. The answer exists somewhere in your factory, but if it lives on paper travelers and spreadsheet rows, finding it takes days of people walking the floor and guessing.
Why Spreadsheets Cannot Answer It
The typical mid-market setup records material consumption on a receiving log, production on travelers or a whiteboard, and shipments in an Excel sheet. None of these are linked. When the recall question arrives, someone has to manually reconstruct which work orders ran during the days the suspect lot was in stock, which orders those work orders fed, and which customers got the output. Every step is a fresh guess, and under time pressure the safe move is to over-recall: pull everything possibly affected, because you cannot prove what was not.
Forward and Backward Genealogy
A proper traceability record works in both directions, and the two directions answer different questions:
- Backward genealogy (where did it come from): pick a finished lot and list every input that went into it. Which raw material lots, which intermediate batches, which machines and operators. This is what you need when a customer complains about a finished unit and you must trace the defect back to its source.
- Forward genealogy (where did it go): pick a material lot and list everything it was consumed by, through every production step, down to finished goods and the shipments that carried them. This is the recall question. One suspect roll in, every affected outbound lot out.
In a multi-step process (film blown, printed, slit, converted, packed, in packaging; resin molded, assembled, tested in automotive) the chain has several links, and one weak link breaks the whole trace. Spreadsheets break at the second step. A genealogy system follows the chain automatically because each link was recorded when it happened.
What a Good Traceability Record Contains
The minimum that survives an audit:
- The material lots consumed by each work order, recorded at the line when the material is actually loaded, not reconstructed later.
- The output lot each work order produced, so parent and child link without human stitching.
- Quantities, timestamps, machine, and operator for each event, so you can answer "when" and "who" as well as "what".
- Inspection and NCR records attached to the same lots, so a quarantined lot is visibly quarantined.
If any of these is missing, the gap becomes your recall scope. Everything you cannot link, you must assume is affected.
How Automatic Genealogy Shrinks Recall Scope
The business case is not "auditors are happier". It is smaller recalls. When consumption is recorded per work order at the terminal, the suspect lot maps to exactly the work orders that used it, those map to exactly the output lots, and those map to exact shipments. The recall list goes from "everything we shipped in March" to three pallets and two customers. Fewer units pulled, fewer replacement runs, a customer conversation backed by records instead of apologies.
The same record answers the quieter, more frequent questions too: which lot is on hold, which supplier batch keeps showing up in NCRs, why yield dropped on one line last week. Traceability is not only recall insurance; it is the dataset that makes everything else explainable.
What This Takes on the Floor
Nothing exotic. Operators confirm the material lot on the terminal when they start or change over a work order, the system records the consumption, and the genealogy builds itself as orders complete. No new paperwork, no end-of-day data entry. The hard part is cultural: the record must be written when the material is loaded, and that only happens if writing it is easier than skipping it.
Voltrus MES records material lots per work order at the work order terminal and walks genealogy in both directions. When a customer or regulator asks, the answer is a per-lot audit pack export: the lot, its parents, its children, the events in between. If you are still rebuilding this chain in spreadsheets, our overview of what a MES actually is is a good starting point, and MES vs Excel scheduling covers the same shift for daily planning.
Frequently Asked Questions
We already print lot numbers on packaging. Is that not traceability?
That is labeling, not traceability. It tells the customer which lot they hold, but it does not tell you which inputs went into that lot or which other lots share them. Traceability is the internal chain between labels, and that chain is what a recall request actually asks about.
Is lot-level traceability required in our industry?
In food, pharma, and increasingly automotive supply (IATF expectations), one-step-up, one-step-down traceability is effectively a condition of doing business, and full-chain tracing is where audits head. Even where it is not mandatory, the first serious customer complaint will make the economics obvious.
Can barcode scanning do this without a MES?
Scanning is how data gets in, not where the chain lives. If scanned material lots land in disconnected files, you still have no genealogy. The scans need to attach to a work order record that also carries output, times, and inspections. That record is the MES.
Genealogy That Writes Itself
Voltrus MES is live: material lots recorded at the terminal, genealogy both directions, audit pack export per lot. One line to start.
See Voltrus MES