Flipkart 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. In the supplied sample, one SKU across 50 Delhi pin-codes came back unavailable in 38 of them — a coverage problem that no pricing report would ever surface.
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 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 — it was populated on all 50 rows of the supplied sample.
Locality alongside the code
locality, city and state carry the readable form, 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 — 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 50 New Delhi pin-codes for a single brand — deliberately deep in one city rather than spread thin.
| Metric | In the supplied sample | What it tells you |
|---|---|---|
| Pin-codes covered | 50 | Every Delhi pin-code on the feed, captured separately |
| Available | 12 of 50 | Where the SKU can actually be bought |
| Unavailable | 38 of 50 | Where the listing exists but cannot be fulfilled |
| EAN code filled | 50 of 50 | Every row joins to your master data by barcode |
Fifty pin-codes in one city 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 Flipkart pin-code records from January 2025 onwards for the pin-codes on this feed.
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 Delhi was fully covered. Pin-code availability said we were unbuyable in thirty-eight of fifty pin-codes in the same city.”
What people use this dataset for
FMCG brands
Verify that your SKUs are genuinely available in the pin-codes your distributors claim to cover.
Sales and distribution teams
Find the pin-codes where a listing exists but cannot be fulfilled, 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 the largest home-grown marketplace in India.
About Flipkart pin-code availability data
Whether a Flipkart product can actually be bought depends on the delivery pin-code — seller serviceability, logistics coverage and local stock all vary. A catalogue-level dataset records one answer and discards the rest.
Deep in one city beats thin across many
The supplied sample covers 50 pin-codes in New Delhi alone. That is deliberate: distribution problems cluster geographically, and sampling one pin-code per city tells you almost nothing about whether a city is covered. Thirty-eight of those fifty came back unavailable — a finding you simply cannot reach from a national or even city-level view.
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 was present on every row of the supplied sample, and it joins cleanly to whatever your supply chain system already uses.
A note on one column name
The availability field is currently spelled stock_avaliblity_status. We would rather you saw that here than in your first delivery. It is being corrected; if you build against it now, tell us and we will keep the old name aliased for you.
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
Your Data Needs
-
Free Sample in 2 HoursShare your requirement, get 500 rows of real data — no commitment.
-
Plans from $500/monthFlexible pricing for startups, growing brands, and enterprises.
-
US-Based SupportOffices in New York & California. Aligned with your timezone.
-
ISO 9001 & 27001 CertifiedEnterprise-grade security and quality standards.
