On-Shelf Availability Tracking for Blinkit, Zepto and Instamart: How to Measure It Dark Store by Dark Store

To track on-shelf availability on quick commerce, count how often your SKU shows as in stock across a fixed sample of dark stores, and report it per store, not per city. A simple definition is: in-stock checks divided by total checks, for each SKU and each serviceable pincode, over a set period. That is a working method, not a platform standard (no platform page I opened defines it). One tracking vendor's example shows how a 95% city figure can mask many stores that are out of stock for days. This page covers the steps, the formula, the tools and the mistakes, as of November 2026.

Why does availability matter more on quick commerce?

A quick commerce shopper sees only the nearest dark store's shelf. If your SKU is out of stock there, the customer buys a rival's, and nothing in your city-level sales report explains the loss. Scale makes this hard to see: Blinkit says it has 2,700+ stores across 400+ cities, Flipkart says Minutes has nearly 1,200 micro fulfilment centres, and Amazon says Amazon Now runs through close to 800 micro-fulfilment and urban fulfilment centres. Every one of those locations can hold a different stock position for your SKU. See our dark store glossary for the basics.

What should you count as "available"?

Decide this before you collect anything, or your numbers will not compare week to week. A usable rule set:

1. In stock: the SKU can be added to cart at that pincode.
2. Out of stock: the SKU page loads but shows sold out or "notify me".
3. Not listed or not serviceable: the SKU does not appear, or the pincode is not served. Keep this separate from out of stock.
4. Quantity capped: the SKU can be added, but only up to a low limit. Record it, because it signals low stock.

The separate bucket in point 3 matters. The tracking vendor page I read does not explain how it separates an out-of-stock reading from an unserviceable zone or a hidden listing. Whatever tool you use, ask that question.

How do you calculate on-shelf availability?

For each SKU and pincode:

On-shelf availability % = checks where the SKU was in stock ÷ checks where the pincode was serviceable × 100

For example, you check one SKU at 20 pincodes, 3 times a day, for 7 days. That is 420 checks. Say 357 show in stock and 21 were not serviceable. Serviceable checks are 399, so availability is 357 ÷ 399 = about 89.5%. Without the serviceability split, the same data would read 357 ÷ 420 = 85%, which would blame stock for what is really coverage.

Then cut it three ways: by SKU, by pincode or store cluster, and by time of day or weekday. The vendor page's own example is a pack out of stock in 22% of high-velocity zones on weekends, which a weekly average would hide. That figure is an illustration from the vendor's marketing, not a benchmark.

What data does the platform already give you?

Start here, because it is free and it is the platform's own view.

• Zepto's brand portal says brands get analytics, product availability information, search share data and advertising options. The page is brief and does not say how any of these work.
• Blinkit is reported to give SKU-level dashboards at dark stores under its inventory-led model, and to recall underperforming products. The Blinkit brand portal I opened carried only the title "Blinkit Ads", so what it shows is not confirmed here.
• Instamart's partner portal is at partner.instamart.in. I did not open it, so I cannot say what availability data it shows.

Download whatever stock and fill data you get, and label the date and unit (SKUs, stores or units). Platform dashboards can use different definitions from your own checks, so do not merge the two without a note.

How do you check availability yourself?

A manual check costs nothing and is the best way to start.

1. Pick 15 to 30 pincodes: your top sales pincodes, a few weak ones and some from each city you care about.
2. Use a phone with each platform's app, and set the delivery location to the pincode.
3. Search by your exact product name and note: in stock, out of stock, capped, not found.
4. Repeat at fixed times, for example 8 am, 1 pm and 8 pm, on weekdays and weekends.
5. Log in a sheet: date, time, platform, pincode, SKU, status.

For a few hero SKUs this takes about an hour a day. Past that, use a tool.

Should you use a third-party tracking tool?

Several vendors sell this. The one whose page I read describes crawls per SKU and per dark store or pincode, with each session tied to a serviceable pincode so the stock status matches what a shopper there sees. Cadence varies: daily snapshots for general tracking, hourly or near-real-time refreshes for hero SKUs in busy periods.

What to ask any vendor:

The vendor claims adaptive scrapers that remap fields after layout changes and a "99% accuracy" figure that is general, not specific to availability. It is vendor marketing and I could not verify it. Also check what the platform's terms say about automated access before you commission a crawler. I have not confirmed any platform's position.

What do you do with low availability?

• If the same few stores keep running out, raise it with the category manager with your log as evidence, and review replenishment.
• If stock is fine but one pincode shows not listed, check serviceability and listing status.
• Pause ads where the SKU is out of stock, and read our Blinkit sponsored ads and pincode availability guide. General ad advice is in the quick commerce ads guide.
• Keep your own count of days out of stock per SKU, and compare with sales dips.

Which mistakes fool brands?

• Reporting one city number. Report per store cluster.
• Mixing "not serviceable" into stock-outs.
• Checking only at the time of day you happen to be free.
• Comparing your tool's numbers with the platform's without checking definitions.
• Treating a tool's accuracy claim as proof.

For a deeper tooling list, see the planned quick commerce analytics tools page, and compare platform behaviour in Blinkit vs Zepto vs Instamart.

FAQ

What is on-shelf availability in quick commerce? It is how often your product can actually be bought at a given dark store. A practical measure is in-stock checks divided by serviceable checks, per SKU and pincode, over a period. No platform page I opened defines it, so write down your own definition.

What is a good availability percentage? I have no sourced benchmark. Set your own target by SKU role: hero SKUs deserve a higher bar than slow sellers. Track the trend by store cluster, because a single average can look healthy while some stores are empty.

Why do city averages mislead? Because shoppers buy from one dark store. A vendor example describes a 95% city figure that can mask many stores out of stock for days. Always cut the data by pincode or store cluster.

How often should I check? Daily for hero SKUs and during festive peaks or weekends, weekly for the rest, is a reasonable start. Vendors describe hourly refreshes for priority SKUs in busy periods. Daily snapshots can miss short stock-outs.

Can I get dark-store availability from Blinkit, Zepto or Instamart directly? Zepto's brand portal lists product availability information. Blinkit is reported to offer SKU-level dashboards at dark stores. For Instamart, I could not confirm. Ask your account manager what is available to you.

Is scraping app data allowed? Not confirmed. I did not find a platform page that addresses it. Read each platform's terms and your vendor's contract, and take legal advice if in doubt.

Next step for your brand

If your availability keeps slipping at the same pincodes and you want help reading the pattern, see Blooprint's quick commerce service.