Visibility & reporting
A recall question takes days to answer
A supplier notifies you that lot 4471 of an ingredient is under investigation. The question lands on your desk: which of your batches used it, and which customers received them? If the honest answer is 'give us two days and three people,' your real recall scope is everything—because you can't narrow it.
Traceability isn't tested on normal days. It's tested on the worst day, under time pressure, with a customer or a regulator waiting. That is when you find out whether your records are a system or a pile.
What it looks like
- A mock recall or traceability exercise takes days—pulling receiving logs, batch sheets, and shipping records, then reconciling them by hand.
- Supplier lot numbers are recorded on receiving paperwork, if anywhere, and never make it into a system connected to production.
- Answering 'which customers got this batch?' means a manual dig through order history, one shipment at a time.
- Customer audits that include a traceability test get scheduled—and quietly dreaded—weeks in advance.
- When scope can't be narrowed, the safe answer is recalling or holding everything, and everyone knows what that costs.
Why it happens
Lot data crosses three territories that rarely share a system: receiving records the supplier lot, production consumes it into a batch, shipping sends the batch to customers. Each step keeps its own records—often paper at receiving, a batch sheet in production, the ERP at shipping—and the genealogy between them is never written down as data.
The structural problem is many-to-many: several supplier lots go into one batch, and one batch ships to many customers, while batches blend and split. Spreadsheets handle one-to-one lists; genealogy needs a structure built for it. Most companies only discover the gap during an exercise—or an event.
What it costs
The honest answer is that it depends on your volumes, your margins, and how long it has been going on. What is consistent across companies is where the cost shows up:
Recall scope
When you can't narrow affected product, you hold or recall everything in the window. Over-broad scope is the single biggest multiplier of recall cost.
Labor
Traceability exercises and audit responses consume days of skilled time in records archaeology—each time the question is asked.
Customer and audit risk
Major customers increasingly test traceability. Failing a timed exercise costs scorecard points; failing twice costs the account.
Regulatory exposure
Recordkeeping expectations for food traceability keep tightening. Records that exist but can't be produced quickly function as records that don't exist.
How a purpose-built system fixes it
A purpose-built traceability layer captures genealogy at each step, as a byproduct of work people already do. At receiving, the supplier lot is scanned or entered against the intake. In production, the batch record ties input lots to the output lot. At shipping, the batch lot ties to customers and purchase orders.
The result is that the recall question becomes one query: supplier lot in, list of batches and customers out—in minutes, with the records behind each link one click away. The same chain runs backward ('where did this customer complaint originate?') and forward ('who else got product from this batch?').
Illustrative Workflow
Mock recalls stop being events. When the exercise is a query plus a printout, audits become demonstrations instead of ordeals—and the first real event finds you practiced.
When a simpler fix is enough
At small scale—few ingredients, few products, batch records already disciplined—a well-kept batch-record system on paper plus a quarterly recall drill can satisfy auditors and genuinely protect you. If you can answer the exercise in a few hours from one cabinet, you may not need software yet.
The break point is SKU and ingredient growth, blending and rework loops, customer audit frequency, or any product where hours matter during an event. When the honest answer to a supplier notification is measured in days, a purpose-built traceability layer over your existing ERP and shipping data is the fix.
Related systems and industries
- Document & data workflowsLot capture at receiving, batch, and shipping—genealogy as a byproduct of the work.
- Operational dashboardsRecall queries, hold status, and lot history visible in minutes.
- System integrationsTie receiving, production, and shipping records into one traceable chain.
- Food manufacturingWhere traceability is audited, tested, and occasionally very urgent.
Common questions
- Recording lots is the ingredient, not the dish. Traceability means the links are captured as data: which supplier lots fed which batch, which batch shipped to which customers. Lots written on receiving paper and batch sheets exist, but the genealogy between them has to be reconstructed by hand—which is why the exercise takes days. The test is simple: time your next mock recall.
- Not necessarily. Scanning is the fastest capture method, but the real requirement is that lot capture happens as part of the existing step—receiving, batching, shipping—not as extra paperwork. Cheap tablets at existing stations cover most floors. The design goal is zero new tasks, just better capture inside current ones.
Your recall scope is 'everything' until you can prove otherwise.
A Workflow Review times a mock trace through your real records—and shows where the chain breaks.