Decision support, authority and customer notification, traceability reconstruction and the post incident report, during a live withdrawal or recall.
A food recall removes unsafe or non compliant product that has already reached consumers. A withdrawal removes product from the supply chain before it reaches them. Product recall support covers the whole incident: deciding which action the situation requires, notifying the competent authority and your customers, reconstructing the traceability to define the affected batches, and producing the post incident report that closes it.
The decision that shapes everything is the first one. Whether a situation is a withdrawal, a recall or a public warning follows from the hazard, who is exposed and where the product has already gone. Getting that assessment right early keeps the incident proportionate and defensible.
Support through a live incident, from the first decision to the closing report. If you have an incident running, say so when you make contact and it is treated accordingly.
The first decision in any incident. It follows from the hazard, who is exposed and how far the product has already travelled.
| Action | What it means | When it applies | Notification |
|---|---|---|---|
| Withdrawal | Product is removed from the supply chain before it has reached the consumer. | Stock still held by you, distributors, wholesalers or retailers. | Authority notification is normally still required where the product is unsafe. |
| Recall | Product that has already reached consumers is retrieved or consumers are told not to use it. | Product on shelf, sold, or delivered directly to households. | Authority notification and, in most cases, a public notice. |
| Public warning | A public statement telling consumers not to consume product they may already hold. | Product widely distributed and the hazard is serious. | Issued with or by the competent authority, depending on the market. |
| No action beyond investigation | Product is confirmed safe and compliant, and the concern is resolved internally. | The decision itself is recorded with the evidence behind it. | None, though the decision record matters if the question is revisited. |
Place a hold on affected stock in your control and at every location you can reach. Every hour of further distribution enlarges the problem.
Separate confirmed fact from assumption. Recalls are frequently scoped on assumption and have to be widened later, which is far more damaging than a wide first scope.
Work the traceability in both directions, including rework, blending and anything reprocessed, which is where most scoping errors originate.
The hazard, who is exposed, and the likely consequence. This assessment drives whether the situation is a withdrawal, a recall or a public warning.
Where product is unsafe, notification is a legal obligation in most jurisdictions and there are time expectations attached to it.
Everyone who received affected product needs the batch detail and clear instructions on what to do with it.
One version of the facts, one named contact, and nothing said publicly that the traceability cannot support.
Times, decisions, who was informed and what they were told. Reconstructing this afterwards is close to impossible and it is the first thing an authority asks for.
Where you have reason to believe product you have placed on the market is unsafe, food law in most jurisdictions requires you to act and to inform the competent authority.
In the European Union that duty sits in Regulation (EC) 178/2002, and alerts move between member states through RASFF. In the United States the FDA operates its own reporting and recall framework. Other markets have their own routes and their own timeframes.
The trigger is reasonable belief. Waiting for certainty before notifying is one of the most frequently criticised decisions after an incident.
These eight cause most of the damage in an incident, and most of them are decisions taken in the first few hours.
Scoping on assumption to limit the size of the recall almost always ends in a second announcement. A widened recall damages credibility far more than a wide first one.
Affected material that went back into the process carries into batches nobody has considered. This is one of the most common reason a recall is incomplete.
The mass balance does not add up, so product is unaccounted for. The recall cannot be closed until the discrepancy is explained.
Waiting for complete information before informing the authority. Most jurisdictions expect prompt notification with what is known at the time, updated as more emerges.
Contact details that were correct when the account opened. During an incident, an unreachable customer is undistributed product still moving.
Sales, technical and management each briefing different people slightly differently. Inconsistency reads as concealment, whatever the intent.
Decisions made in a room and never documented. When an authority reviews the incident, an undocumented decision looks like no decision.
The incident closes, production resumes and the investigation never happens properly. The same failure returns, and the second occurrence is treated very differently.
Produced during the incident and assembled into a record that closes it.
| Element | What it covers |
|---|---|
| Decision support | Assessment of whether the situation requires a withdrawal, a recall, a public warning or no further action, with the reasoning recorded. |
| Scope definition | Affected batches established from the traceability, including rework, blending and reprocessed material. |
| Authority notification | Drafted notification to the competent authority in each market, in the form that market expects. |
| Customer communication | Drafted notices to every customer who received affected product, with batch detail and clear instructions. |
| Consumer notice | Where a public warning is required, drafted wording that is accurate and supportable. |
| Incident log | A contemporaneous record of times, decisions, notifications and responses. |
| Effectiveness check | Reconciliation of what was recovered against what was distributed. |
| Post incident report | The full account with root cause, corrective action and the evidence an authority or a customer will ask for. |
Manufacturers, processors, packers, importers and brand owners facing a live incident, and businesses closing one that has already happened. It suits operations without a dedicated crisis team, and any business facing its first recall.
A test result has come back and you are deciding whether to act.
A customer complaint suggests product already with consumers is affected.
An undeclared allergen has been found on a label or in a product.
A foreign body has been reported and you need to define the scope.
A supplier has notified you of an issue with material you have used.
An authority has contacted you about product you placed on the market.
You are mid incident and the traceability will not reconcile.
An incident has closed and you need the post incident report written.
You describe what has happened, what is confirmed and what is assumed, and where the product has gone.
The hazard and exposure are assessed, and the required action is determined with the reasoning recorded.
Traceability is worked in both directions, including rework and blending, to define the affected batches.
Authority and customer notifications are drafted for every market concerned, and consumer wording where required.
Responses are tracked, an incident log is maintained as events happen, and recovery is monitored.
An effectiveness check reconciles recovery against distribution, then the root cause investigation and post incident report complete the record.
Decisions are yours. Support covers assessment, drafting and record keeping, and the food business operator makes the call and submits the notifications.
Laboratory testing, logistics and physical recovery of product are arranged by you.
Legal advice and public relations sit outside this service. Where either is needed, the support says so plainly.
Every incident is quoted against its own scope. A single batch withdrawal in one market and a multi market recall of six months of production are very different pieces of work. These factors set the price.
These are the primary sources this work is built on. Where a market you sell into has its own requirement, that takes precedence and we assess against it.
A withdrawal removes product from the supply chain before it has reached the consumer, so the product is still with you, a distributor, a wholesaler or a retailer. A recall retrieves product that has already reached consumers, or tells them not to consume it. The distinction matters because a recall usually requires public communication and a withdrawal often does not.
When you have reason to believe food you have placed on the market is unsafe and it has already reached consumers. Most food law places that obligation directly on the food business operator, along with a duty to inform the competent authority. The trigger is reasonable belief, and waiting for certainty is a common and serious mistake.
The competent authority in every market where the affected product was placed, your direct customers, and consumers where a public warning is required. In the European Union this obligation sits in Regulation (EC) 178/2002 and alerts move between member states through RASFF. In the United States the FDA operates its own reporting and recall framework. Other markets have their own routes, so the notification list is built from the markets you sell in.
Promptly, with what you know at the time. Most jurisdictions expect immediate notification once you have reason to believe product is unsafe, updated as the picture develops. Holding back until the investigation is complete is one of the most frequently criticised decisions after an incident.
By working the traceability in both directions from the point of failure, and by including everything that touched the affected material. Rework, blending and reprocessed product are where scoping goes wrong most often, because they carry affected material into batches that look unrelated.
No. Scoping on assumption to keep a recall small usually ends in a second announcement when more product turns out to be affected. A widened recall does more commercial damage than a wide first one, and it changes how the authority reads everything else you say.
It depends on the risk, the distribution and the market. Where affected product is with consumers and the hazard is serious, a public notice is normally required, and it is often issued by or alongside the competent authority. Where product has not reached consumers, a withdrawal without public communication is frequently sufficient.
Every market where the product was placed has its own notification obligation and its own authority. Cross border incidents move through alert systems between authorities, so an incident notified in one market is likely to become known in others. The notification list is built market by market.
Incidents rarely arrive at convenient times. Availability is agreed when you make contact, and where an incident is live it is worth saying so immediately so the request is treated accordingly.
An effectiveness check reconciles what came back against what was distributed, then the root cause investigation runs and corrective action is put in place. The post incident report closes the event and is the document your customers and the authority will ask for.
A mock recall is a planned exercise testing whether your traceability works, run when nothing has gone wrong. This service supports a live incident where product is already affected. Businesses that have run genuine mock recalls handle real incidents considerably better.
Decision support with the reasoning recorded, a defined scope of affected batches, drafted notifications for the authority and your customers, consumer wording where required, a contemporaneous incident log, an effectiveness check and the post incident report.
Confi Food assigns work by subject. HACCP, labelling, certification standards, regulatory compliance, supplier assurance and monitoring are separate disciplines, and each piece goes to someone who works in that area. Every deliverable is reviewed internally by a second specialist before it reaches you.
Our technical positions are built from primary sources, meaning the legislation, the competent authority, Codex Alimentarius, the certification scheme owner or the relevant standards body. We set out how that works in our technical review and editorial policy, and what happens at each stage of an engagement in how Confi Food works.
A timed traceability exercise in both directions, testing whether you can account for product inside the window your standard demands.
Read about Traceability and Mock Recall Assessment →Support responding to a competent authority inspection finding or enforcement notice.
Read about Regulatory Inspection Response →Certificated course covering incident decision making, notification and recovery.
View Certified Recall and Crisis Management Specialist →Expert EU food law consulting worldwide. Compliance with Regulation 178/2002, the Hygiene Package, allergen management and the legal food safety culture requirements...
See EU Food Law Consulting →Expert UK food safety law consulting. Food Safety Act 1990, retained EU hygiene and labelling law, FSA Food Law Codes of Practice, Food Hygiene Rating Scheme, and...
See UK Food Safety Law Consulting →Expert FSMA consulting worldwide. Preventive Controls for Human Food, HARPC food safety plans, PCQI support, FSMA 204 traceability and FDA compliance for food businesses.
See FDA FSMA Consulting →If an incident is live, say so when you make contact and it is treated accordingly.