Lot Tracking for Food Traceability: Trace Recalls Fast.

Introduction.

Lot tracking in food traceability is the practice of assigning unique identifiers to discrete production batches and recording every movement, transformation, and handoff those batches undergo across the supply chain. When a recall hits, the speed and completeness of your lot trace determines how much product you pull, how many customers you have to contact, and how much liability you absorb. In the UK, the legal foundation has been in place since 2005 — food business operators must be able to identify who supplied them and who they supplied, one step back and one step forward — but the operational bar is set far higher than the law alone. If you are certificated to a retailer-recognised standard, you are expected to complete a full forward and backward trace, with mass balance, in four hours. This guide walks through what UK law actually requires, how batch and lot codes are structured, how rotation rules shrink your recall blast radius, and — critically — how to execute a fast, accurate lot trace when a recall is already underway.

What is lot tracking in food traceability?

Lot tracking is the systematic process of linking a unique identifier — a lot or batch code — to a specific quantity of food produced, received, or transformed under the same conditions, and then recording that identifier at every point the food changes hands, location, or form. In the food traceability context, a ‘lot’ typically represents a batch of product sharing a common production run, supplier source, ingredient set, or processing window.

The purpose is straightforward: if a contamination event or quality failure surfaces, you need to know exactly which units are affected, where they went, and who received them. Without lot-level granularity, a recall that could have been contained to a single pallet becomes a facility-wide or brand-wide event.

Lot tracking differs from simple inventory counting because it preserves the identity of each batch through receiving, storage, picking, shipping, and — where applicable — transformation into a new product. A food warehouse managing thousands of SKUs from dozens of suppliers cannot afford to treat inventory as fungible. Every case, pallet, or container needs a traceable lineage.

In UK practice, ‘batch’ and ‘lot’ are used more or less interchangeably, and you will see both on supplier documentation. Some manufacturers reserve ‘batch’ for production-side groupings and ‘lot’ for distribution-side groupings, but the traceability mechanics are identical: group product units under a shared identifier, then trace that identifier forward and backward through the chain.

For a broader look at how lot tracking fits within end-to-end supply chain traceability, see Balloon One’s guide to effective traceability in the food supply chain.

What UK law requires: Article 18 and the one step back, one step forward rule

The legal baseline

Traceability duties for food businesses in the UK sit in Article 18 of assimilated Regulation (EC) 178/2002, the General Food Law. Since 1 January 2005, every food and feed business has been required to keep records identifying its immediate suppliers and its immediate business customers. This is the principle usually described as one step back, one step forward, and it applies across the whole chain: primary producers, manufacturers, wholesalers, distributors, transporters, brokers, retailers, and caterers.

The offences and enforcement mechanisms are set out nationally. In Scotland, Wales, and Northern Ireland these flow through the General Food Regulations 2004; in England the equivalent provisions sit in the Food Safety and Hygiene (England) Regulations 2013. Following EU exit, retained EU legislation became assimilated law on 1 January 2024, so references to Regulation (EC) 178/2002 in Food Standards Agency guidance should now be read as references to assimilated law as it applies in Great Britain.

Enforcement is local. Your competent authority is your local authority or port health authority, and it is the body you notify first if you have placed unsafe food on the market. Where unsafe food may have reached consumers, you must also notify the FSA incidents team, or Food Standards Scotland if you operate north of the border.

Where Article 18 stops and lot-level tracking begins

This is the point most guidance glosses over, and it matters for how you scope a system. Read strictly, Article 18 requires you to name your suppliers and customers. It does not, by itself, require internal traceability — the matching of specific inputs to specific outputs, or records of how batches are split and combined inside your own four walls. A manufacturer is not obliged by Article 18 alone to record which sack of flour went into which cake.

In practice, that distinction is close to academic for anyone operating at scale, for four reasons:

• Commodity-specific law goes further. Sector rules impose batch-level requirements of their own — beef labelling, fishery products, eggs, and, for food of animal origin generally, assimilated Regulation (EU) 931/2011, which requires specific consignment information to be held and made available to the receiving business.

• Article 19 assumes you can act fast. The duty to withdraw or recall unsafe food is only meaningful if you can define ‘unsafe’ narrowly. Supplier-level records alone tell you nothing about which units to pull.

• Retailer and certification requirements are stricter than the law. UK supermarket own-label codes of practice and the BRCGS standards both demand demonstrable batch-level traceability, tested against the clock.

• Durability coding requires it anyway. If you handle perishables, you are already capturing ‘use by’ or ‘best before’ dates at goods-in. Attaching those to a batch identifier is a small step from there.

The practical conclusion: treat Article 18 as the floor, not the specification. Design to the standard your customers and auditors will actually test you against.

