Quick-commerce shelf

# Value-weighted OOS: which stockouts to fix first

Not every out-of-stock SKU costs the same. Weighting a stockout by what the product is worth sorts a long list into Must fix, Watch and Ignore, so a small team spends its week on the gap that matters. Rebuild the list on a fixed schedule as stock and value change.

![](https://rewalto.com/_next/image?url=%2Fbrand%2Fog%2Fguides-value-weighted-oos.png&w=3840&q=75)

In this guide

1. [Why a flat out-of-stock count misleads](#the-problem)
2. [The method: two axes, not one list](#the-method)
3. [A worked matrix (sample figures)](#the-matrix)
4. [Building this from your own list](#build-your-own)
5. [What this method does not decide for you](#limits)
6. [Where this connects to the rest of your shelf reading](#related-reading)
7. [Common questions](#questions)
8. [Notes](#notes)

[Explore commerce data](https://rewalto.com/data/commerce)

By [Varun Mahajan](https://rewalto.com/about), FounderPublished 30 September 2026Last updated 30 September 2026Part of the [stock and availability](https://rewalto.com/guides/listed-but-unavailable) guideMore on [data and APIs](https://rewalto.com/insights/category/digital-shelf)

## Why a flat out-of-stock count misleads

A list of every SKU that is out of stock somewhere, sorted by count, puts a high-volume low-margin item beside a hero product with equal weight. Both show up once on the list. A team with limited time to chase supply issues, working straight down that list, spends as much effort on the SKU that barely matters as on the one that does.

One product team framed exactly this trade-off in a public discussion of prioritisation exercises for a live availability and pricing snapshot: too many stockouts to chase all of them, and no obvious rule for which ones to chase first. Weighting by value is that rule.[1](#note-1)

The same distortion shows up whenever a team reports “N SKUs out of stock this week” as a single headline number. A week where a hero product was out for three days and a week where thirty long-tail SKUs each had a brief gap can produce the same count, and read as the same severity in a weekly report, while costing the business wildly different amounts. A count treats every SKU as interchangeable; a real catalogue never is.

This is not a new problem outside quick commerce. Any retail team that has ever prioritised shelf-replenishment visits by store traffic rather than by an even rota has already applied the same logic. What is new here is the pace: a q-commerce out-of-stock list can change within a day, so a prioritisation method that needs a week to update is already out of date by the time anyone reads it.

## The method: two axes, not one list

Plot every SKU on two axes: how often it is coming back out of stock across your checks, and what it is worth to the business. A SKU high on both is the one to fix first. A SKU low on both can wait. The two axes that are high on one and low on the other need a judgement call rather than an automatic rule, which is exactly what the matrix below is for.

The three bands the matrix sorts a SKU into, and what each one means for a team's time

| Band | What it means |
| --- | --- |
| Must Fix | High out-of-stock share on a high-value SKU. Raise it with the retailer relationship this week, with readings attached. |
| Watch | High on one axis, not the other. Keep checking on the normal schedule; escalate only if the pattern holds or the value tier changes. |
| Ignore | Low on both axes for now. Not unimportant forever, just re-checked on the same cadence as everything else rather than chased this week. |

The two Watch corners are not the same kind of watch. A high-value SKU with a low out-of-stock share is worth watching because losing it would matter a great deal: the risk is low today but the cost of missing a change is high. A low-value SKU with a high out-of-stock share is worth watching for the opposite reason: frequent enough to note, but small enough that it does not need this week’s attention. Keeping the two apart in your own notes stops a busy week from treating them the same.

## A worked matrix (sample figures)

This is a worked example with invented SKU names and invented out-of-stock figures, built to show how the sorting works. It is not a Rewalto reading and it names no real brand or client. Read the figures below as illustration only.

WatchMust FixIgnoreWatchOut-of-stock share, low to highSKU value, low to highHero SKU AHero SKU BMid SKU CMid SKU DLong-tail SKU ELong-tail SKU FMid SKU G

SAMPLE / ILLUSTRATIVE,invented SKU names and invented figures, built to show the method. Not a Rewalto reading and not any client’s data.

Illustrative method, not a measurement.[2](#note-2)

Hero SKU A and Hero SKU B sit in the top-right: high value, and out of stock in more than half of this sample’s checks. Both go on this week’s Must Fix list. Long-tail SKU E has a similarly high out-of-stock share but sits at low value, landing in Watch rather than Must Fix: the same stockout rate, a different priority, because the value axis changes the read. Mid SKU G has a low out-of-stock share and a mid value tier, landing in Ignore for this week.

Mid SKU C and Mid SKU D are the pair worth studying most closely, because they sit at the same value tier and read very differently on out-of-stock share,55% against 20%. That gap is the kind of signal a flat count would never surface: two SKUs a business tier might treat identically get very different treatment once the shelf reading is added, and Mid SKU C is the one that moves up the queue this week while Mid SKU D does not.

Notice how little the diagram needs to be useful. Seven points, two axes and three labelled bands are enough to turn a flat list into a short weekly queue. A team does not need a dashboard to start doing this: a spreadsheet with an out-of-stock-share column and a value-tier column, sorted twice, gets most of the way there before anyone draws a chart at all.

## Building this from your own list

1. Start from a real, dated out-of-stock reading for your SKUs. Rewalto’s free pin-code availability checker, opening shortly, can produce a first one for a handful of products and pin codes.
2. For each SKU, compute an out-of-stock share: checks that came back unavailable, over total checks, for a stated window. Keep the window the same across every SKU so the comparison is fair.
3. Tier each SKU by value: trailing sales if you have them, or a simple high/mid/low call if you do not. The tier does not need to be precise to be useful.
4. Plot the two, or simply sort a spreadsheet by both columns and read off the four corners by eye. The matrix is a way to see the sort, not a requirement to draw one.
5. Rebuild it on the same cadence as your stock checks, and watch which SKUs keep landing in Must Fix across more than one build. A SKU that lands there once is a moment; one that lands there every week is a pattern worth a standing fix.

## What this method does not decide for you

The matrix sorts by two axes you choose; it does not pick those axes for you, and a bad value tier produces a bad sort. If “value” is guessed rather than measured, say so when you share the matrix, and treat the Must Fix band as a starting list to sanity-check rather than a final ranking to act on unread.

It also does not explain why a SKU is out of stock. A supply delay, a demand spike or a store that has stopped serving orders can all produce the same out-of-stock share. The matrix tells you where to look first; the cause still needs the same evidence discipline as any other reading, sources and dated checks included, described in [what a good out-of-stock alert proves](https://rewalto.com/guides/oos-price-rank-alerts).

There is also a limit worth stating plainly: a single week’s matrix can be noisy for any SKU whose sample of checks is small, in exactly the way a thin sample makes any out-of-stock share less certain. A SKU that jumps from Ignore to Must Fix and back to Ignore across three consecutive weeks is more likely showing sampling noise than a real change in how it is selling, and treating every jump as an emergency will wear a team out faster than the underlying problem justifies. Look for a band that holds for more than one build before you treat it as a fixed fact about a SKU.

## Where this connects to the rest of your shelf reading

Value-weighting a stockout list is one layer on top of the underlying reading. For how often a listed SKU is actually out of stock in the first place, with a real, dated figure by app, see [listed but unavailable](https://rewalto.com/guides/listed-but-unavailable). For how visible your products are against a competitor’s in search results, a different kind of priority question, see [digital share of shelf](https://rewalto.com/guides/digital-share-of-shelf). And for reading a discount alongside a stockout, so a SKU that is both under-priced and under-stocked does not get treated as two separate problems, see [discount depth](https://rewalto.com/guides/discount-depth).

Put together, the three form a rough weekly rhythm for a small e-commerce or key-account team: check availability and price for the SKUs and pin codes that matter, sort what came back into Must Fix, Watch and Ignore by value, and take only the Must Fix list into that week’s conversations with retailers or distributors. The rest of the reading is not wasted. It is the record that lets next week’s Must Fix list be judged against a pattern rather than read cold.

## Common questions

### What does 'value-weighted OOS' mean?

It means sorting out-of-stock SKUs by what each one is worth to the business, not just counting how many are out of stock. A long-tail SKU out of stock in ten pin codes can matter far less than a hero SKU out of stock in three.

### What counts as a SKU's 'value' for this method?

Whatever your team already tracks that approximates revenue or margin contribution: trailing sales, listed price times typical volume, or a simple high/mid/low tier if a precise figure is not available. The method works with a rough tier; it does not need a perfect number.

### How often should the matrix be rebuilt?

On the same schedule as your stock checks. A matrix built once from a single week of readings is a snapshot; rebuilding it on a regular cadence turns it into a record of which SKUs keep landing in Must Fix.

### Does a SKU in 'Ignore' never need attention?

It means the SKU is not worth the same urgency as a Must Fix one this week, not that it is unimportant forever. A long-tail SKU with a rising out-of-stock share is worth re-checking on a slower cadence rather than being dropped from the list.

## Notes

1. The prioritisation framing this guide opens with is from a public post on r/indianstartups, 2026, describing a prioritisation exercise over a live availability and pricing snapshot. Quoted for the shape of the problem, not as a Rewalto reading. [Back to text](#ref-1)
2. The matrix on this page is SAMPLE / ILLUSTRATIVE: invented SKU names and invented figures, built to demonstrate the method. It carries no Rewalto measurement and no client’s data, per this site’s rule against publishing a named client’s findings. [Back to text](#ref-2)

## Start with the question you need to answer

Check the current data catalogue, then review the coverage and dates against your question. The research in an older guide does not establish that a service is available today.

[Explore Rewalto data](https://rewalto.com/)[Explore current data](https://rewalto.com/data)

## Related guides

[Quick-commerce shelf

### What a good out-of-stock, price or rank alert proves

What evidence an out-of-stock, price-floor or search-rank alert should carry, and where ours stands.

Explore](https://rewalto.com/guides/oos-price-rank-alerts) [Quick-commerce shelf

### Digital share of shelf: a definition you can defend

How to define and measure the share of results your brand fills, and where the figure misleads.

Explore](https://rewalto.com/guides/digital-share-of-shelf) [Quick-commerce shelf

### Discount depth: reading the gap between selling price and MRP

How to calculate discount depth and read it without over-claiming.

Explore](https://rewalto.com/guides/discount-depth)

---

Canonical page: https://rewalto.com/guides/value-weighted-oos
Last content change: 2026-09-30