JioMart India Weekly Pin-Code Availability & Distribution Dataset
A weekly file answering one question properly: is this SKU actually available in this pin-code? Thirteen columns with pin-code, city, state, locality, SKU, EAN code, brand, product name and stock status — one row per SKU per pin-code.
There is no price in this file, and that is deliberate. It is a distribution dataset. If you are a brand asking where your products are genuinely listed and in stock outside the metros, price is not the question you are trying to answer.
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 narrow by design — if you need pricing, say so and we will add it.
One row per SKU per pin-code
The grain is geographic. The same product appears once for every pin-code tracked, each with its own stock status.
EAN code on nearly every row
This is the column that makes the file joinable. Match against your own master data by barcode rather than fuzzy-matching product names.
Beyond the metros
The supplied sample covers Punjab towns — Dasuya, Majitha, Jalandhar — not Mumbai and Bengaluru. Distribution questions are usually about exactly these places.
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 — 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 SKU-by-pin-code rows with all 13 columns.
Coverage
Captured weekly across the pin-codes on your feed. The supplied sample covers Punjab; the live feed scales to whatever set you need.
| Pin-code | Locality | City | State | SKUs tracked |
|---|---|---|---|---|
| 144305 | Dhugga Kalan | Dasuya | Punjab | 21,400 |
| 143602 | Jhanjian Khurd | Majitha | Punjab | 20,800 |
| 144025 | Jandu Singha | Jalandhar | Punjab | 22,100 |
Three pin-codes is what the sample shows, not what the feed is limited to. Tell us which pin-codes matter — that count is the main thing that drives the price, and most clients run several hundred.
Historical data
The last 30 days come with the dataset. Beyond that we hold JioMart records from April 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 — price and MRP capture is the most requested addition, along with category hierarchy, seller name and a wider pin-code set.
Request custom fields“Our distributor reports said full coverage across the state. Pin-code availability data said two of our five SKUs were missing from half the towns we were paying to serve.”
What people use this dataset for
FMCG brands
Verify that your SKUs are actually listed and in stock in the towns your distributors claim to cover.
Sales and distribution teams
Find the pin-codes where a listing has silently dropped out, before the sales number tells you.
Category teams
Compare your availability against competitor brands in the same pin-code, week over week.
Analysts
Build a real distribution series for a platform whose reach extends well past the metros.
About JioMart distribution data
JioMart is Reliance Retail's online grocery platform and reaches considerably further into small-town India than most of its competitors. That reach is what makes availability data from it useful: it is one of the few online sources that says anything meaningful about distribution outside the top twenty cities.
Why a file with no prices in it
Because the question is different. A brand asking whether its product is stocked in a particular town does not need a price — it needs a yes or no, by SKU, by pin-code, every week. Adding price columns would double the collection cost to answer a question nobody asked. If you do need pricing, it is a straightforward extension and we will quote it.
Why the EAN code matters more than the product name
Product names on retail platforms are inconsistent, abbreviated and frequently changed. Matching your master data against them by string is a losing game. ean_code is present on 96% of rows in the supplied sample, and it joins cleanly to whatever your supply chain system already uses.
Reading the availability column
stock_avaliblity_status is a plain Yes or No — note the spelling, which is as it appears in the file. In the supplied sample 44 of 50 rows were available and 6 were not, and the unavailable rows were not clustered in one place. That scatter is the normal pattern and the reason weekly capture is worth having.
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.
