Reduce Supermarket Expiry Waste by 30%: A Guide

The waste nobody wants to talk about

Every supermarket has a number it doesn't like to look at. It's the total value of products pulled off shelves each month because they passed their expiry date. Not damaged goods. Not theft. Just food and consumer products that sat in the store long enough to become unsellable.

Industry estimates from retail research across Indian supermarkets suggest that expiry-related waste accounts for 2-5% of total inventory value annually. For a mid-size supermarket doing ₹40-60 lakhs in monthly revenue, that translates to somewhere between ₹10 lakhs and ₹36 lakhs lost per year. The range is wide because the variance between well-managed and poorly-managed stores is enormous — and that variance is exactly where the opportunity sits.

The 30% reduction in the title is not an aspirational number pulled from nowhere. It is the kind of improvement that stores consistently achieve when they move from reactive waste management (discovering expired products during shelf checks and writing them off) to proactive waste prevention (knowing what is going to expire before it does, and acting on that information in time). The specific interventions are not complicated. They are, in order: auditing your current waste to understand where the money actually goes, implementing First Expiry First Out rotation, setting up alert systems with adequate lead time, optimising markdown timing, negotiating supplier return policies, and training staff to maintain the system. Each step builds on the previous one.

Step 1: Audit your current waste — you cannot fix what you have not measured

Before changing anything, you need to know your baseline. Most supermarket owners have a rough sense of their waste — "dairy is bad, spices are fine" — but rough senses are not data, and they lead to rough solutions that miss the actual problems.

A proper waste audit takes two to four weeks and requires tracking every single product that is removed from shelves due to expiry. Not just the ones that get formally written off. Also the ones that get quietly binned by staff during morning stocking. Also the ones that get returned to suppliers. Also the ones that get donated. Every unit needs to be recorded with its SKU, batch number, MRP, cost price, expiry date, and the date it was pulled.

What the audit reveals

The patterns that emerge from even a two-week audit are almost always surprising. Stores that assume dairy is their biggest waste category sometimes discover that packaged snacks and biscuits — products with 6-9 month shelf lives that nobody worries about — are generating more total waste because they are over-ordered and ignored. Stores that think their waste is evenly distributed across the floor often find that 60-70% of waste comes from fewer than 15% of their SKUs.

This concentration is important because it means the first interventions don't need to cover your entire product range. They need to cover the specific SKUs and categories that are generating the most loss. A targeted approach to 200 problem SKUs will yield more results than a broad policy applied loosely across 5,000 items.

Categorise waste by cause, not just by product

For each expired item pulled, record why it expired. The main categories are:

• Over-ordering: More units were ordered than demand could absorb before expiry
• Rotation failure: Newer stock was sold while older stock sat behind it
• Short-received shelf life: Product arrived from the supplier with too little remaining shelf life
• Display or placement issues: Product was in a low-traffic location and didn't get customer attention
• Seasonal demand drop: Product was ordered based on higher seasonal demand that has since declined

This cause-level data drives the specific fixes. Over-ordering is solved by better demand forecasting and order discipline. Rotation failure is solved by FEFO implementation. Short shelf life at receipt is a supplier conversation. Each cause has a different remedy.

Step 2: Implement FEFO — First Expiry, First Out

Most stores operate on FIFO — First In, First Out. Products that arrived first are sold first. This works when arrival order and expiry order are the same, which they often are not. Two deliveries of the same dal, arriving a week apart, can easily have expiry dates that are reversed — the older delivery might expire later than the newer one, depending on manufacturing batch timing.

FEFO — First Expiry, First Out — is the practice of always selling the batch with the nearest expiry date first, regardless of when it arrived. This sounds obvious. It is not obvious in practice, because it requires knowing the expiry date of every batch on every shelf, and it requires staff to physically arrange stock so that nearest-expiry products are in front.

How to implement FEFO on the shop floor

At receiving: When goods arrive, record the expiry date for each batch. This is the critical data capture point. If the expiry date is not recorded at receiving, FEFO cannot function downstream. Some stores use a simple register. Others use barcode scanning linked to their inventory system. The method matters less than the consistency — every delivery, every batch, every time.

