Quick Commerce Data: Tracking Blinkit Prices & Stockouts by Pin Code
Quick commerce changed how Indian households buy milk, paneer and everyday groceries. Orders are served from small local warehouses, so what a shopper sees depends on where they are. For brands, retailers and analysts, quick commerce data is the way to see those prices and shelves at scale instead of checking an app by hand.
To make this concrete, we collected a free sample of 60 Blinkit dairy listings and published it as a CSV on the Blinkit dairy prices dataset page. This article covers what the sample shows, what it deliberately does not show, and how a pin code level collection works in practice.
A note on scope first. Our sample was captured without a delivery pin code selected, so it contains prices, MRP and discounts but no stock status or delivery time. We explain below why those fields need a location and how to collect them.
Why quick commerce data matters
Quick commerce platforms such as Blinkit sit between the brand and the shopper, and they set the price the shopper sees. That makes the listing page a useful public signal:
- Brand teams check whether their products are listed below MRP and by how much.
- Retailers and marketplaces compare their own shelf prices against a fast-moving competitor.
- Investors and researchers track assortment and discount behaviour across categories.
- Distributors look at pack-size mix to see which formats the platform pushes.
None of this needs private data. It is the same information any visitor sees on a category page.
What our Blinkit sample shows
The sample covers two categories on Blinkit's dairy aisle: Milk and Paneer & Tofu, with 30 products each. All figures below are computed from the 60 rows of the CSV and describe this sample only, not Blinkit's full catalog.
- Price range: selling prices run from ₹10 to ₹399, with a mean of ₹94.7 and a median of ₹90.
- Discounts: 21 of 60 products (35%) are sold below MRP. The average discount among those is 16.2%, and the deepest is 40.4%.
- Deep discounts: 8 of the 21 discounted products are 20% or more below MRP, while 7 are under 5%.
- Category gap: Milk has a median price of ₹46.5 and only 4 of 30 products below MRP. Paneer & Tofu has a median of ₹110 and 17 of 30 below MRP, with an average discount of 18.9% among those.
- Brand mix: Amul has 17 of the 60 listings, followed by Mother Dairy with 9 and Country Delight with 5.
- Pack sizes: the most common pack is 200 g (23 listings), then 1 ltr (9) and 500 ml (8).
The pattern is clear in this sample: staple milk is mostly sold at MRP, while the paneer and tofu shelf carries most of the discounting. A short excerpt:
| product_id | title | pack_size | price_inr | mrp_inr | discount_pct |
|---|---|---|---|---|---|
| 19512 | Amul Taaza Toned Milk | 500 ml | 30 | 30 | 0 |
| 12872 | Amul Gold Full Cream Milk | 500 ml | 36 | 36 | 0 |
| 526785 | Ananda Cow Paneer | 180 g | 78 | 90 | 13.3 |
| 192 | Mother Dairy Paneer | 200 g | 100 | 100 | 0 |
| 28169 | Milky Mist Paneer | 200 g | 91 | 140 | 35.0 |
The Milky Mist row shows why the MRP column matters. The selling price alone says ₹91. With MRP, you also see that the shopper gets 35% off, which is the number that moves purchase decisions.
Pin code level pricing and stockouts
Quick commerce is local. Each order is fulfilled by a nearby dark store, so two shoppers in different neighbourhoods can see different assortments, prices and delivery estimates. That is why pin code level pricing is the core of any serious quick commerce tracking project.
Three fields depend on the location:
- Stock status. A product can be listed but unavailable in one area and in stock in another. The share of out-of-stock products per pin code is a direct measure of shelf availability.
- Delivery time (ETA). The promised minutes change with the store and with demand.
- Price and MRP. Most staples keep one MRP, but selling price and offers can vary.
Our free sample does not include these three fields, and we would rather say so than invent them. A full collection sets the delivery location first, then records price, stock and ETA for each product, per pin code. Running the same category across several pin codes gives you a stockout rate and an average ETA per area.
Which fields matter and why
If you are designing a quick commerce dataset, these are the fields that earn their place:
- product_id: the stable key for tracking one item across days and pin codes.
- title, brand, pack_size: needed to match the same product across platforms. Pack size is essential for price-per-unit comparison.
- price_inr and mrp_inr: together they give discount depth, the most-watched number in this market.
- discount_pct: computed from the two prices, so analysts can sort and filter quickly.
- in_stock, eta_minutes, pincode: the location layer. Without them you have a catalog, not a service-level view.
- scraped_at_utc: every comparison is only valid with a timestamp.
Use cases
Price monitoring for brands. Track whether your SKUs are sold at MRP or below it, and which competitors discount in the same category.
Availability tracking. Measure stockouts by area to find where a brand loses sales because of supply, not demand.
Competitive benchmarking. Compare quick commerce prices with supermarket pricing. If you work on that side, see our grocery price monitoring example with Tesco data for a similar workflow in the UK.
Market entry research. New brands use listings to learn the typical price points and pack sizes before they launch.
Common challenges in Blinkit scraping
Blinkit scraping is harder than scraping a static catalog, and the difficulties are worth knowing before you plan a project:
- Location dependence. Without a delivery location the page shows a generic view. Pin code level data requires setting the location for each run.
- Partial server-rendered lists. In our sample, each category page returned 30 product cards in the page source. A larger collection needs several categories or a way to load more items.
- Layout changes. Cards, badges and discount labels change often. We saw discount badges inserted before the product title, which can shift naive parsers by one field.
- Anti-bot measures. Consumer apps rate-limit and block repeated requests. Managed infrastructure with residential IPs and rendering is usually required for steady collection.
- Data quality. Category IDs can return unrelated products, so each page needs checking. We discarded one category page during this build because its listing did not match dairy.
If you are looking for a partner in the Indian market, our overview of India data provider services explains what such a project usually includes.
How often to refresh
Quick commerce moves faster than traditional retail. As a rule of thumb:
- Daily for price and discount tracking on a fixed set of categories.
- Several times a day when you track stockouts or ETA, because availability changes through the day.
- Weekly for assortment and brand-mix research.
Always store each run with its timestamp and pin code so you can build a history instead of overwriting it.
FAQ
Can you scrape Blinkit prices by pin code? Yes, the location can be set for each collection run, and the output then records price, availability and ETA for that area. Our free sample was captured without a pin code and does not include those columns.
Does the sample include stockouts? No. Stock status depends on the delivery location, so it is not in this sample. A pin code level project would include it.
What does selling below MRP mean? In this sample, no product is sold above MRP. Where selling price is lower than MRP, the discount_pct column shows the gap as a percentage.
How many records can I get? The free sample has 60 rows. Full datasets can cover more categories and pin codes, depending on your target.
Get a sample of your own target
You can download the free Blinkit sample CSV and check the columns yourself. If you want quick commerce data for your categories, cities or competitors, request a free sample of your own target. You can also see our pricing: datasets from $49.
Author: DataHarbor Team