Written by: JJ Tan, Founder, Jelly
Key Takeaways
- Batch and expiry tracking records each delivery as a distinct lot with its own use-by date. This enables FEFO rotation and supplier-to-plate traceability.
- Precise lot-level tracking protects margins and satisfies EHO inspections, especially against the 4–10% food spend waste figure cited below.
- Effective systems capture lot numbers at goods-in, hold per-batch expiry dates, enforce FEFO, log waste against batches, and produce exportable audit reports.
- Expiry-only tools alert staff to near-expiry stock. Full platforms add traceability and multi-site batch tracking for operators with multiple suppliers or expansion plans.
- Jelly provides automated invoice scanning, live dish costing, expiry alerts and POS-driven depletion at a flat £129/month per location, helping UK restaurants cut waste and meet FSA compliance.
See How Jelly Tracks Batches End To End
What Restaurant Batch And Expiry Tracking Software Must Deliver
Restaurant batch and expiry tracking software must support specific operational and compliance outcomes. The ten points below form the evaluation spine for every system discussed in this guide.
- Lot recorded at goods-in
- Use-by date held per batch, not per product
- FEFO stock rotation
- Supplier-to-plate traceability
- Configurable expiry alerts
- Waste logged against the batch
- Stock counts and purchase orders
- POS-driven depletion
- Multi-site support
- Exportable audit reports
Check Your Operation Against The Ten Points
The Operational Problem: Stock Counting Without Batch Visibility
A system that handles invoices and purchase orders but cannot identify which batch of chicken expires on Thursday is a stock counter with a compliance gap. The distinction matters because batch and expiry tracking is both a margin issue and a regulatory issue for UK restaurants, pubs and boutique hotels.
On the margin side, a bistro with 3–5% uncontrolled food waste loses roughly £4,750 a year on £95,000 of purchases, before any improvement is attempted. Industry research consistently suggests UK restaurants lose between 4% and 10% of food spend to waste. On the compliance side, an Environmental Health Officer (EHO) who arrives unannounced expects to see evidence that rotation actually happens. They look for proof, not only a policy document.
A system that only tracks stock at product level cannot answer either question with precision. It cannot tell you which of two deliveries of the same chicken breast expires first. It also cannot produce the lot-level traceability report an EHO or the Food Standards Agency may request on demand.
Batch, Lot, Per-Batch Expiry And FEFO: Core Definitions
Batch and lot tracking means recording stock as identified lots rather than as a simple quantity of an item. Each lot carries its own lot number, supplier, delivery date and use-by date, and that identity is kept through every subsequent movement. At any moment the system can answer which lots of an item you hold, where they sit, how much remains, when each expires, and which receipt each arrived on.
Per-batch versus per-product expiry: a product-level expiry date applies one date to every unit of a SKU. Per-batch expiry holds a separate use-by date against each delivery, so two cartons of the same product received on different days carry different dates. A product-level expiry setup can automate generic actions such as out-of-stock status, but it cannot replace batch-level lot control.
FIFO versus FEFO: FIFO rotates by arrival order. FEFO rotates by the earliest use-by date regardless of arrival. They produce the same picking decision only when every delivery of a product has the same shelf life and arrives in the same condition. They diverge when suppliers send mixed batches, when the same item is bought from more than one supplier, or when chilled goods arrive with varying use-by dates. FEFO is the safer default for chilled, fresh and prepared foods.
The waste and compliance consequences of weak FEFO controls are concrete. In FEFO systems, expired lots are excluded as a hard eligibility filter, so an expired batch never appears as issuable stock and cannot be picked by mistake. Software that enforces this behaviour produces FEFO compliance in practice. Without per-batch expiry, soon-to-expire stock sits behind fresher deliveries, write-offs stay invisible until stock-take, and a recall cannot be isolated to a single lot.
How Batch And Expiry Tracking Flows From Goods-In To Plate
Batch and expiry tracking spans the entire operation and depends on clear handoffs between roles.
The chain starts at goods-in, where receiving staff capture the lot number and use-by date. If lot numbers or expiry dates are missed at this stage, the entire traceability chain becomes unreliable. From there, kitchen staff rotate by FEFO at the shelf, placing earliest-expiring stock at the front so the right batch is picked first.
That rotation step lets finance see waste and variance logged against the batch rather than only against the product. It also lets operations teams at two to five sites see multi-site exposure in a single dashboard instead of chasing individual site managers for updates.
The category has moved from spreadsheets and paper date labels to connected, real-time systems for a practical reason. A spreadsheet is always accurate on Monday, but by Thursday, after several receiving shifts and a supplier substitution, nobody can say for sure which version is right. A connected system holds the current state of every batch and removes the need for manual reconciliation after each shift.
Key Considerations When Choosing Between Expiry-Only And Full Platforms
The main trade-off in this category sits between expiry-only tools and full batch and traceability platforms. An expiry-only tool solves the date problem by alerting staff when stock approaches its use-by date. It does not solve the traceability problem, because it cannot produce forward and backward traceability reports, link allergen-bearing ingredients to supplier specifications, or support multi-site batch tracking.
A full platform solves both problems but demands more setup discipline at goods-in. Lot numbers must be captured consistently, supplier labels must be legible, and staff must follow the process at every receiving shift. The tier decision usually follows the readiness checklist below rather than the budget.
Single-site operators with a narrow fresh range and no multi-site traceability requirement may find an expiry-only tool sufficient in the short term. Operators with multiple suppliers, mixed-batch deliveries, allergen-record obligations, or expansion plans to two to five sites need a full platform.
How To Assess Your Readiness Before You Shortlist
Assess operational readiness before shortlisting any system. A system only performs as well as the data going in.
- People: A named person at goods-in should capture lot and date on every delivery, and a named person should review the near-expiry report weekly.
- Process: Prepared in-house batches such as sauces, prepped vegetables and cooked components should carry a made-on or use-by date.
- Data Quality: Supplier labels should be legible, with lot numbers and dates in a consistent format.
- Supplier Coordination: Suppliers should agree to consistent lot and date labelling and to informing you of allergen changes.
- Integration: Your POS should deliver item-level sales data, and your accounting software should accept digitised invoices.
The Comparison: How Named Systems Map To The Ten-Point Checklist
The table below maps each named system against three checklist points that most often separate a true batch-tracking platform from a stock counter: batch and lot tracking, expiry and FEFO alerts, and multi-site support. Read it to see how many vendors can evidence all three from published material, because the gaps are as informative as the ticks. Every cell is populated only from published vendor claims. Where a vendor's published page does not state a capability, this is noted explicitly.
A note on UK relevance and budget tier helps narrow the shortlist. Qubi appears in both the Google AI Overview and ChatGPT answers and publishes pricing in euros on a monthly or annual basis. Apicbase and Unleashed also appear in the AI Overview. Unleashed publishes USD pricing and is positioned primarily at food manufacturing and distribution rather than restaurant kitchens. Gastrocore, TruLens, Forkto and ExpGuard are UK-specific names surfaced mainly by ChatGPT and are under-represented in Google's answer. ExpGuard is a US-based manufacturer of stainless steel corner guards and wall protection products, so it falls outside the restaurant inventory category and should be excluded from any shortlist on that basis. Forkto is positioned as a UK food safety management system starting at £13/month per site. Kafoodle's published positioning focuses on menu, allergen and labelling compliance rather than warehouse-grade batch inventory.
That split between tools that only handle dates and platforms that hold lot identity end to end is the most useful way to narrow a shortlist. The next section sets out which tier suits which operator.
Expiry-Only Tools Versus Full Batch And Traceability Platforms
Expiry-only tools alert staff to near-expiry stock. They do not record lot numbers, link batches to suppliers, produce forward and backward traceability reports, or support allergen-record linkage at batch level. They suit single-site operators with a narrow fresh range, a small supplier base, and no multi-site traceability requirement.
Full batch and traceability platforms, including Forkto, Unleashed, Qubi and Jelly, record lot identity from goods-in through to depletion, link allergen-bearing ingredients to supplier specifications, and produce exportable audit reports. They suit operators with multiple suppliers, mixed-batch deliveries, allergen-record obligations under FSA allergen guidance, or expansion plans to two to five sites.
The tier decision follows the readiness checklist above. An operator without goods-in discipline will not get value from a full platform, regardless of price.
Batch And Lot Records Expected In UK Food Safety Inspections
This section translates FSA traceability expectations into the specific fields and reports a system must produce.
Under Article 18 of UK General Food Law, food business operators must keep records of the businesses that supplied them with food and the businesses to which their products have been supplied, and make those records available to competent authorities on demand. The FSA describes this as a “one step back, one step forward” system.
- Supplier, consignor and consignee business names and addresses
- Volume or quantity of the food
- A reference identifying the lot, batch or consignment
- A detailed description of the food
- The date of dispatch
The FSA states that businesses “can also record” batch number, invoices and receipts of food products purchased, and notes this information will often already be on the invoice. This makes batch number capture recommended additional data rather than a mandatory field. In practice, an EHO will look for evidence that rotation actually happens, such as clear labels with delivery or made-on dates, a stocktake routine, and a record of any out-of-date items removed.
For allergen records, FSA allergen audit materials show inspectors expect incoming traceability for allergens, including supplier details and ingredient specifications. Allergen traceability should sit alongside batch and lot records rather than in a separate manual file. The system must be able to produce:
- Lot number, supplier, delivery date and use-by date per batch
- Batch-level depletion showing which batch went into which dish
- Waste records logged against the batch
- Exportable traceability reports, both forward and backward
- Exportable allergen reports linking allergen-bearing ingredients to supplier identity and product specification
Article 19 of UK General Food Law also requires food business operators to withdraw or recall food they believe does not comply with food safety requirements, and to notify competent authorities immediately. A system that cannot isolate a single lot cannot support a targeted recall and forces the operator to pull every unit of a product instead of the affected batch alone.
Jelly: Batch And Expiry Tracking For Growing UK Operators
Jelly suits operators who have moved beyond spreadsheets and need a connected, automated system. It covers invoice scanning, live dish costing, expiry and price alerting, and POS-driven depletion at a flat rate of £129/month per location with no per-user charge.
Judged against the ten-point checklist, Jelly delivers:
- Automated Invoice Scanning: Every line item, including quantity, SKU, price and tax, is digitised from a photo or email. This creates batch-level purchase data without manual entry and forms the foundation of lot capture at goods-in.
- Live Dish Costing: As invoices update ingredient prices, dish costs and GP margins update in real time. A dish that drops its margin shows a red percentage immediately.
- Price Alerts: Jelly flags every supplier price increase or decrease, giving chefs evidence to negotiate and claim credit notes. Amber restaurant saved £3,000–£4,000 per month using Jelly through a combination of price alerts, invoice automation and real-time costing.
- Flash Reports: Jelly provides a daily, weekly or monthly view of GP margin, calculated from invoice costs and POS sales.
- Kitchen Cookbook: Users build dishes by clicking on ingredients already populated from scanned invoices. Unit conversions and maths are handled automatically, so costing a menu item drops from 28 minutes to about 3 minutes.
- POS Integration: Square, EPOS Now, Toast and Lightspeed deliver item-level sales data the moment a transaction completes, driving sales mix and margin calculations. Connecting a POS automates 2–5 hours of weekly work.
Jelly onboards and generates initial value in the first week. Price alerts and spending insights become available once suppliers send invoices to a dedicated email address or within 24 hours of photographing invoices into Jelly. Operators save 10–20 hours of admin per month. Populu lifted GP from 68% to 72% across 16 locations, and one operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue.
Put The Checklist To Work In A Demo
Inventory Theory Questions That Do Not Address Batch Tracking
Several PAA questions in this SERP cover general inventory theory, which sits outside the batch and expiry focus of this guide.
The 80/20 rule highlights which items to count more often, but it cannot identify which batch of chicken expires Thursday. ABC analysis categorises items by value and usage frequency, but it does not produce a FEFO pick list. Inventory turnover ratios show how fast stock moves in aggregate, but they cannot reveal which lot is about to date out. A system that only answers these questions functions as a stock counter rather than a batch and expiry tracking platform.
For a broader treatment of stock control frameworks, see Jelly's guides on stock control software with batch tracking, food inventory tracking software for UK restaurants, and how to automate restaurant inventory with real-time tracking. This article stays narrow on batch, expiry, FEFO and UK compliance.
Frequently Asked Questions
What Does Batch And Expiry Tracking Mean In A Restaurant Inventory System?
Batch and expiry tracking in a restaurant system means recording each delivery as a distinct batch or lot with its own use-by date. The system then rotates stock by the earliest expiry date rather than arrival order, so every ingredient can be traced from supplier to plate and every date-sensitive item is used before it becomes waste. A system that only tracks stock at product level cannot distinguish between two deliveries of the same ingredient with different remaining shelf lives.
What Is The Difference Between FIFO And FEFO In A Restaurant Kitchen?
FIFO, or first in first out, rotates stock by the order it arrived. FEFO, or first expired first out, rotates by the earliest use-by date regardless of arrival order. They only match when every delivery has identical shelf life and condition. FEFO is the safer default for chilled, fresh and prepared foods where use-by dates vary between deliveries.
How Do You Track Use-By Dates Per Batch Rather Than Per Product?
Track use-by dates per batch by capturing the lot number and use-by date at goods-in and holding that date against the batch rather than the product record. The system then enforces FEFO at depletion so the earliest-expiring batch is consumed first. A product-level expiry date applies one date to every unit of a SKU and cannot distinguish between two deliveries of the same ingredient with different remaining shelf life. Per-batch expiry forms the enabling layer underneath FEFO, because without it rotation depends on chance and memory.
What Do UK Food Safety Inspections Expect For Batch And Lot Records?
Under Article 18 of UK General Food Law, records of suppliers and customers must be available to competent authorities on demand. The FSA “one step back, one step forward” system requires supplier, consignor and consignee names and addresses, volume or quantity, a lot, batch or consignment reference, a description of the food, and the date of dispatch. Batch number capture sits as recommended additional data, and an EHO will look for evidence that rotation actually happens, such as clear labels with delivery or made-on dates, a stocktake routine, and a record of any out-of-date items removed. For allergen records, inspectors expect incoming traceability linking allergen-bearing ingredients to supplier identity and product specification.
Is A Cheap Expiry-Checking App Enough?
An expiry-only tool solves the date problem but not the traceability problem. It will alert you to near-expiry stock, but it will not produce forward and backward traceability reports, link allergen-bearing ingredients to supplier specifications, or support multi-site batch tracking. Operators with multiple suppliers, mixed-batch deliveries, allergen-record obligations, or expansion plans to two to five sites need a full batch and traceability platform.
How Long Does Implementation Take?
Implementation time depends on the tier. Expiry-only tools can be live in days. Full batch and traceability platforms typically take longer because they require goods-in discipline, supplier label coordination and POS mapping. Jelly onboards and generates initial value in the first week, with price alerts and spending insights available once suppliers send invoices to a dedicated email address or within 24 hours of photographing invoices into Jelly.
Conclusion: Use The Ten-Point Checklist In Every Demo
Batch and expiry tracking acts as the operational and compliance foundation that separates a system capable of protecting your margins and satisfying an EHO from one that merely counts stock. The ten-point checklist in this guide, covering lot at goods-in, per-batch use-by date, FEFO rotation, supplier-to-plate traceability, configurable alerts, waste logged against the batch, stock counts and purchase orders, POS-driven depletion, multi-site support and exportable audit reports, is the lens to apply to every system before signing.
Use the checklist in every vendor demo. Ask each vendor to show how their system handles a near-expiry alert, a FEFO pick and a traceability report for a recalled lot. Those demonstrations reveal more than any feature list.
Put The Checklist To Work In A Demo
