At 6:40 on a Thursday morning, a food processor got the call every plant manager dreads. A customer found a foreign object in a finished case. The retailer wanted to know how many other cases came from the same batch, and they wanted the answer before the store opened.
This company answered in nine hours. Eighteen months earlier, the same scenario would have taken nine days and probably cost them the account. Here’s what changed in between.
The question you cannot answer slowly
Traceability is not a paperwork exercise. When a recall hits, three questions decide everything: which raw material lots went into this batch, what finished goods came from those lots, and where those goods are right now — plant, truck, warehouse, or shelf.
Their old answer lived in three places: a paper receiving log, a production binder, and a shipping spreadsheet. Reconstructing one batch took a person two full days. If your trace takes longer than a day, you’re choosing between a recall and a reputation.
What we captured, and what we deliberately skipped
The temptation is to track everything. That fails, because people stop recording when recording gets tedious — a pattern any honest ERP Consulting review will show you in the first week of interviews.
We narrowed it to four data points, captured at the moment the work happened.
- Supplier lot number, scanned at receiving — not typed later.
- Batch number created when production started, tied to the lots consumed.
- Case and pallet IDs printed at packaging, tied to the batch.
- Shipment record linking pallet IDs to customer and date.
That’s four links in the chain. The whole thing runs on a handheld scanner a line operator already knew how to use. Training took one shift, not one week.
The nine-hour Thursday, hour by hour
- Hour 1: Customer service pulled the case code. The system returned a batch number and a production date.
- Hours 2–3: The batch record listed two raw lot numbers and every pallet produced that shift — 1,840 cases.
- Hours 4–6: The shipping record showed where all 1,840 cases went: 1,100 to one retailer, 620 still in the warehouse, 120 in transit.
- Hour 7: The retailer got an exact case count and a list of store locations. No guessing, no over-recall.
- Hours 8–9: The warehouse team quarantined the 620 cases and held the in-transit truck with one phone call.
The retailer was impressed enough to expand the account three months later. The recall cost about $14,000 in product. A nine-day version of the same event would have hit six figures and made the local news.
Next week, pick one finished product in your warehouse and trace it backward to its raw materials using only your records. Time yourself. Whatever slows you down is your first project.