UPC, GTIN, EAN, and SKU: Which Product Code Goes Where?

Opening Answer

Use UPC or EAN as an external, GTIN-based product identifier; use SKU as an internal, merchant-controlled reference. Keep these identities separate and map each value to the field required by the relevant store or marketplace. Never invent a code to clear a feed error.

UPC-A is a GTIN-12, while EAN-13 is a GTIN-13. GTIN is the umbrella family for standardized global trade item identifiers. A SKU belongs to the merchant’s catalog system and does not become a GTIN simply because it appears in a product feed.

Table of Contents

• What is the difference between UPC, GTIN, EAN, and SKU?
• Which code belongs in each channel field?
• When does a product need a new GTIN?
• How do you audit a catalog for identifier errors?
• What should you never fabricate?
• Sources
• FAQ

What Is the Difference Between UPC, GTIN, EAN, and SKU?

The key distinction is ownership and purpose: GTIN, UPC, and EAN identify products externally, while SKU identifies a merchant’s internal catalog item.

A SKU can encode size, color, pack count, warehouse logic, or another internal convention. For example, BLUE-MUG-12OZ may be a useful merchant SKU, but it is not a UPC, EAN, or GTIN. A barcode printed for internal warehouse use also does not become a globally assigned product identifier.

Preserve both values when both exist. The GTIN supports product identity across systems; the SKU supports internal operations. GS1’s GTIN guidance describes GTIN as a global trade item identification structure, not a replacement for every internal catalog code.

Which Code Belongs in Each Channel Field?

Map each value according to the field’s definition, ownership, and accepted format.

A channel may call a field “product ID,” “barcode,” “GTIN,” “UPC,” or “EAN.” Similar labels do not guarantee identical requirements. Confirm the destination field before exporting, send the supported GTIN representation, and preserve leading zeroes.

Keep SKU conventions stable and documented so inventory workflows remain dependable. This makes a SKU useful for inventory management without confusing it with a globally assigned identifier. For marketplace work, check identifier mapping together with titles, attributes, and variations; the Amazon listing optimization checklist is a related reference.

When Does a Product Need a New GTIN?

A product needs a new GTIN only when its product identity changes under the applicable identification rules. A feed error alone is not a reason to create one.

A different SKU does not automatically require a new GTIN. Merchants may use separate SKUs for warehouses, suppliers, campaigns, or internal workflows while selling the same product. Conversely, materially different products, variations, pack configurations, or bundles should not be grouped under one external identifier merely because they share a convenient SKU.

Review the item at the level the customer is buying:

1. Determine whether it is the same product, a distinct variation, a different pack, or a separate bundle.
2. Check whether the product owner has already assigned a UPC, EAN, or other GTIN.
3. Preserve an assigned identifier exactly, including leading zeroes.
4. If ownership or assignment is unclear, resolve that question before publishing.

Do not infer a GTIN from a title, SKU, image, or supplier description. Use the GTIN standards as the authoritative framework for what the external identifier represents.

How Do You Audit a Catalog for Identifier Errors?

A reliable audit checks format, ownership, product relationship, and destination field.

1. Confirm that external identifiers are stored separately from SKU values.
2. Treat UPC-A values as GTIN-12 and EAN-13 values as GTIN-13.
3. Preserve leading zeroes; remove accidental spaces, punctuation, and spreadsheet formatting changes.
4. Confirm that each identifier belongs to the submitted product, variation, pack, or bundle.
5. Compare values with the product record and available supplier documentation.
6. Verify that the destination channel accepts the supplied format.
7. Check for one external identifier attached to unrelated products.
8. Record missing identifiers separately from invalid identifiers.
9. Retain SKU as the internal join key for inventory and operational systems.
10. Route unresolved ownership questions for review rather than filling the field with a guess.

A practical catalog structure keeps separate columns for sku, gtin, upc, ean, brand, and mpn, even when some are empty. This prevents an absent GTIN from being silently replaced with a SKU during export. It also keeps product identity separate from listing copy workflows.

For connected catalog, inventory, and publishing workflows, Stack Builder can serve as a planning reference. The source of truth for each identifier should still be explicit. Keep an audit trail showing the original value, normalized value, destination field, and reason for any exception.

What Should You Never Fabricate?

Never fabricate a GTIN, UPC, EAN, brand, or MPN to make a feed pass validation.

If a product has no genuine external identifier, follow the destination channel’s missing-identifier process. That may mean leaving the field blank, declaring that an identifier does not exist, or supplying other genuine product attributes. The correct response depends on the channel’s rules and the product’s actual data.

Do not generate digits from a SKU, reuse one identifier for unrelated items, add a leading zero to imitate another format, or convert an internal number into a supposed GTIN. These shortcuts damage product matching and complicate future corrections.

The same rule applies to brand and MPN. Google’s merchant identifier guidance says not to submit invented GTIN, brand, or MPN values when legitimate identifiers do not exist.

Sources

• Google Merchant Center: Product identifiers
• GS1: GTIN standards
• GS1 US: UPCs, barcodes, and prefixes
• Shopify: SKU guidance