The FSA’s guidance on food traceability, withdrawals and recalls within the UK food industry sets out what the law requires and what good practice looks like across all four nations, including roles and responsibilities during an incident.

How batch and lot codes work: structure, GS1 standards, and what data they carry

What is a lot code in food manufacturing?

A lot code is an alphanumeric descriptor that uniquely identifies a traceability lot within a company’s records. In food manufacturing, the code is typically assigned at the point of initial packing or first receipt and stays with the product through every subsequent handling event.

A well-structured lot code encodes enough information to narrow a trace quickly without requiring a database lookup for basic context. Common elements include:

• Production date or shift — often encoded as a Julian date or YYMMDD format

• Site or line identifier — distinguishing output from different plants or processing lines

• Supplier or source code — linking the lot back to a specific grower, farm, or ingredient supplier

• Sequential batch number — differentiating multiple runs produced on the same date and line

For example, a code like LEE-240614-B03 might indicate the Leeds site, a production date of 14 June 2024, and the third batch of that day’s run. The structure is company-defined, but it must uniquely identify the lot within your records and be applied consistently.

How GS1 standards support lot code interoperability

While individual companies define their own internal formats, interoperability across the supply chain depends on standardised data carriers. The GS1 system, administered in this country by GS1 UK, provides the framework for encoding lot information into barcodes and data matrices that trading partners can read without ambiguity.

Under GS1 standards, lot codes are captured using Application Identifier (AI) 10, which designates the batch or lot number within a GS1-128 barcode or GS1 DataMatrix. Combined with the Global Trade Item Number (GTIN), the lot code creates a globally unique product-batch identifier that any supply chain participant with a compliant scanner can decode.

Note the distinction UK operators need to get right in configuration: AI (15) carries the best before date, a quality indicator, while AI (17) carries the use by date, the food safety one. Selling product after its use by date is an offence; selling after best before generally is not. Your rotation and blocking rules should treat the two differently.

The wider shift toward 2D barcodes at point of sale — the transition GS1 is driving toward 2027 — means lot-level data previously available only at case or pallet level will increasingly travel with individual consumer units. For food warehouses and food service distributors, scanning infrastructure must be capable of reading and recording these data-rich codes at receiving, putaway, and despatch.

To understand how different scanning technologies capture lot data at the physical level, see Balloon One’s comparison of barcode vs. RFID for food inventory tracking.

The four-hour test: BRCGS and retailer traceability requirements

For most UK food distributors and warehouse operators, the requirement that actually drives system design is not the General Food Law. It is the certification standard your customers insist on.

What BRCGS expects

Traceability is a fundamental requirement in the BRCGS Global Standard for Food Safety, meaning a site that fails it can lose certification outright rather than simply collecting a non-conformance. Sites must demonstrate full traceability of raw materials, including primary packaging, forward and backward through the chain, with a mass balance reconciliation at each stage. The system must be tested at least annually, and the test must be completed within four hours.

Four hours is a materially harder target than any regulator currently sets, and it is tested live during audit — the auditor picks the lot, not you. Sites relying on spreadsheets and paper goods-in books routinely discover this the hard way.

Warehouses, 3PLs, and wholesalers are more likely to be certificated to the BRCGS Global Standard for Storage and Distribution, which carries its own traceability requirements including, in the wholesale module, the ability to trace product lots back to the last manufacturer and forward to the customer. If you hold generic branded stock alongside own-label, scope this carefully at the design stage: the obligation is not limited to own-brand lines.

What retailers add on top

UK supermarket own-label codes of practice commonly go beyond the certification standard, typically by requiring:

• Minimum remaining shelf life on delivery, expressed as a fixed number of days or a percentage of total life, and varying by retailer and category

• Batch codes and durability dates on all outbound documentation and pallet labelling

• Electronic despatch advice carrying batch-level data, often via EDI DESADV, with SSCC pallet identifiers

• Participation in the customer mock recall programme at a defined frequency

Verify the mapping of your batch field before your first shipment against a new customer specification. A batch code that exists correctly in your WMS but drops out of the EDI message is, from the retailer’s perspective, a traceability failure.

FIFO and FEFO in food lot tracking: how rotation rules reduce recall exposure

What FIFO and FEFO mean for lot rotation

FIFO (First In, First Out) and FEFO (First Expired, First Out) are inventory rotation disciplines that determine the sequence in which lots are picked and despatched. FIFO prioritises the oldest received stock. FEFO prioritises the stock closest to its durability date, regardless of when it was received.

Both serve the same fundamental goal: preventing product from ageing unnecessarily in storage. But in the context of lot tracking and recall exposure, the distinction matters.

How FEFO reduces recall exposure

