An illustrative view of how product, offer, seller and co…
.
Data Marketplace · Commerce & retail
Connect Walmart catalog, price, seller, fulfilment, rating, and availability records across selected products, categories, and locations.
.
{
"product_id": "illustrative-1042",
"title": "Illustrative countertop mixer",
"price": 84.5,
"currency": "USD",
"fulfilment": [
"delivery",
"pickup"
],
"availability": "available",
"captured_at": "2026-08-07T10:15:00Z"
}Schema and fields
Start with product, offer, seller. Source identity, collection time, and field meaning stay connected so records can move into analysis without losing their context.
product_id stringSource product identity
title stringDisplayed product name
price decimalObserved selling price
currency stringDisplayed currency
seller stringDisplayed seller
fulfilment arrayObserved delivery or pickup options
availability stringObserved stock state
captured_at timestampCollection time
Records in this collection
Explore the Walmart on-demand API
Product
Offer
Seller
Fulfilment option
Review summary
Freshness and delivery
Refresh the same market, store, and fulfilment context on the schedule used for pricing and availability analysis.
Snapshot Start from a dated baseline Selected scope and collection window
Refresh Receive recurring updates Cadence and change behavior
Format Use JSON, CSV, or Parquet Schema, partitioning, and manifest
Validation Run repeatable checks Counts, fields, missing states, and version
Walmart applications
Use source-linked, time-stamped records for retail price monitoring, plus fulfilment visibility. Each application starts from the same documented fields and collection context.
01
Compare displayed prices and promotions across a controlled product and market scope.
02
Track observed pickup, delivery, and availability states with their location context.
03
Study seller participation, offer changes, and catalog position over time.
From sample to production
Start with representative rows, run the joins and calculations that matter, and shape delivery around the system that will consume the data.
01
Select the entities, markets, fields, dates, and business output the collection should support.
02
Check identifiers, fields, joins, missing states, and source context with your own queries or models.
03
Choose the snapshot or recurring schedule, file format, partitions, manifest, and destination.
Walmart dataset FAQ
Connect Walmart catalog, price, seller, fulfilment, rating, and availability records across selected products, categories, and locations. Core records include product, offer, seller, fulfilment option, review summary.
Common applications include retail price monitoring, fulfilment visibility, marketplace seller research. Start with the fields and time window required by the business output.
Refresh the same market, store, and fulfilment context on the schedule used for pricing and availability analysis.
Use the on-demand API when your application chooses individual requests and timing. Choose this dataset for a prepared bulk snapshot or recurring file delivery.
Continue the data journey
Compare the adjacent dataset, open the source API, or continue into the relevant data, industry, and solution pages.
Start with real records
Tell us which product and offer data you need, plus the markets, fields, dates, and destination. We will map the collection to that requirement.