Operations

One naming rule, every variant, no typos

SKUs break when two people invent them. Define the pattern once, generate the full variant grid, and paste the result into your product import — no spaces, no duplicates.

1 min Runs in your browser Free, no signup Updated Feb 12, 2026

Inputs

Edit any value — the result updates as you type.

Short, uppercase, no spaces.

Category or product family.

Comma separated. First three letters become the code.

Comma separated.

Result

SKUs generated 12 Copy the list into Shopify, a CSV column or your ERP. Pattern: prefix-style-colour-size.
Generated SKUs

    Every calculation runs locally. Nothing you type is sent anywhere — check the network tab.

    Most SKU chaos starts with good intentions: someone names the first product by hand, then a second person names the next one slightly differently. Six months later nobody can find anything.

    A SKU is not a product name. It is a machine key: stable, boring and predictable. The colour code should never change because marketing renamed 'Sand' to 'Desert Beige'.

    Generate the grid below, export it, and keep the naming rule in a document that new hires actually read.

    How it is calculated

    SKU = prefix + "-" + style + "-" + colour code + "-" + size
    colour code = first three letters of the colour, uppercase
    example     = ACME-TEE-BLA-S

    Reading the result

    1. Keep the pattern short — Eight to fourteen characters is the sweet spot. Long enough to stay unique as you add categories, short enough that warehouse staff and support agents can read it back over the phone.
    2. Never use spaces — Shopify, Amazon and most ERP imports treat spaces as delimiters. Hyphens are safe across every marketplace feed and survive CSV round-trips.
    3. Lock the rule before launch — Changing a SKU after launch breaks order history, ad catalogues and 3PL mappings. Decide the pattern while the catalogue is still small, then keep it.

    2026 benchmarks

    Metric Typical range Why it matters
    SKU length 8–14 characters Unique without becoming unreadable.
    Variant grid 12–60 SKUs Beyond that, manage by table, not by pattern.
    Separator hyphen Safe in CSV, Shopify and Amazon feeds.
    Reserved characters no spaces, no commas Both break common importers.
    Case uppercase Prevents duplicate keys on case-sensitive systems.

    Conventions that survive contact with marketplaces, 3PLs and ERPs.

    Questions

    Can I export this as CSV?
    Copy the generated list and paste it into a spreadsheet column. In the next release this page will export a mapped CSV file directly, including variant price and option columns.
    What if two colours start with the same three letters?
    Extend the code to four letters for those colours, or insert an extra segment (for example a season code). Consistency matters more than brevity — just apply the rule to every colour.
    Should the size be at the end?
    Yes, by convention. Sorting by SKU then groups styles and colours together, which is what warehouse picking and catalogue exports expect.

    Field limits differ between Shopify (255 characters), Amazon (40) and most ERPs. Keep SKUs well under the smallest limit you use.