Zoho Inventory Expiry Tracking: What It Does

What Zoho Inventory actually does with expiry dates

Zoho Inventory has batch tracking built in. Per its documentation, you can assign a manufactured date and expiry date to each batch when you receive stock, and the system will carry those dates through every movement — sales orders, transfers, adjustments. That's more than most billing-first tools offer, and it's the reason operators in pharmacy, grocery, and FMCG distribution reach for it.

The batch expiry alert feature, again per Zoho's documentation, lets you set a threshold — a number of days before expiry — so the system flags batches crossing that line. You can pull a near-expiry report to see what's approaching the date. For a store that previously tracked this in a notebook or a colour-coded spreadsheet, this is a real step forward.

So if you're evaluating Zoho Inventory for expiry tracking, the short answer is: yes, it does expiry. The longer answer is about where it stops — and that's where most operators run into trouble.

How batch tracking works in practice

Picture a grocery store receiving three batches of the same SKU from two suppliers on the same day. Batch A expires in 45 days, Batch B in 22 days, Batch C in 60 days. In Zoho Inventory, per its documentation, each batch gets its own expiry date at the time of goods receipt. When you fulfil an order, you can select which batch to pick from.

The near-expiry report will surface Batch B when it crosses your alert threshold. That's the mechanism working as designed.

Where it gets harder: the report tells you a batch is near expiry. It doesn't tell you whether you'll sell through it in time. It doesn't rank batches by how much money is sitting in them. It doesn't suggest a markdown amount or a quantity to discount. Those judgement calls still sit entirely with the person reading the report — which is fine if that person has time, context, and a clear process. Many don't.

This isn't a criticism of Zoho Inventory. It's a batch and inventory management tool, not an expiry intelligence layer. The gap is structural, not a bug.

Where Zoho Inventory expiry tracking stops

Three specific gaps come up repeatedly when stores rely on Zoho's native expiry features alone.

No money-at-risk ranking. The near-expiry report shows batches approaching their date. It doesn't sort them by the value of stock at risk. Say you have a batch of a slow-moving item with a high landing cost expiring in 18 days alongside a fast-moving item expiring in 12 days. The fast mover might clear on its own. The slow mover won't. Zoho's report doesn't make that distinction — you have to.

No markdown sizing. Knowing a batch is near expiry is the first step. Knowing how much to discount to clear it before the date — based on your current sell-through rate for that SKU — is the second step. Zoho Inventory doesn't do that arithmetic. You're estimating.

No learning from outcomes. If you mark down a batch and it clears, that's useful information for the next time the same SKU approaches expiry. If it doesn't clear, that's also useful. Zoho's batch tracking doesn't retain or use that pattern. Every cycle, you start from the same place.

These gaps matter more as SKU count grows. For a store with a small, stable range, a daily check of the near-expiry report is manageable. For a store with hundreds of perishable SKUs across multiple categories, the report becomes a list you can't act on fast enough. The inventory system expiry tracking gap post covers this structural problem in more detail.

What good expiry discipline looks like alongside any system

Whether you're on Zoho Inventory, Tally, or a spreadsheet, the operating discipline is the same. A few things that hold regardless of the tool:

• FEFO at the receiving dock. Batches with the earliest expiry date go to the front of the shelf or bin. This is a physical habit, not a software feature. Zoho's batch tracking supports it, but the staff still have to do it.
• A fixed review cadence. Near-expiry reports are only useful if someone looks at them on a schedule — not when they remember. Daily for perishables, weekly for slower-moving categories with longer shelf lives.
• A clear action trigger. The report shouldn't just be read; it should trigger a decision. What happens when a batch crosses 21 days? 14 days? 7 days? If the answer is "we discuss it," the batch will often expire before the discussion ends. The near-expiry stock 7 strategies for Indian retailers post lays out a practical decision ladder.
• A returns process with your distributor. Some near-expiry stock is returnable. Knowing your supplier's return window — and having the paperwork ready — recovers money that most stores leave on the table.

None of this requires software beyond what you already have. What software can do is reduce the time it takes to find the right batches and make the call.

How ShelfSense connects to Zoho Inventory

ShelfSense connects to Zoho Inventory read-only. It reads your stock, batch, cost, and expiry records once a day — it doesn't write anything back, doesn't change a price, doesn't place an order.

What it adds on top of Zoho's native reporting: it ranks your at-risk batches by money at risk, shows the arithmetic behind each call ("approximately 9 of 14 units won't clear by Friday at the current sell-through rate"), and suggests a markdown where one is warranted. A human approves every recommendation. It stays quiet when it isn't sure — you get a small number of high-confidence calls, not a second dashboard to scroll through.

It learns over time from which recommendations cleared and which didn't, so the calls get sharper the longer it runs alongside your operation.

ShelfSense's free audit reads one CSV export, no account needed — so you can see what it surfaces from your own Zoho data before committing to anything. The Watch tier is free forever at 30 SKUs — a daily scan and a health report.

If you want to see how the reasoning behind a recommendation works, /shelfsense/how-it-thinks walks through a real example. Or go straight to /zoho-inventory-expiry-tracking to connect your Zoho account.

The honest summary

Zoho Inventory's batch expiry tracking, per its documentation, is solid for what it's designed to do — recording batch dates, alerting on thresholds, and generating near-expiry reports. If you're not doing any of that today, starting there is the right move.

The gap isn't in the data. It's in the decision layer: which batch to act on first, how much to discount, whether you'll clear it in time. That's where operators lose money — not because they didn't know a batch was expiring, but because they didn't know it was the one that mattered most that week.

A tool like ShelfSense doesn't replace Zoho Inventory. It reads what Zoho already knows and adds the judgement layer that turns a report into an action. That's the difference between knowing and doing.