← All articles

Operations: fulfilment, packaging & compliance

UPC Codes for Retail vs Amazon: What Actually Differs

By Martin Mecar, founderSeptember 25, 20266 min read

On Amazon, a UPC is mostly a key used once: it matches your product to an ASIN at listing time, after which the marketplace runs on the ASIN and, in the fulfilment centre, on an FNSKU. In a store, the UPC is the product. It is how the item is set up in their system, how a reorder is triggered, how the price is attached, and how the sale is recorded when a shopper puts it on the counter.

That is the whole difference, and it explains nearly every problem an Amazon-native brand hits at its first retail account.

How Amazon uses your UPC

When you create a listing, Amazon asks for a product identifier. It uses that number to decide whether your item already exists in the catalogue or needs a new ASIN. Once the ASIN exists, the UPC stops being the operating identifier.

Inside the fulfilment network, units are tracked by FNSKU, an Amazon-specific code tied to your seller account and that ASIN. That is why a unit in an Amazon building often has a sticker over the printed barcode: the building wants its own code, not yours.

Amazon also grants barcode exemptions for some products and brands, which means a seller can operate for years, profitably, without ever licensing a single barcode. That is the trap. The exemption is an Amazon convenience; it has no meaning anywhere else.

How a retailer uses your UPC

A retailer's system starts with item setup. Before a single unit ships, you fill in a form or a portal entry for every sellable variant: the UPC, description, dimensions, weight, case quantity, case UPC if they use one, cost, suggested retail, country of origin, hazardous flags, and often nutrition or ingredient data.

That UPC then becomes the spine. Their point-of-sale keys the retail price to it. Their replenishment system counts sales against it and generates the reorder. Their warehouse receives against it. Their reporting tells you how the item performed by that number.

Which leads to the rules that are non-negotiable in retail and casual on Amazon.

One code per sellable variant. Every size, colour, scent and count gets its own. A brand that has been listing variations under one parent on Amazon may discover it has fewer codes than it has products.

The code has to be licensed to your company. Retailers check the ownership of the prefix, and many will reject an item whose barcode resolves to another company's name. The licensing mechanics are covered in GS1 barcodes for Amazon and retail.

The code never gets reused. If a product is discontinued, its number is retired for years, not recycled onto the next thing.

And the code has to be printed on the package and scannable, not applied as a sticker on arrival.

On AmazonIn a store
Role of the UPCMatches to an ASIN at setupThe permanent item identity
Operating identifierASIN and FNSKUThe UPC itself
Can you skip itSometimes, via exemptionNo
VariantsCan share a parent listingOne code each, always
Where it livesCatalogue recordPackage, item file, till, reorder

What breaks when you arrive without codes

Four failures, in the order they usually happen.

Item setup stalls. The buyer's vendor onboarding form has a mandatory UPC field per line, and you cannot submit it. This is often the first sign a brand notices, weeks after the buyer said yes.

The prefix check fails. You bought a handful of cheap barcodes from a reseller years ago to get listings live. They work on Amazon. The retailer looks up the prefix, sees a different company, and asks you to re-code the range.

The FNSKU sticker causes mis-scans. Units pulled from your Amazon stock still carry the Amazon label, often covering the printed code. At the till it either fails to scan or rings up as something unexpected. This is one of the reasons filling wholesale orders from marketplace inventory is a short-term move, as FBA removal orders for wholesale explains.

The case and the each get confused. A visible item barcode on the outside of a master carton makes a receiving scan book one unit instead of twenty-four. Which barcode belongs on which level is set out in inner packs and master cartons.

There is a fifth failure that appears later and is worse. A brand that submitted one variant under two different codes to two different accounts now has split sales data, two item records, and no way to compare performance between the two retailers. Nobody catches it until a reorder is calculated from half the demand.

Do you need a code for the case as well

Often yes, and it is a separate number from the each.

Retailers that order by the case want a distinct identifier for the case so their receiving and ordering systems can tell one from the other. Some use a case-level item code; larger accounts want a shipping label with a carton-level barcode carrying the purchase order reference.

The practical guidance is to ask, rather than guess. The vendor manual will state what the carton must carry, and it varies more between retailers than the item-level rules do.

What you should never do is put the each barcode on the case and hope. That is the single most common cause of a receiving discrepancy on a first shipment.

Can you keep using the Amazon barcode programme

If your packages carry printed manufacturer barcodes, Amazon can be configured to track units by that code rather than applying its own label. For a brand selling both channels this is worth doing, because one printed code then serves the marketplace, the warehouse and the shop till.

The trade-offs are real. Units become commingled with other sellers' identical items in some configurations, which introduces a counterfeit and quality risk you cannot control. Brands with a registered trademark have stronger options here, including serialisation programmes; the protective side of that is covered in the Amazon Transparency programme.

For most brands the decision comes down to how much wholesale volume is realistic. If retail is a serious channel, a printed manufacturer barcode on every unit removes an entire class of problems. If retail is one boutique, keep the Amazon labelling and accept the sticker.

Getting your codes in order

The sequence is short and worth doing before you talk to a second buyer.

List every sellable variant you actually have, not every listing. Count them. Get licensed codes to cover them with room for the next year of releases, because prefixes come in fixed capacities and outgrowing one is annoying.

Assign a code to each variant and record the mapping in one place — variant, code, ASIN, factory item number, case quantity, case code. That single table is what you will paste into every retailer's item setup form for the rest of the brand's life.

Get the codes printed on the packages at the next production run rather than stickering. Stickers are acceptable temporarily and read as amateur permanently. The package changes that go with it are in retail packaging vs Amazon packaging.

Is it worth doing before you have a buyer

Licensing barcodes has a real annual cost, and doing it for a channel that turns out not to exist is money wasted. The honest answer is to check whether retail demand is plausible for your category first.

Paste your listing into WholesalePilot and the preview shows which retailers and distributors stock comparable products. If that list is substantial, licensing codes is one of the cheapest pieces of retail readiness you can buy, and one of the few that will stall a deal entirely if it is missing when the buyer asks.

Find the B2B buyers for your product

Paste a product link. We find matching wholesale buyers, email them in your name, and hand you the replies.

Keep reading