How to create a SKU naming convention for Shopify

A useful SKU naming convention helps people and systems identify a Shopify variant without turning the code into a second product description. The best format is short, unique, consistent, and stable enough to survive catalog growth.

Start with the systems that consume the SKU

List every place where the value is searched, printed, imported, or matched: Shopify admin, pick lists, POS, a warehouse management system, an ERP, supplier files, and marketplace feeds. Record the strictest length and character rules. A naming format that works only inside Shopify is not dependable if a downstream system truncates or normalizes it.

Shopify permits stores to create their own format and recommends short, consistent, unique SKUs without spaces or confusing special characters. Its current SKU guidancealso emphasizes planning for catalog growth.

Encode only attributes that help operations

Choose two or three stable attributes that staff use to distinguish variants, such as product family, style, color, size, or package quantity. A format such asTSH-104-BLK-M can be readable without storing every characteristic in the code. Product titles and metafields should hold descriptive information that changes frequently.

Avoid prices, inventory quantities, temporary locations, campaign names, or vendor names that are likely to change. Renaming a working SKU can break a match with order history, warehouse records, and integrations even when the new code looks more organized.

Define one pattern with explicit rules

Write the convention before generating values. Define the allowed characters, separators, maximum length, abbreviations, case, and the uniqueness mechanism. Decide whether leading zeros are meaningful and whether systems preserve them. Reserve space for new categories, sizes, or variants so the format does not run out of combinations.

Use the same abbreviation everywhere: if black is BLK, do not mixBK, BLACK, and Blk. Do not rely on letter case alone to distinguish two products because exports and integrations may normalize it. Give every variant its own final value, including variants of the same product.

Test the convention before migrating the catalog

Generate a representative sample that includes the longest product family, similar color names, unusual sizes, bundles, and future variants. Test search, labels, CSV export, import, and downstream matching. Check that the format is understandable to someone who did not design it.

Before applying new SKUs in bulk, export the current catalog, preserve a mapping from old to new values, and check proposed values against all existing variants. The guide tochecking a Shopify product CSV before importcovers the file boundary; the guide tofixing duplicate identifierscovers collisions found during migration.