Walmart Can Now Find Your Products by EAN. If You Have Been Creating Duplicate Listings, That Just Got Cheaper to Fix.

If you sell on Walmart with products that carry a European barcode instead of a US one, you have probably had this experience: you search the Walmart catalog for an item you know is already there, get nothing, create a new listing, and end up with two offers on two item pages splitting the same demand.

On August 20, 2026, Walmart changed the input side of that problem. The Item Search API now accepts EAN and ISBN in the US market, alongside the UPC, GTIN, and ASIN support that was already there.

That is a small documentation update with a real operational consequence, and it arrived attached to a deadline most sellers have not seen yet.

What actually changed

Per Walmart’s developer portal, two things shipped on August 20:

EAN and ISBN search support. In the US market you can now query the Walmart catalog by ean or isbn. With responseFormat=DEFAULT you can search by query, upc, gtin, ean, or isbn. With responseFormat=SPEC you provide exactly one of upc, gtin, ean, isbn, or asin. SPEC format is US only, and asin still works only with SPEC.

MP_ITEM_MATCH moved to 5.x. Seller-fulfilled offer setup by match now supports the 5.x item specification. And here is the part with teeth: support for MP_ITEM_MATCH seller-fulfilled 4.x ends October 15, 2026. After that date, requests using 4.x are no longer supported.

Walmart’s own framing on the search change is that it helps sellers identify existing catalog items more accurately and reduce duplicate setup attempts. That is accurate and it undersells it.

Why matching beats creating, every time

When you match your offer to an existing Walmart item page, you inherit what that page has already earned: content, images, reviews, search history, and whatever ranking equity has accumulated. You are adding an offer to a page that already converts.

When you create a new item page for a product that already exists in the catalog, you get the opposite. Zero reviews. Zero history. Demand for that product now splits across two pages, neither of which ranks as well as one consolidated page would have. And you have added a duplicate that someone will eventually have to clean up, usually you, usually manually, usually at the worst possible time.

For US-based sellers with UPC-native catalogs, search coverage has been decent and this was mostly a solved problem. For brands that came from Europe, the UK, Australia, or anywhere else that runs on EAN-13, catalog search was a partial tool. You could search by GTIN, but if your operational systems and your supplier data carried EANs and your team was working off the barcode on the box, the fastest path was often to skip the match attempt entirely and just create the item.

That workaround is now unnecessary, and it was expensive.

The October 15 date is the part to act on

EAN search is an upgrade. The 4.x sunset is a risk.

If your Walmart integration submits offer setup by match through MP_ITEM_MATCH on the 4.x spec, those requests stop being supported on October 15, 2026. Look at where that falls. Mid-October is when you are pushing holiday assortment live, adding seasonal SKUs, and reacting to what is actually selling. It is the single worst two weeks of the year for your item setup pipeline to start rejecting feeds.

Almost nobody submits these feeds by hand. The exposure sits with whoever owns your integration: your channel management platform, your listing tool, your 3PL, your agency, or your in-house dev team. Which means the migration is their work and your revenue.

What to do this week

Send one question to every partner that touches your Walmart catalog. In writing: are you using MP_ITEM_MATCH seller-fulfilled 4.x, and what is your migration date to 5.x? You want a date, not reassurance. A partner who says “migrating September 15” is fine. A partner who does not know what you are asking is the finding.

Audit your catalog for duplicates you created because search came up empty. Pull your Walmart item list and look for products where you suspect an existing catalog page. This is worth doing manually on your top 50 SKUs before you automate anything. Duplicate consolidation is slow, so start it now rather than in November.

If you run an EAN-native catalog, get your identifiers into the match workflow. Whoever builds your Walmart feeds has probably been mapping around this limitation with converted GTINs or falling back to item creation. Tell them EAN is now a first-class search input in the US market and ask them to rerun match attempts on the SKUs where they previously gave up.

Amazon sellers porting a catalog: use ASIN search with SPEC format. That capability landed back in May 2026 and is still underused. If your Walmart catalog is a subset of your Amazon catalog, ASIN lookup is the fastest way to find the corresponding Walmart items before you set anything up.

Freeze your item setup spec version until after peak. Migrate to 5.x now, validate it with real feeds, then leave it alone from mid-October through January. Do the platform work in the quiet weeks.

The pattern worth noticing

This is the third Walmart integration deadline in six weeks. Simplified Shipping Settings endpoints were deprecated August 4 with SSS 2.0 launching August 31. New Listing Quality and Content Quality report types landed August 17. Now MP_ITEM_MATCH 4.x sunsets October 15.

Walmart is rebuilding its API surface fast, which is good news for sellers who want programmatic control of a marketplace that is growing faster than Amazon off a smaller base. It also means “our integration works” has become a claim with a short shelf life. The sellers who get hurt by these transitions are not the ones with bad integrations. They are the ones who assumed a working integration stays working.

Put the Walmart developer What’s New page on someone’s monthly calendar. Five minutes a month catches every one of these before it becomes a Q4 fire.

If you want someone to audit your Walmart catalog for duplicate listings and check your integration against the October deadline, book a strategy assessment.