Imagine your UPC came straight from GS1 and Amazon still says it is fake.
By Vanessa Hung · July 29, 2026 · Curated by George's Blog
Imagine your UPC came straight from GS1 and Amazon still says it is fake.
A seller had a real barcode for a dietary supplement listing, purchased directly from GS1 and tied to their registered brand, so they submitted it to create the listing, but Amazon rejected it with Error 8572, saying the product identifier did not match the brand.
In this case, the GTIN was purchased legitimaly, it belonged to the seller's own company, and it was the first time it had ever been used on Amazon.
So the question became, how does a valid, first-use barcode get flagged as not belonging to the product?
The thing is that Amazon compares three separate records behind the scenes to know if your product is labeled correctly, and one of them did not line up.
Finding which one, and in what order it needed to be fixed, is what actually moved this case forward, because if we went straight and tried to fix it, Amazon would just say, "Nah, this product is not yours," and close the case.
The full case, including the exact record that was mismatched and the sequence used to resolve it, is broken down in this week's OSS Lab: https://lnkd.in/eP9CUUfS
If you’ve ever had a valid GTIN or UPC suddenly flagged and couldn’t figure out why, this case explains exactly what happens behind the scenes.
Struggling with this or another Amazon issue? Send me a DM!
#AmazonSeller #Ecommerce #SellerCentral #CatalogManagement #BrandRegistry