How To Implement FEFO In A Restaurant: A Complete Guide

Written by: JJ Tan, Founder, Jelly

Key Takeaways

• FEFO overrides FIFO whenever a newer delivery carries an earlier expiry date, so the use-by or best-before date becomes the picking priority.
• Implement FEFO as a seven-step routine that moves from goods-in checks to software adoption, with a named owner for every check along the way.
• Assign named roles for each shift check, such as goods-in checker, shift lead, sous-chef and operations manager, so FEFO runs as a repeatable routine instead of a memory-based task.
• Track expiry waste in £ value and use delivery records to challenge suppliers on short-dated stock that erodes gross profit.
• Jelly scans supplier invoices to capture line-item prices and dates automatically, tracks batches and expiry against live dish costs, and flags price and margin changes in real time without the manual register a spreadsheet or generic ERP requires.

Book a demo with Jelly

FEFO Vs FIFO In Restaurants: Choosing The Right Rotation Method

FIFO, or first in, first out, is the baseline rotation method for any kitchen. Staff use older stock before newer stock of the same product. FEFO applies wherever a use-by or best-before date governs the product and overrides arrival order when a newer delivery carries a shorter date.

FIFO alone fails the moment a supplier delivers stock that expires before what is already on the shelf. A kitchen running pure FIFO would pick the older delivery first and serve food that expires sooner than the batch behind it. FEFO corrects this by making the expiry date the picking priority instead of the arrival date.

The following table illustrates the conflict rule with a chicken-batch example:

Batch B arrived three days later but expires two days sooner. Under FEFO, Batch B is picked first. FIFO would have picked Batch A and left Batch B to expire unused.

LIFO is an accounting valuation method used to calculate the cost of goods sold on a balance sheet. It has no application to how a kitchen shelves a walk-in or picks from a fridge. The rotation methods relevant to foodservice are FIFO as the baseline and FEFO wherever use-by or best-before dates govern.

See how Jelly handles batch and expiry tracking

How To Implement FEFO In A Restaurant: The Seven-Step Sequence

1. Check, record and reject at goods-in before anything enters storage.
2. Label every opened or decanted item immediately with product name, prep date and use-by date.
3. Arrange shelves by expiry date every time stock is put away.
4. Run named daily checks at goods-in, pre-service and close-down.
5. Apply the conflict rule: when a new delivery expires before existing stock, pick the new delivery first.
6. Log expiry waste, audit FEFO compliance and feed findings back into ordering.
7. Move to batch-and-expiry software when paper stops scaling.

Step 1: Goods-In Checks, Records And Rejections

Every delivery requires five checks before anything is accepted: product identity, quantity, temperature, date marking and batch separation. FSA “Managing food safety” guidance requires food businesses to verify on delivery that chilled and frozen food is cold enough, that packaging is undamaged and that the delivery matches the order. Reject anything above the supplier’s maximum temperature or past its use-by date.

Rejection criteria that competitors’ content omits:

• Missing or unreadable date codes
• Broken or compromised seals
• Signs of thawing in frozen goods
• Condensation on chilled items
• Items not matching the order
• Short-dated stock with insufficient remaining shelf life for the production plan

For accepted items, Food-Safety.app’s UK delivery guide recommends recording time, item, batch, temperature and storage location. For rejected items, record the reason, quantity and supplier action taken. These records double as EHO evidence and supplier accountability documentation. See also the step-by-step guide to restaurant inventory inflow control for a fuller goods-in workflow.

Step 2: FEFO Labelling And Date Coding

Every label must answer three questions at a glance: what the food is, when it was made and when it must be used or discarded. Food-safety guidance for UK catering businesses recommends applying labels the moment food is packed away, checking labels at shift change and removing anything that cannot be clearly identified.

Relabel immediately on decanting, because the original packaging’s date no longer travels with the food once it is transferred. That is also why old labels must come off before a container is reused, since two dates on one tub invite the wrong one being read. Facing labels outward is the final piece, because a date nobody can see without moving three tubs is a date nobody checks.

