What is a SKU? Complete Guide for Small Businesses#
If you sell anything โ online, in a shop, on Etsy, at a market โ you eventually hit a wall without a SKU system. Orders get mixed up. Inventory counts don't match. You can't tell your "blue medium" shirt apart from your "navy medium" shirt when reading a packing slip. SKUs solve all of this, and setting them up properly is usually a one-evening job.
This is the guide I wish someone had handed me the first time I built a product catalog. It covers what a SKU is, why you need them even at low volumes, how to design a system that scales, and the mistakes that force people to rebuild from scratch at 300 products.
What is a SKU?#
SKU stands for Stock Keeping Unit. It's a unique code โ usually letters and numbers โ that identifies one specific product variant in your inventory.
The key word is variant. A T-shirt design isn't a SKU. A T-shirt design in a specific size and color is a SKU.
TS-BLK-Mโ T-shirt, black, mediumTS-BLK-Lโ T-shirt, black, largeTS-WHT-Mโ T-shirt, white, medium
Three SKUs, one product line.
SKU vs. UPC vs. Barcode#
These three get confused constantly. Here's the clean version:
- SKU โ Internal. You create it. Unique to your business.
- UPC or EAN โ External. Globally unique, issued by GS1. Used at retail checkout.
- Barcode โ The visual representation of either a SKU or a UPC. Just the format.
You can have a SKU without a barcode. You can encode a SKU inside a barcode. You only need a UPC if you're selling through retailers like Amazon or Walmart that require one.
For most small businesses, a good SKU system is all you need.
Why you need SKUs, even with 10 products#
The pushback I hear is always the same: "I'm too small, I can just remember my products." It breaks down fast.
Without SKUs:
- You describe products in long form on invoices ("blue cotton shirt, medium, the softer one")
- Inventory counts require visual identification of every variant
- Order mistakes go up, especially when someone else helps you
- Multi-channel selling (Etsy + Shopify + markets) becomes a nightmare
- Accounting can't cleanly match items across platforms
With SKUs:
- Every product has one clean identifier everyone can use
- Inventory updates take seconds
- You can hire help without transferring your product memory to them
- Sales data actually means something when you analyze it
- Returns and exchanges are unambiguous
At 50+ products, no SKUs hurts. At 200+, it's impossible. I once looked at a client's inventory spreadsheet before they had SKUs and it took 40 minutes just to figure out what they had in stock.
The anatomy of a good SKU#
The goal is a code a human can partly read at a glance, without getting too long. A solid pattern:
[CATEGORY]-[PRODUCT]-[VARIANT]-[ATTRIBUTE]
Clothing:
APP-TS-BLK-Mโ Apparel, T-shirt, Black, Medium
Home goods:
KIT-MUG-CER-11OZโ Kitchen, Mug, Ceramic, 11 oz
Cosmetics:
SKC-MST-01-50โ Skincare, Moisturizer, Formula 01, 50 ml
Rules I'd stick to:
- Keep it short. 8-12 characters is the sweet spot.
- Use hyphens. Easier to read than one long unbroken string.
- Start broad, end specific. Category first, finest variant last.
- All uppercase. Consistency, and avoids
lvsIvs1confusion. - No spaces, no special characters. Beyond hyphens, these break in spreadsheets and on platforms.
Building your first SKU system โ 5 steps#
Step 1: List your categories#
Group everything into 3-6 top-level categories. Not more. "Mens Tops" and "Mens Bottoms" is fine. "Mens Short-Sleeve Crew-Neck Tees" is too granular.
Step 2: Pick 2-4 character codes per category#
- Apparel โ
APP - Accessories โ
ACC - Home โ
HOM - Kitchen โ
KIT
Write them down somewhere permanent. Never change them. Consistency is the whole game.
Step 3: Decide what variants matter#
For each product type, pick the attributes you actually differentiate on. Apparel: size + color. Electronics: capacity + color. Food: weight + flavor.
Step 4: Create variant codes#
- Sizes:
XS,S,M,L,XL,XXL - Colors:
BLK,WHT,RED,NVY,GRN(3 letters) - Materials:
CTN,POL,WOL,LTH
Step 5: Document the system#
Put it all in a Google Doc or Notion page. Every new product follows the rules. Without documentation, every new team member (or future-you, six months later) reinvents the wheel.
Mistakes to avoid#
- Sequential numbers only (
0001,0002,0003). Zero information at a glance. Useless if your spreadsheet gets corrupted. - Embedding prices. Prices change. SKUs shouldn't.
- Embedding dates. Your
SHRT-24-BLK-Mis awkward when 2024 inventory is still selling in 2026. - Reusing SKUs after discontinuing. Breaks your historical sales data.
- Too long. SKUs over 20 characters are painful on labels and pick slips.
- Mixing
0andO,1andI. Guaranteed typos and scan errors. - No room to grow. If all your sizes fit in one digit today, what happens when you add XXL or a new format?
When to write SKUs by hand vs. bulk-generate#
For your first 20-30 products, write them by hand. You want to think carefully about the structure.
Past 30, generate them. It's faster, more consistent, and avoids typos that cost hours to track down later.
The Toolatu SKU Generator creates clean formatted SKUs in bulk based on a pattern you define, with CSV export that imports straight into Shopify, WooCommerce, or any spreadsheet.
SKUs and barcodes โ when you need both#
Online-only? SKUs are enough. Shopify, Etsy, WooCommerce all track orders by SKU.
In-person or market sales? Add a barcode layer. Print Code 128 or QR code barcodes on product tags with the SKU encoded. You can scan with a phone or a USB scanner at checkout.
Need to turn a SKU into a scannable code? The QR Code Generator encodes any SKU string into a QR for product tags, packaging, or shelf labels.
SKUs on invoices#
Every invoice line should include the SKU. It's the fastest way to settle "I didn't get the right item" disputes โ and those come up more often than people expect once you're shipping regularly.
If you're writing invoices manually, the Invoice Calculator lets you add items with SKU, quantity, and price columns so invoices stay professional and trackable.
Tools that help#
Generate clean, formatted SKUs in bulk from a pattern you define. CSV export imports straight into Shopify, WooCommerce, or any spreadsheet.
Encode any SKU into a scannable QR code for product tags, packaging, or shelf labels. Export as PNG or SVG at any size.
Add SKU, quantity, and price columns to every invoice line โ the fastest way to settle order disputes and keep records clean.
The bottom line#
SKUs feel bureaucratic until the first time you have to track down a missing order or reconcile inventory across two platforms. Then you wonder how you lived without them.
Start simple: 3-letter category codes, short variant codes, all uppercase, hyphens between segments. Document the rules. Generate in bulk as you scale. That's 95% of what you need โ and you can set the whole thing up tonight.

