GTINs, UPCs, And GS1: Getting Product Identifiers Right

What These Identifiers Actually Are

Four terms get used interchangeably and are not the same thing, which is the source of a surprising amount of confusion.

The distinction that matters operationally is between the GTIN, which identifies the product to the world, and the FNSKU, which identifies your specific units inside Amazon's fulfillment network. Historically those were two separate things and you needed both. As of 2026 that is no longer universally true, which is section five.

How Amazon Validates Them

Amazon checks submitted identifiers against GS1's database and treats a mismatch as invalid. GS1 US publishes Amazon's policy language on this directly, which is useful because Amazon's own help page requires a Seller Central login. The policy states that Amazon verifies authenticity by checking the GS1 database, that identifiers not matching GS1 information are considered invalid, and that sellers should obtain them directly from GS1 rather than from third parties.

The validation is not just checking whether the number exists. It compares the record, including the brand owner, against what you submitted. So a real, well-formed, scannable barcode registered to someone else fails, and it fails in a way that looks like a system error rather than a policy violation.

Two timing patterns are worth knowing. Sometimes validation fails at submission and the listing never goes live, which is annoying but cheap. Sometimes it passes at creation and the mismatch is detected later, suppressing an established listing with accumulated reviews and ranking. The second is the expensive version and it is the reason this is worth fixing proactively rather than when something breaks.

Why Cheap Barcodes Fail

The economics of resold barcodes are seductive and the mechanism of failure is specific enough to explain properly.

Vendors sell individual codes for a fraction of what a GS1 company prefix costs. Those codes are typically genuine GS1 numbers originally issued to a company that later dissolved, then sold on without GS1 reassigning the underlying prefix. The number is real. The registration still names the original licensee.

So when Amazon checks the record, it finds a company that is not you. There is no path to fix that through Amazon, because the problem is in GS1's data, and GS1 will not reassign a prefix on the basis that someone resold it.

The delay is what makes this expensive. A brand can list dozens of products on resold codes and operate normally for a year or more, building reviews and ranking on listings that are structurally invalid. Enforcement then arrives across the catalog at once, because the same prefix underlies all of them.

The other legitimate source, worth stating because sellers forget it, is the actual manufacturer of a product you resell. If you are selling someone else's branded product, their GTIN is the correct identifier and you should not be issuing your own.

Checking A GTIN Yourself

You can verify this in a couple of minutes rather than waiting for Amazon to tell you, and this is worth doing before you buy inventory rather than after.

Use GS1's Verified by GS1 lookup service. Enter the number and read the registered company. If it does not name your legal entity, that identifier will not survive Amazon's validation regardless of what the vendor who sold it told you.

Three outcomes. The number resolves to your entity, in which case you are fine. It resolves to a different company, in which case you have a resold or misassigned code. Or it does not appear at all, in which case it is not a legitimate GS1 identifier and no amount of correspondence with Amazon will make it work.

Run this across your existing catalog once, as a batch. Most brands discover either that everything is clean, which takes an afternoon to confirm and is worth the peace of mind, or that a specific historical batch of SKUs shares a problem, which is much easier to fix before it is discovered for you.

What Changed On March 31, 2026

This is the part that turns a listing-creation issue into a recurring cost, and most coverage of GTINs has not caught up with it.

Reporting indicates Amazon eliminated commingled inventory on March 31, 2026. Alongside that, brand owners enrolled in Brand Registry with the Brand Representative role can use their manufacturer barcode, meaning the GS1 GTIN printed on their packaging, as the primary tracking identifier in FBA rather than applying FNSKU stickers. Resellers face the opposite: FNSKU labels on all inventory, with units received without one classified as defective.

Put that next to Amazon ending its prep and labeling services in January 2026 and the consequence is direct. Labeling is now your cost, and a brand owner with a valid GS1 GTIN can avoid it entirely while a brand owner on resold codes cannot.

One widely repeated figure claims the industry was spending roughly $600 million a year on re-stickering to avoid commingling. That comes from a vendor rather than from Amazon, so treat the number as illustrative. The direction is not in dispute: for brand owners this removed a real recurring expense, and capturing it requires a GS1 GTIN that validates.

The strategic read for a private label brand is that a GS1 company prefix has moved from a compliance purchase to an operational one. It buys you out of a per-unit cost that recurs on every unit you ever ship.

Single GTINs Versus A Company Prefix

GS1 offers two routes and the right one depends on how many products you expect to have.

Individual GTINs. Buy one number at a time. Cheaper upfront and appropriate if you genuinely have one or two products and no plans for more.

A company prefix. Licenses you a block of numbers under your own prefix. Higher initial cost, and it is what Amazon's validation system is built around, since a prefix registered to your entity resolves cleanly for every product beneath it.

A widely cited third-party rule of thumb puts the crossover at around eight SKUs, above which a prefix pays for itself within the first year. Treat that as directional rather than precise, since GS1 pricing varies by region and changes, and check current fees with GS1 directly rather than trusting any figure in an article.

The consideration that rule of thumb misses is variations. A product with five colours and three sizes is fifteen GTINs, not one, because every sellable variant needs its own identifier. Brands routinely underestimate their identifier count by a factor of several, then buy individual codes repeatedly and end up above the prefix cost anyway with a messier catalog. Our guide to parent-child variation architecture covers how those families are structured.

The Brand Name Match

Owning a legitimate prefix is not sufficient on its own. The names have to line up, and this is where brands with any corporate history get caught.

Your GS1 record names a company. Your Amazon brand name is a brand. Your Brand Registry enrollment references a trademark. When those three do not agree, validation fails even though every individual piece is genuine.