Composite items carry the earliest ingredient date. A sauce made with a stock prepared two days earlier carries the stock’s date instead of the day the sauce was assembled.

Colour coding, where the standard day-of-week system uses Monday blue, Tuesday yellow, Wednesday red, Thursday brown, Friday green, Saturday orange and Sunday black, speeds up visual checks during service. MESS Brands’ September 2026 comparison concludes that written dated labels are stronger on food safety and waste reduction. Colour coding works best as a supplement for speed and sorting. Most kitchens end up running both, so the colour key must be documented and visible to all staff rather than held in one supervisor’s memory.

Step 3: Shelf Layout By Expiry Date

Front-load the earliest expiry dates. Push newer stock behind existing stock even if it arrived today. This applies every time stock is put away, not only during a weekly tidy.

Separate raw from ready-to-eat per UK food safety rules. New Age Industrial’s August 2026 foodservice storage guide recommends placing ready-to-eat and cooked foods in protected upper zones and raw poultry in the lowest designated raw-food zone. Keep older inventory visible and accessible. A cooler packed too tightly cannot be inspected or rotated, and blocked air paths create uneven temperatures.

Step 4: The Daily Routine With Named Accountability

FEFO fails when it relies on memory. Build checks into existing shift structures with named roles:

• Goods-in checker, on delivery: temperature, date, batch and rejection decisions
• Shift lead, before service: near-expiry review across all chilled and frozen storage
• Sous-chef, end of day: close-down check, label verification, quarantine of anything unlabelled
• Operations manager, weekly: management review of waste logs, compliance rate and supplier date-marking patterns

Set a clear escalation step so staff who find a missing or unreadable label know who to tell and what to do next. The usual action is isolating the food until it can be verified or disposing of it if it cannot. Environmental Health Officers assessing date marking look for evidence that dates are set on a documented basis, applied consistently and recorded over time.

Step 5: Handling Deliveries That Expire Before Existing Stock

The conflict rule is absolute: expiry date beats arrival date, always.

Returning to the chicken-batch example, Batch A is received 12 Oct with use-by 18 Oct and Batch B is received 15 Oct with use-by 16 Oct. Batch B is picked first regardless of arrival order. Quarantine Batch B at the front of the shelf, use it first and challenge the supplier on the short-dating in writing. Record the delivery, the date discrepancy and the action taken. Short-dated deliveries that are signed for unchallenged erode GP and create a pattern that is invisible without delivery records.

Step 6: Auditing FEFO And Proving It Works

Log expiry waste by item, quantity and value each week. Connect waste to GP leakage: every avoidable kilo of food waste is paid for three times, as an ingredient bought, as paid labour to prep it and again as a disposal cost. WRAP estimates the UK hospitality and food service sector throws away 1.1 million tonnes of food every year, 75% of which could have been eaten, costing £3.2 billion.

Use delivery records to challenge supplier date-marking. A pattern of short-dated deliveries from one supplier becomes a negotiation point for pricing or credits. Feed waste findings back into par levels and ordering to reduce over-purchasing of perishables.

Step 7: When Paper FEFO Stops Scaling

Paper FEFO works at a single site with stable batch volumes and reliable supplier date-marking. It stops scaling when:

• Batch volume grows beyond what a manual register can reliably capture
• Operations expand to two or more sites with no central source of truth
• Supplier short-dating becomes frequent enough to require systematic tracking
• Management needs batch-level expiry alerts and invoice-driven cost data without waiting for a weekly admin session

At that threshold, batch-and-expiry software that captures dates from supplier invoices automatically becomes necessary.

Move your expiry tracking off paper

UK Food Safety Requirements: What FEFO Records Must Show

Every check in the seven steps produces a record, and those records are what an EHO will ask to see. FSA “Managing food safety” guidance requires traceability records to be kept up to date and available for inspection at all times. Records must cover supplier name and address, type and quantity of products, and dates of transaction and delivery. Batch numbers and invoice references are additionally recommended and will often already appear on the invoice.

