Racklipedia
Racklify
​
eCommerce

How to Create Product IDs for an Online Store: SKU Naming Rules

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 choices for an online store are a combination of system-generated identifiers and merchant-designed codes (like SKUs or supplier part numbers); to create product IDs you must decide which to use, design a clear SKU naming convention, and enforce rules that prevent duplicates and reserved characters while ensuring required GTINs are attached where marketplaces demand them.


Start by deciding whether you will rely on the e-commerce platform's automatic numeric IDs, create your own internal SKUs, or use supplier part numbers as the canonical identifier. Each approach has trade-offs for human readability, system integration, and marketplace compliance; the rest of this article explains those trade-offs and gives practical naming examples, a duplicate-check checklist, and syncing guidance for storefront, WMS, ERP, and 3PL systems.


Software-Generated IDs Versus Merchant-Designed Identifiers


Many platforms (Shopify, Magento, WooCommerce) create an internal database ID when you add a product. These IDs are typically opaque integers or GUIDs intended for system use and URL routing, not for human picking or supplier communications. Relying solely on them makes integration harder when different systems use different autogenerated schemes.


Merchant-designed identifiers—most commonly SKUs (stock-keeping units)—are controlled by the store owner. They can encode meaningful attributes (brand, category, size, color) to help pickers, customer service, and reporting. Suppliers also supply part numbers; those are authoritative for purchase orders but may not be ideal for storefront presentation or warehouse operations.


  • System ID: Machine-friendly, unique inside one system, non-meaningful (e.g., 12457892 or b3f9a7c2).
  • Merchant SKU: Human-readable, follows store rules, useful for picking, labeling, and internal reports (e.g., SHOE-MEN-10-BLK).
  • Supplier Part Number: Supplier-controlled identifier used on POs and invoices; keep mapped but avoid exposing if it confuses customers.


Simple SKU Naming Examples With Variants


When creating SKUs, keep them consistent, limited in length (12–20 characters is reasonable), and composed of stable elements. Below are example patterns with variants for a merchant selling apparel and accessories.


  • Pattern - Compact: [Brand][Category][Item#][Size][Color] — Example: ACME-TSH-042-L-BLK (brand ACME, t-shirt, item 042, large, black).
  • Pattern - Readable: [Category]-[Gender]-[Style]-[Size] — Example: TSH-M-CLASSIC-L.
  • Pattern - Warehouse-Focused: [Aisle][Bin][SKU] — Example: A05-B12-TSH042-L (useful if warehouse locations change rarely).
  • Variant Rule: Use a fixed order of elements and separators (dash or underscore). Do not mix spaces; use uppercase letters for consistency.


Avoid embedding volatile attributes (price, promotional tag) in SKUs because they change often and would require renaming the SKU. Instead, capture those attributes in product metadata.


Checklist To Avoid Duplicates And Reserved Characters


Before rolling out a SKU system, apply a checklist to prevent collisions and technical issues when syncing to other platforms or barcode systems.


  • Namespace Plan: Reserve prefixes or ranges for brands, private-label, and marketplace-only items so SKUs don’t overlap between lines.
  • Length Limit: Set a maximum SKU length and enforce it in your product import templates and WMS.
  • Character Rules: Disallow spaces and these reserved characters often problematic in URLs and integrations: <, >, %, #, ?, /, \", \\ and leading/trailing dots or dashes.
  • Case Policy: Choose either uppercase or lowercase and apply it across systems to avoid case-sensitive duplicates.
  • Check Digit/Sequence: For high volumes, add a numeric sequence or checksum to guarantee uniqueness (e.g., -0001, -0002).
  • Import Validation: Validate new SKUs against existing master lists before committing to the database.


Syncing IDs Across Storefront, WMS, ERP, And 3PL


Consistent identifiers between systems avoid order errors, mispicks, and reconciliation headaches. Decide on a primary key for your product master (often the SKU) and map all other systems to that key rather than trying to force every system to adopt external platform IDs.


  • Master Product Record: Maintain a single source of truth (product master) in your ERP or PIM that stores SKU, internal ID, supplier part number, GTIN, and alternate IDs.
  • Mapping Table: Publish a mapping table the WMS and 3PL can consume that lists storefront SKU ↔ WMS item ID ↔ supplier part number ↔ GTIN.
  • Automated Sync: Use API-based integrations or scheduled ETL jobs to sync updates; avoid manual CSV edits unless controlled by change management.
  • Change Control: Never change a SKU in place; if you must rename, create an alias entry and keep the old SKU mapped for historical orders and returns.
  • Barcode Labels: Print labels that show SKU and GTIN (when required) so pickers and carriers see both identifiers.


When A Store SKU Is Not A Substitute For A GTIN


A store-specific SKU is an internal identifier and is not a substitute for a GTIN (UPC, EAN) where marketplaces, customs, or retailers require one. GTINs are standardized, licensed identifiers issued via GS1 and recognized globally; some channels (Google Shopping, Amazon, major retailers) require GTINs to list products or enable features like advertising and Buy Box eligibility.


  • Marketplace Rules: Check each marketplace’s product identifier requirements; they often demand GTINs for branded consumer goods.
  • Regulatory Use: GTINs are used in trade documentation and customs processes for certain product categories—keep the GTIN in the product master.
  • Mapping: Store SKUs should be mapped to GTINs in your system so feeds and invoices deliver the standardized identifier when required.


Practical Implementation Tips


Roll out SKUs in stages, start with best-selling lines, and test end-to-end flows (web order → WMS pick → 3PL fulfilment → ERP invoice). Document the naming standard in a short guideline and train customer service and warehouse staff on reading SKUs. Use automation to enforce rules at product import and prevent human error.


  • Audit: Run periodic audits to detect duplicates and orphan SKUs.
  • Fallbacks: Keep the platform-generated ID as a fallback field in integrations in case of malformed SKUs or import failures.
  • Barcode Strategy: Encode SKU in internal barcodes and preserve GTIN in consumer-facing barcodes when selling through retailers.


In short, the Product ID strategy for an online store should use merchant-designed SKUs as the primary human-readable identifier, keep system-generated IDs as internal fallbacks, map supplier part numbers and GTINs in a central product master, and enforce naming and sync rules to avoid duplicates and integration failures.

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.