Quick-commerce shelf

# After Diwali: a five-check shelf review for brands

Diwali fell on 8 November 2026. Before the next sale, review five things on your quick commerce and online shelf: where you ran out during the peak, which festive packs are still listed, whether prices went back to normal, what the apps promised on delivery, and the baseline you will compare the next sale with. Each check needs dated readings by app and pin code, not a screenshot.

In this guide

1. [Why review the shelf in the two weeks after Diwali](#why-review-now)
2. [Check 1: where did you run out during the peak?](#check-1-stockouts)
3. [Check 2: are festive packs still listed, and should they be?](#check-2-festive-packs)
4. [Check 3: did prices go back to normal?](#check-3-prices)
5. [Check 4: what did the apps promise on delivery?](#check-4-delivery)
6. [Check 5: save the baseline for the next sale](#check-5-baseline)
7. [A one-page review template](#review-template)
8. [What a shelf review cannot tell you](#limits)
9. [Where Rewalto fits](#where-rewalto-fits)
10. [Common questions](#questions)

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

By [Varun Mahajan](https://rewalto.com/about), FounderPublished 11 November 2026Last updated 11 November 2026Part of the [stock and availability](https://rewalto.com/guides/listed-but-unavailable) guideMore on [quick commerce](https://rewalto.com/insights/category/quick-commerce)

## Why review the shelf in the two weeks after Diwali

The weeks just after a festival are when a brand still remembers what went wrong and still has time to fix it before the next sale. Category, e-commerce and key-account teams usually take a short review to leadership or to a retailer meeting in this window. The review is only as good as its evidence: a screenshot from one phone at one address says very little about a city, and a recollection of “we ran out a lot” cannot be compared with anything next year.

Each of the five checks below says what to look at, what evidence it needs, and what it cannot prove. Run them in order. The first three look back at the festival; the fourth sets up delivery for the next one; the fifth turns this season into the baseline the next sale will be read against. Keep one shared log, one row per product, app, pin code and day, so the next person can repeat the work.

Two habits make the whole review more honest. First, write down the pin codes and products you will review before you look at any figure, so the list is not shaped by the answer. Second, keep three states apart in every check: a reading that said yes, a reading that said no, and no reading at all. Folding the third into either of the others is the most common way a festive review goes wrong.

## Check 1: where did you run out during the peak?

Read your out-of-stock rate by app, city and day through the festive weeks, and compare it with a normal week before the season. A peak-week rate means little on its own; the gap between it and an ordinary week is what a review can act on. Start with the cities and apps that matter most to your sales.

Pick the normal week carefully. It should be close enough to the festival that your range and your listings were the same, and far enough away that no early festive offer was running. Compare the same apps and the same cities in both weeks; a rate for a city that was added halfway through is not comparable with one read all season.

The current range and last update of Rewalto’s [Out-of-stock rate](https://rewalto.com/data/commerce/out-of-stock-rate) are read from the catalogue each time this page is served, and are on the dataset page.

Then look at how long each gap lasted, with [how long a stockout lasts](https://rewalto.com/guides/how-long-stockouts-last), and fix the costly ones first, with [value-weighted out of stock](https://rewalto.com/guides/value-weighted-oos). For one product at one pin code, day by day, read [Stock state](https://rewalto.com/data/commerce/stock-state):

The current coverage and last update of “Stock state” are read from the Rewalto data catalogue each time this page is served. [/data](https://rewalto.com/data) lists them too.

A rate that rose only in the evenings of the last few days before the festival usually points to replenishment that could not keep up with the peak. A rate that stayed high for days in one city points to stock that never reached the stores serving it. The two need different fixes, so note the pattern, not only the number.

**What it cannot prove:** lost sales. A reading shows the shelf at a pin code and a time, not demand.

## Check 2: are festive packs still listed, and should they be?

Gift packs and festive variants can stay listed after the season, in stock or not. Check each festive pack by pin code and record one of three states: listed and in stock, listed but out of stock, or not listed. [Listed but unavailable](https://rewalto.com/guides/listed-but-unavailable) explains the difference, and the free [pin-code availability tool](https://rewalto.com/tools/pin-code-availability) checks one brand at one pin code.

Decide with your account manager which packs to delist and which to keep for the next festival. A pack left listed but out of stock still shows to shoppers who search for it, and an unknown state is a gap to check again, not a stockout. For a longer list of packs and pin codes, the coverage of Rewalto’s prices and stock data, with the day it was measured:

The current coverage and last update of “Prices and stock by pin” are read from the Rewalto data catalogue each time this page is served. [/data](https://rewalto.com/data) lists them too.

Read the listing as well as the stock state. A festive pack that stays live after the season sometimes keeps a festive title, a gift-box image or an MRP that no longer matches what is in the warehouse. Check the title, the pack size as shown and the MRP against the pack you will actually ship, and raise any mismatch with the platform’s category team with a dated screenshot. The three checks in the [Diwali 2026 price tracker](https://rewalto.com/guides/diwali-gift-packs-by-pin-code) guide set out how to record each one.

**What it cannot prove:** why a pack is still live. That is a question for the account team.

## Check 3: did prices go back to normal?

Compare each product’s price after the sale with its usual price before the season, not only with MRP. The [Diwali 2026 price tracker](https://rewalto.com/guides/diwali-gift-packs-by-pin-code) kept that comparison by category, app and city through the festival, and counts a price as about the usual price when it is within 3 percentage points either way. [Festive sale price tracking](https://rewalto.com/guides/festive-sale-price-tracking) explains why the return to normal matters as much as the peak.

A price that never returned may be a repricing, a seller clearing stock, or a new pack with a new MRP. Check pack size and MRP first, then read the depth with [discount depth](https://rewalto.com/guides/discount-depth).

Read your own products and the rival products beside them in the same way. A rival whose price stayed low after the festival has either changed its everyday price or is still running an offer, and both matter to your next promotional calendar. Keep listed prices and conditional offers, such as bank offers or coupons, on separate lines; a price that needs a card or a code is not the price every shopper saw.

**What it cannot prove:** who funded a discount, or whether it lifted sales.

## Check 4: what did the apps promise on delivery?

Festive weeks can bring longer promised delivery times or limits in some areas. Rewalto makes no delivery-time claim for the Diwali week on this page: its measured delivery-time readings are listed below with the days they span, and where those days do not include the festival, the festival was not measured.

The current coverage and last update of “Delivery time by pin” are read from the Rewalto data catalogue each time this page is served. [/data](https://rewalto.com/data) lists them too.

Use the [delivery time by pin](https://rewalto.com/data/commerce/delivery-time-by-pin) readings to set a baseline now for the next sale. Then check, with the free [dark-store pin code lookup](https://rewalto.com/tools/dark-store-pin-code-lookup), that the apps you sell on still serve your key pin codes:

The current coverage and last update of “Dark-store locations and catchments” are read from the Rewalto data catalogue each time this page is served. [/data](https://rewalto.com/data) lists them too.

A pin code that an app stopped serving, or now serves from a store further away, changes what a shopper sees before price or stock even matter. Note any key pin code that is no longer served, and check it again a week later before you raise it, because store maps change.

**What it cannot prove:** the delivery time in any week or at any pin code that was not read.

## Check 5: save the baseline for the next sale

Keep the weeks after the festival as the normal you will compare the next sale with. Keep at least 30 days of dated prices before any sale: from 1 January 2027, an advertised cut must show the lowest price of the previous 30 days as the price before the cut, as the [30-day prior-price rule](https://rewalto.com/guides/30-day-prior-price-proof) guide explains.

Set up [Monitors](https://rewalto.com/monitors) on your hero products and the rival products beside them, so changes are logged without manual checks. [Spotting a rival’s discount sooner](https://rewalto.com/guides/competitor-promo-lag) shows how often prices move from week to week.

Write the baseline down in the same shape you will use next time: the same products, the same apps, the same pin codes and the same time of day. A baseline built on a different list from the next sale’s cannot be compared with it, however many readings it holds. If you add products or pin codes later, note the day each one joined.

**What it cannot prove:** what the next sale will bring. A baseline makes the next comparison fair; it does not forecast it.

## A one-page review template

One page is usually enough for the review. Put each check on a row, fill in what you read and keep the evidence beside it, and say plainly what each row cannot prove. The template has no figures in it; it is filled with your own dated readings.

One row per check. Fill it in with your own dated readings; it holds no figures.

| Check | What to read | Evidence to keep | What it cannot prove |
| --- | --- | --- | --- |
| 1. Stockouts at the peak | Out-of-stock rate by app, city and day, festive weeks against a normal week | The dated readings, by app and city | Lost sales or demand |
| 2. Festive packs still listed | Each festive pack by pin code: listed and in stock, listed but out of stock, or not listed | Product, app, pin code, state and time | Why a pack is still live |
| 3. Prices back to normal | Price after the sale against the usual price before the season, with MRP and pack size | Selling price and MRP, dated, by pin code | Who funded a discount |
| 4. Delivery promise | The delivery time each app showed at your key pin codes, and whether they are still served | Promised times by pin code, with the date | Delivery in any week that was not read |
| 5. Baseline for the next sale | At least 30 days of dated prices and stock before the next sale | The same products, apps and pin codes, every day | What the next sale will bring |

## What a shelf review cannot tell you

- Sales, margin or the return on ads. Readings show what a page displayed, not what sold.
- The reason behind a price or a stockout. A reading is the fact you bring to a conversation, not the cause.
- Anything that was not read. A check that never ran is not an empty result; see [not checked is not empty](https://rewalto.com/guides/not-checked-is-not-empty). Where a dataset page shows two ranges that do not agree, as noted under Check 1, rely on the days your own read returns.

## Where Rewalto fits

The five checks map to live datasets: Out-of-stock rate, Prices and stock by pin, Stock state, Delivery time by pin and the dark-store map. Read them in the dashboard, through the API or the CLI, or from an AI agent over MCP. Every figure carries its date and source, and a check that did not run says so. Re-date this review for the next big sale rather than starting a new one: the same five checks, read against the baseline you keep now, make the two seasons comparable.

Every account gets 1,000 free credits a month. [Pricing](https://rewalto.com/pricing) explains what a read costs.

See what Rewalto reads every day at [rewalto.com](https://rewalto.com).

## Common questions

### What should a brand review after the Diwali sale?

Five things: where you ran out during the peak, which festive packs are still listed, whether prices returned to normal, what the apps promised on delivery, and the baseline for the next sale. Each needs dated readings by app and pin code.

### How do I check whether I ran out of stock during Diwali?

Read your out-of-stock rate by app, city and day across the festive weeks, and compare it with a normal week before the season. A missed reading is a gap, not proof the product was in stock.

### Should festive gift packs stay listed after Diwali?

It depends on whether you plan to sell them again soon. Check each pack by pin code, listed and in stock, listed but out of stock, or not listed, and agree with your account manager which to delist.

### How do I know if a price went back to normal after the sale?

Compare the price after the sale with the product's usual price in the weeks before the season, not only with MRP. Check pack size and MRP before reading a lower price as a lasting cut.

### Did quick commerce delivery times change during Diwali?

Rewalto's measured delivery-time readings did not cover the Diwali week itself when this guide was published, so this page makes no claim either way. The dated coverage on this page shows which days its readings span, and its daily readings give a baseline for the next sale.

### What baseline should I keep for the next festive sale?

At least 30 days of dated prices before the sale, because from 1 January 2027 an advertised price cut must show the lowest price of the previous 30 days as the price before the cut.

## 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/)[See the out-of-stock rate](https://rewalto.com/data/commerce/out-of-stock-rate)

## Related guides

- [Quick-commerce shelfFestive gift packs by pin code: three checks, kept after Diwali 2026 for the next saleThree checks for each festive SKU at each pin code, kept for the next sale, with the Diwali 2026 price record.](https://rewalto.com/guides/diwali-gift-packs-by-pin-code)
- [Quick-commerce shelfFestive sale prices: the 4 prices to track on Indian shopping appsHow to track prices through a festive sale, from baseline to the return to normal.](https://rewalto.com/guides/festive-sale-price-tracking)
- [Quick-commerce shelfHow long does a stockout last on quick commerce? Count it by pin code with 3 rulesThree rules to count how many days in a row a product has been out of stock at each pin code.](https://rewalto.com/guides/how-long-stockouts-last)
- [Quick-commerce shelfOut of stock, delisted or not listed? How to tell at a pin codeThe 4 shelf states at a pin code and 4 checks to tell them apart, with a dated out-of-stock share by app.](https://rewalto.com/guides/listed-but-unavailable)

## See it in real data.

Ask about a city, a product or a dataset. The answer is free, and any fresh run shows its cost first.

[Ask our data a question](https://rewalto.com/finder)

---

Canonical page: https://rewalto.com/guides/post-diwali-shelf-review
Last content change: 2026-11-11