As of November 7, 2026, India's festive season has turned quick commerce from a grocery habit into a general retail channel, and the strain is showing at the shelf rather than at the checkout. Blinkit, Zepto and Swiggy Instamart all ran into delivery limits and surge fees during the Dhanteras rush, while the festive basket itself widened to fashion, beauty and gifting. Dark-store counts have grown fast: Blinkit reported 2,443 stores by June 2026, Zepto 1,139 across 66 cities and Instamart 1,171 across 131 cities. The open question for brands is narrower and harder: whether the item a shopper searches for is actually pickable in the store that serves their pincode.
The festive basket is wider than the shelf
The category mix moved first. Fashion, beauty, personal care and gifting are now part of the instant basket, which means the assortment a dark store must hold has widened while the pick window stayed at a few minutes. A store built to serve milk, bread and snacks at 20 SKUs per order is now asked to serve a gift purchase with size, variant and packaging constraints. That is a different picking problem, and it shows up as missing items rather than as late deliveries.
Platforms answered the peak with price and access controls: surge fees, minimum order values, temporary service suspensions and longer delivery windows. Those tools protect unit economics during a spike, but they do not add shelf depth. When a shopper cannot find an item in the app, the usual reason is not that the platform refused to sell it, but that the SKU was never listed as available in that store.
Dark store counts do not equal availability
A network of a thousand stores is a distribution asset, not a guarantee. Availability depends on how many of those stores carry the SKU, how deep the stock is, and whether the pick path finds it before the order is packed. The three large platforms differ on all three counts, and the fee stack they charge already reflects how expensive the last mile has become.
| Platform | Dark stores (reported) | Daily orders, Diwali week 2025 | Total on an Rs 84 basket |
|---|---|---|---|
| Blinkit | 2,443 (June 2026) | About 30 lakh | Rs 143, including a Rs 4 handling fee |
| Zepto | 1,139 across 66 cities (March 2026) | Over 20 lakh | Rs 115.50, no handling fee |
| Swiggy Instamart | 1,171 across 131 cities (June 2026) | 14 to 16 lakh | Rs 154, including a Rs 9.80 handling fee |
A missing SKU never shows up in the app
Quick-commerce interfaces hide unavailability by omission. If a store does not carry an item, the item simply does not appear for that pincode, and the shopper assumes the platform does not sell it. For a brand, this is the hardest failure mode to see: there is no out-of-stock label, no substitution prompt and no complaint. The only way to measure it is to compare the listed assortment against the intended assortment, store by store, and to repeat that check during peak weeks when listing rules change.
Surge fees hide the stockout
When a platform raises fees or extends delivery windows, shoppers attribute the friction to price and timing, not to availability. That masks the underlying problem. A brand reading only conversion and average order value will conclude that demand softened, when in fact the item was not pickable. Separating fee-driven drop-off from availability-driven drop-off requires a listing audit that runs at the same cadence as the fee changes.
What to instrument before the next peak
Three measurements are worth running weekly through the festive quarter. The first is listing coverage: the share of a target SKU list that is actually visible for each pincode served. The second is depth: whether the store holds enough units to survive a day of festive demand without going dark. The third is substitution behaviour, meaning what the app offers when the exact item is unavailable.
Listing coverage is the one most brands skip, because it looks like a marketplace operations task rather than a brand task. In practice it drives everything else. A brand with 80% listing coverage across a platform's store network cannot fix a demand problem with more media spend, and a brand with full coverage but shallow depth will lose the peak afternoon regardless of how well it ranks.
Depth is where the festive calendar matters. Demand concentrates in the final two or three days before the festival, and a store that sells out at noon cannot recover until the next replenishment cycle. Tracking units per store per day, rather than aggregate stock, turns a vague worry into a capacity number that operations teams can act on before the peak rather than after it.
Rollout order
Run in this order, the audit produces a store-level worklist instead of a platform-level complaint. That matters because the levers sit at store level: which SKUs to list, how deep to stock them and what to offer when they run out.
The wider festive basket makes this more urgent rather than less. Every category added to instant delivery increases the number of SKUs a store must hold, and every additional SKU raises the chance that the one a shopper wants is the one missing from the shelf.
FAQ
Why do quick-commerce stockouts go unnoticed?
Because the app hides unavailable items by omission. If a store does not carry a SKU, the item simply does not appear for that pincode, so there is no out-of-stock label and no complaint to track.
Does a larger dark-store network guarantee availability?
No. Availability depends on listing coverage, stock depth per store and pick-path efficiency. A large network with shallow depth still loses the peak afternoon in the stores that matter.
How often should listing coverage be audited during the festive quarter?
Weekly. Platforms change listing rules, fees and access limits during peak weeks, and those changes can shift availability without any change in underlying demand.
