Are your Diwali gift packs live? Checking festive SKUs by pin code before Dhanteras

Why check now

Dhanteras falls on 6 November 2026 and Diwali on 8 November 2026, according to a quick-commerce festive playbook published on 25 September 2026.¹ Its checklist for four weeks out tells brands to finalise gift packs and festive SKUs and register them as new listings, so that they are live before the festive purchase order lands. It also says quick-commerce demand peaks in the evenings of the last week, especially the two days before Diwali.

An Inc42 feature from 11 August 2026 makes the wider point: this festive season will be won on assortment, inventory placement, replenishment and store-level availability.²

With under two weeks to Dhanteras, most festive SKUs should already be registered. The useful question now is narrower: did each one actually reach the shelf, in the places your shoppers are?

A gift pack is live only where it is live

A quick-commerce listing belongs to one pin code at one moment. The store that serves one delivery area may stock your gift pack while the store that serves the next area does not. A check from your office pin code tells you about your office pin code, and nothing more. Our guide to pin-code shelf truth explains why.

So start with a short list of pin codes that matter this festive season: where festive stock was sent, where your strongest stores are, and where any festive campaign will run. Write the list down before you start, so that every round of checks uses the same places and the results can be compared. Then run the same three checks at each one.

Check 1: is the pack listed at that pin code?

Set the app to the pin code. Search the way a shopper would, with your brand name and “gift pack” or “combo”, then search again with the exact title you registered. Note what you find and the time you checked.

If the pack does not appear, do not write “not listed” yet. A new title may not match search, or the store serving that pin code may not range it yet. Write “not found at this pin code, at this time” and keep looking for the cause.

Check 2: is it in stock, out of stock, or unknown?

A pack can show up in search and still be impossible to buy. A listing that loads but cannot be added to a basket is listed but unavailable, and it is a different problem from a missing listing.

Record one of three states for each pack, pin code and time:

• In stock: the page showed it could be added to a basket when you checked.
• Out of stock: the page showed it as unavailable when you checked.
• Unknown: the page did not load, the pin code was not served, or the page showed no stock signal.

Keep unknown out of your out-of-stock count. An unknown is a gap in the check, not a stockout. Our guide not checked is not empty covers how to report gaps honestly.

Check 3: does the listing match the box?

A gift pack is usually a new pack, with its own contents, count and net weight. Compare three things on the listing with the printed pack:

1. The title: does it name the right pack, contents and variant?
2. The pack size as shown: count, weight or volume, exactly as the listing prints it.
3. The MRP shown: is it the MRP on the box?

If any of these differ, take a dated screenshot of the listing at that pin code and raise it with the platform’s category team. A mismatch is worth fixing before the festive rush, even when stock is fine.

Not seen is not missing. If you or a tool cannot find your gift pack at a pin code, that tells you about one search, at one time, in one place. It does not prove the pack is unlisted across a city or an app. Look again, at another time, with the exact title, before you escalate.

Keep one log for every check

The three checks are only useful if the next person can repeat them. Keep one shared log, with one row per pack, app, pin code and check time, and these columns:

• the pack, as you registered it, and the title as the app showed it;
• the app and the pin code the app was set to;
• the pack size and MRP as the listing showed them;
• the state: in stock, out of stock, unknown, or not found;
• the date and time of the check, and a link to the screenshot;
• who will follow up, and what they asked the platform to fix.

A log like this turns a worry into a short list. It shows which packs failed at which pin codes, separates real stockouts from unknowns, and gives the category team a dated record instead of a general complaint.

Check one brand by hand: the free pin-code tool

Rewalto’s pin-code availability tool is free. Type a brand and a pin code, and it checks Blinkit, Zepto and Instamart (limited coverage) against Rewalto’s own collected readings. It tells you what it found, and it says plainly when Rewalto has not collected that pin code yet, rather than guessing.³ Its scope is one brand, one pin code, one moment, which makes it a quick first pass before you open each app.

Check many SKUs and pin codes: read the live data

For a longer list of festive SKUs, Rewalto’s “Prices and stock by pin” dataset is live: selling price, MRP, discount and in-stock state per product, by pin code, as the app showed it. Its coverage, as /data shows it now:³

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 lists them too.

The commerce data page lists it with the other shopping datasets. Rewalto holds readings at the pin codes it lists, not every pin code in India. For a pin code it has not read, it says so instead of guessing.

Read the coverage line before you plan a festive check. It names how many pin codes are already held and the day that count was measured, so you can see at once whether your priority pin codes are likely to be in it. If one is missing, ask for a fresh reading on Blinkit there before Dhanteras rather than assuming the nearest held pin code tells the same story.

