Marketplace Management

Marketplace Barcode and GTIN Guide: Prevent Product Matching Errors

Share
Marketplace Barcode and GTIN Guide: Prevent Product Matching Errors

How to manage barcodes and GTINs across marketplaces: valid GTIN rules, check digit calculation, barcodes for bundles, common errors and an audit checklist for your team.

If you list the same product with different barcodes on Trendyol, Hepsiburada and Google, each system sees three separate products. The result is unmatched catalogues, rejected listings and stock and order confusion. This article covers the essentials of managing barcodes and GTINs across marketplaces, plus a checklist you can apply right away.

GTIN, EAN and barcode: are they the same thing?

A barcode is a number drawn as lines; the real identity is the number itself. That number is called a GTIN (Global Trade Item Number). According to the Google Merchant Center Help pages, a GTIN can have 8, 12, 13 or 14 digits and comes as UPC, EAN, JAN or ISBN. For retail products in Turkey the most common format is the 13-digit EAN (GTIN-13). Books use the 13-digit ISBN, and multipacks use the 14-digit ITF-14.

The key principle: the manufacturer assigns the GTIN. If another seller sells the same product, its GTIN is identical to yours; that is exactly how matching works.

Why do marketplaces ask for barcodes?

Marketplaces group sellers of the same product on a single product card. To do that they need a key that identifies the product, and that key is usually the barcode. A wrong or duplicated barcode can attach your product to someone else's card or leave it unmatched.

Requirements vary by platform and category. A 2020 e-commerce guide states that barcodes are mandatory on Amazon, Trendyol and Hepsiburada and optional on N11. Rules change, so do not treat this as current; confirm the requirement for your category in the help centre of your own seller panel.

What does a valid GTIN look like?

Google's rules give a good framework for checking validity:

  • Length: 8, 12, 13 or 14 digits. Spaces and dashes are accepted but ignored.
  • Check digit: the last digit is calculated from the preceding digits. If it is missing or wrong, the number is invalid.
  • Restricted prefixes: numbers starting with 02, 04 or 2 fall in restricted ranges; Google asks that they not be submitted as GTINs. Coupon ranges (prefixes 05, 98, 99) must not be submitted either.
  • One number per variant: every variant, such as each colour and size, has its own GTIN.

Hypothetical example: calculating a check digit

For EAN-13 you calculate the check digit with the GS1 method. Take a made-up example: the first 12 digits are 869123456789. Starting from the left, multiply the digits alternately by 1 and 3: 8×1 + 6×3 + 9×1 + 1×3 + 2×1 + 3×3 + 4×1 + 5×3 + 6×1 + 7×3 + 8×1 + 9×3 = 130. Because the total is a multiple of 10, the check digit is 0 and the number becomes 8691234567890. This number is invented purely to show the arithmetic; it does not belong to a real product and must not be used in a real listing. For real products the number comes from the manufacturer. A spreadsheet formula or a small script is enough to validate the numbers in your file in bulk.

Where do you get a barcode?

If you make your own brand, you obtain barcodes in Turkey by applying through GS1 Türkiye. If you sell another brand's product, the number is on the packaging or available from the manufacturer. Google's help page likewise says the packaging or the manufacturer is the most accurate source. Products that only you sell, or that carry your own brand, generally have no GTIN; Google does not require a number in that case and recommends submitting brand and MPN (manufacturer part number) instead.

Avoid two things. First, inventing numbers: Google explicitly says not to guess or make up values and warns that incorrect identifiers can get a product disapproved. Second, putting your internal stock code (SKU) in the barcode field; Google says that is wrong as well.

The most common barcode mistakes

  • The same barcode used on more than one variant
  • Long numbers turned into scientific notation, or leading zeros dropped, in Excel
  • Hand-typed numbers with a wrong check digit
  • The multipack and the single unit entered with the same number
  • Different barcodes used across marketplaces and the website