At shelving: When new stock is placed on shelves, it goes behind existing stock if the existing stock expires sooner. If the new stock expires sooner than what is already on the shelf, it goes in front. This is the opposite of what feels natural to a helper who is trying to stock quickly. It requires training, signage, and checking.

At the system level: Your inventory management software should be able to track inventory at the batch level, not just the SKU level. When a sale is made, the system should deduct from the batch with the nearest expiry date. When reports are run, they should show batch-level positions so you can see which batches are at risk.

The time cost of FEFO is approximately 8-12 seconds of additional handling per item during receiving and shelving. For a store processing 300 unique line items per day in deliveries, that is roughly 40-60 minutes of additional staff time daily. The waste it prevents is typically several multiples of that labour cost.

Step 3: Set up expiry alert systems with proper lead time

Knowing what is on your shelf is necessary. Knowing what is about to expire — with enough lead time to act — is where waste actually gets prevented.

An effective alert system operates on three time horizons:

The 90-day alert (for non-perishables and packaged goods)

For products with shelf lives of 6 months or more, an alert at 90 days before expiry gives you time for all available options: supplier returns, promotional markdowns, reallocation to faster-moving branches (for chains), or inclusion in clearance zones. Ninety days is enough time to run a two-week discount and still have product that customers will accept.

The 30-day alert (for medium shelf-life products)

Products in the 2-6 month shelf life range — sauces, certain dairy products, packaged breads, ready-to-eat meals — need attention at 30 days. At this point, supplier returns are often still possible if your return policy allows it, and a 15-20% markdown can meaningfully accelerate sales velocity.

The 7-day alert (for perishables and ultra-short shelf life)

Fresh dairy, bread, cut fruits, prepared foods — anything with a shelf life measured in days rather than months. At 7 days out (or 2-3 days for ultra-short items), the decision is binary: mark it down aggressively for quick sale, or accept the write-off. There is no middle ground and no time for complicated strategies.

The critical gap most stores miss

The most common failure is not the absence of alerts but the absence of a response workflow attached to each alert. An alert that generates a report which nobody reads, or that flags items without assigning responsibility for action, is barely better than no alert at all. Each alert tier should have a named person responsible for reviewing and acting, a defined set of actions to take, and a deadline for those actions to be completed.

Step 4: Optimise markdown timing — earlier is almost always better

The instinct to protect margin by delaying markdowns is understandable and almost always wrong. A product marked down by 20% two weeks before expiry has a good chance of selling. The same product marked down by 40% two days before expiry often doesn't sell at that either, because customers can see the date and don't want to buy something that expires tomorrow regardless of the price.

The markdown curve

Retail research on perishable goods pricing suggests a pattern that holds surprisingly consistently across product categories:

• At 50% of remaining shelf life: A 10-15% markdown is usually sufficient to accelerate sales to clear the excess stock
• At 25% of remaining shelf life: A 20-30% markdown is needed, and some stock will still not move
• At less than 10% of remaining shelf life: Even 50% markdowns often fail because the remaining shelf life is too short for the customer to use the product

The takeaway is that early, modest markdowns recover more revenue than late, steep markdowns. A ₹100 product sold at ₹85 two weeks early is better than the same product sold at ₹50 on the last day — and vastly better than the ₹0 you get when it expires.

Markdown zones

Dedicated sections on the shop floor for marked-down near-expiry products work well for two reasons. They give price-sensitive customers a place to find deals, and they give staff a defined location to place flagged items rather than leaving them mixed into regular shelves with a small sticker that nobody notices.

Step 5: Negotiate supplier terms for returns and short-shelf-life rejections

Your suppliers are a critical part of the waste equation, and the terms you negotiate with them directly affect how much waste you end up absorbing.

Return windows

Most FMCG suppliers and distributors in India accept returns of near-expiry stock, but the windows and conditions vary significantly. Some allow returns up to 3 months before expiry with full credit. Others want 6 months of remaining shelf life. The difference between these two policies, for a product with a 12-month shelf life, is the difference between having 9 months to sell it before it becomes a problem versus having only 6 months.

Negotiate return windows that give you maximum flexibility. Your leverage in this negotiation is your purchase volume and your payment reliability. Suppliers prefer accounts that pay on time, and they will often extend return terms to keep those accounts.

