Dairy Distributor Shelf Life Tracking (100+ SKUs)

The spreadsheet that runs the business (until it doesn't)

Every dairy distributor in India has The Spreadsheet. Sometimes it's one file. Sometimes it's a family of files — one per route, one per product category, one that "Ramesh maintains" and nobody else fully understands. The spreadsheet tracks what came in, what went out, what's sitting in cold storage, and when it expires. On a good day, it works. On a bad day — which is any day when someone forgets to update a cell, a formula references a deleted row, or two people edit the same file — it quietly becomes fiction.

The problem is not that spreadsheets are bad tools. They're remarkably flexible. The problem is that dairy distribution has characteristics that systematically break spreadsheets: daily deliveries across dozens of suppliers, products with shelf lives ranging from 48 hours to 30 days, hundreds of SKUs each with multiple batches in stock simultaneously, and decisions that need to happen before 6 AM when the delivery vans leave. A spreadsheet can store this information. What it cannot do is keep it accurate in real time, alert you to what needs attention, or prevent someone from shipping the wrong batch to the wrong retailer.

If you're a dairy distributor managing 100+ SKUs — which is most mid-to-large operations handling milk, curd, paneer, buttermilk, cheese, ghee, flavoured drinks, and the growing universe of probiotic and protein products — the gap between what your spreadsheet says and what's actually happening in your cold room is probably wider than you think. And that gap has a cost.

What 100+ dairy SKUs actually means for expiry management

To understand why this is hard, consider what "100+ SKUs" translates to in practice.

You're not tracking 100 items. You're tracking 100 items, each with multiple batches, each batch with its own manufacturing date, expiry date, and remaining shelf life. A single SKU like "Amul Taaza 500ml" might have three batches in your cold room right now — one manufactured two days ago (good for another 4 days), one from yesterday (good for 5 days), and one that arrived this morning (good for 6 days). Multiply that by 100+ SKUs and you're looking at 300-500 individual batch-date combinations that need tracking at any given time.

Now add routes. If you serve 8 routes with 25-40 retailers each, every morning you need to decide not just what quantity goes on each van but which batch. The retailer in a high-traffic area who sells 20 litres of milk per day can take the batch with 3 days of shelf life — they'll sell through it. The small corner shop that sells 5 litres every 2 days needs the fresher batch, or it'll expire on their shelf and come back as a return you have to absorb.

A spreadsheet does not make these decisions. A spreadsheet sits there, passive, waiting for someone to open it, interpret it correctly, and act on it — all before the vans leave at 5:30 AM.

The seven ways spreadsheets fail dairy distributors

1. No automatic expiry alerts

The most fundamental gap. Your spreadsheet knows that batch D-2847 of paneer expires on February 22nd — if someone entered that date correctly, in the right cell, in the right format. But it will never tap you on the shoulder at 4:30 AM and say "you have 47 units of paneer across 3 SKUs expiring in the next 48 hours, and they're currently allocated to routes where they won't sell in time." That alert — proactive, specific, actionable — is the difference between recovering that stock and writing it off.

2. Batch-level tracking collapses at scale

At 20 SKUs, you can manually track batches in a spreadsheet. At 50, it's tedious but possible. At 100+, with 3-5 batches per SKU and daily turnover, the spreadsheet becomes a maintenance burden that consumes 1-2 hours per day just to keep current. And "current" is generous — by the time someone finishes updating yesterday's numbers, today's deliveries have already arrived and the data is stale again.

3. FEFO allocation requires manual thinking every morning

First Expiry, First Out. The principle is simple: ship the oldest batch first. In practice, FEFO allocation across 8 routes and 100+ SKUs is a combinatorial problem that a human with a spreadsheet solves through approximation and gut feel, not optimization. The van loader grabs what's in front. The salesman delivers what's on the van. Nobody checks whether batch 2841 should have gone to Route 3 instead of Route 5 because Route 3's retailer would have sold it faster.

4. No concurrent multi-user editing (that actually works)

Your warehouse manager updates the stock count. Your purchase manager enters new arrivals. Your sales team logs dispatches. If they're all working in the same spreadsheet, someone's changes get overwritten. If they're working in separate spreadsheets, the data is fragmented and reconciliation becomes a daily chore. Google Sheets helps with concurrency but introduces its own problems — slow with large datasets, unreliable on spotty warehouse Wi-Fi, and no structured workflow for who updates what.

5. Return window tracking is nonexistent

Each supplier has different return policies. Some accept returns up to 3 days before expiry. Some want 5 days. Some require a return request 48 hours in advance. Your spreadsheet does not track supplier return windows, does not calculate which batches are approaching those windows, and does not tell you that if you don't file a return request for 23 units of flavoured milk by end of day Thursday, you'll miss the credit note entirely. This is money that evaporates silently.

6. Route-level profitability is invisible

Which of your 8 routes has the highest expiry returns? Which retailer consistently lets product expire? Which route is over-served relative to its sell-through rate? A spreadsheet can answer these questions if someone builds the right pivot tables and keeps them updated. In practice, nobody does, because there are 47 more urgent things to do before the vans leave. So route-level waste patterns persist for months or years, invisible and expensive.

7. Formulas break, and nobody notices until it's too late

This is the silent killer. A formula that calculates days-to-expiry references row 147. Someone inserts a row above it. Now the formula references row 148, which is a different product. The expiry alert that should have fired for paneer batch 3021 never fires, because the formula is quietly calculating the expiry for cheese batch 4455 instead. Nobody catches it until the retailer calls to complain about expired stock. This doesn't happen every day. It happens often enough to erode trust in the spreadsheet itself, which is arguably worse than the individual incident.

What "replacing the spreadsheet" actually looks like

The goal is not to eliminate spreadsheets for philosophical reasons. The goal is to have a system that does four things your spreadsheet cannot:

Sees everything in real time. When a delivery arrives and gets scanned into the cold room, the system knows immediately. When a van loads 50 units of curd, the system deducts them from inventory and knows exactly which batches left. There's no lag between reality and record.

Thinks about expiry proactively. The system calculates days-to-expiry for every batch, every SKU, every hour. It knows which batches are approaching supplier return windows. It knows which batches need to be prioritized for dispatch tomorrow. It surfaces this information without anyone asking.

Enforces FEFO automatically. When the loading list is generated for Route 3, the system assigns the oldest viable batches first. Not as a suggestion that the van loader might ignore, but as the default allocation that would require deliberate override to change.

Tracks patterns over time. Route 7 has 3x the expiry returns of Route 4. Retailer Sharma on Route 2 returns product within the expiry window 40% of the time — is it a demand mismatch or a refrigeration issue at his shop? SKU "Probiotic Lassi 200ml" expires before selling through in 60% of batches — should you reduce order quantities or stop stocking it? These are questions that take hours to answer with a spreadsheet and seconds to answer with a system that's been tracking the data all along.

The morning dashboard: what dairy distributors actually need at 4:30 AM

Before the vans leave, a dairy distributor needs to know five things:

What's expiring today and tomorrow. Not as a long list to scroll through, but as a prioritized summary: total value at risk, broken down by SKU and batch. "You have ₹18,400 worth of product expiring in the next 48 hours" is more actionable than a 200-row spreadsheet sorted by date.

Which batches to push on which routes. FEFO-optimized loading suggestions that account for each route's typical sell-through rate. Route 6, which services 3 high-volume retailers, can absorb near-expiry milk. Route 2, which services 12 small shops, cannot. The system should know this from historical data.

Which supplier return windows are closing. "File return request for 34 units of Heritage curd by end of today. Estimated credit: ₹4,080." This is money you recover or lose based on whether you act today.

What to reorder and what to skip. Based on current inventory, expiry dates, and demand patterns, the system should suggest today's purchase order. Not "you're low on paneer" but "you have 45 units of paneer with 5+ days of shelf life, average daily sales are 30 units, you don't need to order paneer today." Over-ordering is one of the top three causes of dairy waste, and it's almost entirely preventable with decent data.

Yesterday's waste summary. What expired, what was returned, what was marked down. Not for guilt — for pattern recognition. If the same SKUs appear on the waste list week after week, something structural needs to change.

The replacement vs. return decision

Every near-expiry item presents a binary choice: try to sell it (possibly at a markdown) or return it to the supplier for credit. This decision depends on:

• Days remaining before expiry
• Whether the supplier's return window is still open
• The product's sell-through velocity on available routes
• The markdown price needed to clear it versus the credit note value from a return

A spreadsheet cannot evaluate this decision across 50 near-expiry items simultaneously. It certainly cannot do it every morning at 4:30 AM. An inventory system with expiry tracking can present this as a simple decision matrix: "These 23 items are better to push at a markdown. These 14 items should be returned. Here's why."

This is where the real money is. Industry estimates suggest that a mid-size dairy distributor handling 100+ SKUs loses between 3-7% of revenue to a combination of expired stock, missed returns, and suboptimal allocation. For a distributor doing ₹50 lakhs per month, that's ₹1.5-3.5 lakhs monthly — not all recoverable, but a meaningful portion of it is recoverable with better visibility.

The cold room reality check

None of this works without discipline at the cold room level. The best software in the world cannot help if incoming stock isn't logged with batch numbers and expiry dates. The most sophisticated FEFO algorithm fails if the loader grabs whatever's closest to the door.

Implementation in a dairy distribution context means three non-negotiable practices:

Every incoming delivery gets logged with batch-level detail. Manufacturing date, expiry date, quantity. This adds 5-10 minutes per delivery. It saves hours of guesswork later.

Van loading follows the system's allocation. The loading list says "paneer batch D-3021, 15 units for Route 4." The loader puts batch D-3021 on the Route 4 van. Not batch D-3055 because it was easier to reach. This is a training and supervision challenge, not a technology challenge.

Returns and damages get recorded immediately. When a retailer returns 5 units of curd, it goes into the system at the point of return, not at the end of the day when someone remembers. Same with damage and spoilage at the cold room.

These practices sound obvious. They are obvious. They're also the gap between distributors who manage expiry well and distributors who lose lakhs to it. The technology enables the discipline, and the discipline enables the technology. Neither works without the other.

What to look for when choosing a system

If you're evaluating options to replace your spreadsheet-based expiry tracking, here's what matters for dairy distribution specifically:

Batch-level inventory, not just SKU-level. Many inventory systems track "you have 200 units of paneer." You need "you have 200 units of paneer across 4 batches, expiring Feb 22, Feb 24, Feb 26, and Feb 28." If the system doesn't think in batches, it doesn't solve your problem.

Automated expiry alerts with configurable thresholds. Not just "this expires tomorrow" but "this expires in 5 days, and based on its sell-through rate, it won't sell in time." The threshold should be configurable per product category — 2 days for milk, 5 days for paneer, 15 days for ghee.

Route-wise allocation and dispatch tracking. Which batch went on which van to which retailer. This is essential for FEFO enforcement and for understanding route-level waste patterns.

Supplier return window management. The system should know each supplier's return policy and alert you when batches approach the return window.

Mobile access for warehouse and field staff. The person loading the van at 5 AM is not sitting at a desktop. The salesman on Route 6 who needs to check a batch's expiry date for a retailer is using his phone. If the system requires a desktop, it won't be used when it matters most.

Works with Indian dairy supply chain realities. This means handling frequent small deliveries (not weekly bulk shipments), multiple suppliers for the same product category, variable shelf lives within the same SKU depending on the supplier, and the return/credit note workflow that's specific to Indian distribution.

ShelfLifePro provides batch-level expiry tracking with FEFO-based dispatch allocation, supplier return window alerts, and a morning dashboard built for dairy distributors managing 100+ SKUs. It's designed for Indian dairy distribution workflows — not retrofitted from a warehouse management system. If your spreadsheet is holding your operation together with duct tape and hope, it may be worth a look.