The distinction between use-by and best-before is a legal one. FSA guidance requires the use-by date to be checked on arrival and any food whose use-by date has expired to be rejected. Use-by is a safety date, so food must not be served after it even if it looks and smells fine. Best-before is a quality date, so food past its best-before date is not automatically unsafe but must still be assessed. Applying a best-before date to a product that requires a use-by understates a safety risk.

The FSA’s “Safer Food, Better Business for caterers” pack is a HACCP-based food safety management system for small catering businesses such as restaurants, cafés and takeaways. It helps them demonstrate compliance with food hygiene laws. The law does not require SFBB specifically, though, and other HACCP-based systems are equally valid. FEFO records, including temperature logs, date-marking records, delivery checks and corrective actions, feed directly into the management of food safety assessment that an EHO conducts at inspection. FSA listeriosis guidance states that deliveries of chilled ready-to-eat food should be placed in refrigerated storage promptly and recommends businesses maintain robust HACCP systems with documented validation of Listeria risk management in ready-to-eat foods.

Software: The Batch-And-Expiry Layer For Restaurant FEFO

Once paper stops scaling, the software you choose needs to do three things: capture dates from supplier invoices without manual entry, track batches against live dish costs and surface expiry waste as a GP figure. Jelly is built around those three requirements, which is why it is the primary recommendation for UK kitchen operators implementing FEFO.

Jelly scans supplier invoices line by line to capture product, quantity, price and date data automatically, so no manual register is required. Batches and expiry are tracked against live dish costs, so expiry waste is visible as a GP figure instead of just a bin weight. Jelly integrates with POS systems including Square, EPOS Now, Toast and Lightspeed, and with Xero for accounting. Onboarding generates initial value in the first week. The cost is a flat £129 per month per location with no per-user variable charge. Operators using Jelly cut food costs by 3% on average in the first three months and increase gross margins by an average of 2 percentage points in the first three months. For a broader comparison of batch and expiry tracking options, see the best restaurant batch and expiry tracking software guide for UK operators.

Odoo Inventory is a general ERP whose inventory module is not built around restaurant invoices, recipes or POS sales. Its expiry model is lot-centric and configuration-heavy. Products must be set to “By Lots”. The Lots and Serial Numbers and Expiration Dates features must be enabled separately. FEFO must then be set as a Force Removal Strategy on the storage location or product category. Staff must enter the supplier’s lot number and the expiry date printed on the case on each receipt line before validating, because Odoo otherwise defaults a new lot’s expiry to the receipt date plus configured shelf-life days, which overstates the shelf life of goods that have already spent time in transit. Alerts are passive and assigned to a named “Responsible” user. The documentation describes expiry only in purchase-to-sale and manufacturing flows, with no kitchen workflows such as line checks, goods-in rejection criteria or waste-cost tracking. A July 2026 review found that getting Odoo working well usually requires in-house technical skills or an implementation partner, and advanced features are gated behind other Odoo apps or paid plans. For a UK kitchen operator who needs batch-and-expiry tracking integrated with invoices, recipes and live GP, Odoo requires significant configuration before it delivers what Jelly provides on day one.

MarketMan and Nory are positioned as all-in-one platforms with broader feature sets, but both carry complexity and long onboarding periods that make them harder to deploy quickly across growing sites. Kitchen Cut is an older, more static system typically priced for large chains with dedicated office teams, and it lacks the real-time invoice-driven updates that a multi-site operator needs to act on supplier short-dating the same week it happens.

Common Mistakes And Troubleshooting

Even kitchens that adopt FEFO tend to trip on the same handful of failures. These are the ones that show up most often in audits:

• Decanted items placed in storage without a secondary label, so the original date is lost because relabelling was treated as optional
• No named owner for each check, so the routine depends on whoever happens to be available
• Near-expiry stock pushed to the back of the walk-in during restocking, hiding it from the pre-service review
• Short-dated deliveries signed for without challenge, with no record to support a supplier credit claim

For a broader set of inventory management controls, see inventory management best practices for F&B venues.

How To Measure Success

Use these directional indicators to track whether FEFO implementation is working:

