QuickCommerceData

Methodology

Sources, schema, refresh cadence, and known limitations — documented for researchers, CPG teams, and investors.

Current catalogue snapshot

Platforms

6

Cities indexed

549

Dark stores

6,200

Product SKUs

6,12,912

Brands

27,504

Public pages revalidate every 4 hours after ingest.

What we publish

QuickCommerceData is the catalogue and geography layer of the QuickCompare product family. We normalize product SKUs, brand presence, category trees, and dark store coordinates across Blinkit, Zepto, Swiggy Instamart, BigBasket, DMart Ready, Flipkart Minutes, and FirstClub into one schema you can browse on the web or license as datasets.

Data sources

  • Platform-facing catalogue and store metadata collected on a recurring schedule and stored in PostgreSQL.
  • Brand and category rollups derived from the normalized product table (not hand-curated brand lists).
  • Dark store coordinates from the store registry — geocoded fulfilment nodes used for coverage maps.
  • Live price and ETA lookups remain on the QuickCommerce API (quickcommerceapi.com); this site focuses on catalogue depth and geography.

Normalized schema

  • Products: platform, product ID, name, brand, MRP, category, subcategory, images, last seen timestamp.
  • Brands: national SKU counts and per-platform assortment stats (categories, MRP range).
  • Stores: platform, city, coordinates, area label, active flag.
  • Cities & platforms: rollups linking stores and SKUs to browsable hub pages.

Refresh cadence

Public hub pages and dataset quote counts are cached and revalidated on a fixed interval. Store maps and product samples reflect the latest successful catalogue ingest — not second-by-second platform changes.

Dataset exports and API search results can differ: exports are point-in-time snapshots; the API returns live shelf data for a lat/lon.

Accuracy & limitations

  • City slugs merge common aliases (e.g. Bangalore → Bengaluru) so coverage is not double-counted across spellings.
  • Product counts are distinct SKUs per platform; the same physical item may appear as multiple rows across apps.
  • Store counts include indexed fulfilment nodes; a closed store may remain until the next ingest marks it inactive.
  • Sample tables on brand and product pages show the first 25 rows; licensed exports include the full filtered set.

API vs datasets

Use QuickCommerce API for real-time search, item detail, and delivery ETA at a coordinate. Use QuickCommerceData for national assortment, brand share, store maps, and bulk CSV/API dataset delivery.

Developer APIBrowse datasetsResearch guides