DMart Data Scraping

A retailer that does not move prices changes the refresh economics

Most grocery and quick-commerce collection is priced on observations per day, because prices move within the day and you need to catch the movement.

DMart runs everyday low pricing. It sets a low price and holds it, rather than running a promotional cycle.

• Daily observation catches almost nothing that weekly would miss.
• Hourly is money spent on identical records.
• The interesting event is a price change, and those are rare enough that a weekly cadence catches them adequately.

We will quote for daily if you want it, and we will tell you it is unlikely to earn its cost. This is one of the few retailers where we actively recommend a lower refresh than a client asks for.

Which makes DMart useful as a reference

A price that rarely moves is a stable floor. For a brand or a competitor tracking Indian grocery, DMart's price on a staple is a benchmark that does not need constant re-observation — which is a genuinely useful property rather than a limitation.

The online range is not the assortment, and this matters more here

Every retailer's online range differs from its store range. On DMart the gap is wider and more deliberate, because the online operation is a supplement to a store-first business rather than a parallel channel.

• The online catalogue is a subset, and not a representative one.
• Fulfilment is pickup-oriented in many areas, which shapes what is listed.
• Serviceability is limited relative to the store footprint.

We collect what is published online, record serviceable as its own state, and do not infer store assortment or store pricing from it.

Why we are firm about that

A client asking for "DMart prices" usually means store prices, because that is where the business is. Delivering online prices labelled as DMart prices would answer a different question than the one asked, and the difference would not be visible in the data.

So we state it on the page, in the fields, and in the pilot. If store-level pricing is what you need, extraction is not the route.

Where DMart fits in an Indian panel

Most Indian grocery engagements centre on quick commerce — Blinkit, Zepto, Instamart and the newer entrants — where prices move constantly and pincode-level collection is the design problem.

DMart sits at the other end of the same market and answers a different question.

• Quick commerce shows what a shopper pays for convenience, at speed, in a pincode.
• DMart shows the value floor that convenience is priced against.
• The gap between them is the interesting number, and it is not obtainable from either alone.

Where a client is running a quick-commerce panel, adding DMart at weekly cadence is inexpensive and gives the panel a reference point it otherwise lacks. That is the scoping we would usually suggest, rather than DMart as a standalone engagement.

The pincode discipline from our India coverage page applies to the serviceable areas, though the panel is smaller because the online footprint is.