A SKU (stock keeping unit) is an alphanumeric code you create yourself to identify one specific version of a product, down to its size, color, or style, so you always know exactly what’s in stock, what’s selling, and what needs reordering. Unlike a barcode number, a SKU is entirely internal: you invent the format, you control the length, and nobody outside your business needs to recognize it.
If you sell more than a handful of physical products, whether that’s handmade goods, wholesale inventory, or print-on-demand merchandise, a consistent SKU system is one of the simplest operational habits that prevents real headaches later: mismatched stock counts, confused reorders, and invoices that don’t match what actually shipped.
What a SKU Actually Is (and Isn’t)
SKU vs. UPC vs. barcode
A SKU and a UPC (Universal Product Code) solve different problems. A UPC is a standardized 12-digit numeric code administered by GS1 US, the organization that assigns these codes so that any retailer, anywhere, can scan the same product and get the same result. Getting a UPC means purchasing and licensing a code through GS1 or an authorized reseller.
A SKU is the opposite: a code you create for your own internal use, with no registration, no licensing fee, and no external body involved. You can freely design your own SKU format, and a barcode is simply a scannable visual representation, whether that barcode encodes a UPC or your own internal SKU.
Why a generic product name isn’t enough
“Blue T-shirt” tells you what the item is, but not which size, which print run, or which supplier batch. Once you have more than one variant of a product, size, color, material, or packaging, the plain-language name stops being enough to track inventory accurately. A SKU exists to carry that extra layer of detail in a short, consistent code your team (or your invoicing software) can search and sort on.
What to Include in a SKU
The building blocks
Most workable SKU systems combine three kinds of information into one code: a category or product line abbreviation, one or more variant identifiers (color, size, material), and a sequence number to keep otherwise-identical codes unique. For example, a candle business selling a lavender scent in a medium jar might use CAN-LAV-M-001, where CAN marks the candle product line, LAV is the scent, M is the size, and 001 is the sequence number for that specific batch or variant.
How long should a SKU be
There’s no fixed rule, but shorter is easier for your team to read, type, and scan without error. One widely cited recommendation from Michael Manzione, COO of Rakuten Super Logistics, suggests aiming for around eight alphanumeric characters. Treat that as a practical starting point rather than a hard limit. What matters more than hitting a specific character count is picking a length you can apply consistently across every product line you sell now and expect to add later.
How to Build Your SKU System, Step by Step
Step 1: Map your product categories
List every product line or category you sell, then assign each one a short, memorable abbreviation, ideally three or four letters. Keep these abbreviations distinct enough that you won’t confuse two categories at a glance.
Step 2: Choose your variant codes
For each category, decide which variants actually need their own code: color, size, material, or scent are common choices. Only include variants that genuinely change what you’re tracking. Adding a variant field for something that never varies just adds noise to every SKU you generate.
Step 3: Add a sequence number
Append a short numeric sequence to handle cases where two items would otherwise share an identical code, such as different production batches of the same color and size. Zero-padding the sequence (001, 002, 010) keeps everything sorting correctly as your catalog grows past nine or ninety-nine items.
Step 4: Test it against your real catalog before rolling it out
Run your draft format against ten or twenty real products, including your most complicated variants, before applying it catalog-wide. This is where most systems fail: a format that works cleanly for simple products often breaks down the moment you hit a product with an unusual variant combination.
Building your SKU list by hand gets tedious fast. Try Billbooks’ free SKU generator and create consistent, unique codes for your whole catalog in seconds.
Common SKU Mistakes That Cause Headaches Later
Building a format that can’t grow
A two-digit sequence number works fine until you pass 99 variants of one product line, at which point every code needs restructuring. Build in more room than you think you’ll need from the start.
Reusing a retired SKU for a new product
Once a SKU has appeared on a real invoice, receipt, or sales record, retire it permanently rather than reassigning it to a new item. Reusing an old code creates confusion in historical records and makes past sales data unreliable.
Embedding information that changes
Avoid encoding something like a price or a supplier name directly into the SKU itself. Prices change, suppliers change, and a code that has to be rebuilt every time one of those changes is a code that will eventually get out of sync with reality.
Letting different team members invent their own format
If more than one person creates SKUs, write your format down as a short internal reference so everyone applies the same structure. Inconsistent SKUs across a small team are one of the most common causes of inventory mismatches.
Where SKUs Show Up in Your Invoicing and Bookkeeping
SKUs on invoices and receipts
Including the SKU on every invoice and receipt line item, alongside the plain-language product name, makes it far easier to reconcile what actually sold against your inventory records, especially when a customer orders the same product in multiple variants at once. It also removes any ambiguity if a customer calls about a specific order. This is one more reason it’s worth checking whether a free invoice generator or real invoicing software is the better fit once your product catalog gets more complex.
Connecting SKUs to your day-to-day tracking
Once your SKU system is in place, using it consistently across every quote, invoice, and receipt you generate turns your paperwork into a real record of what moved through your business, not just a list of dollar amounts. That consistency is also what makes it possible to calculate your real profit margin product line by product line, instead of guessing at the business as a whole.
Keep every invoice, receipt, and product code in one place. See how Billbooks helps small product businesses track sales by SKU without a separate inventory system.
FAQ
What’s the difference between a SKU and a UPC?
A UPC is a standardized 12-digit code administered by GS1 US that works the same way across any retailer. A SKU is a code you create yourself for internal use, with no registration or standards body involved.
Do I need a SKU system if I only sell a few products?
If you sell only one version of one or two products, a full SKU system may be overkill. Once you have multiple variants, sizes, colors, or bundles, a SKU system pays off quickly by keeping your records accurate.
Can two products ever share the same SKU?
No. The entire purpose of a SKU is to identify one specific product variant uniquely. If two listings share a SKU, your inventory and sales records for both items become unreliable.
How long should a SKU be?
There’s no fixed rule, but shorter and simpler is easier to use consistently. A commonly cited starting point is around eight alphanumeric characters, though your actual length should fit the number of categories and variants your catalog needs.
Do SKUs need to appear on my invoices?
They don’t have to, but including them is good practice once you’re tracking variants. It gives you a direct link between what a customer was billed for and what left your inventory.
