Amazon India Weekly Pin-Code Level Pricing & Availability Dataset
A weekly file keyed on pin-code rather than product. Thirteen clean columns — ZIP code, locality, city, SKU name, product name, MRP, price, discount and stock availability — with one row per product per pin-code.
This is the leanest of our Amazon files and the one to take if the question you are answering is geographic. Price and availability on Amazon.in vary by delivery pin-code, and a catalogue-level file averages that away entirely.
The file already exists, because this pipeline runs every week whether you buy it or not. Most vendors start collecting after you order — which is why they quote a lead time. Here the most recent file is in your account within minutes of payment, with an API key issued at the same time.
What you get, in plain terms
Four things. This file is deliberately narrow — if you need a deep catalogue extract, take the daily feed instead.
One row per product per pin-code
The grain of this file is geographic. The same SKU appears once for every pin-code it is tracked in, each with its own price and stock flag.
Clean, flat pricing columns
MRP, Price and Discount (%) as plain numbers. No JSON, no parsing, nothing to unpack before you can group by ZIP.
Locality alongside the code
Locality carries the readable form — pin-code, area and state — so reports do not need a separate lookup table to be legible.
However you want it
Direct download, REST API, Amazon S3, Google Cloud, Snowflake or SFTP. The API key comes with the dataset.
Fields included in this dataset
All 13 columns, in the exact order they appear in the file — this list is taken straight from the sample, not from a brochure. The free sample ships with a data dictionary giving an example value for each one.
Sample rows from the real file
Real rows from the sample file, not an illustration. The free sample is 50 product-by-pin-code rows with all 13 columns.
Coverage
Tracked across Delhi NCR pin-codes in the supplied sample, expandable to any metro on request.
| Pin-code | Locality | City | Products tracked |
|---|---|---|---|
| 110001 | Connaught Place | New Delhi | 8,100 |
| 110003 | Lodhi Colony | New Delhi | 7,940 |
| 110006 | Chandni Chowk | New Delhi | 7,620 |
| 110007 | Kamla Nagar | New Delhi | 7,480 |
| 110008 | Karol Bagh | New Delhi | 7,910 |
| 110010 | Delhi Cantt | New Delhi | 6,850 |
Need other cities or a wider pin-code set? That is the usual request on this dataset and it is a straightforward extension — tell us which pin-codes matter and we will price it.
Historical data
The last 30 days come with the dataset. Beyond that we hold records from March 2025 onwards for the pin-codes on this feed. Ask and we will confirm exactly what exists for yours.
Ask about historical dataNeed more data points?
We can extend this dataset beyond the standard 13 columns — more pin-codes is the most common request, followed by category and brand hierarchy, seller name and ratings joined in. Tell us what you would query and we will say whether it is collectable before anything else happens.
Request custom fields“We had national Amazon pricing and it told us nothing about why the same SKU converted differently across Delhi. Splitting it by pin-code took an afternoon once the data arrived in that shape.”
What people use this dataset for
Brands with regional pricing
See what a customer in a specific pin-code is quoted, rather than a national average that matches nobody.
Quick commerce and grocery teams
Compare price and availability across delivery areas in the same city, week over week.
Expansion and distribution teams
Check where your SKUs are actually listed and in stock before committing trade spend to an area.
Analysts
Build a clean geographic price series without having to reshape a catalogue-level extract first.
About pin-code level Amazon pricing
Price and availability on Amazon.in are not national facts. Delivery pin-code changes which sellers can serve you, which shipping options appear and, on many listings, what the price is. A catalogue-level dataset records one of those prices and discards the rest.
Why one row per pin-code
Because reshaping later is painful and lossy. If the file gives you one row per product, adding geography means re-collecting. If it gives you one row per product per pin-code, collapsing to a national view is a group-by that takes seconds. This file is built at the finer grain deliberately.
What this file deliberately leaves out
There is no category tree, no seller name, no ratings and no search position in these 13 columns. That is not an oversight — it is why the file is cheap and fast to work with. If you need those, the daily 25-column feed carries them, and the two join on product identifier.
Why weekly rather than daily
Pin-code level delivery quotes do not move hourly the way marketplace listings do. A weekly reading is enough to see stock-outs appear and clear, and to compare areas against each other, without paying for repetition. If you need daily pin-code capture, ask — it is available and priced on the pin-code count.
Is collecting this data legal?
Collecting publicly visible product and price information is generally lawful in most jurisdictions. Actowiz collects only public pages, respects robots.txt and platform terms, holds no personal data, and aligns with GDPR and CCPA. We are ISO 9001 and ISO 27001 certified, and this dataset carries documented provenance so your legal team can review the source before you buy.
Frequently asked questions
Related datasets, same field names
These join to the file above without any reconciliation work, which is why most buyers take more than one.