FEFO is the stronger discipline for food traceability because it directly accounts for shelf life variability. Two lots of the same product received on the same day may carry different durability dates due to differences in production timing, supplier lead times, or cold chain conditions. FIFO would treat them identically; FEFO would not.

From a recall perspective, FEFO reduces exposure in two concrete ways:

• Smaller recall scope. By consistently despatching the shortest-dated stock first, FEFO ensures that older lots do not linger in the warehouse, accumulating downstream distribution points. When a recall hits, the affected lot has been shipped to fewer locations over a shorter window.

• Fewer expired or near-expired lots in the field. FEFO minimises the chance that recalled product is simultaneously out of date and in consumer hands — a scenario that compounds both safety risk and reputational damage.

A WMS that enforces FEFO at the pick level — directing operators to the correct lot location based on durability date, not just receipt date — eliminates the human judgment that causes rotation failures. This matters most in a food warehouse managing hundreds of lots across temperature zones.

Configuration points worth getting right at the outset:

• Set allocation logic at lot level, not SKU level

• Hold or block lots that fall below a customer-specific minimum remaining shelf life, rather than applying one global threshold

• Prevent allocation of out-of-date stock outright rather than flagging it after the pick

• Update durability dates when product is repacked or relabelled

For deeper coverage of rotation strategies and date management, see Balloon One’s guide to perishable goods inventory management strategies.

Why rotation discipline is a traceability discipline

Rotation failures do not just create waste — they create traceability gaps. When lots are picked out of sequence, the assumed distribution pattern no longer matches reality. During a recall, this means the lot you think went to Customer A actually went to Customer B, and the lot you think is still in the warehouse was picked three days ago.

Enforcing FIFO or FEFO through system-directed picking ensures that the lot data in your WMS matches the physical reality on the floor. That alignment is the foundation of a fast, accurate trace.

How to trace a food lot during an active recall: a step-by-step workflow

This is where lot tracking infrastructure is tested under pressure. When a recall notification arrives — from a supplier, an enforcement authority, or your own technical team — the clock starts immediately. The goal is to identify every unit of the affected lot, determine where each unit currently sits, and initiate containment before the exposure window widens.

It is worth being precise about terms, because your obligations differ. A withdrawal removes unsafe product from the supply chain before it reaches the consumer. A recall goes further, asking consumers who already have the product to return or dispose of it. The FSA may support a recall by issuing a Product Withdrawal Information Notice, a Product Recall Information Notice, or, where local authorities need to act, a Food Alert for Action.

Step 1: Identify the affected lot

The notification will specify the product, the batch or lot code (or range of codes), and typically the production date range. Your first action is to query your WMS or traceability system using that code to pull every record associated with the lot.

What you need within minutes:

• Total quantity received under that code

• Date and source of receipt

• Current on-hand quantity and storage location(s)

• All outbound consignments containing that code, with recipient details and despatch dates

If your system cannot produce this from a single query, you have a gap that will surface at your next audit long before it surfaces in a real incident. Balloon One’s lot-level search is built to return these linked records in a single query to support rapid identification.

Step 2: Quarantine on-hand inventory

Any units of the affected lot still in your facility must be immediately quarantined — physically moved to a hold location or system-locked to prevent picking. A WMS with lot-level inventory control can execute this in seconds by changing lot status to hold, which removes it from available-to-promise inventory without requiring physical relocation first.

Physical segregation should follow promptly, but the system lock is the critical first action. It prevents an operator from unknowingly picking recalled product while the physical quarantine is being arranged.

Step 3: Trace forward to all recipients

Using the despatch records linked to the affected lot, generate a complete list of every customer, distribution centre, or retail location that received product from it. This forward trace must include:

• Customer name and delivery address

• Quantity despatched

• Date despatched

• Carrier and consignment reference for anything still in transit

For food service distributors serving restaurants, institutional kitchens, or convenience retail, this step often involves dozens or hundreds of recipients. The speed of this trace directly determines how quickly you can issue customer-level notifications.

Step 4: Trace backward to the source

Simultaneously, trace the affected lot backward to its origin. Pull the goods-in records linked to the code to identify:

• The immediate previous source (supplier, manufacturer, or co-packer)

• The supplier’s own batch code, if different from yours

• The date and location of receipt

• Any transformation events that combined this lot with other inputs

Backward tracing establishes the scope of the problem and determines whether other lots from the same source may also be affected. If you repack or relabel, this is also where mass balance is proved: the quantity received under a code should reconcile against the quantity despatched, held, and written off.

For operations where cold chain integrity is part of the investigation, Balloon One’s guide to how a WMS ensures food safety in the cold chain covers how temperature data integrates with lot-level tracing.

Step 5: Notify and document

Notification runs on two tracks and both start immediately.

