Product Recall and Withdrawal: What Does Your Food Business Need to Know?
A product recall sounds like red alert, panic and a lot of drama. In reality, though, it is mainly a question of clear processes and a cool head. If you know what to do and when, you react calmly instead of in a hurry. That is exactly what product recall and withdrawal are about. And once you have practised your plan, the topic suddenly feels far less complicated.
Who a recall concerns
In short, anyone who produces, places on the market or passes on food. Manufacturers, distributors and suppliers share the responsibility for safety. Your exact role depends on where you stand in the supply chain.
Responsibility cannot simply be passed up or down the chain. Instead, every party needs to know its part and be able to act in an emergency. That is why it pays to run through the topic calmly before it becomes serious.
What EU food law requires
For food, the central rule is Regulation (EC) No 178/2002, the EU General Food Law. Its Article 19 obliges food business operators to act if they believe a food does not meet food safety requirements.
In that case, they must start withdrawing the food from the market and inform the competent authorities. If the product may already have reached consumers, they must also recall it effectively and inform consumers. So withdrawal and recall are not a friendly recommendation but a clear duty.
In addition, Article 18 requires traceability along the principle of one step back and one step forward. You must know your immediate suppliers and your immediate business customers. Without this information, a fast and targeted recall is hardly possible.
For consumer products other than food, the EU General Product Safety Regulation (EU) 2023/988 has applied since December 2024. It matters, for example, if you also sell equipment or non-food items. However, national rules and procedures can add further details, so always involve your competent authority early.
Product hold, withdrawal and recall
In practice, three steps are often confused. Yet each one means something different, and the right choice depends on where the product is and how serious the risk is.
Product hold. You stop the goods before they move further into the market. This contains a risk while you assess the situation calmly.
Withdrawal. You take the product back from the supply chain before it reaches consumers, for example directly from known business customers. This works only as long as the goods have not been sold to end customers.
Recall. You bring the product back from consumers who have already bought it. Here, you communicate openly so that affected products reliably leave circulation.
What your business needs in place
Here, quality management almost becomes a sport: a hurdle race that well-trained businesses manage with ease. If you are prepared, you do not trip over the first hurdle. Therefore, these points should be in place before anything happens.
Clear responsibilities. Who decides in an emergency, and who stands in if that person is away.
Traceable records. Batches, deliveries and customers documented in a way you can search quickly.
A practised procedure. Hold, withdrawal, recall and warning as defined steps, tested in a mock recall.
A contact list. Authorities, key customers, suppliers and, if needed, laboratories and insurers.
Trained staff. Everyone involved knows the plan and their own role in it.
Well-kept goods-in records are half the battle, for example when temperature monitoring reports a break in the cold chain. The QMSpot product recalls module covers the whole process from first suspicion to notification.
Public warnings: when and how
A public warning comes into play when a product may pose a serious risk and other measures are not enough. In that case, things sometimes need to move faster than lunch in the canteen.
Whether and how a warning is issued depends on the risk, the product and the legal requirements. Often, authorities are involved as well. At EU level, they share information through the Rapid Alert System for Food and Feed. The European Commission's page on the RASFF alert system explains how it works and links to the public consumers' portal.
This is exactly where a clear procedure pays off, because everyone knows what to do. Moreover, a recall that you start yourself usually leaves a better impression than one the authorities have to push.
Lessons from recent cases
Recalls often start with a deviation that someone noticed but nobody escalated. For example, a cold room ran too warm overnight, or a supplier reported a problem with a raw material. In both cases, speed decides how large the damage becomes.
Our article on the cyberattack on supermarket refrigeration systems shows how quickly a technical failure turns into a question of destroyed goods. Similarly, the new EU rules on Listeria in the food industry raise the recall risk for certain ready-to-eat products.
What you need to document
Recall plan. Roles, steps, decision criteria and contact details, reviewed at least once a year.
Traceability records. Suppliers, batches and business customers for every product.
Mock recalls. Date, scenario, time needed and lessons learned from each test.
Incident log. Every deviation that could lead to a hold, with its assessment and decision, tracked in the QMSpot defect management module.
Communication. Notifications to authorities, customers and, where needed, the public, with date and content.
Training. Who knows the plan, recorded in the QMSpot training and instructions module.
Frequently asked questions
What is the difference between a withdrawal and a recall?
A withdrawal removes the product from the supply chain before it reaches consumers. A recall, by contrast, brings it back from consumers who have already bought it.
When must I inform the authorities?
Under Article 19 of Regulation 178/2002, you must inform the competent authorities when you withdraw a food because it does not meet food safety requirements. National rules may set further details, so clarify the procedure with your authority in advance.
Who decides on a public warning?
That depends on the case, and authorities are often involved. What matters is that your business knows internally who informs and who decides.
How often should I test my recall plan?
The law does not set a fixed interval. In practice, many businesses test it at least once a year with a mock recall, and certification standards often expect regular tests.
How to get started
This week, pick one product and run a short mock recall. Trace it back to the supplier and forward to every business customer, and measure how long it takes.
The result shows you at once where your records have gaps. To see how this comes together in one system, take a look at QMSpot quality management software.
Would your team know what to do if a recall started tomorrow?
Then let's talk briefly about your processes and see how you can organise holds, withdrawals and recalls with QMSpot in a calm and traceable way.