Walmart Price Tracker

Affiliate disclosure: Apify links on this page may include referral parameters. If you sign up through them, TrueFetch may receive a commission at no extra cost to you.

Walmart Price Tracker is a ready-to-run Apify Actor for collecting current public Walmart.com search results as structured US retail and marketplace records, helping teams compare USD prices, savings, sellers, fulfillment signals, ratings, and source evidence without manual copying.

• Current US scope: Search the supported United States Walmart storefront with an explicit keyword and result ceiling.
• 58 normalized fields: Keep product identity, price, discount, seller, fulfillment, rating, source, and processing context together.
• Marketplace traceability: Preserve product URL, search URL, query, rank, seller, condition, and sponsored status when available.
• Automation-ready output: Export from Apify, schedule snapshots, call the API, or connect the Actor to an MCP client.

Run a minimum 10-result test with a specific product model before scaling. For code examples tied to your account, use the API tab.

What does Walmart Price Tracker do?

Walmart Price Tracker searches public Walmart.com product results for your keyword. It reads marketplace entries in page order, follows public product pages when additional information is available, removes duplicate URLs, normalizes the results, and stores up to the requested maximum. The Actor provides current search observations rather than an automatic historical-price database.

Records can include title, brand, Walmart item ID, product type, current price, original price, discount, unit price, badges, condition, seller, rating, review count, stock and fulfillment text, variants, specifications, images, product URL, source search URL, query, sponsored status, rank, and processing time. All rows share 58 schema fields, but optional fields remain null when Walmart does not expose a reliable value.

Walmart.com combines Walmart retail offers and third-party Marketplace sellers. Similar titles may differ by seller, condition, package quantity, variant, fulfillment, or included items. The Actor keeps these clues beside the price; it does not declare two records identical merely because the names resemble each other.

Every run is time-bound. Walmart's own terms state that listings, specifications, prices, and availability may change without notice and may differ from store information. Preserve timestamps and source links, and verify consequential decisions at the live listing.

How do I run Walmart Price Tracker?

Open Walmart Price Tracker on Apify, provide all three required fields, and start the run. This guide uses one consistent scenario:

{
  "keyword": "Dyson V15 Detect vacuum",
  "country": "United States",
  "max_results": 10
}

The schema minimum for max_results is 10. This value is an upper bound, not a guaranteed row count. A run can store fewer records when public results are limited, repeated, unavailable, or missing a publishable title and product URL.

Review the first Dataset before scheduling. Confirm that results belong to the intended Dyson V15 Detect vacuum family, not replacement filters, attachments, refurbished units, unrelated models, or bundles. Compare condition, seller, variant, package contents, fulfillment, and warranty before interpreting a price difference.

For price history, schedule runs and retain each Dataset externally. Match records using reviewed product IDs or canonical URLs and keep seller and condition in the key. The Actor does not merge past runs or label a price as a lasting markdown.

What data does Walmart Price Tracker return?

The default Dataset exposes 58 normalized fields. Field names stay stable even when Walmart omits optional values for a particular record.

Data group	Dataset fields
Images and content	main_image, image_urls, title, brand, badges, category, breadcrumbs, description, features
Identity and variants	product_id, sku, gtin, mpn, model, specifications, manufacturer, origin, energy_class, included, condition, release_date, variant_group, variants
Price and promotion	price, was_price, unit_price, currency, price_text, discount_pct, discount_text, promo_text, installment_text
Availability and demand	stock_status, stock_text, sales_text, buy_limit
Rating and seller	rating, review_count, seller, seller_url, seller_score
Fulfillment	shipping_text, shipping_cost, delivery_text, pickup_text, return_text, return_days, warranty_text
Marketplace context	platform, site, country, product_url, source_url, query, rank, sponsored
Processing context	processor, processed_at

This example illustrates the output shape; it is not a current Walmart price:

{
  "title": "Dyson V15 Detect Cordless Vacuum",
  "brand": "Dyson",
  "product_id": "123456789",
  "condition": "new",
  "price": 599.99,
  "was_price": 749.99,
  "currency": "USD",
  "discount_pct": 20,
  "seller": "Walmart.com",
  "rating": 4.6,
  "review_count": 1842,
  "platform": "walmart",
  "country": "US",
  "query": "Dyson V15 Detect vacuum",
  "rank": 1,
  "product_url": "https://www.walmart.com/ip/example/123456789",
  "processed_at": "2026-07-21T12:00:00+00:00"
}

Use the output schema as the field contract. A null value means the public source did not supply a dependable value; it is not equivalent to zero, false, or out of stock.

What inputs can I configure?

Input	Type	Required	Accepted behavior	Example
keyword	string	Yes	A non-empty product, model, brand, category, or search phrase	Dyson V15 Detect vacuum
country	string	Yes	The exact currently supported country	United States
max_results	integer	Yes	A result ceiling from 10 through 10,000	10

The runtime rejects absent required values and does not silently add search defaults. Country text is normalized case-insensitively to United States. max_results must be a true integer; booleans do not qualify. Additional properties are rejected by the input schema.

The current local schema supports only United States. Older online descriptions that mention Canada or Mexico are legacy publication data and should not be used as the contract for new runs.

What platforms and markets does Walmart Price Tracker cover?

This Actor is dedicated to Walmart.com for the United States (US). Its current route maps only US to www.walmart.com, and the input schema exposes only United States. There is no platform selector because the Actor resolves to Walmart only.

Walmart's official Terms of Use explains that products can be offered by Walmart or third parties, listing information can change, and website pricing can differ from store or app prices. Treat output as a public Walmart.com snapshot, not a universal store-price feed.

The Actor does not take a ZIP code, preferred store, shopper account, membership state, or fulfillment selection. Location-specific pickup and delivery decisions require live verification.

