Batch Coding and Lot Traceability

Batch coding is the practice of stamping a unique lot code on every product you make or pack so you can trace it forward to customers and backward to ingredients. Under the Food Standards Code, Australian food businesses must keep one-step-back, one-step-forward records. Good lot coding turns a slow, guessed recall into a fast, targeted one, protecting customers and limiting the volume you have to withdraw. Key takeaways: Traceability means being able to trace one step back (suppliers/ingredients) and one step forward (who you sold to) for every lot.. A lot (or batch) is a defined quantity made under the same conditions; every lot needs a unique, readable code.. Link raw-ingredient lot numbers to the finished-product lot code so you can identify exactly which products contain a suspect ingredient.. Keep records legible, dated and retrievable within hours, not days, because recall speed depends on it.. Test your traceability with a mock recall so gaps are found before a real event.. What to record at each step: Stage, Key details to capture, Direction. Receiving — Supplier, product, quantity, date, supplier lot code — One step back. Production — Ingredient lots used, finished lot code, date, quantity — The critical link. Dispatch / sale — Customer, lot supplied, quantity, date — One step forward. What batch coding and lot traceability actually mean A lot (also called a batch) is a defined quantity of a product produced, packed or received under essentially the same conditions, for example a single production run, a day's output on one line, or a delivery from one supplier. A lot or batch code is the unique identifier you assign to that quantity. Traceability is your ability to follow that lot in two directions: back to the ingredients and suppliers that went into it, and forward to the customers who received it. The Australia New Zealand Food Standards Code requires food businesses to be able to identify the food they receive and, where practicable, where they send it, so that unsafe food can be removed quickly. Batch coding is the mechanism that makes this possible in practice. Lot / batch: a defined quantity made or received under the same conditions.. Lot code: the unique identifier printed on the product or its packaging.. Traceability: the ability to trace that lot back to inputs and forward to customers.. One-step-back, one-step-forward explained The core legal expectation for most Australian food businesses is one-step-back, one-step-forward traceability. One step back means you can identify who supplied each ingredient, packaging item or finished product you received, and which lot it belonged to. One step forward means you can identify the immediate customers you supplied, unless you sell directly to the final consumer, in which case forward tracing stops at your point of sale. You are generally not required to trace the entire supply chain yourself, only your immediate links. When every business in the chain keeps its own one-back, one-forward records, regulators can join them together to trace a product from farm to plate. Confirm the exact record-keeping requirements that apply to your business with FSANZ and your state or territory regulator. One step back: which supplier and which lot each input came from.. One step forward: which customers received each of your lots.. Direct-to-consumer sellers only need to trace back, not forward to individuals.. Designing a lot code that works A useful lot code is unique, readable and meaningful to you without being so complex that staff make errors. Many businesses build the date of manufacture or packing into the code, sometimes with a line or shift identifier and a sequential run number. Whatever structure you choose, document what each part means so anyone in the business, and an auditor or regulator, can decode it. Keep the code physically durable: printed clearly on the label, ink-jetted onto packaging, or embossed so it survives handling, moisture and cold storage. Avoid reusing the same code for different production runs, and avoid codes that smudge or rub off in the fridge or freezer. Make each code unique to a single production run or received delivery.. Consider embedding the manufacture/pack date, line or shift, and a run number.. Document the code structure so anyone can interpret it.. Ensure the code stays legible through chilling, freezing and handling.. Never reuse a code for a different lot.. Linking ingredients to finished product The link between incoming ingredient lots and outgoing finished-product lots is what makes a recall fast and narrow. If a supplier tells you a specific flour lot is contaminated, you want to know within minutes exactly which of your product lots used that flour, and no more. To achieve this, record the supplier lot numbers of the key ingredients used in each of your production runs, and tie them to the finished-product lot code you assign. This is often done on a production or batch record for each run. Without this link, a single suspect ingredient can force you to withdraw far more product than necessary, because you cannot prove which lots are clean. Record supplier lot numbers for key ingredients on each production run.. Tie those ingredient lots to the finished-product lot code you assign.. Keep the record for each run so the link can be reconstructed later.. A strong link lets you recall only affected lots, not your whole stock.. Records you need to keep Traceability lives or dies on records. At a minimum, keep receiving records that capture the supplier, the product, the quantity, the date received and the supplier lot code for each delivery. Keep production or batch records that show which ingredient lots went into which finished lot, plus the date and quantity made. Keep dispatch or sales records that show which customers received which of your lots and when. Records can be paper or digital, but they must be legible, accurate and retrievable quickly during an incident. Decide how long you retain records based on the shelf life of your products and any requirements from your regulator; long-life products generally need longer retention. Confirm retention periods with your state or territory regulator. Receiving records: supplier, product, quantity, date, supplier lot code.. Production records: ingredient lots in, finished lot out, date, quantity.. Dispatch records: customer, lot supplied, quantity, date.. Store records so they can be pulled within hours, not days.. Using traceability in a recall or withdrawal When a problem is identified, whether from a supplier alert, a customer complaint, an internal check or a regulator, traceability determines how quickly and precisely you can respond. A withdrawal removes product for a quality or non-safety reason, often before it reaches consumers; a recall removes unsafe product from the market and may require public notification. In either case you use your records to identify every affected lot, calculate how much was made and where it went, and contact the relevant customers. Australia has a coordinated food recall system overseen by FSANZ working with state and territory agencies, and any consumer-level recall should be managed in line with the current Food Industry Recall Protocol. Notify your local enforcement agency promptly and follow their guidance; confirm the current process with FSANZ and your regulator. Identify every affected lot using your production and dispatch records.. Work out the quantity involved and exactly where it was sent.. Distinguish a withdrawal (not necessarily unsafe) from a recall (unsafe food).. Notify your enforcement agency and follow the current recall protocol.. Testing your system with a mock recall You will not know whether your traceability works until you test it. A mock recall is a rehearsal: you pick a real lot code, then work outward to identify every ingredient that went into it and every customer that received it, timing how long the exercise takes and noting where the trail goes cold. Do this at least periodically and after any significant change to suppliers, products or record systems. The gaps you find, missing lot codes on deliveries, illegible printing, incomplete dispatch records, are far cheaper to fix in a drill than during a live incident. Keep a short record of each mock recall and the improvements you made. Pick a real finished-product lot and trace it both directions.. Time the exercise and note where information is missing or slow.. Run it periodically and after major changes to suppliers or systems.. Record the results and fix the gaps you uncover.. Checklist: Every product carries a unique, legible lot or batch code.. The lot code structure is documented and staff can decode it.. Supplier lot codes are recorded for every ingredient delivery.. Each production run links ingredient lots to the finished lot code.. Dispatch or sales records show which customer got which lot.. Records are retrievable within hours during an incident.. A mock recall has been run and the gaps addressed.. Common mistakes: Assigning lot codes that smudge, rub off in cold storage, or get reused across runs.. Failing to record supplier lot numbers at receiving, breaking the one-step-back link.. Not linking ingredient lots to finished lots, forcing a wider recall than needed.. Keeping records only in one person's head or in a format that cannot be pulled quickly.. Never testing the system, so gaps are discovered during a real recall.. Discarding records too soon relative to product shelf life..