datawebotWalmart product data: items, offers, and availability
Map Walmart item identifiers, Marketplace sellers and fulfillment; compare condition, variants, price and destination availability with current terms and API boundaries.
A Walmart item and a Walmart offer answer different questions
A Walmart item page can connect product details with one or more seller offers and buyer-facing fulfillment choices. Keep catalog identity, the selected seller and condition, who fulfills the order, and the buyer context as linked fields. Walmart's seller labels help distinguish the seller from the fulfillment provider.
Scroll to compare →
| Record layer | Fields to preserve | Comparison decision |
|---|---|---|
| Catalog item | Page URL and path identifier; title; brand; GTIN/UPC when shown | Match model, pack size, edition, and other item attributes before comparing offers. |
| Seller offer | Displayed seller; condition; offer price and currency; comparison price when shown | A seller or condition change is an offer change, not automatically a product change. |
| Fulfillment | Sold-by and shipped-by labels; shipping, pickup, or delivery choice | Keep seller identity separate from the party that stores or ships the item. |
| Observation | Selected offer; destination or store; fulfillment choice; capture time and source URL | Interpret price and availability only in the captured buyer context. |
Keep Walmart and seller identifiers typed
Walmart public pages and Marketplace seller-catalog responses may expose different identifiers. Preserve each raw value with its field name and source. Do not assume the numeric portion of a page URL, Marketplace itemId, WPID, seller SKU, and GTIN/UPC are interchangeable.
Scroll to compare →
| Identifier | Where it belongs | Matching guidance |
|---|---|---|
| Public page path ID | The value embedded in a Walmart.com item URL | Keep the complete URL and label the value as page-path context; do not silently map it to an API field. |
| Marketplace itemId | Walmart item data in an authorized Marketplace workflow | Preserve the API field name, seller context, and source response. |
| WPID | A distinct Walmart product identifier documented in seller-catalog responses | Keep separate from itemId, GTIN, and seller SKU unless source documentation defines a relationship. |
| Seller SKU | A seller's own catalog and inventory reference | Scope it to the seller; another seller may use a different SKU for the same trade item. |
| GTIN or UPC | A trade-item identifier when present | Check pack quantity, model, edition, and condition before treating records as equivalent. |
Variants and condition change what counts as a match
Walmart documents variants as separate items connected by variantGroupId and variant attributes. A shared group expresses a relationship; it does not make sizes, colors, pack counts, or seller offers interchangeable. Marketplace condition choices can depend on category and seller eligibility.
Scroll to compare →
| Observed relationship | Example interpretation | Safe comparison rule |
|---|---|---|
| Shared variantGroupId | Two item records in one group have different size or color values | Compare the same variant attributes; retain each variant's item ID and seller SKU. |
| Same base item, different condition | A New offer and a Pre-Owned or Restored offer appear for related merchandise | Keep condition at offer level and analyze the conditions separately. |
| Same item, different seller | A Walmart-sold offer and a Marketplace-seller offer refer to the same catalog item | Preserve each seller and fulfillment label as its own offer record. |
| Similar title, different pack or model | Two descriptions look alike but quantities or model details differ | Validate GTIN/UPC and source attributes; title similarity alone is not a match. |
Price and availability belong to a buyer context
Shipping, pickup, and delivery options can depend on the item and selected destination or store. Walmart's terms say price and availability are not confirmed until an order is placed. Treat a page as a time-bound observation, not a final checkout amount or exact inventory count.
Scroll to compare →
| Context field | Why it matters | How to compare |
|---|---|---|
| Destination or store | Eligibility and availability can differ across addresses and stores | Compare observations only when the location context is known. |
| Fulfillment method | Shipping, pickup, and delivery are different buyer choices | Retain the selected method and avoid merging delivery estimates into item attributes. |
| Seller, condition, and currency | Different offers can have different prices and terms | Match the same seller and condition, or explicitly compare offers as a group. |
| Displayed price and capture time | Prices and availability can change before checkout | Record the display time and source URL, then verify again before a purchase decision. |
A public page and a seller API serve different jobs
A public Walmart.com page presents buyer-facing item and selected-offer information. Marketplace APIs support authorized seller or approved solution-provider workflows for seller catalog and operations data, using OAuth and seller authorization. They are not anonymous access to a seller's private catalog.
Scroll to compare →
| Source | Useful for | Boundary |
|---|---|---|
| Walmart.com item page | Visible item details, seller labels, condition, and buyer-facing fulfillment choices | It does not establish the seller's complete catalog or exact inventory by itself. |
| Marketplace seller APIs | An authorized seller's catalog, prices, offers, and inventory operations | Use the documented seller authorization and keep seller SKU and any ship-node context. |
| Approved solution-provider workflow | A seller-authorized integration acting for its Marketplace customers | Approval and seller permission are part of the access model; do not infer access from a public page. |
Read robots.txt together with the posted terms
The Walmart robots.txt copy reviewed October 8, 2026 has a wildcard group that disallows paths including /search and /api/. Walmart’s Terms of Use prohibit commercial use and systematic downloading or storage of Materials. They also prohibit specified automated or manual retrieval, scraping, data mining or gathering without express prior written consent. A robots rule does not grant access or reuse rights under the terms.
Scroll to compare →
| Evidence | What it says | What not to infer |
|---|---|---|
| robots.txt | The reviewed file lists crawler directives, including disallowed search and API paths | Do not infer permission for an unlisted path such as an item page. |
| Terms of Use section 2(b) | The posted terms describe restrictions on commercial use, systematic downloads, and automated retrieval or data gathering | Do not treat visible page content as permission to collect, store, or redistribute it. |
| Authorized access | The terms identify express prior written consent for the covered restricted uses | A public URL, seller API documentation, or robots directive is not itself that consent. |
Build a comparison record only for an authorized use
The right fields depend on the question. A cross-retailer price comparison needs item equivalence and buyer context; a Marketplace offer comparison needs seller and condition; variant analysis needs item-level attributes; seller operations use the seller's authorized catalog and inventory context. Keep the intended use and source rights with the record.
Scroll to compare →
| Research question | Fields to retain | Useful next step |
|---|---|---|
| Is this the same product elsewhere? | GTIN/UPC when present; model and pack attributes; Walmart page URL; match confidence | Validate identity before interpreting a price difference. |
| How do offers differ? | Item ID; seller; condition; fulfillment label; displayed price and currency | Compare offers separately from the catalog item. |
| How do variants relate? | variantGroupId; item ID; option names and values; seller SKU when authorized | Keep each variant record distinct within the group. |
| What did a buyer see? | Destination or store; fulfillment choice; timestamp; displayed values; source URL | Keep the observation context and authorization basis attached. |
Content reviewed 2026-10-07.