ISO 22000 clause 8.9.5: make food withdrawal and recall work in practice

What clause 8.9.5 requires in practice

Clause 8.9.5 requires the organisation to be able to withdraw or recall, in good time, lots of end product that have been identified as potentially unsafe. To make that real, it appoints competent people who have the authority to start and carry out the action. Documented information is needed for notifying relevant interested parties such as authorities, customers and consumers, for handling withdrawn or recalled product as well as stock still held, and for the sequence of actions.

Withdrawn or recalled product and stock still in hand is secured or kept under the organisation's control until it is dealt with under 8.9.4.3. Records of why a withdrawal or recall happened, how far it reached and what it achieved are kept, and top management receives them as an input to management review. The clause also expects verification that the arrangements work, using techniques such as a mock or practice withdrawal or recall, and records of that verification are retained.

Prepare authority and the action sequence

Identify who can initiate the process and who carries out its key activities. Consider cover when the usual decision-maker is unavailable. A plan that requires an unreachable signature can undermine timely action.

Maintain documented information for notifying relevant interested parties, including appropriate authorities, customers or consumers as applicable. The exact requirements depend on the product, jurisdiction and event. Use competent advice for those obligations rather than assuming one notification template fits every situation.

Define the sequence sufficiently for personnel to act. Connect product identification, communication, stock control, progress evaluation and disposition. Keep contact information and access arrangements current.

Control returned and remaining stock

Withdrawn or recalled product and end product still in stock must remain secured or under organisational control until managed through the disposition requirements. Recovery does not itself determine what happens to the product next.

Track product identity and status across relevant locations. A successful notification is not the same as confirmed action by every recipient. Obtain and evaluate appropriate responses while maintaining a reliable picture of the event.

Use traceability as a supporting capability. Traceability helps identify the relevant lots and routes, while withdrawal or recall adds the authority, communication and action needed to remove or control product.

Record the event and inform management

Retain the cause, extent and result of the withdrawal or recall and report them to top management as an input to management review. The record should explain the actual scope and outcome, including unresolved issues where relevant.

Examine what the event reveals about the FSMS. The cause may require corrective action, while the response may reveal separate weaknesses in information, contacts or authority. Address both rather than assuming product recovery closes the whole issue.

Test the capability before a real event

Verify implementation and effectiveness using appropriate techniques, such as a practice withdrawal or recall, and retain documented information. Design the exercise to test meaningful dependencies rather than merely completing a prefilled checklist.

Consider whether participants can identify affected lots, reach the right parties, account for stock and obtain decisions within the organisation's required response arrangements. ISO 22000 does not prescribe one universal exercise duration or recall completion time.

Why recall readiness matters before anything goes wrong

A recall is judged by speed and completeness. Customers and regulators will ask how quickly the organisation found the lots, reached the right people and secured remaining stock. A business that has never tested its arrangements discovers outdated contacts, unclear authority and unreliable stock records in the worst possible week. Preparation turns a potential crisis into a managed event and often limits the quantity of product involved. It is also commercial protection: major buyers increasingly ask to see exercise results as part of supplier approval. Reporting each event to top management means the lessons reach people who control resources, so that the next response is better than the last.

How to implement clause 8.9.5

Build the recall capability as a tested routine, with named people and current contact details. A plan that has never been run is a hope, and the exercise will show which parts of it work.

1. Appoint a recall lead and a deputy, and confirm they can reach decisions and authority without waiting for anyone else.
2. Draft the notification sequence for authorities, customers and consumers, with the legal obligations checked with competent advisers.
3. Define how affected lots are identified using traceability, and how stock at every location is secured.
4. Set up the contact list for customers, warehouses and logistics partners and assign someone to keep it current.
5. Plan the handling of returned and remaining stock so that it flows into the disposition process.
6. Run a practice exercise on a real ingredient or finished lot, including external locations, and measure what the team could not do.
7. Record the outcome, correct the weaknesses and feed the result to management review.

Illustrative food-manufacturing example

Illustrative food-distribution example

A distributor tests a withdrawal involving stock at two external warehouses. Central records identify the lots, but one warehouse's status report does not clearly separate stock held from stock already dispatched. The team resolves the information requirement and verifies the revised arrangement.

The test shows why a correct customer list alone does not establish effective withdrawal capability. Product status and action confirmation also matter.

Evidence and common mistakes