SKU vs UPC/GTIN: How They Differ and When To Use Each

SKU A Stock Keeping Unit, an internal identifier used by a merchant to distinguish and track a specific sellable item. SKUs are designed for internal inventory control and do not replace global product identifiers such as UPCs, EANs or GTINs.

Merchants frequently confuse SKUs with barcodes. The fundamental difference is scope. SKUs are merchant-created, flexible, and tailored to operational needs; UPCs/GTINs are standardized codes assigned to a product type and intended for universal recognition across retailers, marketplaces, and supply chains.

Key Differences

• Issuer: SKUs are assigned by the merchant; UPCs/GTINs are issued by the brand owner or via GS1.
• Scope: SKUs are internal and vary per merchant; UPCs/GTINs are global identifiers recognized across systems and markets.
• Purpose: SKUs support picking, storage, and reporting; UPCs/GTINs support point-of-sale scanning, marketplace listings, and cross-company matching.

When To Use SKUs

Use SKUs everywhere you need merchant-level control over inventory processes. They’re critical for warehouse binning, pick lists, internal reporting, promotions, and channel-level product mapping. SKUs can encode attributes like pack size, color, and fulfillment requirements that matter to your operations.

• Internal Operations: Use SKUs for WMS location mapping, cycle counting, and SKU-level reorder points.
• Channel Differentiation: Use separate SKUs if the same UPC is sold in different packaging or bundled with accessories by your business.

When To Use UPCs/GTINs

UPCs/GTINs should be used when dealing externally — consumer point-of-sale, supplier catalogs, and marketplace listings. Marketplaces and many retailers require GTINs for product matching, listings, and analytics. If you sell branded products manufactured by others, make sure you map their GTINs to your SKUs for accurate catalog management.

• Retail Scanning: Use GTINs for checkout scanning and cross-retailer identification.
• Marketplace Compliance: Marketplaces (Amazon, Walmart) often require GTINs for product listings and matching.

Mapping Strategies

Because SKUs and GTINs serve different audiences, robust mappings are necessary. Maintain a master mapping table that links each SKU to its GTIN(s), vendor SKU, and any channel-specific identifiers. This map prevents listing errors, supports accurate invoicing, and helps reconcile inventory across trading partners.

• Many-To-One Mapping: Multiple SKUs may map to a single GTIN when merchants split stock by warehouse, bundle, or regional packaging.
• One-To-Many Mapping: A single SKU mapping to multiple GTINs is less common but possible if the merchant intentionally groups similar GTINs for simpler inventory control.

Practical Example

A large electronics brand assigns GTINs to every model of headphones. A reseller purchases identical headphones but sells them in a branded bundle with extra cables. The reseller creates its own SKU for the bundle to track bundled stock and sales, while the GTIN remains the authoritative code for the base headphone model. On the reseller’s ecommerce platform, the SKU appears in the admin and pick lists; the GTIN appears on the product page and shipping label barcode to meet carrier and marketplace requirements.

Common Pitfalls And Tips

• Pitfall: Treating GTINs as SKUs — don’t rely on UPCs alone for internal logic; they may not reflect your internal variations or bundling.
• Tip: Keep a central reference table that captures SKU ↔ GTIN ↔ Vendor SKU relationships and expose it to ERP, WMS, and ecommerce channels via integration.
• Tip: If selling on marketplaces, validate GTIN requirements early and map SKUs accordingly to avoid delisting or listing duplication.

In short, the SKU is the merchant’s internal key for tracking sellable items; it complements, rather than replaces, globally recognized UPCs/GTINs that enable external product identification and cross-seller consistency.