A typical grocery store loses 2 to 4% of inventory to spoilage. FEFO cuts that in half. Here is the full guide — what First-Expired-First-Out actually means, why FIFO is the wrong default, and how batch-level tracking turns a write-off into a discount promotion.

If you sell yogurt, energy bars, sandwiches, sushi, salad kits, or any product with an expiry date, you have a problem the consumer never sees: a significant fraction of your inventory is going to expire on the shelf. The percentage is small. The dollar amount is not. A grocery store doing $80,000 a month in perishable sales is writing off $1,600 to $3,200 a month in expired stock — between $19,000 and $38,000 a year — that is mostly preventable.

The fix is not more refrigeration, more staff, or more willpower. The fix is a different inventory method, run by software that tracks every batch at the SKU level. This is the definitive guide to FEFO — what it is, why it works, and how Zinggo implements it.

FEFO vs FIFO vs LIFO — what the acronyms actually mean

Three inventory methods, three different rules for which unit leaves the shelf first.

  • FIFO — First In, First Out. The oldest received unit sells first. The logic: you put it on the shelf first, so it should leave first.
  • LIFO — Last In, First Out. The newest received unit sells first. Used mostly in accounting fictions, rarely in physical retail.
  • FEFO — First Expired, First Out. The soonest-to-expire unit sells first. The logic: it doesn't matter when you received it — what matters is when it goes bad.

Here is why FIFO is the wrong default for perishables. FIFO assumes that the unit received first is the unit that expires first. That assumption is false more often than not. A supplier delivery on Monday might have a longer shelf life than a delivery on Wednesday from a different supplier, or from the same supplier on a different batch. If you sell the Monday unit first (FIFO), and the Wednesday unit expires in three days, you've just written off the Wednesday unit — even though you "followed the rules."

FEFO ignores received date entirely. It looks at expiry date. The unit expiring sooner sells first. Every time. Across every batch. It is the only method that respects the physical reality of perishable goods.

Stop losing 2-4% of inventory to spoilage. Zinggo's FEFO engine tracks every batch and alerts you before expiry.
Start free →

Why FEFO matters — and where it matters most

FEFO is not equally important across every retail category. For non-perishables — canned goods, dry pasta, household cleaners — FIFO is fine, because the difference between batches is measured in years, not days. For perishables, FEFO is the only correct method.

The categories where FEFO is non-negotiable:

  1. Grocery and convenience. Dairy, fresh produce, deli, bakery, prepared foods. Shelf life of 2-14 days.
  2. Pharmacies and drugstores. OTC drugs, vitamins, eye drops, insulin. Shelf life of 6-24 months, but expiry is regulated and stockouts-of-fresh stock are reputation-critical.
  3. Food service and cafés. Prepped ingredients, sauces, doughs. Shelf life of 1-7 days.
  4. Pet stores. Wet food, treats, supplements. Shelf life of 6-18 months.
  5. Specialty retail with cosmetics. Skincare, sunscreen. Shelf life of 12-36 months, but expiry matters for safety and compliance.

For all five categories, the cost of getting it wrong is measured in three ways: write-offs (lost margin), customer complaints (returns and bad reviews), and regulatory risk (fines or license issues for expired product on the shelf in pharmacies and food service).

The cost of not running FEFO

Here are the numbers we measured across 220 Zinggo-powered grocery and convenience stores that migrated from FIFO/spreadsheet inventory to FEFO in 2025-2026. The "before" column is the six months prior to migration. The "after" is the six months following.

Spoilage metric (6-month median)Before (FIFO)After (FEFO)
Spoilage as % of perishable sales3.2%1.4%
Spoilage dollar value / month$2,180$960
Expired units on shelf at audit425
Customer returns due to expired product / mo81
Markdown revenue recovered / month$0$410
Net monthly spoilage cost$2,180$550

The net monthly spoilage cost drops from $2,180 to $550. That is $1,630 per month recovered, or roughly $19,500 per year for a mid-sized grocery. The recovery comes from three places: less write-off (the headline), fewer returns (which carry a service cost on top of the refund), and the new revenue from markdown promotions on near-expiry stock that previously went straight to the dumpster.

FEFO is not a marginal improvement on FIFO. It is the difference between treating expiry as a write-off and treating it as a discount opportunity.

— Marcus Chen, Fintech Editor

How Zinggo implements FEFO

The Zinggo FEFO engine runs at the SKU-batch level. Every item received is logged with three pieces of metadata: SKU, batch ID, and expiry date. The system then enforces FEFO across every operation that touches inventory.

01

Receiving — batch-level capture

When a delivery arrives, the store scans the barcode on each case. Zinggo parses the batch ID and expiry date from the supplier's barcode (in GS1-128 format), or prompts the receiver to enter it manually. Every unit is now batch-tagged.

02

Shelving — oldest expiry in front

The system tells the stocker which units to put at the front of the shelf — the ones with the nearest expiry. Newer stock goes behind. The physical flow now matches the data flow.

03

Selling — expiry-aware decrement

When a unit is scanned at the till, Zinggo decrements from the batch with the nearest expiry first. The customer gets the soonest-to-expire unit. The newer batch stays in inventory longer.

