Lot Tracking for Food Traceability: A UK Setup Guide.

Introduction.

If a retail buyer, foodservice customer, or BRCGS auditor has just asked you to demonstrate batch-level traceability, you are not alone — and you are not early. UK food businesses have carried traceability obligations in law for over two decades, but the level of proof now expected has moved on considerably. Retailers want records they can interrogate, auditors want a timed trace exercise, and the gap between “we keep the paperwork” and “we can produce a defensible chain in under four hours” is where most small and mid-sized distributors get caught out. This guide is built for the operations manager who needs to get lot tracking configured correctly, not next quarter, but now. It covers the UK regulatory foundations, the system configuration steps that follow from them, and the operational pitfalls that cause lot data to fall apart at the worst possible moment. Balloon One helps UK food distributors translate these requirements into audit-ready system setups quickly and defensibly.

Who needs lot tracking — and what’s triggering the requirement?

Not every food business woke up one morning and decided to implement lot tracking. In most cases the requirement arrives from the outside — a customer contract, an audit notice, or a failed trace exercise — and it arrives with urgency.

What UK law requires

Traceability is not optional for UK food businesses and never has been. Under General Food Law — assimilated Regulation (EC) No 178/2002 as it applies in England, Wales and Scotland, alongside the General Food Regulations 2004 — every food business operator must be able to identify who supplied their food and which businesses they supplied it to. This is the “one step back, one step forward” principle, and it applies at every stage of production, processing and distribution.

The practical detail sits in the Food Standards Agency and Food Standards Scotland guidance on food traceability, withdrawals and recalls. It sets out the records you are expected to hold: the name and address of each supplier and business customer, the nature of the products, the quantities involved, and the dates of transaction. Crucially, that information must be available to enforcement authorities on demand — not reconstructable given a week and a spreadsheet.

Two points regularly catch distributors out. First, businesses handling products of animal origin and sprouted seeds face additional, more specific traceability requirements beyond the general rules. Second, while retailers selling directly to final consumers are not required to keep traceability records for those sales, the moment you supply another food business the full requirements apply — which covers essentially every wholesale and distribution operation.

Northern Ireland

If you supply into or operate from Northern Ireland, note that food law there continues to follow EU rules rather than the assimilated GB versions. The traceability principle is materially the same, but the legal basis and some documentation expectations differ, so check your position rather than assuming your GB setup transfers unchanged.

Retailer, foodservice and audit triggers

In practice, the sharpest pressure usually comes from customers rather than regulators. If you hold or are working towards BRCGS Global Standard for Food Safety certification, Clause 3.9 makes traceability a fundamental requirement: you must be able to trace raw material lots — including primary packaging — forward to customers and backward to suppliers, and you must test that capability. The working benchmark auditors apply is a full forward and backward trace, with quantities that reconcile, completed within four hours.

That timed element is what separates a real system from a filing cabinet. Major UK retailers and foodservice groups layer their own supplier requirements on top, frequently specifying batch data on outbound documentation and minimum remaining shelf life at the point of delivery. If you are a growing distributor moving into compliance-sensitive retail or foodservice channels for the first time, lot tracking is no longer optional; it is a prerequisite for onboarding. Balloon One’s implementations prioritise demonstrable record exports and the document formats these customers require.

If you export to the United States

Distributors shipping into the US market face an additional layer. The FDA’s FSMA Section 204 rule, the Final Rule on Requirements for Additional Traceability Records for Certain Foods, requires firms handling foods on the Food Traceability List — fresh leafy greens, fresh-cut fruit and vegetables, shell eggs, certain cheeses and nut butters among them — to keep prescribed lot-level records at defined points in the chain. If the US is not one of your markets, this does not apply to you; if it is, the good news is that a system configured properly for UK and BRCGS requirements already captures most of what FSMA 204 asks for.

The practical question is not whether you need lot tracking. It is whether you can demonstrate it when asked. For a broader view of the regulatory and operational landscape, see Balloon One’s guide to effective traceability in the food supply chain.

Batch codes, critical tracking events, and key data elements

Before configuring anything, you need three concepts clear. They are not abstract jargon — they define exactly what data your system must capture, when it must capture it, and how it must be structured.

Batch and lot codes

A batch or lot code uniquely identifies a group of product units that share an origin, production run, or receiving event. UK legislation on lot marking has required this identification on prepacked food for decades, and it is the thread that every other traceability record hangs from.

A lot code is not the same as a SKU or internal stock code. A SKU tells you what the product is; a lot code tells you which specific consignment of it you are holding. If your system currently tracks inventory only at SKU level, it cannot support traceability compliance — no amount of reporting on top will recover information that was never captured.

You may see the term “traceability lot code” or TLC in supplier documentation. That is US FSMA 204 terminology for the same underlying concept; UK guidance and BRCGS simply refer to batch or lot identification.