Minimum remaining shelf life at delivery

This is an underused negotiation point. Set a policy that you will not accept deliveries where the product has less than a specified percentage of its shelf life remaining. For a 12-month product, that might mean you reject anything delivered with less than 9 months remaining. This prevents the supplier from pushing near-expiry stock from their warehouse onto your shelves, which simply transfers the waste problem from their books to yours.

Scheme discipline

Trade schemes that incentivise over-purchasing are a major waste driver. Before accepting any scheme, calculate the weeks of supply the scheme quantity represents. If the answer is more than 6-8 weeks of supply for a slow-moving product, the scheme is not saving you money. It is lending you stock that will expire.

Step 6: Train staff — systems only work when people use them

Every system described above requires human beings to execute it. FEFO requires the person stocking shelves to check dates and arrange accordingly. Alerts require someone to read and act on them. Markdowns require someone to apply the sticker and move the product. Returns require someone to prepare the paperwork before the window closes.

What to train on

• Receiving staff: How to check and record expiry dates, what minimum shelf life to accept, how to flag short-dated deliveries
• Floor staff: FEFO shelving technique, where to place near-expiry flagged items, how to read and respond to daily expiry alerts
• Department heads: How to read the weekly expiry risk report, when to initiate markdowns, how to process supplier returns
• Store managers: How to track waste trends, how to hold weekly waste reviews, how to identify recurring problem SKUs

Make it a weekly rhythm

A 15-minute weekly waste review meeting — looking at last week's write-offs, this week's expiry alerts, and the actions being taken — creates accountability. When waste is reviewed weekly by name (which SKU, whose department, what was the cause), it stays visible. When it is not reviewed, it fades into the background noise of store operations and the old patterns re-establish themselves within weeks.

Measuring progress and what to expect

With these six steps implemented, the trajectory typically looks like this:

Month 1: The audit reveals the baseline, which is usually worse than expected. Waste may actually increase slightly in reporting terms because you are now capturing waste that was previously unrecorded.

Months 2-3: FEFO implementation and alert systems begin catching near-expiry stock earlier. Supplier returns increase because you are identifying returnable stock within the return window. Waste begins declining.

Months 4-6: Markdown timing improves, staff habits stabilise, and the weekly review rhythm catches problems faster. Most stores see a 20-30% reduction in expiry waste from their original baseline by this point.

Months 7-12: The system is self-sustaining. Ordering patterns have adjusted based on actual demand data. Problem SKUs have been identified and their ordering reduced. Staff instinctively stock FEFO. The reduction stabilises around 25-35%, depending on how high the original baseline was.

The role of technology

Manual versions of everything described above are possible. A store can run FEFO with paper registers, manage alerts with spreadsheets, and track waste with a notebook. Stores have done this for decades.

The difficulty is not doing it once. It is doing it consistently, across thousands of SKUs, every day, for months and years. Consistency at scale is where technology becomes not a luxury but a practical necessity. Batch-level inventory tracking, automated expiry alerts, markdown recommendations based on remaining shelf life, waste analytics by category and cause — these are the functions that turn a good intention into a sustained result.

Tools like ShelfLifePro are designed specifically for this kind of batch-level expiry management in retail environments. If you are evaluating whether to build these processes on spreadsheets or invest in purpose-built software, the deciding factor is usually the number of SKUs you manage. Below 500 SKUs, disciplined manual processes can work. Above 1,000, the tracking and alerting requirements generally exceed what manual methods can maintain reliably.

The bottom line

Reducing expiry waste by 30% is not a single dramatic change. It is six mundane, systematic practices executed consistently. Audit your waste. Implement FEFO. Set up alerts with lead time. Mark down early rather than late. Negotiate better supplier terms. Train your staff and review results weekly.

None of these are novel ideas. Every experienced supermarket operator has heard some version of each of them. The difference between stores that achieve low waste and stores that don't is not knowledge — it is execution, sustained over time. The stores that measure, act, and review will reduce their waste. The stores that intend to get around to it eventually will keep writing off the same products month after month.

The money is real. The process is straightforward. The only question is whether you will actually do it.