One Step Back, One Step Forward: Traceability Explained

Traceability means being able to track food one step back to the supplier it came from and one step forward to the customer or business you sent it to. In Australia, food businesses are expected to keep records that identify their immediate suppliers and immediate recipients so that a product can be located quickly during a recall or withdrawal. It is the backbone of a fast, targeted response when something goes wrong. Key takeaways: Traceability is the ability to follow food one step back to your supplier and one step forward to your customer or the business you supplied.. You do not have to trace every internal movement — the legal focus is on your immediate inputs and immediate outputs.. Good records need enough detail (supplier, product, batch or lot, date and quantity) to isolate an affected product fast.. Strong traceability underpins a rapid, targeted recall or withdrawal, limiting risk to consumers and to your business.. Requirements vary by state and territory — confirm the exact expectations with your local council or regulator.. What one step back, one step forward actually means The principle is simpler than it sounds. "One step back" means you can identify the immediate supplier of any food or ingredient you received — the business you bought it from, not the whole chain behind them. "One step forward" means you can identify the immediate business customer you supplied a product to. Between those two points sits your own process, where internal records tie incoming ingredients to the finished products that leave your door. The deliberate limit here matters. You are not expected to map the entire supply chain from farm to fork on your own. If every business keeps solid one-back, one-forward records, regulators can stitch the links together and reconstruct the whole chain when they need to. Your job is to keep your two links strong and legible. One important exception applies at the retail end: when you sell directly to the public, you generally cannot trace one step forward to individual consumers. That is expected and accepted. Your forward traceability obligation is about the businesses you supply, not the shoppers who buy from your counter. Why traceability is the backbone of a recall When a food safety problem emerges — a pathogen, an undeclared allergen, foreign matter, or a mislabelling error — speed and precision decide how much harm is done. Traceability records let you answer the two questions a recall depends on: which batches are affected, and where did they go? Without them, you are guessing, and guessing usually means pulling far more product than necessary or, worse, missing affected stock. Good records turn a blunt instrument into a scalpel. Instead of withdrawing an entire product line, you can isolate a single lot or production run tied to a specific ingredient delivery. That protects consumers faster and protects your business from unnecessary loss and reputational damage. Traceability also supports the less dramatic but more common food withdrawal, where product is removed for a quality issue that is not a safety hazard. The same records that power a recall make routine withdrawals quick and controlled. What the Food Standards Code expects Food safety requirements in Australia sit under the Australia New Zealand Food Standards Code. Standard 3.2.2 (Food Safety Practices and General Requirements) sets out the general obligation for food businesses to be able to identify, to the extent practicable, the supplier of food and food that has been supplied. Standard 3.2.2A adds prescribed food safety management tools for certain higher-risk businesses. The Code does not dictate one universal template or filing system. It focuses on the outcome: you can produce the information that identifies your immediate suppliers and recipients when asked. Whether you achieve that with a spreadsheet, an invoice file, or a digital system is up to you, provided the records are accurate and retrievable. Adoption and enforcement of the Code happens through state and territory legislation, and additional expectations can apply to particular sectors. Requirements vary by state and territory — confirm the specifics for your business with your local council or regulator rather than assuming a single national rulebook. The records that make traceability work Traceability is only as good as the detail you capture. Vague records — "chicken, various suppliers" — collapse under pressure. Useful records let you draw a clean line from a specific delivery to a specific batch of finished product and on to a specific customer. At a minimum, aim to capture the following for goods coming in and going out: Supplier or customer name and contact details. Product description, including brand and pack size. Batch, lot or date codes wherever the product carries them. Date received or dispatched. Quantity received or supplied. Any relevant delivery or invoice reference number. Linking inputs to outputs inside your business The two external links only help if something connects them inside your operation. This is where internal traceability earns its keep. If you can show which ingredient batches went into which production run, you can trace a supplier problem forward to the exact finished products, and trace a customer complaint backward to the exact ingredients. Batch coding is the practical tool that makes this work. Assigning a lot or production code to each run, and recording the ingredient batches used in it, creates the bridge between one-step-back and one-step-forward. For many businesses this is a simple production log; for others it is built into a digital system. Allergen management leans heavily on this internal link. Under Plain English Allergen Labelling (PEAL) within Standard 1.2.3, declared allergens must be accurate, and a labelling error is a common recall trigger. If you can trace which run carried a mislabelled pack, you can confine the recall to that run instead of the whole product. Building traceability into daily habits Traceability fails when it is treated as paperwork done after the fact. It works when it is baked into the moments where information is already changing hands — at goods-in, at production, and at dispatch. Capture the detail as the event happens, not from memory later. Consistency beats sophistication. A tidy, complete paper file that everyone maintains the same way will outperform an elaborate system that half the team ignores. Decide who is responsible for each record, where it lives, and how long you keep it, then make that routine part of induction and daily practice. Test the system before you need it. A quick mock trace — pick a finished product and see how fast you can identify its ingredients and where it went, then pick an ingredient delivery and see where it ended up — reveals gaps while the stakes are low. Checklist: Every incoming delivery is logged with supplier, product, batch or date code, date and quantity. Every finished product carries a batch or lot code linked to the ingredients used. Records exist showing which ingredient batches went into which production run. Outgoing product to business customers is logged with dates and quantities. A named person is responsible for maintaining each record type. Records are stored in one known place and are retrievable within minutes. A mock trace has been run recently in both directions and gaps were fixed. State or territory and sector-specific requirements have been confirmed with the regulator. Common mistakes: Recording suppliers or products too vaguely to isolate an affected batch later. Failing to capture batch, lot or date codes at goods-in, so incoming stock cannot be linked to a delivery. Keeping strong external records but no internal link between ingredient batches and production runs. Treating traceability as after-the-fact paperwork instead of capturing detail as events happen. Never testing the system, so gaps only surface during a real recall when time is critical. Assuming one national rule applies without confirming state or territory and sector-specific requirements.