After managing hundreds of brands on Amazon, we can tell you the most common reason a January product launch slips to March has nothing to do with the trademark, the photography, or the inventory. It is a GS1 record that says the barcode belongs to somebody who isn’t you.
Amazon runs two identity checks on every new ASIN, and brands only prepare for one of them. Brand Registry confirms you own the name. The GTIN check confirms the barcode you supplied is licensed to a company that plausibly makes the product. Those checks pull from two different databases, maintained by two different organisations, and on a meaningful share of the accounts we take over they do not agree. When they don’t, the listing does not get created, an error code appears that nobody on the team has seen before, and the case with Seller Support opens on the same week the first PO lands.
This is a brand management problem wearing an operations costume. Here is how it works, why it surfaces in Q1, and what to fix in September while there is still time to fix it cheaply.
What Amazon actually checks when you submit a UPC
Amazon’s stated policy is that it verifies UPCs against the GS1 database and treats codes that do not match GS1’s records as invalid. In practice, the system is checking three things about the GTIN you entered:
The first check is binary. The second and third are where brands get hurt, because the answer depends on decisions somebody made years ago, often before the brand existed, often to save a few hundred dollars.
When the check fails you get one of two errors. Error 8572 means the UPC does not match the product or is not recognised as valid. Error 5665 means the brand name you entered is not approved for your account, which in a GS1 mismatch case usually means the system cannot connect your brand to the barcode’s licence holder. Both route to a Seller Support case. Both require a GS1 certificate. Neither is a quick fix if the certificate names the wrong company.
The four ways the GS1 record ends up wrong
We see the same four patterns on almost every takeover with barcode problems.
Resold UPCs from a third-party seller. Somewhere around 2019 the founder bought 100 UPCs for $40 from a barcode reseller. Those codes were legitimately issued under a GS1 prefix in the 1990s or 2000s, to a company that has since dissolved, and the reseller carved up the block. GS1 will show the original licensee. Amazon will see a barcode belonging to a defunct manufacturer on a listing for your brand. Sometimes it goes through. Increasingly, it does not, and the ones that went through in 2020 are not protected from re-verification when you edit the listing in 2026.
GS1 licence in the wrong entity’s name. The prefix was licensed to the founder personally, or to a holding company, or to the previous owner of the brand before an acquisition, and nobody updated GS1 when the operating entity changed. Amazon’s system requires a close match between the GS1 company name and the brand or its documented owner. “Northstar Holdings LLC” does not match “Northstar Outdoor,” and Seller Support is not going to infer the relationship.
One GS1 prefix, multiple brands. A company runs three brands under one GS1 licence in the parent company’s name. Every barcode traces to the parent, none traces to the brand on the box. This works right up until Amazon’s check tightens or a brand gets sold separately, at which point the buyer discovers every GTIN on the catalogue belongs to a company they did not acquire.
Barcodes reused across products or variants. A UPC assigned to the 12-ounce in 2021 gets recycled onto the 16-ounce because the founder ran out of codes. GS1 rules say every trade item variant needs its own GTIN. Amazon’s catalogue agrees, and the second listing either fails or gets merged into the first, which is a different and worse problem.
Why this became a bigger deal in 2026
Two changes this year turned a launch-week annoyance into a standing exposure.
First, since March 31, 2026, Amazon ended FBA commingling and split barcode requirements by seller type. Brand Registry brand owners can send inventory under manufacturer barcodes without FNSKU stickers. Everyone else has to label every unit. That is a real operational advantage for registered brands, saving prep cost and prep time on every shipment. It only works if the manufacturer barcode on your packaging is one Amazon accepts as yours. A brand-registered seller whose GTINs trace to a dissolved company from 2003 is a brand owner on paper and a reseller at the inbound dock.
Second, Amazon’s catalogue systems have spent the year applying automated checks to existing listings, not just new ones. The 75-character title rewrite, attribute enrichment, variation family reviews. Each of those is an edit event, and edit events can trigger GTIN re-verification on ASINs that were created under looser standards. We have watched an ASIN live since 2021 get flagged during an unrelated attribute update because the UPC failed a check it had never been subjected to before.
The dollar math on a January launch that slips
Take a $200K a month brand launching four new ASINs in January, which is exactly when we tell brands to launch rather than into Q4 traffic. Assume each is planned at $15K a month by month three, with roughly $19 contribution per unit on a $38 product.
The launch gets stuck on a GTIN mismatch. The case takes eleven business days to resolve because the first response asks for a GS1 certificate, the certificate names the holding company, the second response asks for documentation linking the entities, and the third response asks you to re-submit. Call it three weeks of delay across four ASINs.
Three weeks of a $15K a month ramp is not $11K in lost revenue. The inventory is already inbound, so it is three weeks of storage on units not yet sellable. It is a launch window that now overlaps with your own Q1 reorder cycle. And it is three weeks in which the Vine enrolment, the launch campaigns, and the coupon you scheduled all had to be pushed by a person who was supposed to be doing something else. On four ASINs the direct contribution delay runs $8K to $12K. The real cost is that your Q1 test slate, which was supposed to produce a read by April, produces one in May.
The alternative is $250 a year for a GS1 US prefix of your own, in your operating entity’s name, set up in an afternoon in September.
What to check this week
This is a 90-minute audit, one person, no tooling.
Pull the GTIN for every live parent and child ASIN. Export the catalogue. You want the barcode column next to the brand column.
Run a sample through GS1’s public lookup. GS1 offers a verification service that returns the licensee for a given GTIN. Check your top ten SKUs and any SKU you plan to duplicate or vary in Q1. Write down the company name it returns. If it is not your operating entity or your registered brand, you have found the exposure.
Compare the GS1 licensee to the Brand Registry rights owner. These should be the same legal entity or have a documented relationship. If Brand Registry lists your brand under one LLC and GS1 lists your prefix under another, prepare the documentation now, not during a case.
Identify any barcodes not issued to you. Resold, inherited, or “borrowed” from a supplier. Every one of them is a listing that can fail on the next edit event. Plan to migrate them onto your own prefix when the product next gets a packaging run, since the barcode on the box has to match the barcode on the listing.
Check for reused GTINs across variants. One GTIN per sellable unit. If two child ASINs share one, fix it before Amazon’s catalogue tooling notices.
Assign your Q1 launch GTINs now. From your own prefix, in your own entity’s name, recorded in the canonical product record alongside the dimensions and the claim set. A barcode assigned in September is a barcode that will not be the reason January slips.
What good looks like
One GS1 company prefix licensed to the legal entity that owns the trademark and operates the seller account. Every GTIN in the catalogue issued under that prefix. The GS1 company name, the Brand Registry rights owner, and the Seller Central legal entity name matching or explicitly linked by documentation kept in one folder. New GTINs assigned at the moment a SKU enters the product record, months before the listing is created.
None of that is difficult. It is just never anyone’s job, because the barcode is treated as a packaging detail and Brand Registry is treated as a legal one, and the fact that Amazon reads them as the same question about who you are does not come up until a listing fails.
FAQ
Can I keep using UPCs I bought from a reseller if the listings are already live?
You can, in the sense that Amazon has not taken them down. You cannot rely on them surviving the next verification event, and you cannot use them cleanly for new variants or new marketplaces. Treat them as legacy and migrate on the next packaging run.
Does Brand Registry override a GS1 mismatch?
No. Brand Registry establishes that you own the brand name. It does not tell Amazon that a barcode licensed to a different company belongs to you. The GTIN exemption process exists for brands without barcodes, but a brand that has barcodes registered to the wrong entity is not exempt, it is mismatched, and those are handled differently.
Our GS1 prefix is in the parent company’s name and we run three brands. Is that a problem?
It is workable if the parent company is the documented brand owner in Brand Registry for all three. It becomes a problem the moment you want to sell one brand, because the buyer inherits barcodes licensed to a company they do not own. If exit is anywhere on the horizon, put each brand’s GTINs on a prefix that can transfer with it.
How long does a GTIN mismatch case take to resolve?
If your GS1 certificate names your operating entity and matches your brand, often a few days. If it names a different entity, expect two to three rounds and two to three weeks, because each round asks for a document you did not attach the first time. Attach everything up front.
Is this worth doing before Q4?
Yes, for one reason: your Q1 launch ASINs should be created in December so the listings are indexed and Vine is running by early January. That means the barcodes have to be right by November, and November is not the month to be on the phone with GS1.
If you’re looking for a team that manages every lever — creative, advertising, and operations — Velocity Sellers works with brands doing $100K+/month on Amazon. Contact us for a free account audit.