Why use Walmart Price Tracker?

The Actor provides a repeatable Dataset instead of detached price copies. Analysts can compare current price with original price, discount, unit price, seller, condition, rating, and fulfillment. Catalog teams can retain identifiers, variants, images, specifications, and source URLs. Search-monitoring workflows can preserve rank and sponsored status.

Walmart's official listing-error guidance notes that price, images, descriptions, size, features, quantity, and included items can contain listing errors. Keeping source context and validating high-impact observations is therefore essential.

For the Dyson V15 Detect vacuum scenario, condition and seller are especially important because refurbished offers, third-party accessories, bundles, and other Dyson models can appear near the intended product.

Who is Walmart Price Tracker for?

• Retail analysts monitoring public Walmart.com prices, discounts, sellers, and search placement.
• Brands observing how specific models appear across Walmart retail and Marketplace offers.
• Procurement teams collecting source-linked evidence before manual verification.
• Catalog teams enriching internal records with public product identifiers, variants, specifications, and images.
• Data teams building scheduled snapshots, dashboards, or change alerts.
• AI-agent developers retrieving structured shopping context through API or MCP.

The Actor is not a checkout bot, local-store inventory guarantee, seller-account tool, or automatic repricer. Verify material purchase and pricing decisions at the source.

How can I use Walmart Price Tracker through the API or MCP?

The Apify API tab provides generated examples for your token and client. The public Actor ID is qCZ6lLRbj0XdR6ZmQ.

{
  "actorId": "qCZ6lLRbj0XdR6ZmQ",
  "input": {
    "keyword": "Dyson V15 Detect vacuum",
    "country": "United States",
    "max_results": 10
  }
}

Use schedules for repeat snapshots and webhooks when another service should process a completed run. Retrieve items from the default Dataset and keep seller, condition, source, and processing context.

For MCP clients, follow the official Apify MCP integration guide. Apify supports a Streamable HTTP endpoint with OAuth and Actor selection through tools=actor. Provide all required fields explicitly.

How much does Walmart Price Tracker cost?

The local publication metadata uses one Actor start event and one result event for each stored Dataset row. The intended tiered prices verified on 2026-07-21 are:

Apify tier	Actor start	Price per stored result
FREE	$0.01000	$0.00880
BRONZE	$0.01000	$0.00851
SILVER	$0.01000	$0.00821
GOLD	$0.01000	$0.00792
PLATINUM	$0.01000	$0.00792
DIAMOND	$0.01000	$0.00792

At FREE pricing, storing 10 results costs 0.01000 + (10 × 0.00880) = $0.09800. Fewer stored rows incur fewer result events. Confirm the effective post-publication terms on the pricing tab, because legacy online pricing data may remain visible until a release is published.

How does Walmart Price Tracker compare with alternatives?

Option	Best fit	Important trade-off
Walmart Price Tracker	Repeatable US Walmart.com public search snapshots with seller and source context	No ZIP/store input and no automatic history
Product Price Tracker	Compatible multi-source comparisons	Broader records require careful product matching
Manual Walmart browsing	A few store-aware checks with direct human review	Slow to repeat and difficult to audit at scale
Walmart seller tools	Managing an authorized merchant's own catalog and offers	Different purpose, credentials, and data scope

Choose this Actor for structured public search collection. Use live Walmart.com or the app when a decision depends on a specific store, ZIP code, account, pickup window, or checkout total.

What are the limits and troubleshooting steps?

Symptom or limit	Explanation and next step
Empty Dataset	Confirm country is United States; retry a specific model with max_results: 10.
Fewer rows than requested	The limit is a ceiling; public matches may be sparse, duplicated, blocked, removed, or incomplete.
Canada or Mexico input is rejected	Those values are not in the current local schema or Walmart route.
Website and store prices differ	Walmart states that site, app, and store prices can differ; verify the relevant context.
Similar titles have different prices	Compare item ID, seller, condition, package quantity, variant, and included items.
Fulfillment appears inconsistent	The Actor has no ZIP/store input; verify pickup or delivery live.
Optional fields are null	Walmart did not expose a reliable value; preserve null rather than inventing data.
Cost looks unexpected	Count stored rows and compare effective post-publication event pricing.

Public pages can change or restrict access. The Actor cannot guarantee row count, completeness, ranking, response time, or continuous availability. Start with the schema minimum and inspect the result.

Frequently asked questions

Does the Actor keep price history automatically?

No. Schedule runs and retain successive Datasets externally.

Does max_results: 10 guarantee ten products?

No. It is a ceiling, and only valid unique public records are stored.

Does the current actor support Canada or Mexico?

No. The current local input schema and route support United States only; online claims to the contrary are legacy data.

Does availability apply to every Walmart store?

No. There is no store or ZIP input, and public fulfillment signals are not universal inventory guarantees.

Are README prices live Walmart quotes?

No. Examples document shape. Run the Actor and verify the source listing.

How is billing counted?

One start event plus one result event per stored Dataset record under the intended local pricing configuration.

Can an AI client call the Actor?

Yes. Use the Actor API or Apify MCP server with all required inputs.

Related TrueFetch Actors

• Product Price Tracker for compatible multi-source searches.
• Amazon Price Tracker for Amazon country storefronts.
• Target Price Tracker for Target.com US search.

Support and last updated

Open an Actor issue with the input, run ID, expected behavior, and a small redacted sample. You may also use the TrueFetch group or support channel.

The public Store page checked on 2026-07-21 reported 7 total users, 3 monthly active users, one 5.0 rating, and 1 bookmark. Its multi-country text and some public API pricing are legacy data that differ from this local publication source; these dated signals are not proof of current readiness.

Last updated: 2026-07-21.