Critical tracking events (CTEs)

Critical tracking events are the points in the chain where traceability data must be recorded. For most distributors and food warehouse operators, these are:

• Receiving — when product arrives at your facility

• Transformation — when product is repacked, relabelled, or combined (if applicable)

• Shipping — when product leaves your facility

Each event requires a defined set of data tied to the lot code. Missing one means a gap in your chain — exactly the kind of gap that surfaces during an audit trace exercise or a live withdrawal.

Key data elements (KDEs)

Key data elements are the specific pieces of information captured at each event: the lot code, the product description, the quantity and unit of measure, the location identifiers for origin and destination, and the date. These map directly onto the records the FSA guidance expects you to hold, and onto the evidence a BRCGS auditor will ask to see.

Understanding how your ERP or inventory system captures and stores these elements is foundational. Balloon One’s overview of ERP batch traceability provides additional context on how these records flow through enterprise systems.

How to configure lot tracking in your inventory or WMS platform

This is where most guides stop and where most distributors get stuck. Understanding the regulatory framework is necessary, but it does not tell you what to do inside your system. The steps below apply whether you are configuring a standalone inventory management platform or a full warehouse management system.

Step 1: Enable lot-level inventory control

Your system must track inventory at the lot level, not just the SKU level. This means every unit of a given product in your warehouse can belong to a different lot, and the system must distinguish between them during every transaction — receiving, putaway, picking, and shipping.

In most WMS and inventory platforms, this requires activating a lot tracking module or flag at the item master level. Do this for every item that falls under a traceability requirement, not just the ones a single customer has asked about. Retrofitting lot tracking item by item is one of the most common sources of compliance gaps.

Step 2: Define your lot code assignment rules

You need a clear, documented rule for how lot codes are assigned. There are two common approaches:

• Inherit the supplier’s lot code. When you receive product, you capture the lot code from the supplier’s documentation (delivery note, pallet label, or case mark) and use it as your own. This is the simplest approach and is appropriate when you do not transform the product.

• Assign your own lot code at receiving. If you repack, relabel, or combine product from multiple supplier lots, you must assign a new code and maintain a record linking it back to the original supplier lot codes.

Whichever approach you use, your system must enforce it consistently. Manual lot code entry without validation consistently causes data quality failures. Configure your system to require lot code entry at the point of goods receipt, and use barcode scanning wherever possible to eliminate keying errors.

Step 3: Capture date codes at receiving

For perishable products the lot code alone is not enough. Your system must also capture the date code at goods-in. In the UK this means being precise about which date you are holding: a use by date is a food safety limit and it is an offence to sell product beyond it, whereas a best before date is a quality indicator. Your system should store the date type alongside the date itself, because the two drive very different handling rules.

Configure your receiving workflow so that date entry is mandatory for all lot-tracked perishable items. If your system allows it, set up validation rules that reject dates in the past or dates falling outside a reasonable shelf-life window for the product category.

Step 4: Map lot data to CTEs in your system

Your system needs to record the lot code, along with all required data elements, at each critical tracking event. At a minimum, this means:

If your system does not automatically carry the lot code through each of these transactions, you will end up with orphaned records — product received under a lot code but shipped without one, or vice versa. Audit this flow before you go live. Balloon One includes transactional flow tests as a standard part of implementations to catch these gaps early.

Step 5: Configure withdrawal and recall workflows

The entire point of lot tracking is to enable a rapid, targeted withdrawal or recall. Your system should let you query a single lot code and immediately return every transaction associated with it: where it came from, where it was stored, which customers received it, and how much remains in stock. You should also be able to reconcile quantities — auditors look for a credible mass balance, not just a list of movements.

Test this before you need it. Run a mock trace exercise quarterly: pick a lot code at random, trace it forward and backward, and verify the data is complete and reconciles. If it takes longer than the four-hour benchmark, or requires manual cross-referencing across spreadsheets, your setup is not ready. Document the results — the evidence of testing is itself an audit requirement.

For guidance on selecting a system that supports these workflows, see Balloon One’s guide to choosing a WMS for food and beverage traceability, lot control, and recall readiness.

Managing date codes with FEFO and FIFO logic

Lot tracking and date code management are inseparable for perishable food operations. Once your system captures dates at the lot level, you need to configure your pick logic to enforce proper stock rotation.

FEFO vs. FIFO: which to use

• FIFO (First In, First Out) rotates stock based on the date it was received. The oldest received stock is picked first.

• FEFO (First Expired, First Out) rotates stock based on the date code. The stock closest to expiry is picked first, regardless of when it was received.

For food traceability, FEFO is almost always the correct choice. Two lots of the same product can arrive on the same day but carry different dates — for example, if one came from a supplier with a longer transit time or an earlier production run. FIFO would treat them identically; FEFO ensures the shorter-dated stock moves first.

