Retail GTINs

Why you should not invent UPC or EAN numbers

Plenty of “free UPC generators” will happily draw bars for a 12-digit string that passes a check digit. That is a math trick, not a catalog identity. Retailers, Amazon, Walmart, and Target treat a GTIN as a licensed number. This guide is the blunt version of that distinction, written so a shop does not print 500 stickers of someone else’s code.

LabelStack editors · August 28, 2026 · 12 min read

Two different meanings of “valid”

A UPC-A is valid as a barcode when the twelfth digit matches the GS1 modulo-10 of the first eleven. LabelStack checks that, because a typo in a number you already own should not reach a printer. A UPC-A is valid as a product identity when a GS1 company prefix that you licensed sits at the front of those digits and the rest is a number you assigned under that prefix.

Those are not the same test. You can satisfy the first without coming anywhere near the second. If a site offers “generate a UPC for my new candle,” it is offering the first test. It is not offering a prefix. It is not talking to GS1. It is drawing bars.

What actually happens when a homemade GTIN hits a marketplace

Catalog systems match GTINs globally. If the 12 digits you invented collide with a real product—and with only a billion UPC-A combinations in the naive sense, collisions are not theoretical—the listing is tied to someone else’s brand, images, and safety data. Marketplaces then suppress the listing, or worse, map your inventory onto that brand. “But the check digit was correct” does not unwind that.

Some resellers sell “blocks of UPCs” that are not GS1 prefixes. Whether a given reseller is legitimate is a GS1 question, not a LabelStack question. We do not broker numbers. We encode the digits you bring. If you do not have a paper trail from GS1 (or a channel GS1 recognizes), do not print the number as a retail barcode.

What to print instead when you do not own a GTIN

Internal SKUs, bin locations, lot codes, and most Etsy shop stickers should be Code 128 of a value you control: MUG-BLUE-12, LOT-2026-08-14, BIN-A-04. Those never collide with a Target scan because a Target scanner is looking for UPC/EAN, not your house Code 128. Amazon FBA inbound wants an FNSKU Amazon assigned, also Code 128, also not a homemade UPC.

If a sales channel requires a GTIN and you do not have one, the honest paths are: get a GS1 prefix, use a channel’s exemption if they offer one for handmade or private-label in that category, or do not list on that channel. Printing a random EAN is not a fourth path.

How LabelStack is built around that line

The bulk UPC and bulk EAN pages validate check digits and encode bars. They do not issue prefixes. The tool will encode a well-formed 12-digit string you typed for a test; it will also encode a licensed GTIN you pasted from your GS1 account. The difference is your right to use the number, which no browser app can see. The about page and the terms say the same thing in legal language. This guide says it in operational language: if you would not put that number on a package going to a grocer, do not put it on a 5160 sheet either.

When you do own the number, use the validator. That is the whole remaining job: catch the transposed digit before the sheet comes out. Worked arithmetic lives in the check-digit guide, including the confectionery EAN-13 4006381333931.

Keep reading

More original guides

Ready to print? Open the generator. Questions: contact@labelstack.app. Inventory stays in this browser.