A product recall tests a business at the worst possible time. Something has gone wrong, customers may be at risk, and the FSA expects a fast, accurate answer to one question: exactly which batches are affected, and where did they go. A business with proper batch tracking answers that question in minutes. A business without it spends days reconstructing the answer from delivery notes, invoices, and memory, while the affected product keeps moving further down the supply chain.
This is not a hypothetical risk for UK food and pharmaceutical businesses. Recalls happen, expiry dates matter for both safety and compliance, and the FSA holds businesses accountable for traceability regardless of how the tracking actually happens internally. Manual batch tracking, spreadsheets, paper logs, or memory, works until the day it genuinely needs to work fast, and that is exactly the day it tends to fail.
This post covers what proper batch tracking actually requires, why manual methods break down during a real recall, and what to look for in software built to handle expiry dates, lot tracking, and recall management properly.
What batch tracking actually needs to capture
Lot tracking software exists to answer a specific set of questions at any moment: which batch is this product from, where did the raw materials in that batch come from, where did the finished product go after production, and who received it. Every one of those questions needs a reliable answer, not a reconstructed guess, when a recall happens.
A proper system captures batch identity at every stage. Raw materials come in with a batch or lot number attached. Production links the finished product batch back to the specific raw material batches used. Distribution records exactly which customers or locations received units from each finished batch. And expiry dates attach to each batch specifically, not as a general product-level assumption that ignores when that particular batch was actually produced.
This chain, raw material to production to distribution, is what makes a real recall fast instead of chaotic. Break any link in that chain, and a business can identify the affected batch but cannot confidently say where it went, which defeats the entire purpose of tracking it in the first place.
Why manual batch tracking fails exactly when it matters most
Spreadsheets and paper logs can technically capture batch information. The problem is not whether the data can be recorded manually. It is whether that data stays accurate and complete under the pressure of daily operations, and whether it can actually be searched fast enough during a real recall.
Manual entry introduces gaps naturally. Someone forgets to log a batch number during a busy production run. A delivery note gets misfiled. A spreadsheet formula breaks and nobody notices for weeks. None of these gaps matter on a normal day. Every one of them matters enormously the day a recall notice goes out and a business needs to trace exactly where a specific batch ended up.
Search speed matters just as much as data completeness. Even a business that captured every batch record accurately faces a real problem if that data lives across multiple spreadsheets, delivery notes, and separate systems that do not connect. Reconstructing a batch’s full journey from raw material through distribution, done manually under recall pressure, can take days. The FSA does not grant extra time because the tracking system was slow.
What FSA expectations actually require
The FSA expects food businesses to maintain traceability that allows them to identify the immediate supplier and immediate recipient of any batch, sometimes described as one step back, one step forward traceability. During a recall, businesses need to move quickly to identify affected product, notify the relevant parties, and remove that product from the supply chain.
Meeting this expectation on paper is not the same as being able to meet it under real pressure. A business can technically have the required records somewhere in its filing system and still fail to produce a fast, accurate recall response if those records are not organized, connected, and searchable at the moment they are needed. FSA compliance in a recall scenario is really a test of speed and accuracy together, not just whether the data theoretically exists.
What expiry date management adds to the problem
Expiry tracking compounds the batch tracking challenge because it is not a static piece of data. A batch produced today has a different expiry date than a batch of the same product produced last week, and stock rotation needs to account for that difference to avoid selling or using expired product.
Manual expiry tracking usually relies on someone physically checking dates on shelves or in storage, a process that scales poorly as SKU count and batch volume grow. A business managing expiry dates manually across many products and batches is relying on consistent human attention to catch every date correctly, every time, which is exactly the kind of task that starts slipping once operations get busy.
Automated expiry tracking flags stock approaching its expiry date proactively, before it becomes a waste problem or, worse, a compliance problem from expired product accidentally reaching a customer.
What to look for in batch tracking software
Not every inventory system that mentions batch or lot tracking actually delivers full traceability. A few things are worth checking before assuming a platform handles this properly.
The system should capture batch identity at every stage, from raw material receipt through production and distribution, linking each stage to the next rather than tracking them as separate, disconnected records. Expiry dates should attach to individual batches, not a generic product-level assumption. Recall functionality should let a business search by batch and instantly see everywhere that batch went, customers, locations, quantities, without manual reconstruction. And the system should generate the traceability reports FSA compliance actually requires, ready to produce on demand rather than assembled under pressure during an active recall.
How Monesize Core approaches this
Monesize Core tracks batch identity through the full chain, from raw material receipt through production and final distribution, so a business can trace any batch’s complete journey without piecing records together from separate sources. Expiry dates attach to individual batches automatically, and the system flags stock approaching expiry before it becomes a waste or compliance issue.
During a recall, that connected tracking means a business can search a specific batch and immediately see every customer or location that received product from it, generating the traceability report FSA compliance requires in minutes rather than days. For a UK food or pharmaceutical business, that speed is not a convenience. It is the difference between a controlled recall and one that spreads further while the affected product keeps moving.
Being ready before the recall happens
Batch tracking only proves its value on the day a business actually needs it, and that day rarely gives any advance warning. A business relying on spreadsheets and paper logs can look compliant on a normal Tuesday and still fail an FSA traceability test the moment a real recall puts that system under genuine pressure.
If your business cannot currently trace a batch from raw material to customer in minutes, that gap is worth closing before a recall forces the question.
Track batches, expiry dates, and recalls automatically with Monesize Core. Request a demo to see how it handles your traceability requirements.