Configuring FEFO in your system

• Ensure date codes are captured at the lot level during receiving, with the date type recorded (see Step 3 above).

• Set your system’s pick allocation logic to prioritise lots by date, ascending.

• Configure customer-specific minimum remaining shelf life rules. UK retailers commonly specify a required proportion of shelf life remaining at delivery, and this varies by customer and category.

• Configure alerts or holds for lots approaching their threshold — product that should be flagged for review rather than shipped.

• Block picking of expired lots entirely. Your system should prevent an out-of-date lot being allocated to an order, not just flag it after the fact. For use-by products this is a legal exposure, not a service issue.

Common mistakes with FEFO configuration include setting the logic at SKU level rather than lot level, applying a single global shelf-life threshold instead of customer-specific rules, and failing to update date codes when product is relabelled or repacked.

For more on managing perishable inventory effectively, Balloon One’s article on perishable goods inventory management strategies covers the operational side in detail.

Where lot data breaks down in the food supply chain — and how to prevent it

Lot tracking systems do not fail because the software is incapable. They fail because lot data gets lost, corrupted, or never captured at specific handoff points. These are the points auditors and customers scrutinise most closely.

Receiving

This is the single most common point of failure. If your goods-in team does not capture the supplier’s lot code — or captures it incorrectly — every downstream record is compromised. The fix is straightforward but non-negotiable: require barcode or label scanning at receiving, validate lot codes against the delivery note or purchase order, and never allow product to be put away without a confirmed lot assignment.

Pick and pack

During order fulfilment, lot data breaks down when pickers take product from the wrong location, override system-directed picks, or fail to scan the lot code at the point of pick. This is especially common in food warehouse operations where throughput is prioritised over accuracy. System-directed picking with mandatory scan confirmation at each pick point eliminates this risk.

The choice of capture technology matters here. Barcode scanning is the minimum standard; RFID offers faster, hands-free capture in high-volume environments. Balloon One’s comparison of barcode vs. RFID for food inventory tracking can help you decide which approach fits your operation.

Outbound documentation

Even if your internal lot data is perfect, traceability breaks down if the lot code does not reach your customer’s records. Configure your system to populate lot codes automatically on delivery notes and packing lists. Where customers take an electronic despatch advice — the EANCOM or GS1 EDI DESPADV message most UK grocery retailers use — verify that the batch field is populated and mapped correctly before the first live shipment. A missing batch segment in an ASN is a common and avoidable onboarding failure.

Common lot tracking setup mistakes food distributors make

Having configured lot tracking systems for food businesses across a range of scales, we see the same mistakes repeatedly. Avoiding these will save you time, audit findings, and customer relationships.

• Tracking lots for some items but not others. If you enable lot tracking only for the items one customer has asked about, you will be caught short when a second customer — or an auditor — asks about a product you did not cover. Enable it for everything that could reasonably fall under a traceability requirement.

• Relying on manual lot code entry without validation. Free-text lot code fields lead to typos, inconsistent formatting, and duplicate codes that mean different things. Use barcode scanning and system validation rules.

• Not linking inbound and outbound lot records. Your system must maintain a clear chain from the supplier’s lot code through your internal assignment to the code on your customer’s despatch documentation. If these records live in separate systems or spreadsheets, the chain is broken.

• Ignoring customer-level shelf-life requirements. Different customers specify different minimum remaining shelf life at delivery. A single global threshold will meet your internal rules while breaching your customer’s.

• Never running a timed trace exercise. A lot tracking system that has not been tested against the clock is not a lot tracking system — it is a hypothesis. Run mock traces regularly, reconcile the quantities, and document the results.

• Treating lot tracking as an IT project, not an operational process. Configuring the software is half the job. Warehouse staff need training, SOPs need updating, and compliance ownership needs assigning to a named person or role. Without this, even a perfectly configured system degrades over time.

For operations involving cold chain or temperature-sensitive products, the stakes are higher still. Balloon One’s guide on how a WMS can ensure food safety in the cold chain addresses the additional lot management considerations for these environments.

Ready to get your lot tracking configured? Talk to Balloon One.

If you are a food distributor, wholesale food distributor, or food warehouse operator facing a traceability requirement for the first time — or realising that your current setup will not survive an audit trace exercise — the steps in this guide give you a clear path forward. But configuration decisions depend on your specific system, your product mix, and the requirements of the customers and channels you serve.

Balloon One implements and configures inventory management and warehouse management systems that meet traceability requirements from day one. We work with UK food distributors, wholesale food distributors, and food warehouse operators scaling into compliance-sensitive channels. Whether you need to evaluate whether your current ERP can support lot tracking (our guide to vital ERP features for food distribution is a good starting point) or you are ready to scope a full implementation, our team can help you move from compliance gap to audit-ready.

Get in touch with Balloon One’s food and beverage logistics team to start the conversation.