SKU Vs UPC Vs GTIN: How They Differ And When To Use Each

SKU is a stock keeping unit used to identify and manage a specific product or variant. SKUs are internal identifiers set by retailers or distributors. They often coexist with external product identifiers such as UPCs and GTINs; understanding how each identifier is used avoids confusion in procurement, listing and fulfillment.

Retailers frequently ask whether a SKU is the same as a UPC or GTIN. The short answer: they are different systems with different purposes. A SKU is internal and flexible; UPC and GTIN are standardized, globally-recognized product identifiers used by manufacturers, marketplaces and trading partners.

Key Differences Between The Identifiers

• SKU: Internal code used to track product variants, created and managed by the retailer or warehouse. Not standardized across companies.
• UPC (Universal Product Code): A barcode symbology primarily used in North America that encodes a GTIN-12; assigned to a trade item by the brand or manufacturer.
• GTIN (Global Trade Item Number): A family of GS1 identifiers (GTIN-8, GTIN-12, GTIN-13, GTIN-14) used globally to identify trade items consistently across supply chains.

When To Use Each Identifier

• SKU: Use for internal picking, replenishment, returns handling and reporting by variant. Useful when multiple sellable units map to the same GTIN (e.g., bundled products).
• UPC/GTIN: Use when interacting with suppliers, marketplaces, barcode scanning at POS, EDI transactions and customs documentation; required by many global retailers and online platforms.
• Both: Map SKUs to GTINs/UPCs to ensure accurate listings, avoid duplicate entries and enable cross-referencing between internal systems and external partners.

How They Interact Technically

A SKU record in your ERP or WMS typically contains fields for the merchant’s SKU, the manufacturer’s GTIN/UPC, and any marketplace identifiers (ASIN, EAN). Integration layers or middleware translate SKUs into GTINs when sending orders to suppliers or marketplaces. Scanners read barcode labels (UPC, EAN) at the receiving dock and the scanned GTIN is matched to the internal SKU for putaway.

Practical Example

A brand sells a bottled sauce that has a manufacturer-assigned GTIN-12 printed as a UPC. A grocery retailer assigns its own SKU (GROC-SAU-001) to track shelf placement, promotional pricing and shrink. When the retailer receives cases, the UPC scanned on the case maps to the retailer’s SKU so the WMS can update stock levels and route items to the right store bay.

When You Might Only Need One Identifier

• Small independent sellers: Might operate only with SKUs if they don’t sell through channels requiring GTINs.
• Private label lines: If you manufacture your products, you still benefit from GTINs when selling to other retailers or marketplaces.

Common Problems And Solutions

• Duplicate Listings: Occur when the same GTIN is assigned multiple internal SKUs without reconciliation; fix by regular SKU-GTIN mapping audits.
• Mismatched Attributes: When a GTIN describes a different variant than the SKU; resolve with stricter incoming inspection and supplier data validation.
• Marketplace Rejections: Marketplaces often require GTINs for listings; maintain a master mapping table to automatically populate marketplace feeds.

Tips For Retailers

• Maintain A Master Mapping Table: Store SKU-to-GTIN/UPC mappings in a single source of truth (PIM or ERP).
• Validate Supplier Data: Require suppliers to provide GTINs and sample labels before listing or receiving stock.
• Use Barcodes On Labels: Print both the internal SKU and the GTIN barcode on pack labels to make receiving and returns smoother.

In short, the SKU is your internal product identifier and should be used alongside GTINs/UPCs to ensure smooth trading, accurate listings and reliable fulfillment across retail and ecommerce channels.