Mon – Sat: 9:00 AM – 7:00 PM IST
Warehouse

FIFO vs FEFO in inventory

Picking oldest-first versus expiring-first — and why getting this wrong writes off stock.

In short

FIFO picks the oldest stock first, by receipt date. FEFO picks the stock that expires soonest, by expiry date. They are usually the same thing, and occasionally they are not — a later receipt with a shorter remaining shelf life must go first. For anything with an expiry date, FEFO is the correct rule and FIFO is a near-miss that eventually causes a write-off.

Why It Matters

Why this matters in practice

The distinction looks academic until a consignment is received with a short remaining shelf life, which happens routinely with pharmaceuticals, food and chemicals. Under FIFO that consignment sits behind older-but-longer-dated stock and expires on the shelf. The write-off is then attributed to over-ordering rather than to the picking rule that caused it.

FEFO prevents write-off where receipt order and expiry order differ
FIFO is adequate where nothing expires
Both need enforcement at pick, not policy on paper
Lot or batch tracking is a prerequisite for FEFO
How It Works

How it works in practice

1

Capture expiry at receipt

FEFO is impossible without an expiry date recorded against the lot at goods receipt. This is the prerequisite step.

2

Set the picking rule

The WMS allocates stock by rule. FEFO sorts available lots by expiry ascending rather than by receipt date.

3

Enforce at the scan

The picker is directed to a specific lot and location. Allowing a different lot to be scanned without reason defeats the rule.

4

Handle exceptions deliberately

Customer-specified minimum shelf life sometimes overrides FEFO. That is a configured exception, not an override by judgement.

5

Report on ageing

A shelf-life report showing stock approaching expiry turns a future write-off into a current commercial decision.

Worked example

A worked example: when FIFO issues the wrong batch

A warehouse holds two batches of the same product. Batch A was received in March and expires in September. Batch B was received in May and expires in July — it came from a supplier whose production run was older, which is entirely normal with seasonal or multi-sourced goods.

Under FIFO, the system issues batch A first because it arrived first. Batch B sits, and in July it expires on the shelf. The stock was rotated correctly by the rule that was configured and wrongly by the rule that mattered. The loss is not an operational failure; it is the predictable consequence of using a receipt-date rule on expiry-dated goods.

Under FEFO, batch B goes first and both batches sell. The distinction matters whenever receipt order and expiry order can diverge — multiple suppliers, variable production dates, returns coming back into stock with life already consumed. For anything with an expiry date, FIFO is an approximation that works until it does not, and the occasions when it fails are exactly the ones that cost money.

Key terms

The vocabulary, briefly

Term What it means
FIFO First in, first out — issue the oldest receipt first. A valuation and rotation convention.
FEFO First expired, first out — issue the earliest expiry first, regardless of when it arrived.
Shelf life Total life from manufacture to expiry. Remaining shelf life is what customers actually care about.
Minimum remaining life A customer requirement that goods arrive with at least a stated proportion of life left.
Quarantine A hold state preventing issue pending inspection or release.
What Goes Wrong

Common mistakes worth avoiding

Running FEFO without expiry capture

The rule cannot work if the date was never recorded. Receipt discipline comes first.

Allowing free lot selection

If pickers can take any lot, the rule is advisory. The system has to direct and the scan has to verify.

Ignoring minimum shelf life on despatch

Many customers specify a minimum remaining life. Shipping short-dated stock produces a return, not a sale.

No ageing visibility

Without a report, approaching expiry is discovered at write-off rather than while it can still be sold.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Expired write-off value The direct cost of getting rotation wrong. Should trend to near zero on managed goods.
Average remaining shelf life at dispatch Whether customers are receiving goods with enough life left.
Batches issued out of expiry order Rotation discipline. Any override should carry a reason.
Stock within expiry threshold Forward visibility, so near-expiry goods can be moved while they still have value.
FAQ

Questions we are asked about this

For pharmaceuticals and food, expiry control and traceability are generally required, and FEFO is the practical way to satisfy them. Confirm the specific requirement for your sector.
No. Expiry belongs to a lot or batch, so the lot has to be tracked through receipt, storage and pick for the rule to have anything to sort by.
Yes, and it is a common and correct arrangement. Physical rotation and cost flow assumption are separate decisions: FEFO governs which batch leaves the building, while the valuation method governs what cost is attached to the issue. Most ERP systems configure these independently for exactly this reason, and conflating them is a frequent source of confusion during implementation.
FIFO is the sensible default, since receipt order is the only meaningful order available. It is worth asking whether the goods genuinely have no deterioration mechanism, though — electronics with batteries, adhesives, rubber components and calibrated instruments all age even without a printed date. Where that is true, a review-by date behaves like an expiry date and should be managed as one.
Make it a rule in allocation rather than a check at dispatch. If a customer requires, say, seventy-five percent of shelf life remaining, the system should refuse to allocate batches below that threshold to that customer, so the problem surfaces at order entry when there is still time to source. Catching it at dispatch means a rejected delivery and a return, which is the same stock problem plus freight.
Decide the policy before you need it, because decisions made under time pressure tend to be worse. Common approaches are discounting into channels that will consume quickly, allocating preferentially to customers with shorter supply chains, returning to supplier where the agreement allows, or writing off early to avoid handling cost on goods that will not sell. What matters most is visibility — a near-expiry report nobody reads produces the same outcome as no report.
Related

Where to read next

What is a WMS?

Read more

What is cycle counting?

Read more

ERP with warehouse management

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.