Barcode Guide: GS1, EAN and Marketplace Product Matching
What GS1 barcodes are, how EAN-13 and UPC differ, which marketplaces verify them, and a step-by-step checklist for a clean barcode setup across all channels.
A barcode is the one identifier that every channel, warehouse and ERP recognises for the same product. GS1 is the organisation that issues barcode numbers worldwide, and EAN-13 is the most widely used thirteen-digit format in that system. For clean marketplace listings, correct stock matching and reliable warehouse work, every sellable variant needs exactly one permanent barcode. This guide explains what barcodes are, how you obtain them, what marketplaces verify, and how to set up a barcode structure for a multichannel business.
Barcode, SKU and model code are three different things
These three concepts get confused constantly in day-to-day operations, and no barcode structure survives that confusion.
- Barcode (EAN/UPC): The universal identity of the product. It stays the same on every channel and in every warehouse. Its source is the GS1 system.
- SKU: Your internal stock code. You define the rule; "TSH-RED-38" can be perfectly readable. It has no external standard.
- Model code: The parent identifier that groups variants. Model "TSH-001" contains several colours and sizes.
Marketplaces ask for these in different fields. One makes the barcode mandatory, another highlights the stock code, a third uses the model code for variant grouping. We covered the channel-by-channel field mapping in matching products by SKU and barcode.
What GS1 is and how you get an EAN-13
GS1 is an international organisation with member organisations per country. You join through your local GS1 office and receive a company prefix. You append your own item numbers to that prefix to create EAN-13 codes; the final digit is a check digit that validates the number.
Membership terms, fees and the number of codes allocated vary by country and change over time, so get the current details from your local GS1 organisation. The important part is this: the number belongs to the GS1 system, not to you, and your right to use it continues as long as your membership does. That is why buying "ready-made barcodes" from random websites is risky; those numbers may be registered to another company and will fail brand verification on marketplaces.
The same GS1 numbers work on every channel worldwide. Amazon, eBay and Walmart can verify a code against the GS1 registry, so it matters that the registration is in your brand's name. We touched on this in the checklist for launching on a new marketplace.
Which barcodes marketplaces accept
Channels behave differently on barcodes, and their rules change. The general pattern looks like this:
- Some channels require a barcode for every variant but may not check GS1 registration.
- Some require a GS1-registered code in specific categories or for brand matching.
- Global channels may check which brand the code is registered to in GS1; a mismatch gets the listing rejected.
- For own-manufactured goods or barcode-free categories, some channels offer a formal exemption.
Confirm the exact rule in each channel's current listing documentation. Products uploaded without knowing the rule get rejected or suppressed later; reasons listings get removed includes several barcode-related cases.
Step-by-step checklist for a clean barcode setup
This list is for businesses building a barcode structure from scratch or cleaning up a messy one.
- Confirm your GS1 membership and company prefix. If the membership is in someone else's name or a former company name, brand verification will fail.
- List every sellable unit. Each colour × size × pack combination is its own row. Cartons and inner packs need their own codes too.
- Assign exactly one barcode per unit. Never one code for two variants, never two codes for one variant.
- Store the barcode on the master record in your ERP. The ERP is the source of truth; a barcode typed by hand into a marketplace panel will eventually contradict it.
- Audit existing marketplace listings. Which listing carries which barcode? List the blanks, duplicates and mismatches.
- Resolve conflicts. If one barcode sits on two products, move one to a new number and note the stock history.
- Reprint warehouse labels. Shelf and item labels must match the system. Test them with a scanner.
- Declare the barcode immutable. Names, prices and images change; the barcode does not. If it must change, create a new product.
Once the barcode structure is right, every new channel stops being a matching project and becomes an "upload and publish" task.
Common barcode mistakes
These are the errors we see most often in real operations.
- One barcode for all sizes. Customers get the wrong size, returns climb, and stock reports become meaningless.
- Using the barcode as the SKU. It seems convenient until a supplier changes or a code is reissued, and every internal record breaks.
- Barcodes with spaces or letters. EAN-13 is digits only. Spreadsheets silently dropping a leading zero is a classic; keep the cell as text.
- Generating numbers with a wrong check digit. Scanners will not read them and marketplaces will reject them. Use a tool that calculates the check digit.
- Giving a bundle the component's barcode. A three-pack of socks and a single pair are different units; the bundle needs its own code.
- Listing a supplier's barcode under your own brand. Brand mismatch can take the listing down.
Barcodes in the warehouse
The real value of a barcode shows up in the warehouse. When picking, packing, returns acceptance and stock counts all run on scans, error rates drop sharply. Scanning a returned parcel ties it to the right order; scanning during a count removes the "counting by eye" error. Stock counts and negative stock errors covers that link in detail.
When you print labels, make sure the code is readable: enough quiet zone, sharp print, adequate size. A barcode squeezed onto a tiny label is the most expensive label you can buy, because every failed scan becomes a manual step.
How it works with Bulutegra
In Bulutegra, product matching runs on SKU and barcode. During the Match step of setup, barcodes from your ERP or catalogue source are compared with your marketplace listings; blanks, duplicates and mismatches are collected in one list and resolved channel by channel. This step usually takes one to three days. Then shadow mode starts: for a week or two the system only reads and writes nothing to any channel, so you can confirm the matches are right before anything goes live.
After matching, the barcode becomes the key to the single stock pool. A unit sold on one channel updates every other channel through that barcode. The quality tab lists listings with missing or malformed barcodes as findings you can fix with one click, and users in the Warehouse role handle returns and counts by scanning.
To see matching run on your own catalogue, request a demo.
Frequently asked questions
Can I sell on a marketplace without a GS1 barcode?
Some marketplaces and categories accept seller-generated identifiers or offer a barcode exemption, but brand matching and listing on global channels usually require a GS1-registered EAN or UPC. Check each marketplace's current listing rules for the category you sell in.
What is the difference between EAN-13 and UPC?
EAN-13 is a thirteen-digit code and UPC-A is a twelve-digit code. Both belong to the GS1 system and can identify the same product; a UPC with a leading zero becomes a valid EAN-13. UPC is common in the US, EAN-13 in Europe, Turkey and most other regions.
Do I need separate barcodes for each colour and size?
Yes. A barcode identifies the smallest sellable unit. Red size 38 and red size 40 are different products and each needs its own barcode. Reusing one barcode across variants leads to wrong-item shipments and unusable stock reports.