04

Alerting — proactive expiry warnings

At T-7 days before expiry, the system flags the batch on the manager's dashboard. At T-3 days, it suggests a markdown promotion (e.g., 25% off). At T-1 day, it suggests a steeper markdown (50% off). At expiry, it blocks further sale of the batch.

05

Promotion — auto-discount near-expiry

The markdown promotions are auto-applied at the till. A unit at T-3 days rings up at 25% off automatically. The customer sees the discount. The shelf clears. The write-off is avoided. Revenue is recovered.

Turn expiry into revenue. Zinggo's FEFO engine auto-marks down near-expiry stock before it becomes a write-off.
See pricing →

The case of Summit Wholesale, Austin

Summit Wholesale — the same distributor we profiled in our B2B marketplace piece — runs a perishable-heavy catalog serving 180 corner stores. Before Zinggo, their spoilage ran at 4.1% of perishable sales, almost double the industry median. The cause was structural: their inventory system tracked quantity at the SKU level but not at the batch level, which meant FEFO was impossible. They ran FIFO by default. Half of their spoilage was batches that arrived later but expired sooner — exactly the failure mode FEFO prevents.

After migrating to Zinggo, every received case was batch-tagged. Shelving and picking switched to FEFO. Markdown promotions fired automatically at T-7, T-3, and T-1. Within four months, Summit's spoilage dropped from 4.1% to 1.6%. The recovered margin was $4,200/month. The markdown revenue (which had previously been $0 because they threw away near-expiry stock) added another $1,100/month. Total uplift: $5,300/month, or $63,600/year — on a Zinggo subscription of $39/month.

Summit Wholesale — 4-month FEFO outcomeBeforeAfter
Spoilage % of perishable sales4.1%1.6%
Spoilage dollar value / month$5,400$1,200
Markdown revenue recovered / month$0$1,100
Customer complaints re: expired product11/month2/month
Net monthly financial uplift—+$5,300

The interesting second-order effect: Summit's reputation with their retail customers improved. Stores that had been quietly complaining about short-dated stock started ordering more aggressively. The reorder frequency from their top 30 stores went up 18% in the four months after FEFO went live — because the stores trusted that the next delivery would have a longer shelf life.

The distributor's FEFO problem

FEFO is hard at the distributor level for a different reason. A distributor doesn't sell one unit at a time — they sell cases. When a retailer orders a case of yogurt, the distributor picks a case from the warehouse. If they pick the case received most recently (which is what most warehouse systems default to), they may be shipping a case with a longer shelf life than the case sitting one pallet over that expires next week. The longer-shelf-life case goes to the retailer. The shorter-shelf-life case stays in the warehouse, expires, and gets written off at the distributor's cost.

Zinggo's distributor-side FEFO solves this. When a retailer orders a case, the system routes the pick to the batch with the nearest expiry — not the most recent receipt. The retailer gets the soonest-to-expire case (which is still well within the sellable window). The longer-shelf-life case stays in the warehouse for a future order that might need the longer window. The distributor's spoilage drops, the retailer's spoilage drops, and the total supply-chain spoilage drops.

FEFO is the rare inventory method where the right thing for the distributor is also the right thing for the retailer is also the right thing for the consumer. Everybody wins except the dumpster.

— Field notes, Zinggo operations

Common FEFO mistakes

FEFO is conceptually simple. Operationally, it has failure modes. Here are the four most common ones we see when merchants try to implement it without proper software.

  1. Tracking batch ID but not expiry date. Some systems log the batch but don't capture expiry. Without the date, FEFO is impossible — you'd be doing FIFO by batch instead of by expiry.
  2. Letting staff override FEFO at the shelf. If the stocker can put newer stock in front because it's easier, FEFO breaks. The system has to enforce the order, not suggest it.
  3. Alerting too late. A T-1-day alert is almost useless — by then, the markdown is too steep to move the volume. T-7 is the right first trigger.
  4. Not running markdown promotions. FEFO without markdowns still writes off stock. The point isn't to know about expiry earlier — it's to convert that knowledge into a discount that moves the unit.
Get FEFO right the first time. Zinggo Merchant handles batch capture, shelf routing, alerting, and markdowns — all automated.
Start free →

The 2026 verdict

Every grocery store, every pharmacy, every café, every distributor that handles perishables should be running FEFO. The math is unambiguous: 2-4% of inventory lost to spoilage, cut in half. $19,500 recovered per year for a mid-sized grocery. $63,600 recovered per year for a mid-sized distributor. For $39/month.

The reason most merchants don't run FEFO is not that they don't understand it. It's that their software doesn't support it. Spreadsheets cannot track batches at the SKU level. Most legacy POS systems don't either. The friction is not in the concept — it's in the tooling.

Zinggo's FEFO engine is built into Pro. Setup takes one batch import. The alerts, the shelf routing, the markdowns — all automated. The dumpster gets less. The shelf gets smarter. The P&L gets greener.

The 2-4% spoilage number has been treated as a cost of doing business for thirty years. It isn't. It is the cost of running FIFO on software that can't see batches. Fix the software, fix the number.