Racklipedia
Racklify
​
eCommerce

Product ID vs. SKU vs. Model Number: What's the Difference?

Updated November 10, 2026
Published November 9, 2026

Product ID

Definition

A product ID is an identifier used to distinguish a product or product record in a catalog, ecommerce platform, or inventory system. Depending on the system, it may be an internal ID or a standardized code such as a GTIN.

Overview

Product ID is a general term for an identifier that distinguishes a product or product record in a catalog, ecommerce platform, or inventory system; compared to a merchant SKU and a manufacturer model number, a product ID can be either a platform/internal identifier or a standardized code such as a GTIN. In short: product IDs identify catalog records (may be standardized or internal), SKUs are merchant-assigned inventory keys, and model/part numbers are assigned by manufacturers to identify a family or configuration of items (with serial numbers optionally identifying single units).


This article explains what each identifier does, who assigns it, whether it’s standardized, whether it changes across sellers, and gives practical examples for apparel variants and electronics plus a checklist to choose the right identifier for inventory, support, receiving, and integrations.


How Each Identifier Works


Product ID (Platform / Standardized): A product ID may be an internal database key used by an ecommerce platform or WMS (for example, an internal numeric ID) or a standardized external identifier such as a GTIN/UPC/EAN that represents the product definition shared across channels. Platforms also use platform-specific identifiers (e.g., an ASIN on Amazon) to link listings, catalog metadata, and fulfillment records.


SKU (Stock Keeping Unit): A SKU is a merchant-created code used to track inventory, pricing, and variants inside a seller’s systems. SKUs are intentionally flexible so merchants can encode location, style, color, size, or other attributes. They are not standardized across companies and are not intended to be used as universal barcodes.


Model/Part Number: A model number (or part number) is assigned by the manufacturer to identify a product family, configuration, or component. It’s used in product documentation, compatibility checks, spare parts ordering, and warranty support. Model numbers are consistent across sellers for the same manufacturer and configuration, but manufacturers may have overlapping schemes across different brands.


Serial Number: A serial number uniquely identifies an individual manufactured unit (one-of-a-kind identifier). Serial numbers are critical for warranty, returns, and asset tracking and always change unit-to-unit.


Who Assigns It And Whether It’s Standardized


  • Platform/Internal Product ID: Assigned by the platform, marketplace, or your internal database; not standardized across systems unless mapped to a shared identifier.
  • GTIN/UPC/EAN (as Product ID): Assigned under GS1 standards by an organisation that has obtained company prefixes; standardized and globally recognized for product-level identification.
  • SKU: Assigned by the merchant or warehouse operator; not standardized.
  • Model/Part Number: Assigned by the manufacturer; standardized only within that manufacturer’s product catalog.
  • Serial Number: Assigned by the manufacturer during production; standardized format varies and is unique per unit.


Does The Identifier Change Across Sellers?


  • Platform Product ID: Changes by platform. The same GTIN may map to different internal product IDs on different marketplaces or in different ERP/WMS systems.
  • GTIN/UPC/EAN: Does not change across sellers for the same product configuration — multiple sellers carrying the identical GTIN refer to the same product definition.
  • SKU: Changes freely between sellers. Two retailers selling the same manufacturer model will typically use different SKUs.
  • Model/Part Number: Remains the same across sellers for the same manufacturer configuration; sellers reference the manufacturer’s model to describe the item.
  • Serial Number: Always unique to each unit and therefore different across all sellers and units.


Choosing The Right Identifier: A Flowchart-Like Checklist


  • Step 1 — Purpose: Do you need to identify a catalog record across marketplaces or integrate feeds? — Use a standardized GTIN/product ID where available; fall back to platform product IDs only if mapping to external codes isn’t possible.
  • Step 2 — Internal Inventory & Picking: Is the goal to run picking, replenishment, and bin locations inside your warehouse? — Use merchant SKUs (designed to include warehouse/location codes if needed).
  • Step 3 — Customer Support / Returns: Are you identifying the product family for warranty, spare parts, or compatibility? — Use manufacturer model/part numbers and capture the serial number for unit-specific support.
  • Step 4 — Receiving From Multiple Vendors: Will different suppliers deliver the same product? — Validate by GTIN or model number, not by SKU; record supplier SKUs as cross-reference fields.
  • Step 5 — Integrations / Marketplaces: Does the integration require a marketplace product identifier (ASIN, marketplace product ID)? — Map your internal product ID or GTIN to the marketplace product ID and include your merchant SKU for merchant-facing workflows.
  • Step 6 — Barcode Scanning: Will warehouse scanners use the code on cartons or labels? — Use barcodes tied to GTINs or SSCCs for logistic units; use barcodes that encode SKUs only if they are your internal standard and applied consistently.


Practical Examples — Apparel Variants And Electronics


Apparel (T-shirt with size/color variants): A manufacturer assigns a model number for the basic style (e.g., MOD-100). The brand may publish a GTIN per specific variant (GTIN for blue-large, different GTIN for blue-medium). A merchant assigns SKUs for each warehouse and sales channel (e.g., TS-BLU-L-001 for storefront, WH1-TS-BL-L for warehouse). Customer sees SKU or GTIN on packing slip depending on merchant practice; returns teams use SKU plus GTIN to reconcile stock.


Electronics (laptop): Manufacturer model/part number (e.g., ABC-15X-256) denotes configuration; a GTIN/UPC often exists for that configuration and will be used in retail listings. Each laptop also carries a serial number unique to the chassis, used for warranty and returns. Different sellers will use different SKUs to manage price, promotions, and inventory but will share the manufacturer model number and usually the GTIN for the same configuration.


Tips And Common Pitfalls


  • Don't Treat SKU As A Universal Barcode: SKUs are internal; they’re not a substitute for GTINs or manufacturer identifiers when publishing to marketplaces or shipping internationally.
  • Map, Don't Replace: Keep mapping tables between your SKU, manufacturer model, GTIN, and platform product IDs so integrations, returns, and analytics work consistently.
  • Capture Serial Numbers When Needed: For electronics and serialized apparel (e.g., limited edition), record serial numbers at receiving and before shipping to simplify warranty and chargeback handling.
  • Use GTINs For Shared Product Definitions: When multiple sellers list identical products, use GTINs to avoid mismatched listings and reduce customer confusion.


In short, the Product ID is a flexible term covering internal platform keys and standardized codes like GTIN; merchant SKUs are seller-assigned internal inventory codes, manufacturer model numbers describe product configurations consistently across sellers, and serial numbers identify individual units. Choose GTINs or manufacturer model numbers for cross-seller identification and integrations, SKUs for warehouse and merchant workflows, and serial numbers for unit-level support and traceability.

Sources And Additional Reading (4)

More from this term
Looking for a 3PL?

Compare warehouses on Racklify and find the right logistics partner for your business.