Supplier Approval and Food Traceability

An approved supplier program means you only buy food from vendors you have vetted and can identify, while traceability means you can track every product one step back (who supplied it) and one step forward (who you supplied). Together they let you isolate affected batches fast during a recall. Australian food businesses must generally be able to identify the food they receive and the supplier's name and Australian address - confirm the detail with your local regulator. Key takeaways: An approved supplier program limits your buying to vendors you have vetted, documented and re-review periodically - it is your first line of defence against contaminated or fraudulent ingredients.. Under the Food Standards Code you must generally be able to identify the food you receive and the supplier's name and address in Australia, and keep those details.. 'One-up-one-down' traceability means recording one step back (your supplier and product) and one step forward (who you sold or supplied to) so a recall can be scoped precisely.. Batch and lot records - linking incoming ingredient lots to the finished products and dates they went into - turn a whole-of-business recall into a targeted one.. Requirements vary by jurisdiction and food type; always confirm with your state or territory food regulator and local council.. Receiving checks that anchor traceability: Check at receiving, Requirement. Source — From an approved supplier. Chilled potentially hazardous food — Received at 5°C or colder. Frozen food — Received frozen hard. Packaging and dates — Intact packaging; within use-by or best-before. Record kept — Supplier, product, quantity, batch or lot code, date. What an approved supplier program is and why it matters An approved supplier program (ASP) is a documented system that restricts your business to purchasing ingredients, packaging and ready-to-eat foods only from suppliers you have assessed and formally approved. It is the practical expression of a simple food-safety truth: you can only make safe food from safe inputs. If a supplier ships you contaminated spinach, undeclared allergens or mislabelled product, that hazard flows straight into your kitchen and onto a plate. An ASP matters for three reasons. First, prevention - vetting suppliers up front screens out operators with poor hygiene, weak allergen controls or no recall capability. Second, speed - when a supplier issues a recall or you detect a problem, an ASP tells you exactly which of your products and batches are affected. Third, due diligence - a documented program demonstrates to an environmental health officer (EHO), an auditor or a court that you took reasonable steps to source safe food. For most retail and food-service businesses an ASP is good practice rather than a specific line-item legal requirement, but the underlying obligations to identify your food and suppliers and to keep records are built into the Food Standards Code. Some sectors, third-party certification schemes and customers impose stricter, contractual supplier-approval requirements on top of the Code. Building your approved supplier list Start by listing every supplier that provides food, food-contact packaging or ingredients. For each one, decide what evidence you need before approval - proportionate to the risk of what they supply. A supplier of high-risk ready-to-eat foods (smallgoods, pre-cut salads, dairy) warrants more scrutiny than a supplier of tinned tomatoes. Typical approval evidence includes the supplier's business name and Australian address, a current food safety certification or third-party audit (for example a HACCP-based or GFSI-recognised scheme), product specifications, allergen declarations, and confirmation they have a recall procedure. Record an approval date and a review date. Re-assess suppliers periodically - annually is a common cadence - and immediately if they change ownership, have a recall, or you receive a complaint or non-conforming delivery. Keep the list current: an approved supplier list is only useful if it reflects who you actually buy from today. Legal identity: business name and address in Australia. Certification or audit evidence appropriate to the risk. Product specifications and current allergen declarations. Confirmation the supplier has a working recall procedure. Approval date, reviewer and next review date. Receiving checks: the front line of traceability Traceability begins at the loading dock. Under the Food Standards Code, when a business receives food it should generally only accept it if it can identify the food and the name and Australian address of the supplier - and it must keep those details. Practically, that means every delivery is checked and logged before it is put away. At receipt, confirm the delivery is from an approved supplier, check temperatures of chilled and frozen goods (as a guide, receive potentially hazardous cold food at 5 C or colder and frozen food frozen hard), inspect packaging integrity and use-by or best-before dates, and record the supplier, product, quantity, batch or lot code and date received. Reject and document anything that fails - out-of-temperature, damaged, past date, or from an unapproved source. The delivery docket or invoice is often your primary traceability record, so keep it and make sure it carries the batch or lot information you will need if that product is later recalled. One-up-one-down traceability explained 'One-up-one-down' - also called 'one step forward, one step back' - is the core traceability principle across the Australian supply chain. One step back is knowing who supplied a food to you and being able to identify that food. One step forward is knowing who you supplied it to. For a restaurant or cafe selling directly to the public, 'one step forward' is typically the point of sale, so the back-tracing records matter most. For manufacturers, wholesalers and distributors, both directions are essential. FSANZ guidance for primary producers and processors (for example in horticulture) is explicit that you must be able to trace produce at least one step forward and one step back - who and where you receive produce from, and who and where you supply it to. The same logic underpins effective recalls at every level: if you can only say 'we use lettuce' rather than 'this lettuce, from this grower, this lot, went into these products on these dates', a recall becomes a guessing game. Build your systems so any product can be traced in both directions quickly, ideally within hours. Batch and lot records: linking inputs to outputs Receiving records tell you what came in; batch (lot) records connect those inputs to what you made and sold. This linkage is what converts a broad, expensive recall into a precise one. Without it, a single contaminated ingredient lot can force you to withdraw weeks of production because you cannot prove which finished goods contained it. A workable batch record captures, for each production run or day: the finished product and its batch or date code; the ingredient lots used (from your receiving records); the production date and quantity made; and where that batch was sent or how it was sold. For a small kitchen this can be as simple as a dated production sheet that lists the key ingredient batch codes. For a manufacturer it may live in a production or ERP system. The test is the same at any scale: given a suspect ingredient lot, can you identify every finished batch it went into, and given a suspect finished batch, can you identify every ingredient lot and every customer who received it? Finished product name and batch or date code. Ingredient and packaging lots used, tied back to receiving records. Production date and quantity produced. Customers or destinations the batch was supplied to (for non-retail). Enough detail to trace in both directions within hours. How supplier approval and traceability support recalls When a recall is triggered - by your own testing, a customer complaint, an EHO, or a supplier notification - your approved supplier and traceability records determine how fast and how narrowly you can act. A supplier recall notice will usually quote specific batch or lot codes. If your receiving and batch records link those codes to your finished products and onward customers, you can scope the recall to exactly the affected stock, notify the right customers, and provide the coordinating authority with accurate distribution information. Food recalls in Australia are coordinated by FSANZ in consultation with the business and the relevant state, territory and Australian government agencies, following the Food Industry Recall Protocol. Speed is critical during a serious food incident. Record-keeping obligations vary: notably, businesses covered by Standard 3.2.2A's record-keeping (evidence tool) requirement must keep the relevant records for at least three months - a period designed to support foodborne-illness outbreak investigations. Keeping records longer is sensible where products have a longer shelf life. Confirm the retention period and recall obligations that apply to you with your state or territory food regulator. Worked examples: Running a mock traceability exercise: A kitchen picks a random ingredient lot and traces it forward to the finished products and, for wholesale, the customers it went to, then picks a finished batch and traces it back to its ingredient lots and suppliers. They time the exercise and fix any gaps before a real incident tests the system. A substitute delivery during a shortage: During a supply shortage a supplier offers stock from a different source. Rather than accepting it blind, the business records the supplier, product and batch code at receiving and only adds the new supplier to its approved list once it has the risk-appropriate evidence, keeping traceability intact. Checklist: Approved supplier list exists, is current, and is accessible to receiving staff. Each supplier has a legal name and Australian address on file. Risk-appropriate evidence (certification, specs, allergen declarations, recall procedure) collected before approval. Approval and review dates recorded; suppliers re-assessed periodically and after incidents. Written receiving procedure covering approval check, temperature, dates and packaging. Every delivery logged with product, quantity, batch or lot code, supplier and date. Non-conforming deliveries rejected and documented. Batch or lot records link incoming ingredient lots to finished products and dates. For non-retail supply, records identify who each batch was sent to. Mock traceability exercise completed and gaps closed. Records retained for at least the period required in your jurisdiction. Retention and recall obligations confirmed with your state or territory regulator. Common mistakes: Keeping an approved supplier list that is never reviewed, so it no longer matches who you actually buy from.. Accepting deliveries from unapproved or substitute suppliers during shortages without recording or re-vetting them.. Filing invoices that lack batch or lot codes, leaving you unable to link a supplier recall to specific stock.. Recording what came in but never linking those lots to finished products - so a single lot forces a whole-of-production recall.. Assuming a verbal supplier assurance is enough; approval evidence and allergen declarations should be documented.. Never running a mock recall or traceability exercise, so gaps are only discovered during a real incident.. Discarding receiving records too soon, before the minimum retention period required in your jurisdiction..