Expiry Management in Retail: The Four Loops

The shelf walk only works if the system behind it works

Every grocery manager knows the shelf walk — that morning sweep where someone pulls the short-dated yogurt to the front and tosses anything that's already gone. It feels like expiry management. It isn't, not really. It's the last line of defense, and by the time you're doing it, the expensive failures have already happened upstream.

Real expiry management in retail is a set of four repeating loops: capture at receiving, rotate at stocking, flag by days remaining, and act on what's flagged. Each loop feeds the next. Skip one and the whole chain breaks.

This post maps each loop, what it needs from people, and what it needs from software — honestly, without pretending a spreadsheet can do what it can't.

Loop 1: Capture — recording expiry at the receiving dock

The problem starts here. A delivery truck arrives. There are 40 line items, the driver wants a signature, and the receiving clerk is also covering the register. Expiry dates on incoming stock either get recorded carefully, recorded roughly ("the yogurt batch, exp roughly March"), or not at all.

What capture needs from people: a written or digital receiving protocol that makes date entry non-optional before a delivery is signed off. One person, one task at a time. This sounds obvious; it rarely happens without a policy that enforces it.

What capture needs from software: a receiving screen that won't let a batch be booked without an expiry date field filled in. Barcode scanning that pulls the date from the product's GS1-128 or DataMatrix code directly — no manual typing, no approximation. For context on how those 2D barcodes carry expiry data, the post on how 2D barcodes eliminate expiry date typing is worth reading before you spec a receiving setup.

What a notebook can do: capture the date, the batch number, and the quantity in a ruled column. It works for low-SKU operations. It breaks the moment you have multiple batches of the same SKU arriving on different days, because you now need to query "which batch expires first?" and a notebook can't answer that in ten seconds.

Loop 2: Rotate — getting the right batch to the shelf

FEFO — First Expired, First Out — is the rotation rule. The batch expiring soonest goes to the front of the shelf or the top of the pick pile. Every retail operator knows this in theory. The gap is at the stocking moment, usually late evening or early morning, when staff are moving fast and the oldest batch is buried at the back of the cold room.

What rotate needs from people: a stocking discipline where the stocker physically checks the date on what's already on the shelf before placing new stock. The Monday morning shelf walk system covers how to build this as a repeatable staff habit rather than a one-off instruction.

What rotate needs from software: a pick list or put-away list that tells the stocker which batch to pull first, by batch number, not just by product name. Without that, the stocker makes a judgment call under time pressure — and the newer stock (which arrived in neater cases) often goes out first.

What a notebook can do: a FIFO/FEFO log on a clipboard at the cold room door can cue staff to check dates. It works if someone updates it after every receiving. In practice, the update step gets skipped when it's busy, which is exactly when rotation errors happen.

Loop 3: Flag — surfacing what's going to expire before it already has

This is the loop where stores have the most room to recover money. A product with 14 days left can be marked down and sold. A product with two days left probably can't. The difference between those outcomes is whether someone knew about the 14-day window in time to act.

What flag needs from people: a defined review cadence — say, every Monday, pull a list of anything expiring in the next 21 days and assign it to a category manager. Without the cadence, the review happens when someone notices something, which is too late.

What flag needs from software: automated alerts sorted by urgency, tied to actual batch expiry dates captured in Loop 1 — not estimated dates, not category averages. The alert needs to reach the person who can act on it (the department manager, the buyer) not just sit in a system log. For a broader look at how this fits into a full tracking setup, the expiry date tracking guide for small businesses covers the tooling options at different scales.

What a notebook can do: a dated column in a register, reviewed on a schedule, works for a small operation with under 200 SKUs. Suppose you run a small deli counter with 30 products — a weekly review of a handwritten expiry log is entirely workable. At 500 SKUs with multiple batches per SKU, the manual review becomes a full-time job, and things fall through.

Loop 4: Act — markdown, return, or dispose

The flag is only useful if it triggers a decision. There are three options: mark down and sell before expiry, return to the supplier (if the return window is still open), or dispose and document the loss.

What act needs from people: pre-agreed decision rules so the department manager doesn't have to escalate every near-expiry item. For example: anything with more than seven days left goes to a markdown shelf at a set discount; anything inside seven days goes to a food bank or disposal log. Without pre-agreed rules, decisions get delayed, and the markdown window closes.

What act needs from software: a markdown workflow that updates the price in the POS system and logs the batch as marked-down inventory — so your shrink reporting reflects reality. For supplier returns, the system needs to generate a return document with batch number, quantity, and expiry date attached. The grocery inventory management software post covers what to look for in a system that handles this end of the loop.

What a notebook can do: document the disposal — quantity, batch, date, reason. That documentation matters for accounting write-offs and, in some states, for food donation liability records. A notebook is fine for the record. It can't trigger the action automatically.

Where the chain breaks in practice

The four loops look clean on paper. In practice, the break points are predictable:

• Capture breaks when receiving is rushed and dates get skipped or estimated.
• Rotate breaks when stocking staff don't know which batch to pull first because the batch data wasn't captured properly in Loop 1.
• Flag breaks when the review cadence isn't owned by a named person — it becomes everyone's job and therefore no one's.
• Act breaks when there are no pre-agreed rules, so near-expiry items sit flagged but undecided until the window closes.

Notice that three of the four breaks are people-and-process failures, not software failures. Software can enforce capture, automate flagging, and generate return documents. It can't make a store manager commit to a Monday review or train a night-crew stocker to check batch dates. The system has to be designed with both layers in mind.

Building the system without starting from scratch

If you're starting from a manual setup, fix Loop 1 first. Every other loop depends on having accurate expiry data in the system. A structured receiving checklist — even a paper one — that makes date entry mandatory is a better first step than buying software before you've fixed the discipline.

Once capture is reliable, Loop 3 (flagging) gives you the fastest return: you'll find batches you didn't know were short-dated, and you'll recover some of that value through markdowns you'd otherwise have missed.

ShelfLifePro is built for exactly this kind of retail operation — across grocery, pharmacy, dairy, and other perishable-heavy verticals. If you want to see how the four loops work in a live system, the 14-day free trial, no credit card required gives you enough time to run a real receiving cycle and see what the flag list looks like on day seven.

The shelf walk still matters. But the system behind it is what determines whether you're catching problems or just witnessing them.