• Authorities. Tell your local authority or port health authority, which will advise on further action. If you believe unsafe food has reached consumers, notify the FSA incidents team (or Food Standards Scotland). The FSA publishes templates for point-of-sale recall notices and a quick reference guide alongside its main guidance.

• Customers. Issue business-to-business notifications to every affected recipient with specific batch codes, quantities, and required actions, and track acknowledgement.

In parallel, compile the evidence pack: complete trace history for the affected code, the mass balance reconciliation, quarantine confirmation for on-hand stock, and customer notification records with timestamps. You will need this for the authority, for your certification body, and for the root cause analysis afterwards.

Balloon One’s WMS is designed to compile this documentation rapidly, so the constraint on your response is decision-making rather than data assembly.

Step 6: Confirm containment and close

Track responses from recipients confirming they have quarantined or returned the affected product. Update your system to reflect the final disposition of every unit — destroyed, returned, or confirmed consumed. Close the incident with a complete audit trail, and carry out a root cause analysis: the FSA advises this after any food safety incident, and your certification body will expect to see it.

Exporting to the US? What FSMA 204 adds

If you supply the American market, one further framework applies to your product before it clears the border. The FDA Food Traceability Final Rule, known as FSMA 204, requires firms that manufacture, process, pack, or hold foods on the FDA’s Food Traceability List to keep enhanced records and produce them within 24 hours of a request.

The mechanics will look familiar if you already run batch tracking for BRCGS. FSMA 204 requires a Traceability Lot Code to be assigned and propagated, and a defined set of Key Data Elements to be captured at each Critical Tracking Event: receiving, transformation, and shipping.

The compliance date moved from January 2026 to 20 July 2028 after the FDA proposed a 30-month extension, subsequently made binding by Congress. The rule itself was not changed, only the enforcement date.

Two things are worth noting for UK exporters. First, the four-hour BRCGS test is a tighter operational standard than the FDA’s 24-hour retrieval window, so a site that genuinely passes its BRCGS traceability test is close to meeting the retrieval requirement already — the gap is usually in the prescribed data fields, not the speed. Second, US retailer mandates are running ahead of the regulator, and several major chains already require batch-level data on advance shipping notices as a condition of supply.

Lot tracking for small food businesses: moving beyond spreadsheets and paper logs

Small food businesses — artisan producers, regional distributors, emerging brands — often begin with spreadsheet-based lot tracking or handwritten production logs. This works at low volume but breaks down predictably as the business scales, and it breaks down fastest at exactly the moment you are trying to win a retail listing.

The failure points are consistent:

• Manual entry errors — transposed digits, skipped rows, or inconsistent code formats make traces unreliable.

• No real-time visibility — a spreadsheet updated at the end of a shift cannot tell you where a lot is right now.

• Disconnected records — goods-in logs, production records, and despatch documents held in separate files cannot be cross-referenced in a single query.

• Audit exposure — when an auditor or environmental health officer asks for a trace, assembling the answer from paper takes hours or days, not the four you are allowed.

The transition from manual tracking to a digital system — a standalone lot tracking module, an ERP with batch traceability, or a full WMS — is not a technology upgrade. It is an operational prerequisite for recall readiness and, in most cases, for retail listing.

The minimum capabilities to look for:

• Batch code assignment at goods-in or production

• Lot-level inventory visibility across all storage locations

• FEFO-driven pick logic with customer-specific shelf life rules

• Forward and backward trace reporting, with mass balance, by batch code

• Durability date tracking with alert thresholds

For businesses evaluating how ERP-level batch traceability replaces manual processes, Balloon One’s guide to the importance of ERP batch traceability provides a detailed comparison.

Traceability duties apply regardless of business size. A small producer that cannot produce a trace is in the same legal position as a large distributor that cannot; the difference is that the small business has less margin for error and less capacity to absorb the consequences.

See how Balloon One makes lot traceability recall-ready from day one.

Every concept in this guide — batch code assignment, one step back and one step forward records, mass balance, FEFO-enforced rotation, forward and backward tracing against the clock — describes a process. Balloon One’s WMS makes that process executable at the speed a recall demands.

Balloon One works with food warehouses, food service distributors, and food manufacturers across the UK to implement lot tracking systems built for compliance and tested under pressure. From container-level tracking at goods-in to lot-specific pick direction on the warehouse floor to instant trace reporting during an incident, the system is designed around the reality that traceability is only as good as the data you capture and how fast you can retrieve it.

If you are preparing for a BRCGS audit, responding to a new retailer specification, replacing manual batch tracking, or simply ensuring your operation can handle a recall without scrambling, explore Balloon One’s warehouse management systems for food and beverage or visit the food and beverage logistics solutions page to see how the platform fits your operation.