Consumer-Level vs Trade-Level Food Recalls

A consumer-level recall removes affected food from every point in the supply chain, including consumers' homes, and is publicised through the media and point-of-sale notices. A trade-level recall applies when product has only reached businesses — wholesalers, distributors, manufacturers or caterers — and not the public, so recovery stays within the trade and no public alert is issued. FSANZ coordinates both, but their scope, communication and records differ. Key takeaways: The recall level is set by how far the product has travelled: consumer-level when it has reached the public, trade-level when it has only reached other businesses.. Consumer-level recalls require public communication — media releases, point-of-sale notices and, often, website and social alerts — while trade-level recalls are handled through direct contact with affected businesses.. Both levels are coordinated with FSANZ under the Food Industry Recall Protocol and notified to your relevant state or territory food regulator.. Accurate one-up, one-down traceability records are what let you scope a recall correctly and prove where every affected unit went.. A recall is not the same as a withdrawal; withdrawals cover quality or non-safety issues that do not require regulatory recall action.. What a food recall is under the Food Standards Code A food recall is the action of removing unsafe food from the supply chain and, where necessary, from consumers. It is used when there is a food safety hazard — such as an undeclared allergen, microbial contamination, a foreign object, or a chemical or labelling defect that could make people ill. Standard 3.2.2 of the Australia New Zealand Food Standards Code requires food businesses that engage in wholesale supply, manufacture or import to have a written recall system and to be able to activate it. Recalls in Australia are coordinated nationally by Food Standards Australia New Zealand (FSANZ) through the Food Industry Recall Protocol, working alongside your state or territory food regulator. The first decision you make once a hazard is confirmed is how far the affected product has spread — and that single question determines whether the recall is classified as consumer-level or trade-level. Recalls address safety hazards, not routine quality complaints.. Standard 3.2.2 requires a documented, tested recall system.. FSANZ coordinates recalls with the relevant state or territory regulator.. Consumer-level recalls: product has reached the public A consumer-level recall is the most extensive type. It applies when affected food has moved past the trade and is available to, or already held by, members of the public — on retail shelves, sold online, or supplied through food-service outlets to diners. Because you cannot contact every household directly, the recall must reach consumers through broad public channels. That means a recall notice is typically published, media are notified, point-of-sale signage is displayed at retailers, and the recall is listed on the FSANZ recalls page. Many businesses also alert customers through their website, email databases and social media. The goal is to make sure anyone who may have the product knows to stop using it and can obtain a refund or safe disposal advice. Consumer-level recalls carry the highest reputational and logistical weight, so the notice wording, the affected batch or use-by details, and the described hazard all need to be accurate and easy for a shopper to check against product in their pantry. Triggered when product is accessible to or held by the public.. Requires public communication: media, point-of-sale notices and online alerts.. Notice must clearly identify affected units and the hazard.. Trade-level recalls: product stayed within the trade A trade-level recall applies when the affected food has only been distributed to other businesses and has not reached consumers. Typical examples include product still sitting with a distributor or wholesaler, ingredients supplied to another manufacturer, or stock delivered to a caterer or retailer but not yet placed on sale or served. Because the public is not exposed, recovery is handled by contacting the affected businesses directly — usually by phone and in writing — and arranging return, isolation or disposal of the stock. No public media release or point-of-sale notice is normally required, which makes a trade-level recall faster and less disruptive when it can be justified. The key is certainty. You can only classify a recall as trade-level if your records genuinely confirm that no affected product has been sold or served to the public. If there is any doubt, or if some units have slipped through to consumers, the recall must be escalated to consumer-level. Triggered when product is confined to wholesalers, manufacturers, distributors or caterers.. Managed by direct contact with affected businesses, not public alerts.. Only valid when records confirm no public exposure.. How to decide which level applies The decision hinges on distribution. Work through where every affected batch went and whether any of it became available to the public. This is where your traceability records earn their keep: if you can show that a batch was only ever held by named trade customers who have not on-sold it, a trade-level recall may be appropriate. If you cannot rule out public access — for example, a retailer received the stock and may have shelved it, or a caterer may have served it — treat it as consumer-level. Regulators and FSANZ expect a cautious approach; where the evidence is incomplete, the safer, broader classification is the correct one. Classification is not made in isolation. You notify your state or territory food regulator and FSANZ, and the level is confirmed in consultation with them under the recall protocol. Requirements and contacts vary by state and territory — confirm with your local council or regulator. Map every affected batch against your distribution records.. Trade-level only if you can prove no public exposure.. Confirm the level with FSANZ and your state or territory regulator.. Communication and notification differences The two levels differ most visibly in how you communicate. A trade-level recall relies on direct, documented contact with each affected business — a recall notification letter or email stating the product, batch codes, the hazard, and the action required, followed up to confirm the stock has been recovered or isolated. A consumer-level recall layers public communication on top of that trade contact. Depending on the case this can include a recall press release, notices at the point of sale, listing on the national recalls register, and direct customer alerts through owned channels. The recall notice must give consumers a clear way to identify the affected product and a defined action, such as returning it for a refund. In both cases you notify the relevant food regulator and FSANZ promptly. Keeping a written log of every notification, its timing and its recipient is essential for demonstrating that the recall was carried out effectively. Traceability: the records that make a recall work Neither recall level can be scoped accurately without traceability. Standard 3.2.2 requires businesses to keep records that allow product to be traced one step back to the immediate supplier and one step forward to the immediate customer — the 'one-up, one-down' principle. In practice this means recording supplier and customer details, delivery dates, product descriptions, and batch or lot identifiers. Strong batch coding is what lets you narrow a recall to the affected units rather than pulling an entire product line. When an undeclared allergen or a contamination event is identified, the batch and use-by data on your records and on-pack labelling are what consumers and trade customers use to check their stock. Test your recall system periodically with a mock recall. A practice run exposes gaps — missing customer contact details, unclear batch codes, or slow escalation — before a real event, when speed and accuracy matter most. Keep one-up, one-down records: immediate supplier and immediate customer.. Record batch or lot codes so recalls target only affected units.. Run mock recalls to test that records and contacts are current.. Recalls versus withdrawals Not every product issue is a recall. A withdrawal is the removal of product for a reason that is not a food safety hazard — for example, a minor quality defect, a spelling error on a label that does not affect allergen or safety information, or a marketing decision. Withdrawals are managed commercially and do not trigger the formal recall protocol. A recall, by contrast, is reserved for genuine safety hazards and is coordinated with FSANZ and your regulator. Undeclared allergens are always treated seriously; Plain English Allergen Labelling (PEAL) requirements under Standard 1.2.3 mean an allergen labelling failure is a common trigger for a consumer-level recall. If you are unsure whether an issue is a withdrawal or a recall, contact your state or territory food regulator early. It is better to raise a borderline case and be advised it is a withdrawal than to under-classify a genuine safety hazard. Checklist: Affected product, batch codes and use-by dates identified. Distribution traced one step back and one step forward. Recall level (consumer or trade) determined and justified. State or territory regulator and FSANZ notified. Trade customers contacted in writing (all levels). Public notices issued where consumer-level applies. Recovered, isolated and disposed stock reconciled. Actions, timings and notifications logged for the record. Common mistakes: Classifying a recall as trade-level when records cannot actually prove the product stayed out of public hands.. Treating an undeclared allergen as a minor issue rather than a likely consumer-level recall trigger.. Pulling an entire product line because batch coding was too weak to isolate the affected units.. Delaying notification to FSANZ and the state or territory regulator while trying to manage the issue alone.. Confusing a withdrawal (non-safety) with a recall (safety hazard) and skipping the recall protocol.. Never testing the recall system, so gaps in contact details or batch records only surface during a real event..