Your Wastage Register Already Tells You What to Order Less

The register nobody reads back

Picture a typical neighbourhood grocery store at closing time. Someone walks the dairy chiller, pulls the curd that's past its date, the bread that's gone hard and the paneer that smells off. They write each one into the wastage register, total it up and put the book back under the counter.

Next morning the distributor's salesman comes by and the owner places the same order as last week. Same curd, same bread, same paneer. Nobody opened the register.

So the wastage register works as a record of what you lost. It almost never works as an instruction for what to buy. That's a shame, because it holds the most honest demand data in the shop. Every line in it is a unit you paid for and nobody wanted.

Why wastage and ordering live in different places

It isn't laziness. The two jobs sit with different people at different times of day.

The register gets filled in by whoever does the evening shelf check. The order gets placed by the owner or manager, usually from memory, often with the salesman standing right there pushing a scheme. The register sits in one drawer and the purchase bills sit in another. Nobody puts the two next to each other.

There's a second reason too. Wastage feels random day to day. One evening it's three curds, the next it's none, and the busy person ordering decides it's just bad luck. You only see a pattern when you stack a few weeks together, and nobody has time for that at 9 am with a delivery truck at the gate.

If your store doesn't yet have a clear rule for what gets pulled and recorded, sort that out first. Our expired stock policy SOP covers who checks, when, and what goes in the book.

The four-week wastage-to-order sheet

Here's the method. It takes about an hour once a month, and all you need is a notebook or a spreadsheet.

Take four weeks of the wastage register and four weeks of purchase bills for the same period. One week is too noisy to read, and a full quarter mixes in festival swings. Four weeks gives you enough repeats to tell a pattern from bad luck.

For every line that shows up in the register, make one row with these columns:

• SKU — the exact item and pack size, not "curd" but "curd 400g cup"
• Units ordered — the total from your purchase bills over the four weeks
• Units wasted — the total from the register
• Weeks with wastage — how many of the four weeks had at least one unit written off
• Minimum drop size — the smallest quantity the supplier will deliver
• Wastage ratio — units wasted divided by units ordered

Add a last column for cost: units wasted multiplied by your cost price, not MRP. That's the column that tells you which line to fix first. The expiry loss calculator does the same sum if you'd rather not do it by hand.

Reading the ratio: four kinds of lines

Once the sheet's filled in, every row lands in one of four buckets.

• Wasted every week, steady ratio. You're over-ordering, plain and simple. Cut the standing order by roughly the average weekly wastage.
• Wasted every week, but the supplier's minimum drop is bigger than what sells between deliveries. Here the problem is the pack size, not your judgement. Ask for a smaller pack, alternate-day delivery, or a split crate with another line from the same supplier.
• Wasted heavily in just one week. That's usually a one-off: a power cut, a festival you misjudged, a batch that arrived with a short date. Note why and leave the order alone.
• Never wasted, but ran out. Check these too. A line with zero wastage that's empty by evening is probably under-ordered, and that costs you sales you never see. We wrote about that side in the hidden cost of out-of-stocks on perishables.

The second bucket is the one people miss. The owner sees the waste, blames the ordering, cuts back, and then runs out, because the real issue was a pack size the shop can't sell through in time.

Worked example: a dairy and bakery shelf

For example, say a small grocery store's four-week sheet for its dairy and bakery shelf reads like this:

• Curd 400g: 168 ordered, 34 wasted, wastage in all four weeks
• Paneer 200g: 120 ordered, 30 wasted, wastage in all four weeks, minimum drop of 10 packs
• Brown bread: 84 ordered, 3 wasted, wastage in one week
• Cheese slices: 40 ordered, 12 wasted, all 12 in a single week
• Buttermilk 500ml: 112 ordered, 0 wasted, ran out on four evenings

Worked example, continued: curd's ratio is 34 ÷ 168, about 20%, and the waste is spread evenly across the weeks. That's about 8 or 9 cups a week the store is buying and binning. Bring the standing order down by about one cup a day and look again in four weeks.

Worked example, continued: paneer wastes 30 of 120, a 25% ratio. But it comes in drops of 10 and sells around 6 between deliveries, so 4 go off every time no matter how carefully the owner orders. Cutting the order won't fix it. A 100g pack or a drop every second day will. Our post on 48-hour paneer and curd wastage goes through the short-shelf-life side of this.

Worked example, continued: brown bread at 3 of 84 is fine, so leave it. Cheese slices lost 12 in one week, and if that turns out to be a batch that came in with a short date, it belongs in a supplier claim, not an order cut. Buttermilk wasted nothing and ran out four times, so it's the one line here that should go up.

Turning the sheet into next week's order

The sheet only earns its hour if it changes the order. So write the changes down as standing instructions for whoever orders: "curd down one a day", "paneer, ask for smaller pack", "buttermilk up". Tape the list next to wherever orders get placed.

Change one thing per line at a time. If you cut curd and also change the delivery day, you won't know which one worked. Then re-run the sheet four weeks later and check that the ratio fell without the line running out.

Lines that keep wasting even after you've cut them may not belong on the shelf at all. Slow movers vs dead stock helps you decide whether a line needs a smaller order or needs to go.

Where a paper register runs out

The monthly sheet is a real improvement, and plenty of stores could run it in a notebook forever. But it does have limits.

It looks backwards. By the time you've added up four weeks, the waste has already happened. It also doesn't see batches. The register says "12 cheese slices wasted" but not that they all came from one short-dated delivery, unless someone wrote that down at the shelf.

It also takes discipline to keep going. The first month gets done. The third month gets skipped during Diwali stock-up, and the sheet quietly dies. A daily expiry-tracking spreadsheet template keeps the dates in one place, but someone still has to read it and turn it into an order.

Letting the records do the reading

If the hour a month is the bit that keeps slipping, that's the job ShelfSense by ShelfLifePro was built for. Once a day it reads your stock, batch, cost and expiry records. It sizes reorders from sell-through and cost basis, and it flags batches that won't clear in time, showing the arithmetic behind every call. It only recommends. A person approves every change. Over time it learns which of the accepted calls actually sold and which ones still ended up as waste.

You don't need to switch systems. Start with a CSV export of your stock and expiry dates. If you run Tally, export to CSV today, and a direct connection is available on request. ShelfSense's free audit reads one CSV export, no account needed. The Watch tier is free forever at 30 SKUs — a daily scan and a health report. You can start free on the ShelfSense page.

Software or not, read the register back. It's already telling you what to order less of.