Settings → Product types & SKUs

The most powerful settings page. Product types are the dropdown behind every product, and they control how SKUs are generated, what variant options a new product starts with, and its target margin and forecast.

Where: setlist → Settings → Product types Feeds: the product Type dropdown, all SKU generation, default variant options, suggested prices, starting forecast, and the subcategory dropdown

What a product type controls

Each product type (e.g. Rings, Earrings) carries:

• An auto-derived SKU code (e.g. Ring → R) — read-only, never typed
• A SKU template — the ordered tokens that build SKUs for its products
• Default option types — the variant options a new product of this type starts with (e.g. Size: 5,6,7,8,9)
• Target margin — drives the suggested price for its variants
• Target forecast — the starting forecast a new product gets
• Subcategories — a dependent dropdown on the product form

The global SKU prefix

At the top of the page, set one SKU prefix for the whole shop (e.g. ACME). It's prepended to a SKU only when a type's template includes the "Prefix" token. Type it and click Save prefix (this one uses an explicit save, not autosave). Leave it blank for no prefix.

Adding & editing product types

1. In the Add product type box, type a Name (e.g. "Ring"). A live SKU code preview shows the auto-derived code as you type. Click Add product type.
2. Click a type to open its detail page, where you configure everything below. Each field there autosaves.
3. Delete a type with the trash icon on its detail page.

How the SKU code is derived

• It's the first letter of the name, uppercased: Ring → R, Earring → E.
• If that letter is already taken by another type, it uses first + last letter: a second type starting with R (e.g. "Rope") → RE.
• Existing types keep their codes — only the new/edited one adjusts. The code is read-only; you never type it.

The SKU template (token builder)

This is how SKUs are assembled. A SKU is an ordered list of tokens; each resolves to an uppercased code, empty ones are skipped, and the rest join with -.

Building it

On the type's detail page, the SKU template section shows your chosen tokens as an ordered list. Use Add a token… to add one, the up/down chevrons to reorder, and the trash icon to remove. A live Preview shows a sample SKU as you go. The builder autosaves.

If a type has no template, setlist uses a sensible default: Type code → Name → All option values.

The tokens

Codes are derived automatically: multi-word values use initials (Sterling Silver → SS, Gold Filled → GF); single-word values use the first two letters (Silver → SI); numbers keep their digits (size 7 → 7). You can override any option value's code on the value itself.

Use "Option type: {name}" to place a specific option at an exact spot (say, material right after the type code). Anything you place explicitly is dropped from the "All option values" catch-all so it never appears twice.

Examples

• Template Type code → Name → All option values for a necklace "Layered choker" in Gold Filled, 18": N-LAYERED-GF-18
• Template Prefix → Type code → Option type: Material → Name with prefix ACME: ACME-N-GF-LAYERED

Default option types

The variant options a new product of this type starts with. Set up, say, Size: 5, 6, 7, 8, 9 for Rings, and every new ring begins with those options pre-filled (the merchant can still change them on the product).

It uses the same row-based editor as the product page:

• Up to 3 option types (Shopify's limit), each a name + a list of values.
• Each value can have an explicit SKU code (blank = auto-derived).
• Tests required for this option (on by default) — turn off for options that don't need QA tests (e.g. Size).
• Apply forecast weights (off by default) — split this type's forecast across its values by weight instead of evenly (weights are relative; they don't need to total 100%). A Distribute evenly button helps.

Targets

Two defaults that pre-fill product work (both autosave):

• Target margin (%) — the gross margin used to suggest each variant's price (suggested = COGS ÷ (1 − margin)). Leave blank to fall back to a variant's own target.
• Target forecast + Per — the default forecast a new product of this type starts with (split across its variants):
  • Flat total — the number as-is.
  • Per week / Per month — a rate multiplied by the whole weeks/months in the assigned launch's window (falls back to a flat total when the launch has no end date).

Merchants still finalize price and forecast in the Review stage — these are just smart starting points.

Subcategories

A dependent picklist owned by the type (e.g. Earrings → Hoop, Stud, Threader…). Add them on the type's detail page; they populate the Subcategory dropdown on the product form once that type is chosen. Each rename autosaves on blur.

Set it up: step by step

1. Set the global SKU prefix at the top (or leave blank), and Save prefix.
2. Add a product type by name — the SKU code auto-fills.
3. Open the type and:
   • Build its SKU template (add/order tokens; watch the Preview).
   • Add default option types + values (set per-value SKU codes, forecast weights, or tests-required as needed).
   • Set Target margin and Target forecast.
   • Add subcategories.

Tips & gotchas

• The prefix only shows if the template includes the Prefix token. The default template doesn't — add the token if you want your prefix in SKUs.
• Codes auto-derive; you rarely type them. Override only the specific option-value codes that guess wrong.
• Targets are starting points, not locks — they pre-fill, and the merchant finalizes in Review.

See also

• Products · The Product Workspace
• Launches — the window that scales weekly/monthly forecast targets