FEFO (First-Expire, First-Out)

FEFO (First-Expire, First-Out) – Prioritizing Soonest Expiry to Protect Quality and Compliance

This topic is part of the SG Systems Global regulatory & operations glossary.

Updated October 2025 • Shelf-Life Governance & Traceability • WMS, MES, QA/QP

First-Expire, First-Out (FEFO) is an inventory control principle that requires the lots with the nearest expiry or retest date to be issued, picked, or shipped before lots with later dates—provided they remain qualified and suitable for use. FEFO is the life-limited corollary to FIFO and is essential where stability, potency, and label claims degrade or where regulations impose strict shelf-life control. FEFO logic is encoded into Directed Picking, kit build, issue-to-batch, and ship-confirm workflows so the system automatically presents the soonest-to-expire eligible stock and blocks younger, longer-dated alternatives unless an exception is justified and approved through Approval Workflow. FEFO reduces waste, prevents inadvertent use of expired or beyond-retest materials, and simplifies release by stabilizing inputs and making expiry logic visible and auditable at the point of action.

“If shelf life matters, the system—not the operator—must decide which lot is next. FEFO transforms expiry control from a policy in an SOP to a control embedded in every scan.”

Unlike FIFO, FEFO sorts the eligible candidate set by expiry/retest first and then uses receipt chronology as a secondary tie-breaker. Candidate eligibility checks include item match, released status after Component Release, environmental/condition compatibility, reservations, and exclusion for holds (e.g., stability outliers, EM excursions). When executed faithfully, FEFO aligns day-to-day picks with the rules defined in the specification and master data governed by Document Control and referenced by eMMR and eBMR steps.

TL;DR: FEFO means you must consume or ship the soonest-to-expire suitable lot first. Suitability = correct item + released status + within expiry/retest + right condition + attribute compatibility. Enforce FEFO in WMS/MES with Directed Picking, expiry-aware queues, scan interlocks, and tie-break by FIFO when expiry dates match. Prove FEFO decisions via audit trails, genealogy, and shipping events (e.g., EPCIS).

1) What It Is

FEFO governs the sequence of consumption based on time to expiry or retest. This sequence is calculated from authoritative data in the material specification and item master—fields such as shelf life, expiry basis (manufacture vs. receipt), retest period, and storage conditions—and from the lot’s specific manufacture/receipt timestamps and any post-qualification retest or extension decisions. The WMS maintains, for each item/site, a priority queue of eligible lots ordered by expiry/retest date; Directed Picking tasks, issue-to-batch actions, and shipping waves consume from the top. If multiple lots share the same expiry, FIFO is applied as a tie-breaker. FEFO is especially critical for APIs, reagents, perishable ingredients, sterile barrier materials, temperature-sensitive packaging, and finished goods with labeled expiry; it also applies to labels and inserts where printed expiry or artwork versions must stay synchronized with product claims governed through Document Control.

2) Why FEFO Matters in Regulated Supply Chains

FEFO protects patient and consumer safety by minimizing the chance that inventory passes its usable life while still in storage or during long logistics chains. It reduces write-offs and out-of-stock events by smoothing consumption and exposes early warning indicators—e.g., a spike in “blocked due to expiry proximity” events—that feed into CPV and APR/PQR. In food and dietary supplement environments governed by the Food Safety Plan (FSP), FEFO ensures preventive controls remain effective through the product’s intended shelf life and supports Expiration & Shelf-Life Control. In pharmaceuticals and biologics, FEFO ties directly to labeled claims and CoA acceptance limits, while for devices FEFO on sterile barrier materials mitigates barrier degradation risk captured later in the DHR. Because release decisions must reference actual lots and their validity at the time of use, FEFO also streamlines QA review by reducing exceptional rationales and by aligning practice with Data Integrity expectations.

3) Core Elements of a FEFO Program

Master data & specifications. Define shelf life, expiry basis, retest window, storage class, and attribute compatibility (e.g., allergen, potency band, language/UDI variant) under Document Control. Expiry-aware location strategy. Use Bin / Location Management to reduce intermix, keep near-expiry stock at pick faces, and segregate conditions (ambient/chilled/frozen). Directed Picking & interlocks. Generate tasks from the FEFO queue and block out-of-order scans with clear prompts; require positive scans of item/lot and, where relevant, expiry/retest date with Barcode Validation. Reservations & Dynamic Lot Allocation. Let Dynamic Lot Allocation filter by attributes and status, then apply FEFO inside the compatible subset. Exception handling. Where operations require a younger lot (e.g., campaign planning, customer-specific shelf-life-on-delivery), capture reason codes and route for approval; if risk is material, open a Deviation/NC with photos and evidence.

4) FEFO vs. FIFO and Special Cases

