Stock-Out & Availability Heatmap

A platform fill rate is one number for a whole city, calculated by the platform itself, and it cannot be challenged. We sample availability per dark store every twelve minutes, so you get a number per store and per pin-code that you can put in front of a category manager with evidence attached. The gap between the two is usually four to eight points.

By comparing behaviour across stores and time. A SKU out everywhere at once is a depot issue. Out in one store while neighbours hold stock is a store issue. Missing from the catalogue rather than showing as unavailable is a silent delisting. Available but never surfacing in search is throttling. Each has a different owner and a different fix, which is why lumping them into one fill rate helps nobody.

A SKU removed from a store's assortment rather than marked out of stock. It disappears from the app in that pin-code entirely, so it never appears in a stock-out report — the platform is not out of stock, it simply no longer carries the item there. This is typically a quarter of what brands think are supply problems.

Because quick commerce demand is concentrated in the evening and availability is usually lowest at exactly that point. A daily average of 93% can contain a 9pm figure of 62%. We report the evening and late-night windows separately for that reason, since those are the hours that decide whether a customer switches brand.

Blinkit, Zepto, Swiggy Instamart, BigBasket Now and Flipkart Minutes across 52 Indian cities and roughly 4,200 pin-codes. Blinkit refreshes every 12 minutes, the others between 15 and 25 minutes. We also cover GCC quick commerce if you sell in the Middle East.

Both. You get the live dashboard, a REST API for your supply planning system, daily CSV or Parquet exports to S3 or GCS, and Slack or WhatsApp alerts the moment a priority SKU goes out in a priority pin-code. Store-level detail is in every export, not just city aggregates.