Food Product Withdrawal Records: What Should You Keep?

A good food product withdrawal record should let somebody reconstruct the incident later: what product was affected, why action was needed, which stock and locations were involved, what each person did, what happened to the product and how the business confirmed that the response was complete.

Where TapTick fits: TapTick keeps a structured withdrawal record with product, batch, quantity, barcode, photos, responsible person and outcome, with site completion visible centrally. See how TapTick works.

Why food withdrawal records matter

A withdrawal is the removal of unsafe food from the supply chain before it has reached consumers. If unsafe food may already have reached consumers, a recall is required and consumer communication becomes part of the response.

In either case, traceability and evidence matter. FSAI says food businesses must be able to trace food one step back and, when supplying another food business, one step forward, and must be able to provide relevant records to the inspector. UK guidance similarly requires businesses to identify suppliers and food-business customers so unsafe product can be withdrawn or recalled effectively.

The withdrawal file is therefore more than a form. It is the evidence trail connecting the alert to the operational response.

For the basic distinction between the two processes, see Food Withdrawal vs Recall: What’s the Difference?

1. Record the original alert and why action was taken

Start by preserving the source information rather than rewriting it from memory.

Record:

• Date and time the issue was first identified or received.
• Who raised the issue: supplier, authority, head office, customer complaint or internal check.
• The reason for the withdrawal or recall.
• The known or suspected hazard, if stated.
• The original supplier or authority notice.
• The person appointed to lead the response.

If the information changes during the incident, keep the earlier version and record the update. Do not silently replace the original instruction, because the timeline may later explain why a site took a particular action.

2. Capture the exact product identity

The record should distinguish the affected product from similar stock. Capture as much of the following as applies:

• Product and brand name.
• Pack size.
• Barcode or GTIN.
• Batch, lot or production code.
• Use-by or best-before date.
• Supplier.
• Delivery date or reference.
• Photographs of the product, label and affected code.

Good product identification reduces two opposite risks: leaving affected stock in circulation and unnecessarily removing unaffected stock.

3. Keep the traceability and quantity records together

Traceability should answer where the product came from and where it went through the food-business supply chain. FSAI describes the legal minimum as one step back and, where relevant, one step forward. Its guidance also notes that stronger batch-level traceability can reduce the commercial impact of a withdrawal or recall.

For the affected product, capture:

• Supplier name and contact details.
• Relevant delivery notes, invoices or transfer records.
• Quantity received.
• Sites or food-business customers supplied.
• Quantity sent to each location where available.
• Quantity still in stock.
• Quantity sold, served, transferred or used.
• Quantity recovered, returned or disposed of.
• Any unresolved difference in the totals.

A quantity reconciliation is particularly useful during a multi-site incident. It can expose a missing location, stock transfer or ingredient use that a simple “completed” status would miss.

4. Record what each affected site actually did

If several locations are involved, each site response should become part of the central incident record.

For each location, record:

• when the alert was sent;
• when the site acknowledged it;
• who completed the check;
• whether affected stock was found;
• the batch or date information checked;
• the quantity isolated;
• photographic evidence where useful;
• whether the product had already been used as an ingredient;
• any discrepancy or question raised;
• the completion time.

“No affected stock found” is still a result and should be attributable. During a large response, head office also needs a list of sites that have not yet confirmed either outcome.

For a broader operational process, see how to manage a food recall across multiple sites.

5. Keep a decision and communication log

Food incidents develop. The first supplier message may be incomplete, the affected batch may widen, an authority may issue further instructions or a site may discover that a withdrawn ingredient was used in another product.

Keep a time-stamped record of important decisions and communications, including:

• contact with the supplier and competent authority;
• changes to the affected product scope;
• instructions sent to sites or customers;
• consumer communication where a recall is required;
• decisions to quarantine, return, destroy or retain stock;
• escalation of non-responsive sites;
• significant discrepancies and how they were resolved.

The UK FSA includes a key decision log among its practical recall tools. The value is simple: decisions made under pressure should remain understandable afterwards.

6. Connect failures to corrective action

A withdrawal may reveal weaknesses in purchasing, stock control, internal communication or traceability. Record those findings as corrective or preventive actions rather than burying them inside the incident narrative.

Examples include:

• a site contact list was out of date;
• staff could not identify the affected batch;
• direct local purchases were missing from central data;
• product was found in a secondary display after the main shelf had been cleared;
• ingredient-use records could not identify which finished products were affected;
• stock was disposed of before quantities were recorded.

Assign an owner and due date and verify completion. That turns the incident into evidence that the food-safety system was reviewed and improved.

7. Record the final outcome of the product

Isolation is temporary. The incident record should eventually show what happened to the affected stock.

That might be:

• returned to the supplier;
• collected by a distributor;
• destroyed or disposed of under instruction;
• retained for investigation or testing;
• released after confirmation that it was not affected.

Record who authorised the outcome, when it happened and any supporting evidence such as collection details or disposal confirmation.

8. Close the withdrawal formally

A strong closure note should make clear that the incident lead has reviewed the evidence rather than simply stopped receiving messages.

Before closure, confirm:

• all affected locations have responded;
• unresolved discrepancies have been investigated;
• affected product is controlled;
• traceability information is complete enough for the incident;
• return or disposal has been recorded;
• authority and supplier requirements are complete;
• corrective actions have owners and due dates;
• a final responsible person has approved closure.

Food product withdrawal record checklist

• Incident reference number.
• Date and time identified.
• Source of the alert.
• Incident lead.
• Product, pack size and barcode.
• Batch or lot code.
• Use-by or best-before date.
• Reason and hazard.
• Supplier and delivery information.
• Affected locations or customers.
• Quantities received, supplied, found, sold, recovered and disposed of.
• Photographs and label evidence.
• Site acknowledgements and completion times.
• Authority, supplier and customer communications.
• Key decisions.
• Corrective and preventive actions.
• Final stock outcome.
• Closure date and approval.