Flipkart India Twice a Day Product, Pricing & Category Dataset
Two captures a day of the Flipkart catalogue — 22 columns covering price, MRP, discount, sold-out status, shipping, promised arrival date, ratings, a structured three-level category hierarchy and the POP UPI product identifier.
One behaviour to plan for: in the supplied sample, price fields are populated on the 32 in-stock rows and empty on the 18 sold-out ones. That is correct — an unbuyable listing has no price to record — but it means an inner join on price will silently drop your stock-out rows.
The file already exists, because this pipeline runs twice a day 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. Take this file rather than a daily one if you are watching price movement within the day.
Two readings every day
Morning and evening, each with its own scrape timestamp. Enough to catch a price change that reverses before the next day.
Category tree as structured JSON
category_hierarchy arrives as l1/l2/l3 — Baby → Potty Training → Wet Wipes — rather than a breadcrumb string you have to split.
UPI product identifier included
POP UPI Product ID is populated on every row of the supplied sample, which matters if you are reconciling against payment-side records.
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 22 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 listings with all 22 columns.
Coverage
Captured twice a day across the catalogue on your feed. The supplied sample is weighted towards baby and personal care, where price competition is most active.
| Field | Filled in sample | Why it is not always there |
|---|---|---|
product_name |
50 of 50 | Always present |
POP UPI Product ID |
50 of 50 | Structural identifier |
avg_rating |
46 of 50 | Only on products with at least one rating |
mrp / product_price |
32 of 50 | Empty on sold-out listings — there is no price to record |
discount |
31 of 50 | Empty when not discounted, and on sold-out rows |
page_url / position |
0 of 50 | Populated only on search-sourced rows |
These are counts from the 50-row sample, not guarantees. Download it and check the fields you actually need — five minutes there prevents almost every problem we see.
Historical data
The last 30 days come with the dataset, at full twice-daily granularity. Beyond that we hold Flipkart records from January 2025 onwards — enough to cover two Big Billion Days cycles.
Ask about historical dataNeed more data points?
We can extend this dataset beyond the standard 22 columns — seller name and Buy Box winner is the most requested addition, along with keyword rank, coupon data joined in and your own product list captured more often.
Request custom fields“Half our reporting broke because we joined on price and lost every sold-out row. Once we understood the file that was a one-line fix, but nobody had told us.”
What people use this dataset for
Brands selling on Flipkart
Track price, discount depth and availability on your own listings and the competitive set.
Pricing teams
Benchmark Flipkart against your other channels, with MRP and discount kept as separate fields.
Category managers
Watch assortment and discount shift within a sub-category, and see where sold-out listings cluster.
Analysts
Category-level price and rating series for demand estimation and festive-season analysis.
About Flipkart marketplace data
Flipkart is the largest home-grown marketplace in India and the main competitor to Amazon.in. Its category tree is deep and its promotional calendar is aggressive, which makes both the shape of the category field and the frequency of capture matter more than they would on a single-retailer site.
Empty price fields on sold-out rows are correct
In the supplied sample the 32 in-stock rows carry MRP, price and discount, and the 18 sold-out rows do not. An unbuyable listing has no price to record, and filling it with zero would read like a measurement. Plan for it: use a left join from your product list rather than an inner join on price, or you will silently drop exactly the rows that tell you about stock-outs.
Why the category hierarchy is JSON
A breadcrumb string forces you to guess where one level ends and the next begins, and the separator changes between departments. Here category_hierarchy arrives as an object with l1, l2 and l3 keys, so a group-by on department is a field access rather than a regular expression you have to maintain.
A note on the source label
The source column in the supplied sample carries a value that does not match this platform. It is a configuration label rather than part of the data, and it does not affect the product, pricing or category columns — but it is being corrected, and we would rather point at it here than have you find it yourself.
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.
