If you manage inventory with expiry dates—food, beverages, pharmaceuticals, cosmetics, or chemicals—you know the pain of expiry management. One expired product shipped to a customer can mean returns, complaints, and reputation damage. One pallet of expired inventory discovered too late is pure margin loss.
FEFO (First Expiry First Out) warehouse management is the solution, but implementing it properly requires the right systems and processes. This guide covers everything you need to know.
What Is FEFO and Why Does It Matter?
FEFO (First Expiry First Out) is an inventory rotation method that ensures products with the soonest expiry dates are picked and shipped first. Unlike FIFO (First In First Out), which focuses on receipt date, FEFO focuses on expiry date.
Why FEFO beats FIFO for perishables:
- Receipt date ≠ expiry date – A product received today might expire before something received last week
- Supplier variability – Different suppliers ship different shelf life remaining
- Customer requirements – Many retailers require minimum days of shelf life remaining
Whether FEFO is required depends on the product, jurisdiction, customer contract, and quality program. In Canada, certain food businesses have traceability obligations under the Safe Food for Canadians Regulations, while drug-product records must support lot or batch traceability. Those obligations do not make a WMS, or a FEFO configuration, a certification by itself.
The True Cost of Poor Expiry Management
Measure the cost of poor expiry management from your own operating data rather than relying on a generic industry percentage.
Direct cost categories:
- Expired-product write-offs and disposal
- Rework, returns, credits, and customer chargebacks
- Labour used to investigate lots or manually correct records
Indirect cost categories:
- Service failures caused by allocating stock that cannot meet remaining-shelf-life rules
- Audit remediation when traceability records are incomplete
- Lost capacity when quarantined or unidentified stock occupies usable locations
Build a baseline from write-offs, near-expiry holds, return reasons, and investigation time. Then compare the same measures after introducing FEFO warehouse management. The financial case depends on that measured baseline and should not be presented as a guaranteed payback.
Implementing FEFO in Your Warehouse
Step 1: Capture the identifiers required by your traceability program For in-scope products, configure receiving to record the product identifier, lot or batch, expiry or best-before date, and any supplier or shipment references your rules require. Validate the format and handle duplicates according to the source system and business policy.
Step 2: Configure FEFO picking rules Set your WMS to direct pickers to the earliest expiry first. The system should override location efficiency when necessary to ensure proper rotation.
Step 3: Set expiry alert thresholds Choose thresholds from product shelf life, customer requirements, inspection time, and disposition lead time. A long-life product and a short-life product should not inherit the same arbitrary warning window.
Step 4: Establish near-expiry procedures
- Discount and sell through
- Donate to food banks
- Return to supplier
- Destroy and write off
Step 5: Apply status controls Configure quarantine, allocation, and picking blocks to match the applicable quality and disposition policy. Test both the normal FEFO path and authorized exceptions before launch.
FEFO Reporting and Compliance
Proper FEFO implementation requires robust reporting:
Daily operations:
- Inventory by expiry date range (0-30, 31-60, 61-90, 90+ days)
- At-risk SKUs approaching expiry threshold
- Lots requiring attention today
Audit readiness:
- Full lot traceability—forward and backward trace
- Pick history showing FEFO compliance
- Adjustment records with reasons
Management visibility:
- Expiry write-off trends over time
- Days of inventory by product
- Near-miss reports (products shipped close to expiry)
The reporting design should make the required traceability and operating records reproducible. A software report can support an audit trail, but it does not by itself establish regulatory or certification compliance.
Combining FEFO with Cycle Counting
FEFO and cycle counting work together. When counting inventory with expiry dates:
- Verify expiry dates – Ensure system matches physical product
- Flag rotation issues – Note when old product is behind newer product
- Identify at-risk locations – Areas with repeated expiry issues need process review
Many warehouses combine FEFO audits with their cycle counting program, checking a sample of expiry dates during each count.
Technology Requirements for FEFO
To run FEFO effectively, your WMS needs:
Must-haves:
- Lot and expiry tracking at receiving
- FEFO-directed picking
- Expiry date validation
- Automatic expiry alerts
- Expired product blocking
Nice-to-haves:
- Customer-specific shelf life requirements
- Supplier shelf life tracking
- Integration with quality management systems
- Mobile expiry date scanning
Use this list to evaluate WarePulse FEFO WMS against your receiving data, allocation rules, integrations, exception policy, and regulatory scope. Confirm each required workflow in a trial or implementation review before treating it as production-ready.
Conclusion
FEFO is a useful control for many warehouses handling perishable or expiry-dated products, but the exact policy must come from the product, customer, quality, and regulatory requirements that apply to the operation.
Start with reliable lot and expiry capture, then test picking, alerts, status controls, exceptions, and reporting. Track write-offs, holds, service failures, and investigation time against the pre-implementation baseline to determine the actual result.
Ready to implement FEFO? Explore WarePulse for expiry management or review pricing to plan the next step.