A mock recall is a rehearsal. You pick a lot, pretend it has a problem, and find out how fast and how completely you can trace it, both back to its ingredients and forward to every customer who received it. It is the most honest test of your traceability, and many food safety certification schemes ask for one at least once a year.
Why it matters
In a real recall, time and completeness are everything. If you cannot say quickly which batches used a suspect ingredient and where they went, you may have to recall far more product than necessary, or worse, miss some. A mock recall exposes the gaps while the stakes are low.
Step 1: Choose the scenario
Pick something realistic. Two common choices are a raw-material lot, such as a batch of fruit pulp or sugar that a supplier has warned about, or a finished batch that has received complaints. Vary the choice each time, and do not warn the team which lot it will be.
Step 2: Trace backward
For a finished batch, list every ingredient and packaging lot used, with quantities. For a juice batch, that means the pulp or concentrate lots, sugar, acids, water treatment records for the day, bottles, caps and labels. Note where each piece of information came from and how long it took to find.
Step 3: Trace forward
For a raw-material lot, find every batch that used it, and for each batch, every dispatch: customer, invoice, date, quantity and vehicle. Include samples, free goods and stock transferred between warehouses, which are easy to forget.
Step 4: Reconcile the quantities
This is the step most plants skip. Add up what was produced from the lot, what is still in stock, what was dispatched and what was lost or sampled. The totals should match. If 1,000 litres were filled and you can only account for 940, you have found a gap.
Step 5: Time it and record the result
Record when the exercise started and finished, who took part, what was found and what was missing. Certification standards often expect traceability to be completed within a few hours; check the exact requirement in the standard you follow.
Step 6: Fix the gaps
Typical findings include lots not recorded at issue, packaging lots never written down, handwritten dispatch notes without batch numbers, and stock moved between locations without a record. Each one needs a change in practice, not just a note in the report.
Who should take part
A mock recall is not a quality-department exercise alone. Stores know where lots were issued, production knows what went into each batch, dispatch knows which vehicle carried what, and sales holds the customer contacts you would need to call. Involve all of them, and include someone who was not on duty when the chosen batch was made, because in a real recall the person who remembers may not be available. Run at least one exercise a year outside normal office hours to see how the team copes.
How ERP changes the exercise
On paper, a mock recall means pulling registers, invoices and production sheets, often taking most of a day. When every lot is linked to its batches and every batch to its dispatches, the trace becomes a query. In Formezy, you open the lot or batch and see the full chain backward and forward, with quantities, so the effort shifts from searching to checking.
That only works if the records are captured at the time: lots at receipt, issues against the batch, packing runs with their codes, and batch numbers on every invoice. The beverage ERP process flows show where each of these is recorded in a juice or soft drink plant, and our page on food traceability and recall software explains the full approach.
A simple mock recall checklist
- Lot or batch chosen without warning the team
- Backward trace: all ingredient and packaging lots with quantities
- Forward trace: all customers, invoices and quantities
- Quantity reconciliation completed and explained
- Start and finish times recorded
- Gaps listed with an owner and a date to fix each one
WhatsApp