Amazon Error 8572: “UPCs, EANs, ISBNs, ASINs, or JAN Codes That Do Not Match the Products You Are Trying to List”

Your barcode is structurally fine, yet Amazon insists it belongs to something else. Here is what the platform really checks, and in what order to untangle it.

You have the product ready and the listing drafted — and Seller Central answers your upload with error 8572, saying your product IDs do not match the products you are trying to list. The frustrating part: the number usually looks perfect, and the check digit passes. Here is why that happens and what actually resolves it.

What this error actually means

Error 8572 is a conflict error, not a format error. Amazon has publicly stated that it verifies product UPCs against the GS1 database and treats UPCs that do not match GS1's information as invalid. When you submit a GTIN (the umbrella term for UPC, EAN, ISBN, and JAN numbers), Amazon compares it against two things:

• GS1 records — who licenses that number, and what brand it is registered under; and
• Amazon's own catalog — whether the ID is already attached to an existing ASIN with different data.

If either comparison disagrees — the GS1 licensee is a different company, the registered brand does not match your listing's brand attribute, or the ID is already tied to a different product — the upload is rejected with 8572. A merely malformed number produces a different rejection — see our broader guide to fixing invalid GTIN errors on Amazon; error 5665 (brand name) and error 8541 (ASIN match conflicts) are close relatives.

Why a “valid” barcode still fails: ownership vs. arithmetic

A UPC's final digit is computed from the others, so any made-up number can pass validation — verify any code with our GTIN check digit calculator, or a whole spreadsheet with the bulk barcode validator. But a passing check digit only proves the number is self-consistent; it says nothing about who licenses it. (Our guide on how check digits work explains why.)

That distinction drives most 8572 cases. GTINs are licensed through GS1, whose registry records which company holds each number. Many cheap barcode packs sold online are carved out of prefixes licensed to another company years ago — so-called recycled or resold UPCs. Every one passes a checksum test, but when Amazon looks the number up, the registry names a different company than the brand on your listing, or the code is already attached to a different product. That mismatch is exactly what 8572 reports. Marketplaces increasingly verify ownership against the GS1 registry rather than just validating digits — the same checks lie behind Google Merchant Center GTIN errors, eBay UPC rejections, and Shopify barcode issues.

The fix path, step by step

Work through these in order.

1. First, rule out a plain data error. Confirm you submitted the full, correct number: no truncated digits, no dropped leading zero (a classic spreadsheet casualty — see Excel and leading zeros in barcodes), and the right code type (a 12-digit UPC in an EAN field is a frequent slip; the UPC to EAN converter shows how the two relate). If you find a typo, fix it and re-upload — you may be done.
2. If the number is right, look up who licenses it. GS1 operates a free public lookup called Verified by GS1 on gs1.org (GS1 US offers a similar database search). Enter your full GTIN and note the licensee it returns; everything below depends on this answer.
3. If the licensee is you or your company: compare the brand name registered with GS1 against the brand attribute in your Amazon listing — sellers report that even small wording differences (“Acme Co.” vs. “Acme”) can trigger the error, so align the listing with the GS1 registration. Also consider timing: newly licensed GTINs reportedly take a week or more to propagate to Amazon, so a days-old license may simply need to sync. If the brand matches and the license is not brand new, move to the support step below with your GS1 certificate.
4. If the licensee is the brand you are reselling: the barcode is doing its job — it identifies their product. A legitimate reseller generally should not create a new product page at all; find the existing ASIN for that exact product and add your offer to it. On a reseller upload, 8572 often signals an attempted duplicate detail page, or attributes that do not match what the catalog already holds for that GTIN.
5. If the licensee is an unrelated company, or the lookup returns no usable record: you are most likely holding resold or recycled numbers, and re-uploading will not change what the registry says. The durable fixes are to license your own GTINs through GS1 so the registry lists your company and brand, or — if your product qualifies — to apply for Amazon's GTIN exemption and list without a product ID. We do not recommend replacement codes from third-party resellers; that route is how most sellers end up on this page.

What to send support if nothing works

If your ownership records are genuinely in order and the error persists, open a case with Seller Support rather than resubmitting endlessly. Amazon asks for a specific evidence package, and cases move faster when it is complete on the first message:

• Product name, manufacturer name, and brand name exactly as they appear in your feed;
• The UPC/EAN/ISBN/JAN in question (Amazon does not ask for the batch or feed ID that produced the error, but including it helps support trace the rejection);
• Brand owners: a current, unexpired GS1 certificate covering the GTIN range used in your listings;
• Resellers: a letter or email from the manufacturer or brand confirming that the product ID you are using for this product is valid;
• Photos of the physical product showing the barcode and brand on the packaging — not on Amazon's stated list either, but sellers report they shorten the back-and-forth.

Keep the case ID for follow-ups. If your GS1 license is only days old, mention the issue date — support can confirm whether you are simply inside the sync window.

What won't work

A few dead ends worth naming. Re-running validators will not help once the digits are confirmed correct — 8572 is about registry and catalog conflicts, not arithmetic. Tweaking a digit to dodge the conflict creates a fabricated ID and risks worse enforcement than a rejected feed. Another batch of cheap reseller codes usually reproduces the same registry mismatch under a different number. And a support case cannot override GS1's records: if the registry says another company licenses the number, no letter you write yourself changes that. Amazon is enforcing ownership; the fixes that last are the ones that make the ownership records agree with your listing.

FAQ

Why does Amazon reject my UPC with error 8572 when the check digit is valid?

Because error 8572 is not about the math. A correct check digit only proves the digits are internally consistent. Amazon compares the product ID against GS1 records and its own catalog, so a UPC whose registered licensee or brand does not match your listing is rejected even though it passes every checksum test.

How do I find out who actually owns my UPC or EAN?

Use the public Verified by GS1 lookup on gs1.org (GS1 US also offers a company database search). Enter the full GTIN and it returns the licensing company, when GS1 has data for it. If the licensee is not you and not the brand on your listing, that mismatch is the likely cause of error 8572.

My barcodes came directly from GS1 and I still get error 8572. Why?

Two common reasons. The brand name you registered with GS1 must match the brand attribute in your Amazon listing; even small wording differences can trigger the error. And newly licensed GTINs can take a week or more to propagate to Amazon, so very recent licenses sometimes fail temporarily. If both check out, contact Seller Support with your GS1 certificate.

Can I fix error 8572 by buying cheaper UPCs from a third-party reseller?

That usually causes the problem rather than fixing it. Amazon verifies UPCs against the GS1 database and treats codes that do not match GS1 records as invalid. Numbers bought outside GS1 typically trace back to another company's license, so the registry shows a different owner than your brand. For eligible products, Amazon's GTIN exemption is the legitimate alternative.

This guide is for general information only and is not affiliated with or endorsed by Amazon or GS1. Marketplace policies change over time; confirm current requirements in Seller Central and with GS1 directly. Check digit validation confirms internal consistency of a number, not that it is licensed to you or registered with GS1.