A SKU is a code you make up to identify one variant: one size, one scent, one flavor. Shopify doesn't create SKUs for you; you type them into each variant's Inventory section or the product CSV's SKU column. A good pattern is short, readable and built from the same parts every time: a product code, then the option codes, such as CND-LAV-8 for an 8 oz lavender candle. Keep SKUs unique, never reuse one for a different product, and avoid characters spreadsheets mangle.
The short version
- One SKU per variant, unique across the store.
- Build it from parts: category or product, then options, then size.
- Use capital letters, numbers and dashes. Avoid spaces, slashes, and leading zeros.
- Don't put the price, the supplier or the date in it. Those change; SKUs shouldn't.
- Change SKUs in the product CSV or the admin. The inventory CSV shows SKUs but doesn't update them.
A pattern that works
| Part | Example | Notes |
|---|---|---|
| Product line | CND | 2 to 4 letters |
| Main option | LAV | Scent, flavor, color |
| Size or pack | 8 | Ounces, count, or S/M/L |
| Result | CND-LAV-8 | Read aloud as "candle, lavender, eight" |
For a made-up coffee roaster, Upcountry Roasters:
| Product | Variant | SKU |
|---|---|---|
| Kona Medium | 12 oz whole bean | KON-MED-12-WB |
| Kona Medium | 12 oz ground | KON-MED-12-GR |
| Kona Medium | 5 lb whole bean | KON-MED-80-WB |
| Ka'u Dark | 12 oz whole bean | KAU-DRK-12-WB |
Sizes are in ounces (80 for 5 lb) so they sort. Every SKU reads the same way, so anyone packing an order can tell what it is without looking it up.
Where SKUs go in Shopify
- Admin: open the product, then the variant, and fill in SKU in the Inventory section.
- Product CSV: the SKU column, one row per variant. Use this for more than a handful.
- Inventory CSV: the SKU column is for reference. Editing it there doesn't change the SKU.
Mistakes that cost you later
- Reusing a SKU for a new product after the old one is discontinued. Old orders and reports then mix the two.
- Meaningful-only-to-you codes like "A7". A new staff member can't read them.
- Leading zeros (0012). Spreadsheets drop them when you edit the CSV.
- Too long. Labels, pick lists and POS screens cut long SKUs off.
- Confusing SKU and barcode. The SKU is yours; the barcode is what a scanner reads. Shopify SKU vs barcode covers both.
Where this stops working
SKUs name what you sell. A maker also buys and uses dozens of things that aren't on the store: green coffee, bags, valves, labels. Those need codes too, and the pattern above works for them, but Shopify has nowhere to put them unless you list them as products. And a SKU names the product, not the batch: KON-MED-12-WB roasted Monday and the one roasted Friday share it. Shopify lot numbers covers telling batches apart, and Shopify SKU generator covers making codes in bulk.
How TaroStack does it
TaroStack for Shopify runs inside your Shopify admin and keeps your Shopify SKUs as they are, matched to your products. It adds codes for everything behind them, the green coffee, bags and labels, and a lot code for every batch, so Monday's roast and Friday's are told apart on the label and in a recall. Free for 14 days.
