What is Amazon Error 8572?
Amazon Error 8572 means Amazon could not match your UPC, EAN or other product ID to your brand in the GS1 database. Amazon checks every barcode against GS1, the organisation that issues them. If the code was not licensed from GS1, is registered to a different company, or the brand name you entered does not match the GS1 record exactly, the listing is rejected. The fix is to use a GS1 barcode registered to your brand, make the brand name match character for character, and give GS1's data time to reach Amazon. If your product genuinely has no barcode, apply for a GTIN exemption instead.
What does the Error 8572 message say?
"8572: You are using UPCs, EANs, ISBNs, ASINs, or JAN codes that do not match the products you are trying to list."
It usually appears when you create a new listing or upload a file, and occasionally on older listings after Amazon re-checks the barcode.
Why does Error 8572 happen?
Amazon staff and GS1 US give the same short list of causes:
- The barcode did not come from GS1. Amazon has said it uses the GS1 database to verify UPCs, so codes from other databases or resellers may not be accepted as valid.
- The brand name does not match the GS1 record. Amazon staff say it must match exactly, and that the information is case sensitive. "Acme Home" and "ACME Home Ltd" are different to the system.
- The GTIN is not licensed to the brand owner. For example, the prefix belongs to your manufacturer or a previous company.
- The GS1 record is new. Amazon staff note that new codes can fail while Amazon waits for GS1 data to arrive.
- The listing has no brand, but the code belongs to one. Entering "Generic" or leaving the brand blank for a branded barcode triggers the error.
- The wrong product ID type is selected, such as EAN for a UPC.
How do I check who owns a barcode?
Look the code up before you change anything:
- Verified by GS1 shows which company the GTIN is licensed to, plus product data if it has been added. It replaced GS1's older GEPIR lookup at the end of 2023, and allows up to 30 single lookups a day.
- GS1 US company database lets you search by GTIN, company name or prefix, also with a daily limit.
If the company shown is not yours, or nothing is returned, the barcode is the problem. If it is yours, the brand name or product data is the problem.
How to fix Amazon Error 8572, step by step
Look up the barcode in Verified by GS1
Search the exact code. Note the company name and, if shown, the brand name and product description. Screenshot the result: you will need it if you contact Amazon.
If the code is not licensed to you, get GS1 barcodes
Codes bought from resellers are a frequent cause, and Amazon recommends obtaining GTINs directly from GS1. In the US, GS1 US sells single GTINs and company prefixes for larger ranges on its barcodes for Amazon page. Check current prices there, as they change. Outside the US, buy from your national GS1 organisation.
Make the brand name match exactly
Compare the brand in your Seller Central listing with the brand on the GS1 record, character by character: spelling, spacing, punctuation and capitalisation. Change whichever one is wrong so they are identical, and keep it identical on your packaging and in Brand Registry.
Complete the product record in GS1
GS1 US licences include access to GS1 US Data Hub, where you assign each GTIN to a product and enter its brand name and description. GS1 describes the basic product data shared through Verified by GS1 as the GTIN plus attributes such as brand name, product description, image, category, net content and country of sale. Fill these in for every code you list.
Wait for the GS1 data to reach Amazon
An Amazon staff member has said it can take up to 14 days for GS1 information to come across to Amazon, and that each new GS1 edit resets that time. Make your changes once, carefully, then try listing again every day or two rather than editing repeatedly.
If it still fails, open a case with Selling Partner Support
Contact Selling Partner Support from the Help menu in Seller Central, or at sellercentral.amazon.com/cu/contact-us. Amazon staff list what to include:
- The product name, manufacturer, brand and the exact UPC, EAN or JAN
- A screenshot of the error, with the batch ID if you used a file
- Brand owners: a valid, unexpired GS1 certificate for the GTIN range, or a GS1 database screenshot showing the code and owner
- Resellers: a letter or email from the manufacturer or brand confirming the code
- If the GS1 owner and the brand are different companies, proof of the relationship between them
What if my product has no barcode at all?
If the brand does not supply barcodes, for example a private label or handmade product, you may qualify for a GTIN exemption and list without a product ID. Exemptions are not available for products that already carry GS1 barcodes. One important limit from Amazon staff: you cannot add a product ID later to a listing created under an exemption. You would need a new listing.
Error 8572 troubleshooting table
| What you find | Cause | Fix |
|---|---|---|
| Verified by GS1 shows a different company | Barcode not licensed to your brand | Buy GS1 barcodes in your company name |
| No record found | Code not from GS1, or data not published | Buy from GS1, or complete the record in Data Hub |
| Record shows your company, different brand spelling | Brand mismatch | Make both brand names identical, then wait |
| Record is new or just edited | GS1 data not yet at Amazon | Wait up to 14 days without further edits |
| Listing brand is "Generic" or blank | Branded code on an unbranded listing | Relist with the correct brand name |
| GS1 owner is your manufacturer | Licence held by another company | Send proof of the relationship, or get your own codes |
Common mistakes
- Buying cheap barcodes from resellers. They may scan in a shop but fail Amazon's GS1 check.
- Editing the GS1 record every few days, which restarts the sync.
- Using a trading name on GS1 and a different brand name on Amazon.
- Letting the GS1 licence lapse.
- Reusing a barcode from a discontinued product.
- Choosing "Generic" as the brand to get around the error.
How to prevent Error 8572
- Buy barcodes only from GS1, in the same legal name you use for Brand Registry.
- Assign each GTIN to one product in Data Hub before you create the Amazon listing.
- Use one brand spelling everywhere: GS1, packaging, Brand Registry and Seller Central.
- Keep your GS1 certificate handy for support cases.
Frequently asked questions
It means the UPC, EAN or other product ID you entered does not match your product or brand in the GS1 database, which Amazon uses to verify barcodes.
An Amazon staff member has said it can take up to 14 days for GS1 information to reach Amazon, and that each new edit in GS1 resets that time.
They often fail. Amazon verifies barcodes against GS1 and recommends getting GTINs directly from GS1, so codes that are not licensed to your brand commonly trigger Error 8572.
Search the code in Verified by GS1, which replaced the older GEPIR lookup at the end of 2023. It shows the company the GTIN is licensed to.
Yes. Amazon staff say the brand must match exactly and that the information is case sensitive, so spelling, spacing and capitalisation all matter.
Only if your product genuinely has no barcode from its brand, such as a private label or handmade item. Exemptions are not available for products that already have GS1 barcodes.
The product name, manufacturer, brand, the exact product ID, an error screenshot with the batch ID, and either a valid GS1 certificate (brand owners) or a letter from the brand or manufacturer (resellers).
Official documentation
Amazon Help pages need you to be signed in to Seller Central:
- Amazon: Error 8572 help page
- Amazon: Product UPCs and GTINs
- Amazon: List products that do not have a product ID (GTIN exemption)
- GS1 US: Barcodes for Amazon
- GS1: Verified by GS1
Amazon guidance in this article comes from Amazon's Seller Central help references and Amazon staff posts on the Seller Forums. GS1 details come from GS1 and GS1 US. Prices and limits can change, so check the source before you buy.
Barcode Problems Holding Up a Launch?
We sort out GS1 records, brand mismatches and Selling Partner Support cases so new products go live without weeks of back and forth.
Request a Free Account Audit