Zoho Inventory Reorder Point: Set It From Real Sales

The field that gets filled in once

When you set up an item in Zoho Inventory, there's a reorder point field on the item screen. When stock on hand drops to that number, the item shows up as low stock, and that's your cue to raise a purchase order.

Picture a typical store setting up its catalogue. Someone is entering hundreds of items in a weekend, the reorder point field is sitting right there, and they type a round number that feels about right. Then nobody opens that screen again for a year.

The low stock alert is only as good as the number behind it. If the reorder point is a guess, the alert is a guess too, just one that looks official.

Why a guessed number drifts

A reorder point is supposed to answer one question: how much stock do I need on the shelf to get through until the next delivery arrives? That depends on two things that keep moving: how fast the item sells and how long the supplier takes to deliver.

Both of them change. A brand runs a scheme and sales jump. A distributor changes beat days and deliveries come two days later. A new store opens down the road and an item that used to fly slows to a crawl. The number in Zoho stays exactly where you left it.

You end up with two kinds of failure, and they show up in different places. On fast items the reorder point is too low, so the alert fires when it's already too late and the shelf is empty before the truck turns up. On slow items it's too high, so you keep reordering stock that's still sitting in the godown. The first one costs you sales. The second costs you cash, and on anything with a date it costs you expiry. We've covered both sides of that trade-off in the hidden cost of out-of-stock perishables.

The three inputs you need

You don't need forecasting software to set a defensible reorder point. You need three inputs per item:

• Daily sell-through: units sold per day, averaged over a recent window. Four weeks is a sensible starting window because it smooths out one odd weekend without going back so far that you're counting last season.
• Lead time: days from placing the purchase order to the stock being received and shelved. Take it from your actual orders, not from what the supplier's rep promised. Zoho records the PO date and the receive date, so the gap is already in your data. Our piece on supplier lead time from purchase orders walks through pulling it out.
• Safety buffer: extra units to cover a busy day or a late delivery while you're waiting.

The formula is the one in every textbook: reorder point = (daily sell-through × lead time) + safety buffer. If you want the general method with more variations, see reorder point calculation using the sell-through method. The rest of this post is about doing it with the numbers Zoho already holds.

Worked example: one item, start to finish

Worked example: take a 1 kg pack of a branded atta. You export the sales-by-item report for the last 28 days and see 168 units sold. That gives 168 ÷ 28 = 6 units a day on average. The busiest single day in that window sold 10.

Worked example, continued: looking at your last several POs to that distributor, delivery usually takes 4 days from the order and the slowest one took 6. Here's a simple way to size the buffer: plan for a bad day combined with a bad delivery, then subtract the normal case.

• Worst case cover: 10 units/day × 6 days = 60 units
• Normal case cover: 6 units/day × 4 days = 24 units
• Safety buffer: 60 − 24 = 36 units
• Reorder point: 24 + 36 = 60 units

Worked example, continued: if the old guessed reorder point in Zoho was 20, the low stock alert was firing with less than four days of normal sales left, against a delivery that can take six. That's the stockout you keep blaming on the distributor.

That worst-case buffer is deliberately cautious. On cheap, long-life, fast-moving items, being cautious is fine. On anything perishable or expensive, you want a tighter buffer, and that's where the next section comes in.

Two corrections before you trust the number

Strip out the zero days. If the item was out of stock for five days in your window, those days show zero sales, but they weren't zero demand. Divide by the days the item was actually available, or you'll lower the reorder point and cause the very stockout you were trying to fix.

Mark the abnormal weeks. A festival week, a scheme, or one bulk order from a caterer will push the average up. Either drop those days or keep them knowingly, if you expect the spike to come back next month.

The expiry ceiling on perishables

Here's where the textbook formula lets down anyone selling dated goods. It tells you when to reorder. It doesn't tell you when to stop.

Suppose a curd cup sells 8 a day and arrives from the dairy with 7 days of shelf life left. Whatever you're holding, on hand plus on order, needs to clear in about 7 days, so the ceiling is roughly 8 × 7 = 56 units. If the buffer formula pushes your reorder point plus order quantity past that, the extra units don't protect you from a stockout. They're just next week's write-off.

So for perishables, check one more thing: the reorder point plus the order quantity shouldn't be more than you sell inside the remaining shelf life on arrival. If it is, order smaller and more often, or have a markdown plan ready. Zoho's reorder point field has no idea about expiry, and tracking batches and dates there takes a separate setup, which we cover in Zoho Inventory expiry tracking.

Keeping it current without a weekly spreadsheet session

Working out one item by hand takes ten minutes. Doing it for your whole catalogue every month isn't going to happen, and it's fine to admit that. Here's a routine you can actually keep up with a spreadsheet:

• Export sales by item and your purchase receives once a month.
• Sort by revenue and recalculate only the top slice of items, the ones where a stockout actually hurts.
• Separately, recalculate every item with a short shelf life, since those are the ones where an oversized reorder point turns into waste.
• Update those reorder points in Zoho and leave the long tail on its guessed numbers for now.

Here's where that routine runs out. It's a monthly snapshot. A lead time that slips in week two, or a slow mover that quietly loses half its pace, won't show up until the next export. And the spreadsheet will tell you the reorder point, but it won't tell you which batch is already in trouble. If you want a one-off look at where your stock stands today, an inventory health check from one CSV export is a good first pass.

Where a daily read-only scan fits

This is the gap ShelfSense by ShelfLifePro is built for. It connects to Zoho Inventory, read-only, and once a day it reads your stock, batch, cost and expiry records. It sizes reorders from sell-through and cost basis, with a safety buffer and a lead time it learns from your own orders. Next to that, it flags at-risk batches days ahead, with the units that won't clear and a recommended markdown. Every call shows its arithmetic, and none of it touches your Zoho data: it recommends, and you decide whether to change the reorder point or place the order.

It also learns over time from which accepted recommendations sold and which got wasted. When it isn't sure, it stays quiet, so you get a handful of calls a day rather than a dashboard of everything.

If you run on Zoho and the reorder points haven't been touched since setup, see how it works on Zoho Inventory expiry tracking with ShelfSense. The Watch tier is free forever at 30 SKUs — a daily scan and a health report. That's enough to test it on your top items and compare its numbers with the ones you worked out above.