The real difference between a recall and a withdrawal, the removal steps a full mock recall rehearses beyond tracing, and how to prove with numbers that your product actually came back.
Do these first
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
After this lesson you can tell a recall apart from a withdrawal without guessing, run the part of a mock recall that comes after the trace — reaching customers and pulling product — and put a number on whether it worked. The reason to sort this out now is that during a real event you will not have time to look up which word applies or who you were supposed to call.
Operators use "recall" for anything that comes back off a truck. The law does not, and the difference decides who you have to notify and how fast. FDA defines the three in 21 CFR 7.3, and the lines are worth learning exactly.
A is the serious one. The product reached the market and there is a safety or legal problem with it.
A is the quality cousin. Product moved, but the reason you are pulling it does not rise to a legal violation.
A is the easy case: you caught it before it went anywhere, so it is neither a recall nor a withdrawal.
Two honesty points, because the words drift. First, your certification scheme and your customers may not use "withdrawal" the way FDA does. SQFI's own guidance, for instance, describes a product withdrawal as product pulled from the distribution chain before it reaches the consumer — closer to FDA's stock-recovery idea than to FDA's market withdrawal. Second, the classification is FDA's call as much as yours during a real event. Go by the definition your regulator and your customer actually apply, not by the label that feels least alarming. When it is a safety problem and the product is out there, it is a recall.
Once it is a recall, FDA sorts it by hazard into three classes, and the class drives everything downstream. A . A Class II recall is where the product may cause temporary or reversible health consequences, or where serious harm is remote. A Class III recall is product not likely to cause any adverse health consequence — a labeling or quality breach with no real hazard.
The class shapes three decisions your recall plan has to make, all named in FDA's recall strategy guidance: how deep you go (all the way to the consumer, or only to the retail or wholesale level), whether you issue a public warning, and how hard you check that the recall worked. A Class I problem reaches to the shelf and often to a press release; a Class III one may stop at your direct accounts with no public notice at all. You do not decide this in the moment — you decide the logic now, so the drill rehearses the real shape of the thing.
Your last drill traced the lot both ways and reconciled the quantities. A full mock recall goes one move further: it rehearses getting the product back. That part has three pieces, and each one is a place a real recall stalls.
You tell every customer who received the lot. FDA's rules for a recall communication (21 CFR 7.49) are plain about what it has to carry: it identifies the product, size, and lot or code numbers; it says clearly that the product is being recalled and that further distribution or use should stop; it tells each account to pass the notice on to their customers; it gives specific instructions on what to do with the product; and it gives the recipient an easy way to report back how much they have. Brief, factual, no marketing — a notice, not a letter.
In the mock, you are not sending it. You are proving you could: that your contact list is current, that it maps to the customers your forward trace turned up, and that the person who would send it knows where the template lives.
Then you get the product back or quarantined. In a real recall this is trucks and credits and a customer segregating stock. In the drill, you confirm the mechanics exist — where returned product would go, how you would tell your own on-hand and on-hold stock apart from good stock, who signs off. The point is to find the gap on a quiet day, not during the event.
Finally you decide what happens to what comes back — its . This is not an afterthought. FDA will not consider a recall finished until the product has been removed and, in the words of its termination rule (21 CFR 7.55), "proper disposition or correction has been made." Write down your options and who has the authority to choose among them, so nobody improvises destruction of a lot that could have been reconditioned, or the reverse.
Here is the part operators skip, and it is the whole reason the exercise exists. Getting product back is not the same as proving you got it back. FDA calls the proof , and it sets levels for how many you check (21 CFR 7.42): Level A is 100% of consignees, Level B is some share above 10% and below 100%, Level C is 10%, Level D is 2%, and Level E is none. The higher the hazard, the higher the level — a Class I recall leans toward checking everyone.
Effectiveness comes down to numbers you can state out loud. In a real recall, FDA's status reports (21 CFR 7.53) ask how many consignees you notified and when, how many responded, how much product they had, how many never answered, and the quantity you have accounted for. Your mock recall produces the same numbers on a smaller stage: the percentage of the lot you accounted for — the same mass-balance figure the step-by-step drill reconciled — and the time it took to reach every customer on the list. Those two numbers, recovery and speed, are your effectiveness evidence.
One caution so you cite it right. Neither FDA's recall rules nor the SQF code sets the recovery percentage or the clock you have to hit — SQF requires only that your system be tested and shown effective, at least annually. The specific targets, like accounting for 100% of a lot within a set number of hours, come from your customers, which the previous lesson on the 2-to-4-hour bar untangled. Measure recovery and speed every time; take the target from the strictest customer who gives you one.
A real recall runs three notification clocks at once, and blurring them is how operators miss one. Sort them now.
One jurisdiction note: this is FDA's framework. If your product is meat, poultry, or processed egg, it falls under USDA's Food Safety and Inspection Service instead, and FSIS runs its own recall process on its own terms. Know which agency owns your product before you need to call one.
You can now name the event correctly, rehearse the removal, and prove the result with a recovery percentage and a time. Notice what every piece of it rested on: knowing exactly which lot is which, what is on hold, what shipped, and what is still in your building. A recall you can actually execute is built on lots you can actually control — and that is the next course, where FEFO, QA holds, and defensible expiry turn the records you have been tracing into the daily discipline that keeps them true.
Do this in your operation