Recall Readiness

manufacturing
FSANZ
Verified April 2026

Definition

The preparedness of a food manufacturer to conduct a product recall quickly and effectively, including having traceability systems, communication plans, and documented procedures in place.

Key Takeaways

  • Recall readiness means your business can initiate, execute, and close a food recall efficiently without creating a crisis
  • A written recall plan must name roles and responsibilities, define decision-making authority, and list all required contacts
  • You must be able to identify all affected product by lot number and provide a distribution list within hours of the recall decision
  • FSANZ requires notification within 24 hours of a recall decision — internal delays before that clock starts can be costly
  • Mock recalls (traceability exercises) should be conducted at least annually to test whether your systems work under pressure

Regulatory Source

  • Food Industry Recall ProtocolFSANZ administers the national food recall system — businesses must be able to rapidly identify and withdraw affected product from all points of sale
  • Standard 3.2.2Food safety practices — food businesses must have documented procedures for product withdrawal and recall

Last verified against current standards: April 2026

Regulatory authority: Food Standards Australia New Zealand

What is Recall Readiness?

Recall readiness is a food business's demonstrated capability to rapidly identify, trace, and withdraw an unsafe or non-compliant food product from all points in the supply chain. In Australia, FSANZ administers the national food recall system under the Food Industry Recall Protocol, and Standard 3.2.2 requires all food businesses to have documented procedures for food withdrawal and recall.

The test of recall readiness is not whether you have a recall procedure document — it is whether you can execute it effectively under real-world conditions, within the timeframes that regulators and consumers expect. FSANZ expects businesses to be able to initiate a voluntary recall within hours of identifying a food safety problem.

The Recall Readiness Framework

A genuinely recall-ready food manufacturer needs four things to work together:

1. Traceability data: Complete batch records linking every finished product batch to the specific raw material lots used to produce it. Without this, you cannot identify which batches are affected by a specific ingredient problem.

2. Customer dispatch records: A complete record of which finished product batches were shipped to which customers (and when), so you can notify the right people to return or destroy affected product.

3. A documented recall procedure: A step-by-step procedure specifying who is responsible for each action, who makes the decision to recall, how FSANZ and state food authorities are notified, how customers are notified, how product is retrieved and disposed of, and how the effectiveness of the recall is verified.

4. A tested recall procedure: A mock recall exercise — conducted at least annually — that verifies the procedure works in practice. The exercise should measure traceability accuracy (can you identify 100% of affected product within a defined timeframe?) and response speed (how long does it take from identification to customer notification?).

Recall Readiness in Practice for Australian Food Manufacturers

The Mandatory Notification Rule: Under the FSANZ Food Industry Recall Protocol, if a food business decides to recall a product, it must notify FSANZ and the relevant state and territory food authority. FSANZ then coordinates the recall nationally and may issue a consumer-level recall notice.

Common gaps in recall readiness:

No lot number on outgoing product. If your finished product does not carry a lot number or batch code that corresponds to your internal batch records, you cannot link a consumer complaint or regulatory finding back to a specific batch.

Customer records not searchable by lot number. Knowing that you sold to Customer X last month is not enough. You need to know that Customer X received batch BB-2024-041 specifically — and that batch BB-2024-042 went to Customer Y.

Recall procedure never tested. A recall procedure that has never been exercised is untested. The first time you run it for real should not be during an actual recall event.

Worked example: A Victorian condiment manufacturer conducts an annual mock recall. Starting from a specific ingredient lot number (a mustard lot received in January), they have one hour to: identify all production batches that used that lot, identify all customers who received those batches, and prepare a draft customer notification letter. The exercise reveals that three batches are identified correctly within 35 minutes, but the customer notification template does not exist — only a draft recall procedure with a note to "draft template when needed." They add the template to the procedure before the real thing happens.

How Batchbase Enables Recall Readiness

Batchbase's traceability system is built for exactly this scenario. Given any ingredient lot number, Batchbase can identify every production batch that consumed that lot and every customer order linked to those batches — typically in under two minutes if your records are current.

The batch record system ensures lot numbers are captured at the point of production, not reconstructed later. Customer dispatch records are linked to batch numbers at the point of dispatch. Together, these provide the complete forward and backward traceability chain that makes a rapid recall response possible.

Related Standards and References

  • FSANZ Food Industry Recall Protocol — foodstandards.gov.au/industry-and-trade/food-recall
  • FSANZ Standard 3.2.2 — Food safety practices (product withdrawal and recall, Division 2)
  • FSANZ food standards code

Manage recall readiness compliance in Batchbase

Batchbase automates FSANZ compliance, nutrition labelling, allergen tracking, and batch costing for Australasian food manufacturers.

Built to meet Food Industry Recall Protocol, Standard 3.2.2 requirements.