Analysts with API access can run the first two checks through the commerce data reference: search listings at a pin code, with each listing’s newest price, MRP and pack size as shown, then ask for the stock state of each listing. Every stock answer is in stock, out of stock or unknown, with the reason and the time of the reading.

# 1. Is the gift pack listed at this pin code? Empty means "not seen in the last 30 days".
curl --fail-with-body -G "https://api.rewalto.com/v1/data/listings/search" \
  -H "Authorization: Bearer $REWALTO_API_KEY" \
  --data-urlencode "q=<gift pack words>" \
  --data-urlencode "brand=<brand as the app writes it>" \
  --data-urlencode "pincode=<six-digit pin code>" \
  --data-urlencode "include=latest" \
  --data-urlencode "limit=20"

# 2. Is it in stock there? Use the listing id from step 1.
curl --fail-with-body -G "https://api.rewalto.com/v1/data/availability" \
  -H "Authorization: Bearer $REWALTO_API_KEY" \
  --data-urlencode "pincode=<six-digit pin code>" \
  --data-urlencode "listingId=<listing id>"

Keep your API key on your server, never in a browser or a shared prompt. Unknown stock answers and empty searches cost no credits. Rewalto for developers explains the API; the developer docs and our India data API guide cover keys, costs and pages of results.

Festive prices by pin code: how deep is the discount?

Availability is half the festive question; the other half is price. Two live datasets answer it at different levels.

At one pin code: the listing search above returns each listing’s newest selling price and MRP read at that pin code, so you can see whether your festive price reached the shelf where your shoppers are, and whether a competitor’s gift pack is cheaper there.

Across the season: the “Festive discount tracker” on /data rolls Rewalto’s own price readings up into one row per brand, category, app and day: how many readings were priced below MRP, and the average, median and deepest discount against MRP. One row covers a brand and category on an app for a day, not a single pin code. Its catalogue entry, as it reads now:⁴

The current coverage and last update of “Festive discount tracker” are read from the Rewalto data catalogue each time this page is served. /data lists them too.

# How deep did your brand discount on one app, day by day, from a day you choose?
curl --fail-with-body -G "https://api.rewalto.com/v1/data/discounts" \
  -H "Authorization: Bearer $REWALTO_API_KEY" \
  --data-urlencode "retailer=<app key, from /v1/data/retailers>" \
  --data-urlencode "brand=<brand as the app writes it>" \
  --data-urlencode "from=<first day, as year-month-day>"

Discounts come back in basis points of MRP: 1,500 means 15% off MRP. Compare your own brand’s median against your category’s, day by day, to see whether a competitor started its festive discount earlier or went deeper. Reads charge the published rate shown above, and an empty page costs nothing.⁴ Our discount depth guide explains how to read the figure without over-claiming.

Because the history starts before the festive run-up, it gives you a baseline. Read your brand’s earliest days as the ordinary level, then read October against it. A median that moves from that level to a much deeper one tells you when festive discounting began; a deepest discount far below the median usually points to one or two packs, not a whole range.

What these checks cannot tell you

A reading shows what a page displayed at a pin code and a time. It does not measure sales, demand or lost sales, and it does not explain why a pack is out of stock. Daily stock history is “Stock state” on /data, which shows whether its daily run is switched on.³

A countdown to Dhanteras

• Now: run the three checks for every festive SKU at your priority pin codes. Fix title, pack-size and MRP mismatches first, and check again after each festive delivery.
• 2 to 5 November: check your priority pin codes daily, including in the evening, when the playbook says festive demand peaks.
• 6 November: Dhanteras.
• 8 November: Diwali.

If you also plan festive ads, settle availability first: our guide on availability before retail media explains why a promoted pack that cannot be bought wastes the spend.

Questions worth settling

Notes

1. Blooprint, “Diwali on Blinkit, Zepto and Instamart 2026: Stock, Ads and Fill Rate Playbook”, published 25 September 2026, read 26 October 2026: blooprint.in. Back to text
2. Inc42, “Inside Dark Store Festive Stock Up Strategy”, published 11 August 2026, read 26 October 2026: inc42.com. Back to text
3. Rewalto /data and the public catalogue (“Prices and stock by pin”), read live each time this page is served, and the pin-code tool page. Back to text
4. Rewalto public catalogue entry “Festive discount tracker”, read live each time this page is served, and the commerce data reference (API contract 0.96.0), read 26 October 2026. Back to text