For life-limited items, FEFO is the primary rule; FIFO is the secondary tie-breaker. For items without expiry/retest constraints (e.g., durable spares), use FIFO. For returned goods and reworked lots, FEFO applies only after suitability is restored through Change Control and, when systemic, CAPA. For labels and packaging with printed expiry or variable data, FEFO avoids mixing short-dated components into long-dated product; superseded artwork should be hard-blocked and scrapped under Document Control. For finished goods, FEFO interacts with customer promises (e.g., minimum remaining shelf life at receipt); these constraints narrow the candidate set before FEFO is applied, with decisions documented for Finished Goods Release.

5) Data Integrity & Evidence

Electronic FEFO requires 21 CFR Part 11/Annex 11 controls: unique users, role-based access, e-signatures with meaning, secure audit trails for put-away, moves, retest decisions, and picks, and validated time synchronization. The system must store the FEFO decision context: the candidate list at the time of pick (lot IDs, expiry/retest, status), the selected lot, scans captured, any blocked attempts to pick longer-dated lots, and the reason/approval for exceptions. Cycle counting should verify both quantities and age profile at pick faces; discrepancies in age distribution indicate process drift. For shipment, event history (SSCC, EPCIS) links FEFO selections to customers and lanes for rapid recall scoping.

6) Common Failure Modes & How to Avoid Them

  • Visual or convenience picking. Operators grab accessible pallets, ignoring expiry. Fix: enforce directed tasks, require scans, and block non-FEFO picks without authorized exception.
  • Retest dates not synchronized. QMS retest decisions don’t update WMS. Fix: integrate Component Release/LIMS with WMS; block issue until handshake completes.
  • Condition segregation gaps. Mixed ambient/chilled stock confuses FEFO queue. Fix: strict location zoning and temperature mapping.
  • Reservation starvation. Customer promises reserve long-dated lots indefinitely, aging the rest. Fix: review reservations, set expiry-based release rules, and allow attribute splits.
  • Label/version mismatch. Short-dated labels applied to long-dated product. Fix: treat labels as controlled components; align FEFO across packaging BOMs under Document Control.
  • Data capture gaps. Missing expiry fields or manual entry errors. Fix: barcode expiry capture where encoded; device validation and field constraints; periodic data quality checks.
  • Policy vs. system divergence. SOP says FEFO; system doesn’t. Fix: reconcile configuration with SOPs; validate and train against realistic edge cases.

7) Metrics That Prove FEFO Is Working

Track FEFO adherence (percent of picks that consumed the soonest-to-expire eligible lot); blocked non-FEFO attempts; average remaining shelf life at issue/ship; write-offs due to expiry; near-expiry exposure (inventory within X days); reservation aging; and mock-recall time-to-trace. Segment by item class, storage condition, and warehouse zone; feed signals into APR/PQR and CPV for management review.

8) How This Fits with V5

V5 by SG Systems Global operationalizes FEFO at the scan, pick, and ship steps. In V5 WMS, expiry-aware Directed Picking surfaces the soonest-to-expire eligible lot; scans of longer-dated lots are blocked with clear prompts and, where justified, routed for approval via Approval Workflow. Dynamic Lot Allocation respects attribute filters (allergen, potency, language/UDI) and applies FEFO within the subset; Bin / Location logic and task interleaving keep near-expiry stock in front-of-house locations. In V5 MES, eBMR steps enforce FEFO at issue-to-batch, require expiry-aware barcode scans, and block progression when validity windows are exceeded. QA sees FEFO adherence and exceptions while performing Batch/Finished Goods Release; shipping captures SSCC/EPCIS events that preserve expiry context downstream. All evidence is retained under Data Integrity and Part 11 controls for rapid inspection retrieval.

9) FAQ

Q1. When should FEFO take precedence over FIFO?
For any item with expiry or retest control, FEFO is the primary rule. FIFO is used only as a tie-breaker when expiry dates are identical or not applicable.

Q2. Can we override FEFO to meet customer shelf-life promises?
Yes, but only through documented reservations and exceptions that constrain the candidate set and record approvals. Repeated patterns indicate planning or slotting issues to address via Change Control or CAPA.

Q3. How do retest and extension decisions affect FEFO?
Retest extends the validity window per specification; FEFO must consume the updated date immediately after QMS approval. Integrate LIMS/QMS with WMS to prevent stale dates.

Q4. What evidence demonstrates FEFO in an audit?
The FEFO candidate list and selected lot at time of pick, scan logs including expiry, blocked attempts, exception approvals, and reconciliation to genealogy and SSCC/EPCIS shipping events.

Q5. How should FEFO be validated?
In WMS/MES PQ using scenarios that attempt non-FEFO picks, exercise retest updates, stress deep-lane rotations, and test customer minimum-shelf-life constraints, capturing audit-trail and role segregation behavior.


Related Reading
• Shelf Life & Release: Expiration & Shelf-Life Control | Finished Goods Release | CoA
• Warehouse & Picking: Directed Picking | Dynamic Lot Allocation | Bin / Location Management | Barcode Validation
• Traceability & Governance: Batch Genealogy | EPCIS | FIFO | Data Integrity | 21 CFR Part 11