The Excel problem is especially sneaky: if you do not keep the barcode column in text format, 13-digit numbers are silently corrupted, and you only notice when a listing is rejected.

Hypothetical example: the scale of the problem

Suppose you have a catalogue of 400 variants and 24 of them turn out to have duplicated or corrupted barcodes. That is 6 percent of the catalogue (24 / 400). Each conflict carries a risk of a wrong card match on the marketplace and of disapproval in Merchant Center. If you receive 200 orders a month and 6 percent of them belong to the affected variants, 12 orders are exposed to the risk of a wrong product card or a stock mix-up. The figures only illustrate the logic.

Special cases and process

A few cases outside standard single products are the real source of barcode errors.

Sets, bundles and multipacks

Sets are the most confused area. According to Google's help page, a bundle created by the manufacturer uses the bundle's own GTIN, while a bundle you create as a seller uses the main product's GTIN, MPN and brand. In practice: define the manufacturer's multipack as a separate product, and link sets you build yourself to the main product. Explain this distinction clearly to your product team. Writing the single unit's barcode onto a multipack is the easiest way to tie two different products to one card.

Products without barcodes: handmade and custom-made

Not every product has a GTIN. Products carrying your own brand, or sold only by you, may have none. The answer is not to produce a number but to describe the product through other fields: a clear brand name, a unique MPN and a consistent product title. Marketplaces may have their own rules for selling without barcodes, so find out from your seller panel whether your category has a barcode exemption or a separate application route, and write it down.

A written barcode policy for your team

Barcode errors are usually process errors, not technical ones. If the person adding a new product does not know where to get the number, who approves it and which file to enter it in, mistakes are inevitable. A one-page policy is enough:

  • Source: numbers are taken only from manufacturer documents or the GS1 record.
  • Owner: one person or team approves the barcode field in the catalogue.
  • Format: the barcode column is always text, and the check digit is validated before the file is saved.
  • Change: if the barcode of a live product must change, first list which channels it affects.

These rules matter most when you open a new marketplace or migrate from another platform, because bulk product imports are when barcode errors multiply fastest.

Managing from one source, and auditing

Entering the barcode separately on every channel invites mistakes; a fix on one channel does not reach the others, and months later the same error reappears somewhere else. A sturdier model: define the barcode once in the central catalogue (your ERP, a product information system or your main store such as Shopify) and let it flow from there to every other channel. On Shopify, product variants have a barcode field, which can be the natural source for the Google channel and marketplace integrations. For how to build the integration layer, see our article on ready-made integrator or custom API. For how stock and price are synchronised across channels through the barcode, read our guide on multichannel stock and price synchronisation.

Barcode audit checklist

  1. Export all barcodes in the catalogue to a single file and set the column to text format.
  2. Validate the digit count (8, 12, 13, 14) and the check digit in bulk.
  3. Find duplicate barcodes; each variant needs its own number.
  4. Filter out numbers starting with 02, 04 or 2 and those in the coupon ranges.
  5. For products without barcodes, check that brand and MPN are filled in.
  6. Confirm each marketplace's current barcode rule in its own seller panel.
  7. Make corrections in the central catalogue first, then push them to channels.
  8. Repeat the same check on newly added products every month.

We covered barcode-related disapproval reasons and fixes in Merchant Center in Google Merchant Center product feed errors. For the link to seller score and the Buy Box, see our Trendyol store management guide.

Conclusion

A barcode may look like a small field, but it is the key to your product being recognised correctly on marketplaces and in Google. Get the number from the manufacturer, verify the check digit, give every variant its own number and manage it from a single source. These four habits prevent most matching and disapproval problems from the start.

Sources: Google Merchant Center Help, "Use the GTIN [gtin]" and "About unique product identifiers" pages (accessed 2026); Yengeç, "Evrensel Barkod Uygulaması Hakkında 4 Soru-Cevap" (2020, updated 2022); GS1 check digit method. Calculation examples are hypothetical.

More

Related posts