Food Withdrawal vs Recall: What’s the Difference?

A food withdrawal removes affected product from the supply chain before it has reached consumers. A food recall is required when unsafe food may already have reached consumers and they need to be informed and protected.

Where TapTick fits: TapTick gives sites a structured product-withdrawal record with product, batch, quantity, photos, outcome and responsible person kept together. See TapTick’s food-safety records.

The difference between a food withdrawal and recall

Both processes remove unsafe or otherwise non-compliant food from the market, but the location of the product determines the language and urgency of consumer communication.

Food withdrawal

A withdrawal applies where affected food has not reached the consumer. Product may be in a warehouse, distribution centre, shop stockroom, display or another business in the supply chain. The aim is to stop further distribution or sale and bring the affected stock under control.

Food recall

A recall applies where unsafe food has reached consumers. Consumers must be informed so they can avoid eating the product and follow the stated return, disposal or medical advice. Public notices, point-of-sale information and direct customer communication may form part of the response.

FSAI describes the distinction directly: withdrawal is required where unsafe food has not reached the consumer; recall is required where it has. UK FSA guidance uses the same practical distinction within its food-incident process.

Immediate actions when a problem is identified

1. Stop sale and distribution

Use tills, stock systems, staff messages and physical controls to prevent further sale. Do not rely on a message in a manager group while the product remains available on shelves.

2. Isolate affected stock

Move stock to a clearly marked quarantine area or otherwise prevent access. Record the quantity isolated at each location. Do not mix returned product with unaffected stock.

3. Confirm the product identity

Capture the exact product name, brand, pack size, barcode, batch or lot code, use-by or best-before date and supplier. Photographs of the pack and label reduce mistakes when several similar lines are stocked.

4. Escalate and notify

Follow the organisation’s incident plan and contact the competent authority promptly. In the UK, FSA business guidance says businesses should immediately tell their local authority when they need to withdraw or recall products. In Ireland, food incidents can be reported to the FSAI, with out-of-hours contact arrangements for urgent cases.

5. Preserve evidence

Keep supplier communications, delivery records, labels, photographs, stock counts, till data, customer complaints and decisions. Do not dispose of every sample before the incident lead or authority confirms what should be retained.

Trace the affected product quickly

Traceability is what turns an alert into a controlled response. A food business should be able to identify the business that supplied the food and any other food business to which it supplied the product. For retail sales to final consumers, the “one step forward” requirement may not identify each individual customer, which is why effective consumer communication can be essential.

Work through the numbers:

• How much affected product was received?
• Which deliveries, sites or storage locations received it?
• How much remains in stock?
• How much was sold, served, transferred or disposed of?
• How much has been recovered?
• Does the total reconcile?

A mass-balance calculation does not need to be complicated, but unexplained gaps should be investigated. If 100 units were received and only 30 are isolated, the response needs to establish what happened to the other 70.

What should a withdrawal or recall record contain?

• Date and time the incident was identified.
• Who raised and who leads the incident.
• Product name, brand, pack size and barcode.
• Batch or lot code and durability date.
• Supplier and delivery details.
• Reason for withdrawal or recall and known hazard.
• Sites, customers or channels affected.
• Quantity received, sold, isolated, recovered and disposed of.
• Photographs of the product and label.
• Authority, supplier and customer communications.
• Consumer notice details where a recall is required.
• Final product outcome and disposal evidence.
• Root-cause review and preventive action.
• Formal closure and approval.

Record the sequence of events with actual times. During an incident, the difference between “we told stores” and “all stores confirmed removal by 14:20” is significant.

What should an individual shop, deli or food-service site do?

A site may receive an instruction from head office, a supplier, a symbol group or the authority. The local response should be simple and verifiable:

1. Confirm receipt of the alert.
2. Identify every affected product location, including stockrooms and food-preparation areas.
3. Stop sale and remove or isolate stock.
4. Record quantities and label details.
5. Display the required customer notice for a recall.
6. Check whether the product was used as an ingredient in another item.
7. Report completion and discrepancies to the incident lead.
8. Retain the stock until collection or authorised disposal.

Sites should not substitute a similar batch or assume a slightly different date is included. If the alert details are unclear, pause and escalate.

Test the plan before a real incident

A written recall plan can look complete until somebody tries to use it. Run a periodic traceability or mock-withdrawal exercise using a real product and batch. Ask sites to find the item, report quantities and provide label evidence within a defined time.

The test should measure more than speed. Check whether contact details worked, whether the affected batch was interpreted consistently, whether stock figures reconciled and whether any product had been used as an ingredient. Record gaps and assign improvements exactly as you would for another food-safety action.

A mock exercise should not create false consumer alarms or unnecessary supplier escalation. Label it clearly as a test, control who receives the message and confirm when the exercise is closed. The purpose is to prove that the people, data and communication routes work together.

Withdrawal and recall readiness checklist

• A named incident lead and deputy are identified.
• Authority, supplier and internal contacts are current.
• Staff know how to stop sale and isolate stock.
• Batch, delivery and transfer records can be retrieved quickly.
• A quarantine location and labelling method are available.
• Consumer-notice templates and approval routes are known.
• Each site must confirm quantities and completion.
• Recovered and disposed stock is reconciled.
• The plan is tested periodically using a realistic product.
• Lessons from incidents and tests lead to documented improvements.