Listed but unavailable: the out-of-stock gap on quick commerce

What 'listed but unavailable' means

A product is “listed but unavailable” when its page is still live on a shopping app, searchable, showing a price, showing a pack, but the store serving a shopper’s pin code has none of it to sell. The shopper sees the product, taps it, and finds it cannot be added to the basket, or the app never mentions it was ever there at all if they simply never searched at the right moment.

This is not the same failure as a delisting, where the product disappears from search entirely. A listed-but-unavailable SKU still counts, in most internal reporting, as “live”. A brand team checking a catalogue export or a listing count would see it as present. Only a check against a real pin code, at a real moment, shows the gap.

A buyer put this plainly in a public post about a q-commerce catalogue: a SKU showing as live on the app while out of stock in several of the stores actually serving orders for it.¹ That is the exact shape this guide measures.

Why a product stays listed after a store runs out

Quick-commerce apps separate the catalogue from the inventory. The catalogue decision, which products a store is allowed to sell, changes rarely. The inventory count changes constantly, every time an order goes out or a delivery comes in. A listing staying live while stock runs to zero is not a bug in the app; it is the catalogue and the inventory telling two different, both-true stories at once.

The two systems are built for different jobs. The catalogue exists so search, category pages and the app’s own recommendations have something stable to point at. Tearing a listing down and rebuilding it every time a shelf empties and refills would make the whole app slower and noisier for every shopper, not just the one looking for a product that happens to be out. The inventory count exists to answer one narrow question at checkout time: can this order actually be fulfilled from this store, right now. Most of the time the two agree closely enough that nobody notices the seam. The gap this guide is about is what shows up in the minority of cases where they do not.

• Demand outran supply. A popular SKU sells out between restocks, and the store has no mechanism to pull its own page down the moment the last unit ships.
• A delayed restock. The distributor or the brand’s own supply chain missed a delivery window, and the store is waiting on stock that has not arrived.
• A pack-size mismatch. The store holds a different pack of the same product, and the specific pack a shopper searched for reads as unavailable while a near-identical one sits on the shelf.
• A store the app no longer serves. The address maps to a store that has closed or paused orders, and every listing at that store reads as unavailable until the app re-routes the pin code.

None of these is visible from a catalogue export. All four look identical from the outside: a product page that loads and cannot be bought. Telling them apart usually needs more than one reading. A SKU that is unavailable at 9am and available again by 6pm points at demand outrunning a single delivery cycle; one that stays unavailable across several days in the same pin code points at a stalled restock or a store the app has quietly stopped serving.

How often a listed SKU was actually out of stock

Rewalto reads price and stock by pin code, the same way a shopper’s app does, and records the source of every reading. For personal care, over the seven days to 30 September 2026, this is the share of checks that came back out of stock, by app.

Source and measurement notes.²

Read the two bars beside their own sample, not against each other as a scoreboard. Blinkit’s reading covers 662,654 checks across 30 pin codes and 7,458 SKUs in this window, enough to call 0.16% a stable figure for the category. Zepto’s reading covers 735 checks across 18 pin codes and 735 SKUs, a real number, from real reads, but a small enough sample that 6.4% could move a lot on the next week’s check. Neither bar says which app sells more of anything; both say what a shopper trying to buy from this category actually found, at the pin codes and the moment Rewalto checked.

What this chart does and does not show

A category-level out-of-stock share is a starting point, not a verdict on any one brand. It says how often a check in this category, this window, came back unavailable, nothing about which SKUs, which pin codes or which stores carried the gap. A brand’s own products could sit well under the average or well over it, and the category figure alone cannot tell you which.

It also does not measure demand lost. An out-of-stock reading shows a shopper could not buy at that moment; it says nothing about how many shoppers tried, or what they bought instead. That is a separate question your own sales data, not a shelf reading, has to answer.

And it is a snapshot of one week. Stock recovers, restocks land, a store re-opens. A single window is evidence of a pattern only once it repeats across several checks, which is the same discipline pin-code shelf truth asks for on price.

It is also worth remembering what the category figure cannot substitute for: a conversation about your own products. Two brands selling into the same personal care category, on the same app, in the same pin codes, can sit on opposite sides of the average, one comfortably in stock all week, the other repeatedly missing. The category share tells you what the shelf as a whole looked like; only a reading against your own SKUs tells you where you stand inside it. That is the reason the method further down this page starts from your own SKU list rather than from the category number.

How to check your own listings for this gap

You do not need a paid tool to find a first instance of this gap. Rewalto’s free pin-code availability checker, opening shortly, runs the same kind of check this guide describes for a single product and pin code, so you can see whether a specific SKU is showing available where you expect it to be sold. Until it is live, the same check can be run by hand with the steps below.

1. List the SKUs that matter most: your best sellers, and any product you suspect has a supply problem right now.
2. Pick the pin codes where those SKUs sell in volume. A handful of metro areas is a reasonable start.
3. Check each SKU in each pin code, on each app you care about, and record whether it could be added to a basket, not just whether the page loaded.
4. Save the page or a screenshot with every reading, so a number can be checked later.
5. Repeat on a fixed schedule. One check is a moment; a repeated check is a pattern you can act on.

The same three-state discipline pin-code shelf truth describes applies here: keep “in stock”, “out of stock” and “not checked” as three different things in your sheet, never collapsing the third into the second.

What to do once you find the gap

A single out-of-stock reading is a fact, not an action. What you do with it depends on how it repeats. A SKU out of stock in one pin code on one day is worth a note. The same SKU out of stock across several nearby pin codes, on repeated days, is worth raising with whoever manages that retailer relationship, with the readings, the pin codes and the dates attached, so the conversation starts from evidence rather than an impression.

Availability also belongs in a retail media checklist before it belongs in an escalation. Spend on a sponsored slot for a SKU that a shopper cannot actually buy in their area is spend that cannot convert. The practical checklist is in checking availability before you spend on retail media. And a stockout alert is only useful if it names the product, the app, the pin code and the time it applies to, what a good out-of-stock alert proves sets out what to demand from any alert before you trust it.

It is worth deciding, before you raise anything, which of the four causes named earlier you are actually looking at. A distributor that missed a delivery window needs a different conversation than a store the app has stopped routing orders to, and treating both as one problem tends to send the right evidence to the wrong desk. A short note describing the pattern you saw, attached to the readings themselves, usually settles which conversation it is faster than a call would.

Where to go next on stock and availability

To decide which stockouts to fix first, use value-weighted OOS. For what a stock alert should prove, read stock, price and rank alerts, and for a worked fill-rate reading, see the Blinkit fill-rate post. The records behind this kind of check are the stock state by pin code and the out-of-stock rate by brand and city datasets.

For the words, see the glossary entries for availability, out of stock, fill rate and assortment. If you need this as a regular check, see assortment and availability and e-commerce teams.

Common questions

Notes

1. The buyer complaint framing this guide opens with is from a public post on X, 25 September 2026, describing a SKU shown live on a quick-commerce app while out of stock at several of the stores serving it. Quoted for the shape of the problem, not as a Rewalto reading. Back to text
2. The chart’s figures are Rewalto’s own, measured 30 September 2026 from digital shelf readings over the personal care category, taken by Rewalto itself and never bought from a third party, for the seven days to that date. Each figure counts the pin-code checks in that week and how many of them came back out of stock. Back to text