A recall is one of the highest-stakes events a food manufacturer can face. The decisions you make in the first few hours matter enormously: how quickly you can identify affected product, how completely you can account for it, and how confidently you can communicate with distributors, retailers, and regulators.
A mock recall doesn't simulate the pressure of a real event. What it does is test whether your systems (your lot codes, your distribution records, your traceability chain) actually work before you need them to.
For most small manufacturers, running a mock recall once a year is sufficient. The exercise itself takes about two hours. What it reveals can take considerably longer to fix if you wait until a real event to find out.
What a mock recall tests
A mock recall is a traceability exercise. You select a finished product lot, then work through two questions:
Forward trace: where did this product go? Which customers, distributors, or retailers received it, and in what quantities?
Backward trace: what went into this product? Which ingredient lots were used, received from which suppliers, on which dates?
A complete mock recall answers both questions fully and accounts for 100% of the selected lot: product sold, product on hand, and product disposed of or sampled. The gap between what you can account for and 100% is your traceability exposure.
Before you start: what you need in place
A mock recall is only as useful as the records behind it. Before running the exercise, confirm you have:
Lot codes assigned to every finished product batch
Receiving records linking ingredient lot codes to suppliers and receipt dates
Batch production records linking ingredient lots to finished product lots
Distribution records linking finished product lots to customers or shipments
A recall plan that identifies who does what and in what order
If any of these are missing or incomplete, the mock recall will surface that gap quickly. That's a useful outcome, but it means the first exercise may be more diagnostic than procedural.
Running the exercise: step by step
Step 1: Select a lot (5 minutes)
Choose a finished product lot at random. Avoid selecting the most recent lot or the one with the cleanest records. The exercise is more valuable when it covers a typical production run, not your best one.
Note the lot code, production date, and batch size.
Step 2: Run the forward trace (30 minutes)
Starting from your distribution records, identify every unit of the selected lot that left your facility. For each destination, record:
Customer or recipient name
Quantity shipped
Ship date
Whether the product has been sold through, is still in inventory, or has been disposed of
Total the quantities. They should equal your original batch size minus any retained samples, internal use, or documented waste. If they don't, identify where the gap is.
Step 3: Run the backward trace (30 minutes)
Starting from your batch production record for the selected lot, identify every ingredient used. For each ingredient, record:
Ingredient name and supplier
Lot code of the ingredient used
Quantity used
Receiving date
Then work back one level further: for each ingredient lot, confirm you have a receiving record that links it to a purchase order or supplier delivery. This is the level of traceability a regulator or auditor expects.
Step 4: Calculate your recovery rate (15 minutes)
Tally what you can account for across both traces. A strong result accounts for 99% or more of the selected lot within the two-hour window. Document any gaps and their likely causes.
Recovery rate matters because in a real recall, regulators expect rapid and complete product recovery. Knowing your baseline before an event is the only way to address weaknesses proactively.
Step 5: Document and debrief (30 minutes)
Write up the exercise results: lot selected, time taken, forward trace results, backward trace results, recovery rate, and any gaps identified. This documentation is part of your food safety records and may be reviewed during an inspection.
If gaps were identified, note the corrective action and target date for resolution. A mock recall that surfaces a gap and results in no corrective action is a missed opportunity.
What good looks like
A well-functioning traceability system produces complete forward and backward traces in under two hours, with a recovery rate at or near 100%. The records are retrievable without significant searching, the lot code linkages are clear, and the documentation tells a coherent story from supplier to customer.
If your first mock recall takes four hours and accounts for 85% of the selected lot, that's useful information. It's also fixable. The same result during a real recall, with a regulator waiting, is a different situation.
Frequently asked questions
How often should a small manufacturer run a mock recall?
Once per year is a reasonable baseline for a small, stable operation. If you introduce new products, change your lot coding system, add distribution channels, or make significant changes to your recordkeeping, run an additional exercise after the change. The goal is to confirm your systems work under current conditions, not just the conditions that existed when you last ran the exercise.
Does a mock recall need to be witnessed or formally documented?
Under SFCR, your recall plan and its testing are part of your food safety program records. The mock recall results should be documented and retained. There's no requirement for a third-party witness, but the written record of the exercise (including any gaps and corrective actions) should be available for inspector review. Under FDA's Preventive Controls rule, similar documentation expectations apply as part of your written Food Safety Plan.
What's the difference between a mock recall and a real recall?
A mock recall is an internal exercise with no external notification, no product removal from the market, and no regulatory reporting. A real recall involves notifying affected customers, removing product from distribution, and in most cases reporting to CFIA or FDA depending on jurisdiction and the nature of the hazard. The traceability skills the mock recall tests are the same ones a real recall demands, which is exactly why the exercise has value.