On this page
FIFO — first in, first out — is the default inventory rotation method for good reason: for most products, the unit that arrived first is also the unit closest to becoming obsolete, damaged in storage, or simply less current. But that assumption quietly breaks down for perishables, where the thing that actually determines whether a unit is sellable isn't when it arrived, it's when it expires. And receipt order and expiry order don't always match.
FIFO Assumes Receipt Order Predicts Spoilage — That's Not Always True
FIFO rotation assumes the oldest stock by receipt date is always the stock closest to needing to move. For non-perishable goods, that's usually a safe assumption. For perishables, it breaks down whenever a later-arriving batch has an earlier expiry date than a batch already on the shelf — which happens more often than most retailers assume. A supplier's production run date, not their delivery date to you, determines shelf life, and different batches from the same supplier can have meaningfully different production dates even when they arrive close together.
The result, under strict FIFO, is that staff rotate stock by when it arrived rather than by which batch is actually closer to expiring — and a shorter-dated batch that arrived more recently can sit behind an older-arriving, longer-dated batch until it expires unsold.
What FEFO Actually Does Differently
FEFO — first expired, first out — rotates stock strictly by expiry date, independent of when each batch was received. The oldest-dated batch by expiry, not by arrival, is always the one sold or pulled first. This requires one thing FIFO doesn't strictly need: an expiry date captured and tracked at the batch level, for every batch, from the moment it's received.
This is a meaningful operational shift, not just a labeling change. It means receiving has to capture expiry data as part of the intake process, inventory has to track stock at the batch level rather than treating all units of a SKU as interchangeable, and picking or restocking decisions have to reference expiry date rather than shelf position or arrival sequence.
Why Manual FEFO Fails at Scale
In a small operation with a handful of perishable SKUs, FEFO can be managed by staff visually checking dates and rotating stock by hand. That approach does not survive contact with a real product catalog — hundreds of perishable SKUs, multiple batches of each in stock simultaneously, and staff turnover that means the person restocking the shelf today wasn't trained by the person who did it last month.
The failure mode is predictable: staff restock from the back of the shelf out of habit rather than checking every date, a shorter-dated batch gets pushed behind a longer-dated one, and the result is either product sold past its safe date or, more commonly, product pulled and written off well before it needed to be, because nobody trusted the rotation enough to sell it right up to the date.
Enforcing FEFO at the Point of Sale
Reliable FEFO requires the system, not staff memory, to enforce rotation. That means the inventory platform needs to capture an expiry date against every batch at receiving, and connect that data through to both the warehouse floor and the point of sale.
At the operational level, this looks like automatic pick suggestions that direct staff to the shortest-dated eligible batch first, proactive alerts as batches approach their expiry threshold so markdown or transfer decisions can happen before the product is a total loss, and — critically — a hard block at the point of sale that prevents an expired batch from being sold at all, regardless of whether a staff member noticed the date.
- Expiry date captured at the batch level during receiving, not estimated later
- Automatic pick/restock suggestions ranked by nearest expiry, not arrival order
- Proactive alerts as batches approach expiry, ahead of the deadline
- Point-of-sale block on selling any batch past its recorded expiry date
The Compliance Angle: Why This Isn't Just an Efficiency Question
For food and beverage retailers, selling expired product isn't just a customer experience failure — it's a food safety and regulatory liability. Health inspections and audits increasingly expect a documented, batch-level rotation process, not a verbal assurance that staff 'check the dates.' A system-enforced FEFO process with a recorded audit trail — which batch was sold when, and confirmation that no sale occurred against an expired batch — is the difference between a defensible compliance position and a liability exposure that surfaces during an inspection or, worse, after a customer complaint.
FIFO remains the right default for most retail inventory. But for food, beverage, and any other perishable category, expiry date — not receipt date — is the variable that actually determines whether a unit is sellable, safe, and worth the shelf space it occupies. FEFO gets that right, but only if it's enforced by the system rather than left to staff memory, because the failure mode of manual FEFO isn't dramatic, it's just a slow accumulation of markdowns, write-offs, and near-misses that a batch-aware system would have caught automatically.
Batch-Level Precision for Every Perishable SKU
Momentum records expiry dates at the batch level from receiving through sale, can draw stock from the batch that expires first (FEFO), and writes expired stock off overnight so it no longer counts as sellable. Batch Expiry and Expired Batches reports show what is coming up at every location. Book a demo to see FEFO run by the system, not left to someone checking labels.
