Traceability Tests and Mock Recalls That Prove Your System Works
How to design traceability tests and mock recalls that prove your system works under pressure
Key takeaways
- Traceability must work one step back (suppliers) and one step forward (customers), including packaging, rework and outsourced processes.
- Test traceability at least annually; BRCGS Food Safety targets completion within 4 hours, including a quantity reconciliation (mass balance).
- A mock recall tests more than traceability: decision-making, communication, contact lists and the incident team.
- Choose difficult test cases: a raw material used in many products, a rework batch, a product shipped to many customers.
- Record timings, gaps and actions, and repeat the test after corrective actions.
1. Traceability and recall are different tests
| Test | Question | Typical scope |
|---|---|---|
| Traceability test | Can we identify all affected materials, batches and customers quickly and accurately? | Backward and forward trace, mass balance |
| Mock recall or withdrawal | Can we decide, communicate and act effectively in a real incident? | Incident team, decision process, customer and authority notification, product retrieval |
Both are required in GFSI-recognised schemes; ISO 22000 also requires the withdrawal and recall procedure to be tested.
2. Designing a challenging traceability test
Avoid easy tests on a single-ingredient product sold to one customer. Better choices include:
- A raw material used across many products and dates.
- A packaging material with a labelling or migration issue.
- A batch that included rework.
- A product made on a shared line with allergen implications.
- A product partly processed by a subcontractor.
Run the test without warning, at different times, and involve the people who would really do it, not only the quality manager.
3. What a complete trace includes
| Direction | Information to retrieve |
|---|---|
| Backward | Supplier, delivery date, supplier lot, receiving checks, certificates of analysis, storage location |
| Internal | Production batches using the material, quantities used, rework, line and shift, intermediate products |
| Forward | Finished product lots, quantities produced, dispatched and in stock, customers, delivery dates |
| Mass balance | Quantity received = quantity used + in stock + waste + samples, within an explained tolerance |
A large unexplained difference in the mass balance means product could be in places the system cannot see.
4. Timing and targets
Measure time from the start of the test to the moment complete information is available. BRCGS Food Safety expects the traceability test to be completed within 4 hours. Customers may set their own targets. Record the actual time, and if the target is not met, analyse where time was lost: manual records, unavailable staff, missing system links.
5. Running a mock recall
- Scenario: for example, a supplier notifies you that a spice batch contains an undeclared allergen.
- Incident team activation: who is called, how quickly, and who decides.
- Assessment: which products are affected, where they are, what the risk is.
- Decision: withdrawal (trade) or recall (consumers), with documented rationale.
- Communication: customers, regulators, certification body (within the scheme’s timeframe, often 3 working days), and where needed consumers.
- Execution: hold stock on site, contact customers, track returns.
- Debrief: what worked, what did not, and actions.
Use a simulated scenario but real contact lists, so outdated phone numbers are found before a real incident.
6. Records to keep
- Test scenario, date, start and end times.
- Documents and systems used.
- Results: products identified, quantities, customers, mass balance.
- Gaps found and corrective actions.
- Sign-off by the incident team leader and review at management review.
7. Common weaknesses
- Tests always on the same simple product.
- Packaging and rework not included.
- Mass balance not calculated, or differences not explained.
- Contact lists out of date.
- Mock recall limited to paperwork, without testing decisions and communication.
Conclusion
Traceability and recall procedures are only proven when they are tested under realistic conditions. Challenging scenarios, honest timings and a full debrief turn the annual test from a formality into the best preparation for the day a real incident happens.
Plan your next test around your most widely used ingredient and time it from the first phone call.