Trade Item vs SKU vs GTIN: Choosing The Right Identifier For Retail

Trade Item A product or service for which predefined information may be retrieved and which may be priced, ordered, or invoiced in the supply chain. Identifying which identifier to use for each trade item—internal SKU, GTIN, or serial—drives accuracy in ordering, fulfillment, and invoicing. Retailers must choose identifiers based on the intended use: internal operations, external commerce, or unit-level traceability.

Confusion between identifiers causes duplicate records, misplaced inventory, and pricing errors. This article clarifies roles and provides practical rules for when to require GTINs, create SKUs, or capture serial/lot information for trade items in retail environments.

What Each Identifier Is For

Identifiers are tools. The GTIN enables cross-company commerce; the SKU optimizes internal processes; serial/lot numbers support traceability and after-sales service. Treat them according to the business function they serve rather than assuming they’re interchangeable.

• GTIN: A globally unique identifier used by trading partners and required by many retailers and marketplaces for product listing and ordering.
• SKU: A merchant-specific code designed for store layout, inventory bins, and merchandising analytics.
• Serial/Lot: Unit-level identifiers used for warranty, recall management, or regulated goods that need traceability.

When To Use GTIN

Require GTINs when items are part of cross-company commerce—supplier catalogs, EDI purchase orders, marketplace listings, or barcode scanning at checkout. GTINs eliminate ambiguity across systems and partners by providing a recognized standard link to product data.

• Cataloging: Use GTINs for supplier-provided product catalogs to avoid duplicate entries.
• EDI & Invoicing: GTINs align purchase orders and invoices across trading partners.
• Barcode Scanning: GTIN-based barcodes are read at POS and in warehouses for receiving and picking.

When To Use SKUs

Create SKUs for store-specific operations: pricing strategies, promotions tied to shop-floor locations, and internal analytics. SKUs can encode merchandising attributes (department, category, size) and are typically optimized for human readability and internal systems.

• Store Operations: SKUs guide shelf placement, replenishment triggers, and cycle counts.
• Reporting: SKUs feed sales and margin reports tuned to merchant semantics.
• Variants: When a GTIN covers a range but the merchant needs finer control, map multiple SKUs to a single GTIN.

When To Capture Serial And Lot Numbers

Capture serial or lot numbers for items requiring traceability—for recalls, warranty claims, returns, or regulated products (pharmaceuticals, medical devices, some electronics). These identifiers are not replacements for GTIN or SKU; they are supplemental to enable unit-level tracking and post-sale service.

• Recalls: Lot numbers let retailers identify and isolate affected inventory quickly.
• Warranties: Serial numbers support ownership and service history for individual units.
• Returns: Serial/lot data helps validate returns and detect fraud.

Practical Rules For Retailers

Adopt practical governance to prevent identifier chaos. Standardize on GTINs for external commerce, use SKUs for internal processes, and capture serial/lot data only where necessary to manage risk or obligation.

• Require GTINs: For any new supplier product that will appear on the website, marketplace, or be ordered via EDI.
• Generate SKUs: Automatically create SKUs from a template that includes department and category to keep internal systems consistent.
• Limit Serial Capture: Only enable unit-level tracking where service or regulation demands it to avoid data bloat.

Example: Clothing Variant Management

A supplier sells a T-shirt in three sizes and two colors. The manufacturer may assign a unique GTIN per size/color combination. The retailer might choose a single SKU per color and manage size as a location-level attribute, or create a SKU per size/color depending on inventory control needs. The decision affects ordering, picking, and returns; aligning identifier policies with operational needs is essential.

In short, the Trade Item is the commercial unit that needs identification. Use GTINs to speak the same language as suppliers and marketplaces, SKUs to run store and DC operations efficiently, and serial/lot numbers only when true unit-level traceability is required. Clear policies linking identifiers to business functions prevent duplicate records, mis-picks, and reconciliation headaches.