GTIN, UPC and brand registry: getting your identifiers right the first time

Most new sellers hit the product identifier issue at the exact moment they're trying to launch, get a confusing error about a missing or invalid barcode, and either panic-buy a cheap UPC from an unofficial reseller or spend hours trying to figure out what Amazon actually wants. Neither is necessary once you understand what these codes actually are and which one applies to your situation.

What a GTIN actually is

GTIN stands for Global Trade Item Number, and it's the umbrella term for the family of standardized product identifiers used in retail globally. UPC, the 12-digit barcode most common in North America, and EAN, the 13-digit version common internationally, are both types of GTIN. Amazon's listing requirements generally ask for a GTIN, and a valid UPC or EAN satisfies that requirement.

The confusion usually comes from Amazon's error messages sometimes saying "UPC" and other times saying "GTIN," which reads like two different requirements when it's really the same requirement described two different ways.

Why a cheap UPC from a reseller is a real risk

Legitimate UPCs are issued by GS1, the global organization that actually owns and licenses the barcode number space, and they're registered to your specific company. Codes sold cheaply on marketplaces outside GS1, sometimes at a fraction of GS1's price, are often recycled from a company that let its GS1 membership lapse or was never properly licensed in the first place.

Amazon has been tightening verification against the GS1 database over the past several years, and listings built on a UPC that doesn't trace back to a legitimate GS1 registration can get flagged or suppressed, sometimes well after the listing has been live and selling for a while, when Amazon runs a verification pass. At that point, fixing it means either getting a proper GTIN exemption or replacing every affected UPC across the catalog, which is a much bigger job than just buying the right code in the first place would have been.

When you might not need a UPC at all: GTIN exemption

Amazon offers a GTIN exemption process for situations where requiring a manufacturer barcode doesn't make sense, most commonly for private label products where you're the actual brand owner and manufacturer of record, not reselling an existing branded product.

The exemption application generally asks for proof that you're the brand owner, which for most private label sellers means being enrolled in Amazon Brand Registry with a registered trademark, along with product images showing your branding. Amazon reviews the category and brand combination and, if approved, that specific brand-category pairing no longer requires a GTIN for new listings going forward.

This is different from getting exempted product by product. Once approved for a brand in a category, it generally applies going forward for that same brand and category combination, which matters if you're planning to launch multiple products under one private label brand.

Brand Registry and identifiers: how they actually connect

Brand Registry itself doesn't replace the need for a GTIN or a GTIN exemption. It's a separate enrollment that requires a registered trademark and gives you access to brand protection tools, enhanced content options, and reporting features. But Brand Registry enrollment is typically a prerequisite for the GTIN exemption application, since Amazon uses your registered trademark as part of verifying you're actually the legitimate brand owner claiming the exemption.

Sellers sometimes assume Brand Registry automatically removes the barcode requirement. It doesn't on its own, but it's usually the document that unlocks the exemption application, which is where the actual removal happens.

What happens when your listing's identifier doesn't match Amazon's records

Sometimes a listing was created correctly with a valid UPC, but later shows a product identifier mismatch error. This can happen if the underlying GS1 database record for that UPC changed, if a flat file upload accidentally altered the identifier field, or if the product was somehow associated with a different, pre-existing ASIN that has conflicting identifier data attached to it.

Checking the current identifier in Seller Central against your own GS1 records, and against what's actually printed on your product's physical barcode, usually reveals which of these it is. If your own records and the physical barcode agree with each other but disagree with what Amazon shows, that points to something changing on Amazon's side or in a past upload, rather than an error in your original product setup.

A practical decision tree

If you're reselling an existing branded product you didn't manufacture, you generally need a real GTIN, either the manufacturer's own UPC if you have access to it, or your own properly licensed one if the manufacturer's isn't available to you.

If you're the brand owner selling your own private label product and don't already have Brand Registry, getting enrolled first, then applying for the GTIN exemption using that trademark registration, is the standard and most defensible path.

If you already have a UPC you're unsure is legitimate, checking it against the GS1 registry directly, rather than assuming it's fine because it's worked so far, is worth doing before it becomes a live listing problem rather than a quiet cleanup task.

The cost of getting this wrong later versus doing it right at launch

Fixing an identifier problem after a listing has sales history, reviews, and ranking attached to it is considerably more disruptive than sorting it out before the first listing goes live. A flagged or suppressed listing loses momentum during the fix, and depending on the specific issue, sometimes requires creating a new listing entirely if the identifier problem can't be corrected on the existing one, which starts the review and ranking history over from zero.

Getting the identifier situation right before the first product launches, even though it takes an extra step or two upfront, avoids a much more expensive fix down the line once the product actually has sales momentum worth protecting.