How-to
How to run a mock recall: a step-by-step guide for food brands
Published · 5 min read
The short answer
A mock recall is a timed drill: pick a real lot, trace it back to its ingredients and forward to every customer, reconcile the quantities, and draft the notices you would send. Done well, it takes a few hours and tells you exactly where your records would fail you in a real recall.
Why mock recalls matter
Nobody finds out their traceability is broken on a calm Tuesday. They find out when a supplier calls about a contaminated ingredient, or when a retailer asks for lot records by the end of the day. A mock recall moves that discovery into a drill you control.
Many food safety certification schemes (such as those benchmarked by the Global Food Safety Initiative) and many retail customers expect you to test your recall procedure at least once a year, and FDA's Food Traceability Rule expects covered firms to produce traceability records within 24 hours of a request. Even if none of that applies to you yet, the drill is the cheapest insurance in food manufacturing.
Before you start
- Name a recall coordinator and a small team: someone from quality, someone from operations or the warehouse, someone who can talk to customers, and someone from finance.
- Agree on the clock. Most teams time from the moment the scenario is announced to the moment the reconciled list of affected customers is complete.
- Decide the scenario in advance, but do not tell the team which lot until the clock starts.
- Have your written recall plan and contact lists to hand. The drill tests those too.
Step 1: Pick the lot and write the scenario
Choose a lot that will actually stress your records. Good choices are an ingredient lot that went into several production runs, or a finished-goods lot that shipped to many customers through more than one channel. A lot that was received and sold untouched proves very little.
Write a one-paragraph scenario: "Supplier X notified us that lot 24-0912 of dried oregano may contain undeclared allergen. Identify all affected product and customers." Alternate between ingredient-driven and finished-goods-driven scenarios from one drill to the next.
Step 2: Trace backward
Start from the lot in the scenario and work toward the source. For a finished-goods lot, list every ingredient and packaging lot that went into it, with quantities, and the supplier of each. For an ingredient lot, confirm the supplier, the receipt date, the quantity received, and any certificate of analysis on file.
Record where each answer came from (the system, a batch sheet, an email) and how long it took to find. Those notes are the real output of the drill.
Step 3: Trace forward
Now find everything the lot touched. For an ingredient lot, that means every production run that consumed it, every finished-goods lot those runs produced, and, if any of them were sub-assemblies such as a seasoning blend or a sauce base, every product those went into in turn. Then, for each affected finished lot, list every shipment: customer, ship date, quantity, order number, and tracking number.
Do not forget non-obvious destinations: samples, internal transfers to another warehouse or a 3PL, donations, and product that is still in transit.
Step 4: Reconcile the quantities
This is the step most teams skip and the one that matters most. For each affected lot, the numbers should balance:
| Line | What it means |
|---|---|
| Quantity received or produced | What came into existence under this lot |
| Less: quantity consumed in production | What went into other lots (trace those forward) |
| Less: quantity shipped to customers | What left the building, by customer |
| Less: quantity scrapped, sampled, or adjusted | Documented losses |
| Equals: quantity still on hand | Should match a physical count |
If the balance does not close, you have found a gap. Typical causes are unrecorded scrap, production that consumed a different lot than the one written down, and shipments recorded by SKU without a lot. Many programs set a target, such as accounting for all or nearly all of the product; agree on yours in advance.
Step 5: Put the affected stock on hold
In a real recall, the first operational action is to stop the affected product moving. In the drill, confirm you could do that: identify every location holding affected stock, and check that your system or process would prevent it from being picked. If your only control is a sign on a pallet, write that down.
Step 6: Draft the notifications
Using the forward-trace list, draft (but do not send) the notices: who you would contact at each customer, by what channel, and what you would say. Check that your contact details are current. Note which customers would need a call rather than an email, and which retailers have their own recall portals.
Step 7: Stop the clock and debrief
Record the total time and the time for each step. Then hold a short debrief while it is fresh:
- Which answers came from the system and which from paper or memory?
- Where did quantities fail to reconcile, and why?
- Which steps depended on one person who might not be available in a real event?
- What would have to change for the next drill to be faster?
Write the findings up as corrective actions with owners and dates. A mock recall that produces no actions was probably too easy.
Running the drill in Skygn
If your receipts, production, and shipments run through Skygn, steps 2 through 4 are mostly lookups. On the recall screen in the Quality module you pick the lot (ingredient or finished good) and get every posted customer shipment it reached, including shipments of finished goods built from it through multi-level production, with customer, quantity, date, sales order, and tracking number. The same view shows the backward trace to source lots and their suppliers, and the shipment list exports to CSV for reconciliation and notification drafting.
For step 5, lot statuses are configurable, and pick lists only allocate lots whose status allows shipping, so moving a lot to a quarantine status keeps it off new picks. For the corrective actions from the debrief, Skygn's CAPA records give each finding an owner and a due date, and supplier issues can go out as a SCAR to the supplier.
Skygn does not run the drill for you, time it, or write the notices; those stay with your team and your recall plan. What it removes is the hunt through spreadsheets. See lot traceability software for food manufacturers for how the underlying genealogy is recorded, or the features page for the quality module.
How often to run one
At least once a year, and again whenever something material changes: a new ERP, a new 3PL, a new co-packer, or a new product line. Rotate the coordinator so more than one person knows the procedure. If you sell foods covered by FSMA 204, use the drill to practise producing a sortable spreadsheet for a single lot within 24 hours.
Frequently asked questions
- How long should a mock recall take?
- There is no single legal standard for every firm. Many teams aim to complete the trace and reconciliation within a few hours, and FDA's Food Traceability Rule asks covered firms to provide records within 24 hours of a request. Set a target, time every drill, and work to shorten it.
- What percentage of product should a mock recall account for?
- Programs and customers set their own targets, often all or nearly all of the affected lot. Whatever your target, the point is to reconcile the quantity produced or received against what was consumed, shipped, scrapped, and remains on hand, and to explain any difference.
- Should we tell customers we are running a mock recall?
- Usually not for the drill itself; you draft notifications without sending them. Some brands do arrange a test contact with a key customer to confirm their recall contact details work. Agree on that with the customer in advance.
See it on your own items, lots, and recipes
Skygn is the ERP for food & beverage and CPG brands. One plan with every module, and a 14-day free trial.