How to run a digital shelf audit yourself

The short answer

A digital shelf audit is a repeated, dated reading of how your products appear on the apps that sell them: whether each one is in stock, what it costs against its MRP, where it sits in search, and whether the listing is complete. You can run one yourself with a fixed list of products, apps and pin codes, a simple record of each reading, and a regular day to repeat it.

Rewalto does not sell a shelf audit as a service. This guide is the method, so your own team can run it. If you would rather not collect the readings by hand, the last section says where dated records can come from instead.

What a digital shelf audit is

It answers one question with evidence instead of a guess: what does a shopper in one pin code, on one app, at one time, see when they look for your product?

The word "shelf" is borrowed from a physical store on purpose. A brand that would never accept a bare shelf or a wrong price tag in a supermarket often has no such view of Blinkit, Zepto or Amazon. There, the shelf is different for every app, every pin code and every hour. See pin-code shelf truth for why the pin code changes what a reading shows.

What to read, together rather than apart

A single reading of a listing is a snapshot of a moment. The value comes from reading several things about the same product at the same time, so they can be compared rather than judged alone.

• Availability: in stock or not, at that pin code and that moment, not averaged across a city.
• Price: selling price and MRP together, so a discount can be read against the MRP it was calculated from.
• Search rank: where the listing sits for the terms a shopper would actually type, and whether that position is organic or sponsored.
• Listing content: whether title, images, pack size and description are present and match the same product on other apps.

How to run one yourself, step by step

Start small and keep it fixed. An audit you can repeat exactly is worth more than a large one you run once.

• Pick the list: the products you are measured on, the apps that sell them, and a handful of pin codes in the cities that matter most. Write the list down and do not change it between rounds.
• Set the shopper: on each app, set the delivery location to the pin code before you search, and search the words a shopper would type, not your internal product name.
• Record each reading on one row: date and time, app, pin code and product. Then add stock, selling price, MRP, position in the results, whether that slot was an ad, and a screenshot.
• Repeat on the same day and time each round, then compare rows for the same product, app and pin code across rounds, not one round against your memory of the last.

Mistakes that make a hand reading wrong

Most errors in a home-made audit come from the reading, not the record. Four are common enough to check for every round.

• The wrong location: an app keeps the last delivery address it was given, so a reading taken without resetting it describes a different pin code from the one on the row.
• A different pack: the same product often has several pack sizes and multipacks. Record the pack you meant, and treat a missing pack as missing even when another size shows.
• Counting ads as rank: a sponsored slot can sit above every organic result. Note which slots are marked as ads and count organic position apart from them.
• Reading at different times: stock on quick-commerce apps can change between the morning and the evening. Two rounds taken at different hours can disagree with no real change behind it.

Reading the results across rounds

One round tells you what a shopper saw on one day. The audit starts to be useful from the third or fourth round, when you can see which gaps repeat. A product out of stock at one pin code once is a data point. The same product out of stock at the same pin code every week is a problem worth raising with the account team.

Keep each round's rows as they were taken and add new rows rather than editing old ones. When a figure looks wrong later, the screenshot and the time on the original row are what let you check it. Then sort the rows by product and pin code, and mark the changes: a product that went out of stock, a price that moved against its MRP, a listing that dropped down the results.

Choosing how often to read

The right frequency depends on how quickly the thing you are watching can change. Price and stock on quick-commerce apps can move within a day, so a question about today's promotion needs a same-day or next-day reading. Whether a listing's content is complete changes far more slowly, and a monthly check is usually enough.

Split your fields. Read price and availability as often as they change in your category. Read listing content and search rank less often, unless you are mid-launch or mid-promotion.

Who uses the results, and for what

An e-commerce or digital-shelf manager is usually first, because they answer for how listings perform and rarely have more than spot checks. A category or brand manager tends to want a narrower answer: is a promotion showing as agreed, or is a rival discounting harder than it seems?

Key-account teams use the same rows when a retailer's buyer disputes stock, price or ranking: a dated record of what the app showed is a better starting point than a general complaint. Decide at the start which of these jobs the audit is for, because it sets which products, apps and pin codes go on the list.

What a shelf audit cannot tell you

It records what a listing showed, not why. It cannot say whether a rival funded a discount, why an app ranked a listing where it did, or whether a stockout cost a sale. A reading can inform those questions but not answer them alone.

It is also not a sales or margin figure. A product that is in stock, correctly priced and well ranked can still sell poorly for reasons the shelf does not show. Treat the audit as evidence about what a shopper was shown, and keep that apart from claims about outcomes.

Guides for each part of the audit

Each reading in the audit has its own guide. For search, read organic rank on Blinkit and Zepto, why organic rank 1 is not position 1 and how to tell a rank drop from a delisting. For how much of the results you fill, read digital share of shelf and share of search on quick commerce. For retailer own brands beside yours, read private label on Indian apps.

If the audit feeds an ad budget, start with Blinkit and Zepto ads: five checks before you spend, then checking stock by pin code before you pay for ads, who verifies ad ROAS and the festive bid premium. For the measures behind a repeated audit, read what digital shelf analytics measures, see digital shelf analytics for what Rewalto supplies, and browse digital shelf insights.

Where the readings can come from

Reading by hand is real evidence and the right place to start. It stops scaling at a few dozen products and pin codes, and it is easy to drift from one round to the next. The alternative is to start from records someone else has already read and dated.

As of 31 October 2026, Rewalto held readings from 18 apps and marketplaces across 5,482 pin codes, each with the time it was read. Check the fields, coverage and freshness for your own list in Data before you plan around it.

Start with one product, one app and one pin code you already read by hand, and compare. If the records answer your question, widen the list from there.

Common questions