That last line is the practical instruction. When these disagree, sellers instinctively edit the Amazon side because that is the interface they control. GS1's record is the authority Amazon checks against, so aligning downward from GS1 is the only fix that holds.

The acquisition case deserves particular attention. If you bought a brand, confirm the GS1 prefix actually transferred rather than assuming it came with the deal. Prefixes are licensed to entities and do not automatically follow an asset purchase, and this surfaces months later as unexplained suppressions across the acquired catalog.

If your brand and trademark situation is unsettled, that is worth resolving before the identifier work rather than alongside it. Our Brand Registry and trademark playbook covers that sequence.

Error Codes And What They Mean

Two codes account for most identifier failures, and knowing which one you have tells you where to go.

These codes are widely reported by third parties rather than documented on a public Amazon page, so treat the numbers as the community's shorthand rather than gospel. The distinction they represent is the durable part: an identifier problem and a brand authorization problem look similar from the seller's chair and have completely different fixes.

The wasted effort pattern is opening a support case for a 5461. Support cannot make GS1's database say something different. Verify the record first, and only contact Amazon once you know whether you have a valid identifier that Amazon is misreading, which is rare, or an invalid one, which is common.

GTIN Exemption: When It Fits

Amazon allows listing without a GTIN in defined circumstances. It is a legitimate mechanism that gets used for the wrong reason constantly.

Where it genuinely fits. Handmade products with no barcode. Private label products in eligible categories where you are testing before committing to GS1. Bundles you assemble that have no manufacturer identifier of their own. Genuinely generic products in categories that permit it.

Where it does not. As a way to avoid paying GS1 for a brand you intend to scale. Reporting indicates Amazon has stated exemptions are not available for brands that already have GS1-approved barcodes on their products, so this is not a choice between two equivalent routes.

The honest framing is that exemption is a good tool for products that genuinely have no barcode and a poor tool for deferring a cost you will pay anyway. If you are confident enough in a product to build a brand on it, buy the prefix. If you are testing, exemption is a reasonable way to keep launch costs down, and our product launch checklist covers where that sits in a launch sequence.

Migrating Off A Bad GTIN

If you discover invalid identifiers on established listings, the goal is changing the identifier without losing the listing's history.

1. Verify before acting. Confirm in Verified by GS1 that the identifier genuinely fails. Do not migrate on suspicion.
2. Obtain correct identifiers first. A GS1 prefix registered to the entity that holds your brand. Get this in place before touching listings.
3. Confirm name alignment across GS1, your Amazon brand field, and Brand Registry, using section seven.
4. Ask about preserving history explicitly. GS1 US guidance points sellers toward working with Seller Support to move a listing from an old identifier to a GS1-issued one without losing reviews and purchase history. That preservation is the whole point of the exercise, so raise it upfront rather than after the change.
5. Have your documentation ready. GS1 company prefix certificate or GTIN certificate, and brand documentation.
6. Do it before Q4, not during. Any catalog operation carries risk of temporary disruption, and the cost of that risk multiplies in peak season.

Timing is the piece sellers get wrong. Discovering this in October and deciding to deal with it in January means operating through your highest-revenue quarter on listings that could be suppressed at any point. The migration is unpleasant whenever you do it and considerably worse when forced.

Variations, Bundles, And Multipacks

Three cases where identifier requirements are misunderstood often enough to be worth stating explicitly.

Variations. Every sellable child needs its own GTIN. A parent listing is a container and does not consume one. This is where identifier counts balloon and where brands buying individual codes discover they needed far more than planned.

Multipacks. A three-pack of your product is a distinct trade item and needs its own GTIN, not the single unit's identifier. Reusing the single-unit code across pack sizes creates a catalog conflict that gets messier the longer it runs.

Assembled bundles. A bundle you create from multiple products has no manufacturer identifier because nobody manufactures it. This is one of the cleaner uses of GTIN exemption, since the product genuinely does not have a barcode and never will.

The through-line is that a GTIN identifies a trade item as a customer buys it, not a product concept. Different sizes, different counts, and different configurations are different trade items even when they contain the same thing.

Identifier Hygiene At Scale

Past a few dozen SKUs this needs to be a maintained record rather than something you reconstruct when a listing breaks.

1. Keep one identifier register. Every SKU, its GTIN, the source, the date issued, and which listings use it. This is a spreadsheet, not a system, and its absence is what makes catalog problems take weeks.
2. Audit annually against Verified by GS1. An afternoon a year. Catches historical problems before enforcement does.
3. Assign identifiers at product creation. Not at listing creation. By the time you are building a listing, packaging is often already printed.
4. Never reuse a retired GTIN. Identifiers are not recycled. A discontinued product's number stays with that product.
5. Re-verify after any corporate change. Acquisitions, restructures, and entity changes all break the alignment in section seven silently.
6. Check the whole family when one fails. Products sharing a prefix share its problems, so an isolated failure is usually not isolated.

When This Is Not Worth Worrying About

If you are a brand owner with a GS1 company prefix registered to the same entity as your Brand Registry trademark, and your listings are not throwing errors, you are done. There is no ongoing work here beyond assigning identifiers to new products correctly and an annual check. This is not an area that rewards continuous attention.

The brands that need to act are the ones with any of three markers: barcodes bought from a reseller, a corporate history involving an acquisition or restructure, or a catalog built by an agency or contractor whose GS1 account you have never seen. If none of those apply, verify a handful of identifiers to confirm and move on to something that grows the business.