Where Lot Traceability Breaks: Three Handoffs Most Plants Miss
Most plants that struggle with a trace don’t have a data problem. The supplier lot number was written down, the production run was logged, and the pallet was labelled. The information exists somewhere in the facility. What’s missing is the connection between those records.
Those connections break at the handoffs: receiving to storage, storage to production, and production to finished goods. Each is a point where one record has to be tied to the next, and where a manual step can quietly drop the link. Here is where that happens, and what it costs when a supplier calls.
Lot traceability gaps at receiving: where the first link breaks
The first link is made at the dock, and it is the easiest to get wrong. A supplier lot number is keyed in with a typo. Four pallets are logged under one receiving entry. Or product goes into the cooler before anyone enters it, and the record is created at the end of the shift from memory. In each case the plant knows the ingredient arrived, but can’t reliably tie each pallet to its supplier lot.
The operational risk: when a supplier flags a lot, you can’t say with confidence which pallets are still in inventory and which have already gone to production.
Capturing supplier and lot data at the moment of receipt, with a barcode label on every pallet, is the job of receiving management. Scanning also removes the keying errors behind most typos, as covered in how barcode scanning eliminates manual entry errors.
Handoff 2: Storage to production
Production is where simple records turn into many-to-many relationships.
Picture three lots arriving in one week, two used in the same run and the third added later. Unless consumption is recorded against each lot as it happens, that sequence has to be reconstructed from memory after the fact.
The operational risk: when an ingredient problem surfaces, you can’t say which finished batches contain the affected material. QA ends up holding more product than it needs to.
Recording consumption as it happens, rather than at the end of the shift, is the discipline behind real-time batch tracking and digital batch creation. Rework adds another layer: returned product needs its own lot identity, or genealogy gets blended, as explained in Rework in Food Manufacturing.
Lot traceability gaps in finished goods: when the label and the record diverge
A finished lot has to inherit its history, and that only happens if production, labelling and inventory share the same transaction. When they don’t, you see the same symptoms:
- Finished lot numbers assigned by hand
- Labels printed from a system separate from the production record
- Quantities entered after the product is packaged
- Inventory that doesn’t match what was actually produced
The operational risk: after a raw material problem, QA has to compare production logs, inventory records and shipping documents by hand to work out which finished goods are affected, and may still end up uncertain.
Generating the label as part of the production transaction keeps the lot on the carton and the lot in the record the same thing. That is the idea behind piece, case and pallet labelling tied to production.
Why your ERP can’t see these gaps
An ERP is only as accurate as the information it receives, and plant-floor activity entered hours later is a reconstruction, not a record. The ERP may show 500 pounds of an ingredient consumed against a production order. Does it show which supplier lots made up those 500 pounds? When operators switched from one lot to another? Which finished goods lots consumed them?
The answers depend on how production transactions are captured and how the systems connect. You don’t need to replace the ERP to fix this. You need the plant floor to capture lot relationships as events happen and pass them to the ERP, which is the approach described in Traceability Without the Complexity and connecting production floor software with your ERP.
Find your lot traceability gaps before a recall does
Pick one handoff and trace one lot through it, forward and backward. The five-question mock recall self-test walks through the exercise. If you want the whole chain from dock to customer, see Food Manufacturing Traceability: Receiving to Shipping.
Whether you’re working toward FSMA 204 or the Safe Food for Canadians Regulations, the underlying test is the same: can you connect each lot one step back and one step forward without digging through paper? Even where enforcement has been delayed, there are good reasons to start now.
The best time to find a gap is before a recall, an audit or a customer complaint.
