A SKU is a code you invent to identify a variant in your own business, made to be read by people: CND-LAV-08 for an 8 oz lavender candle. A barcode is a number a scanner reads, usually a GS1 barcode (UPC or EAN) that identifies the product worldwide, or an internal code you print yourself. In Shopify, both live on each variant. SKUs match products in imports, purchase orders and reports; barcodes make counting, receiving and selling at POS fast. Many makers use both.
The short version
| SKU | Barcode | |
|---|---|---|
| Made by | You | GS1 (UPC/EAN), or you for internal codes |
| Read by | People | Scanners |
| Format | Letters, numbers, dashes | Numbers (UPC 12 digits, EAN 13) |
| Unique across | Your store | The world (GS1) or your store (internal) |
| Required by | Nobody, but useful | Retailers and some marketplaces |
When you need each
- SKU: as soon as you have more than a handful of variants, for CSVs, purchase orders and picking.
- Barcode: when a retailer stocks you (GS1), or when you want to scan in counts, receiving and POS (internal is fine).
Setting up both for a new product
- Choose the SKU from your pattern when you create the variant, such as CND-PLU-08.
- If a retailer will stock it, assign a GTIN from your GS1 prefix and print it on the label.
- If it's only for your own scanning, generate an internal code and print a sticker.
- Enter both on the variant in Shopify, or in the product CSV.
- Scan one finished unit to check the barcode reads and finds the right variant.
Doing both at creation saves fixing hundreds of variants later.
Can they be the same?
Some stores put the barcode number in the SKU field. It works, but you lose a readable code: "012345678905" tells a packer nothing. Keep the SKU readable and the barcode scannable.
How they work together
- Scanning a count reads the barcode; the count screen shows the SKU and name.
- A purchase order CSV can identify variants by SKU, by barcode, or both.
- The inventory CSV shows SKUs for reference; changing them there doesn't update them.
Duplicate barcodes cause errors in Shopify's stock counts; duplicate SKUs confuse imports and apps. Keep both unique.
A made-up example
Kahana Candle Co. sells in two gift shops and online. Each candle has a SKU (CND-PLU-08) for its own lists and a GS1 UPC printed on the label for the shops' registers. The shops scan the UPC; the packer reads the SKU on the pick list; Shopify holds both on the variant. Shopify SKU numbers and Shopify barcodes cover each in depth.
Where this stops working
Neither code says which batch a unit came from. Every 8 oz plumeria candle has the same SKU and the same UPC, whichever pour it was. For that, you need a lot code, printed beside the barcode or carried in a GS1-128 barcode on the case. Shopify lot numbers covers it.
How TaroStack does it
TaroStack for Shopify runs inside your Shopify admin and keeps your SKUs and barcodes as they are in Shopify, then adds the third code: a lot for every batch, printed on GS1-128 labels with its dates if you want them. Free for 14 days.
