SKU (Stock Keeping Unit)

A SKU — Stock Keeping Unit — is the code that identifies one exact, sellable thing. Not the product line: the specific size, color, flavour, and pack count that a customer can actually buy and a picker can actually pull off a shelf.

A black crew-neck tee in large is one SKU. The same tee in medium is a different one. The three-pack is a third. If two physical items can be told apart by a customer, they need different SKUs.

SKU vs. UPC vs. ASIN vs. FNSKU

Four identifiers, four owners:

The one to internalize: the SKU is yours. It's the only one of the four whose structure you control, and it's the one every other system in your business keys off.

How to Structure SKUs That Don't Break

Good SKUs are readable by a human and unambiguous to a scanner.

Use a consistent pattern, general to specific:

TEE-CRW-BLK-L      Crew-neck tee, black, large
TEE-CRW-BLK-M      Same product, medium
CAND-VAN-8OZ       Vanilla candle, 8 oz
CAND-VAN-3PK       Vanilla candle, 3-pack

Rules worth following:

• Keep it short. Under about 20 characters. Long codes get misread and misspoken.
• Encode only stable attributes. Size and color are fine. Price, supplier, and season are not — they change.
• Never reuse a retired SKU. Old order history will collide with new inventory.
• Avoid ambiguous characters. O/0 and I/1/l cause real mistakes in a warehouse.
• Skip spaces and special characters; dashes are safe everywhere.
• Give kits their own SKUs. An assembled bundle is a distinct sellable unit with its own count.

Anti-patterns that cause real damage: the same SKU shared across sizes, SKUs that differ by one easily-transposed digit, and codes generated by a platform that mean nothing to the person holding the box.

Why Messy SKUs Cost Money

SKU structure looks like admin until it fails, and then it fails expensively:

• Mispicks. Two SKUs a character apart, on adjacent shelves, in a hurry.
• Oversells. Counts drift when variants share codes, and you sell inventory you don't have.
• Broken channel sync. Shopify, Amazon, eBay, and Etsy all key inventory off the SKU. Inconsistencies between channels create phantom stock.
• Useless reporting. You can't analyze what sells if you can't tell variants apart.
• Slow onboarding. Every new employee — and every 3PL receiving your inventory — has to learn your naming. Clear conventions transfer; arbitrary ones don't. Clean SKUs are the single thing that makes onboarding to a fulfillment partner fast instead of painful.

SKU Rationalization

More SKUs is not more revenue. Every additional variant consumes shelf space, forecasting attention, safety stock capital, and pick-path complexity.

Periodically pull sales by SKU and rank them. In most catalogs a small share of SKUs drives the large majority of revenue, while a long tail consumes storage and cash. Cutting the tail usually improves margin, simplifies the warehouse, and raises pick accuracy at the same time — and it costs nothing to analyze.