Free · 3,600 monthly searchers

SKU Lookup — Walmart Item IDs and Cross-Retailer Matches

Type a Walmart item_id, UPC, or any retailer SKU and see how it maps across Walmart, Amazon, Target, Best Buy, Lowes, and Home Depot. Built for inventory tools, repricers, and arbitrage research.

Try:

3,600 people search Google for "sku lookup" every month — almost none of them get cross-retailer data.

One SKU, every retailer

Stock-keeping units are retailer-internal. Walmart calls their SKU an item_id. Amazon uses ASIN. Target uses TCIN. Best Buy uses SKU directly. The same physical product, with the same manufacturer UPC, gets a different SKU at every retailer. For an arbitrage seller or repricer, that means 6 distinct lookups per product across 6 separate APIs.

retailerapi collapses that into 1 query. The input is any SKU or UPC. The internal pipeline normalizes to GTIN-14, queries the Walmart catalog, then fans out to 5 other retailers in parallel. Average response time is 2.1 seconds for a fully enriched cross-retailer answer, or 1.8 seconds when the cross-retailer cells hit the 30-day cache.

The pattern is the same whether you start with a Walmart item_id (11 to 12 digits), a UPC-A (12 digits), an EAN-13 (13 digits starting with non-0), or an MPN. Auto-detection routes the request, and the response always includes the canonical GTIN-14, so downstream tools can de-duplicate.

Use cases

  • Repricer feeds. Refresh prices on a 100,000-SKU catalog nightly. Pro tier at $429 per month covers it.
  • Arbitrage research. See which Walmart SKUs are priced below Amazon by more than 20%.
  • Brand monitoring. Track every SKU carrying your brand across 6 US retailers in real time.
  • AI agents. The MCP server exposes sku_lookup as a callable tool for Claude and ChatGPT.

Frequently asked questions

What is a SKU and how is it different from a UPC?

A SKU (Stock-Keeping Unit) is a retailer-internal product ID. Walmart calls theirs item_id. Amazon uses ASIN. Each retailer creates its own SKU for inventory and pricing. A UPC, by contrast, is a manufacturer-issued identifier that every retailer shares for the same physical product. A single UPC can map to different SKUs at Walmart, Target, and Best Buy.

How do I find a Walmart SKU?

The Walmart item_id is the numeric portion of any Walmart product URL. For walmart.com/ip/Apple-Watch-Series-10/19667262713, the item_id is 19667262713. Walmart also displays the item_id on the product detail page under "Specifications". Marketplace third-party sellers may show their own merchant SKU separately.

Can retailerapi match a SKU across retailers?

Yes. Start with any Walmart item_id and retailerapi resolves the GTIN, then cross-references at Amazon, eBay, Target, Best Buy, Lowes, and Home Depot. The result lists the matched SKU and current price at each retailer where the product exists. Cross-retailer cells cache for 30 days, so popular SKUs resolve instantly on repeat visits.

What is the difference between a SKU lookup API and a UPC API?

A SKU lookup is retailer-specific: the input is a retailer SKU and the output is data about that single listing. A UPC lookup is manufacturer-specific: the input is a UPC and the output is every listing across every retailer that carries the product. retailerapi exposes both through one /v1/products/{id} endpoint, with auto-detected input format.

Is there a SKU lookup API for inventory tools?

Yes. The /v1/products/{item_id} endpoint takes any Walmart item_id or numeric SKU and returns title, brand, current price, sellers, and price history. Inventory tools typically run this against thousands of SKUs nightly. The Pro tier at $429 per month covers 10.8 million SKU lookups per month.