• Expiry waste value per week: track in £ rather than kg so it connects directly to GP
• Stock accuracy: variance between counted and expected stock at each audit
• FEFO compliance rate at audit: percentage of storage locations where earliest-expiry stock is front-loaded and labelled correctly
• Admin time saved: Jelly saves 10–20 hours of admin per month by automating the flow from invoice capture to dish costing
• GP movement: use GP movement as the headline metric and track against the 2-point margin gain and 3% food cost reduction cited above

Frequently Asked Questions

Do Restaurants Use FIFO Or LIFO?

Restaurants use FIFO, or first in, first out, as the baseline rotation method for kitchen storage. LIFO is an accounting method, not a kitchen rotation rule, and as covered above it has no place on a walk-in shelf. Where products carry use-by or best-before dates, FEFO overrides FIFO by making the expiry date the picking priority instead of the arrival date.

What Inventory Procedure Is Commonly Used In Foodservice To Ensure Proper Rotation?

FIFO is the standard baseline procedure in foodservice, so older stock is used before newer stock of the same product. FEFO is applied wherever a use-by or best-before date governs the product and takes precedence over arrival order when a newer delivery carries a shorter date. In practice, most UK commercial kitchens run FIFO as the default and apply FEFO to all perishables with a printed date, which covers the majority of chilled and fresh stock.

Why Is FIFO Important In Food Storage?

FIFO keeps older stock moving while it is still safe and within date, which reduces the risk of products expiring unused at the back of a shelf. It also creates a predictable rotation pattern that staff can follow consistently without needing to check every individual date on every pick. FIFO does not authorise the use of expired food, so a product that has passed its use-by date must be discarded regardless of when it was delivered or where it sits on the shelf. FEFO addresses the gap FIFO leaves when a newer delivery expires sooner than existing stock.

Who Is Responsible For FEFO Checks Each Shift?

Responsibility should be assigned by role and time of day instead of being left to whoever is available. The goods-in checker is responsible at the point of delivery for temperature, date, batch and rejection decisions. The shift lead is responsible for the pre-service near-expiry review across all chilled and frozen storage. The sous-chef is responsible for the close-down check, label verification and quarantine of anything unlabelled. The operations manager conducts the weekly management review of waste logs, compliance rates and supplier date-marking patterns. Named accountability is what converts FEFO from a policy into a repeatable daily routine.

How Often Should FEFO Be Audited?

Daily checks built into shift routines at goods-in, pre-service and close-down provide the operational layer. A weekly management review covers waste value, stock accuracy and FEFO compliance rate across storage locations. At the point of an EHO inspection, the auditor will look for evidence that checks are happening consistently over time instead of only on the day of the visit. Records of temperature logs, date-marking checks and corrective actions taken are the evidence base. For multi-site operators, a central audit view across locations becomes necessary once paper records stop providing that visibility.

When Should You Move From Paper FEFO To Inventory Software?

Paper FEFO is adequate for a single site with stable batch volumes and reliable supplier date-marking. The threshold for moving to software is reached when batch volume grows beyond what a manual register can reliably capture, when operations expand to two or more sites without a central source of truth, when supplier short-dating becomes frequent enough to require systematic tracking or when management needs batch-level expiry alerts and invoice-driven cost data without a weekly admin session. At that point, a system that captures dates from supplier invoices automatically removes the dependency on team discipline that paper FEFO cannot survive at scale.

Conclusion: FEFO As A Daily Routine Backed By Records

The seven steps work as a system that removes dependencies on memory, from the goods-in check through to the software handover. Each step creates records that show what arrived, how it was labelled, where it was stored and when it was used or discarded.

Jelly is the best restaurant inventory software for implementing FEFO in a UK kitchen because it scans supplier invoices to capture line-item prices and dates automatically, tracks batches and expiry against live dish costs and flags price and margin changes in real time without the manual register a spreadsheet or a generic ERP like Odoo requires.

FEFO only works as a repeatable daily routine backed by records. Those records protect customers, satisfy EHOs and recover GP that would otherwise leave the business in the bin.

Put FEFO on autopilot with Jelly