SKUs and Barcodes: Setting Up a System That Scales

Every product you sell needs a name your systems can agree on, and that name is the SKU. Whether you are running a single shop or moving stock across multiple warehouses and marketplaces, a well-designed SKU system is the quiet backbone that keeps inventory accurate, picking fast and reporting honest. In this guide we explain what a SKU is, how it differs from a barcode, how to structure one that will not collapse as you grow, and the common mistakes that turn a tidy catalogue into a mess. The goal is a system that scales with your business rather than one you have to rebuild every time you add a product line or sales channel.

What a SKU is

SKU stands for Stock Keeping Unit. It is a short, internal code you assign to each distinct sellable item so that your team and your software can identify it precisely. A SKU is unique at the variant level, which means a black medium t-shirt and a black large t-shirt are two different SKUs even though they share a name. The code is yours to design and control; it does not have to follow any external standard, and that freedom is exactly why getting the structure right matters.

A good SKU is human-readable enough that an experienced picker can glance at it and have a rough idea of what it represents, while still being machine-friendly. It typically encodes a few meaningful attributes such as product type, colour and size, and it stays consistent across your entire catalogue. The SKU is what ties together your purchase orders, stock counts, sales reports and order lines, so it needs to be stable: once an item has a SKU, that code should not change for the life of the product.

SKU vs barcode

People often use the words SKU and barcode interchangeably, but they do different jobs. A SKU is an internal identifier you design and manage. A barcode is a machine-scannable representation of an identifier, and the number behind it is frequently a global standard such as a GTIN, UPC or EAN that a manufacturer or GS1 assigns. In short, the SKU is your private label for an item, while the barcode is usually a public, standardised number that travels with the product through the supply chain.

The two work together rather than competing. You can print a barcode that encodes your own SKU for items you make or repack, or you can store the manufacturer’s barcode against your internal SKU so a single scan resolves to the right line. The table below summarises the differences.

Aspect	SKU	Barcode
Owner	You, internally	Manufacturer or GS1 (often)
Purpose	Identify and organise stock	Fast scanning at point of action
Format	Alphanumeric, meaningful	Numeric standard plus a scannable symbol
Changes	Stays fixed for the item’s life	Fixed by the standard

How to structure SKUs

The most reliable approach is a segmented structure where each part of the code describes one attribute, separated by a hyphen for readability. Move from the most general attribute to the most specific. A common pattern is category, then product, then variant attributes such as colour and size. For example, a code might read TS-CREW-BLK-M for a black medium crew-neck t-shirt, where TS is the category, CREW the style, BLK the colour and M the size.

Keep each segment to a fixed, short length so codes line up neatly and are easy to sort. Use a consistent set of abbreviations and write them down in a reference sheet that everyone follows; BLK should always mean black, never BK or BLA. Avoid characters that cause trouble in spreadsheets and scanners, such as spaces, slashes, leading zeros that get stripped, and letters that look like numbers. Decide your convention once and apply it everywhere, because half the value of a SKU system is the discipline of using it the same way every time.

Best practices

• Make SKUs meaningful but not overloaded. Encode three or four attributes at most; a code that tries to capture everything becomes unreadable.
• Keep them short. Aim for something a person can read aloud without losing their place.
• Start the code with a letter, not a number, to avoid spreadsheet formatting and sorting problems.
• Maintain a single source of truth. One master list, ideally in your inventory software rather than scattered spreadsheets, prevents duplicate or conflicting codes.
• Document your abbreviations and structure so new staff can create correct SKUs without guessing.
• Never reuse a retired SKU for a different product, as historical reports will become misleading.
• Generate SKUs in a consistent way, whether manually following the rules or automatically through your system, so the catalogue stays uniform as it grows.

If you are still building the broader foundations, our inventory management guide puts SKU design in the context of counts, reorder points and stock control.

Common SKU mistakes

• Embedding data that changes. Putting price, supplier or season into the SKU means the code goes stale the moment that detail changes. Keep volatile data in fields, not in the code.
• Using the manufacturer’s part number as your SKU. If you switch suppliers or the manufacturer renumbers, your whole catalogue breaks. Map their number to your own SKU instead.
• Inconsistent abbreviations. Mixing RED, RD and R for the same colour quietly creates duplicates and ruins reporting.
• SKUs that are too long or cryptic. A forty-character code is unreadable and invites typing errors.
• Reusing old codes. Recycling a discontinued item’s SKU corrupts your sales history.
• Letting each channel invent its own. When Shopify, Lazada and your warehouse all use different identifiers, reconciliation becomes a daily headache.

A worked example

Imagine a small homeware brand launching a range of ceramic mugs. They sell three glaze colours (white, sage, charcoal) in two sizes (standard and large). First they fix a structure: category-product-colour-size. The category for drinkware is DW, the product is MUG, colours are WHT, SGE and CHR, and sizes are STD and LRG. That yields six clean SKUs, for instance DW-MUG-SGE-STD and DW-MUG-CHR-LRG.

Next they handle barcodes. The mugs are made to order, so the brand generates its own barcodes that encode each SKU and prints them on the packaging. When a customer orders a sage standard mug on a marketplace, the order arrives carrying the SKU DW-MUG-SGE-STD. The picker scans the shelf label, the scan resolves to that exact SKU, and stock for only that variant drops by one. Because the same SKU is used on the website, the marketplace listing and the warehouse shelf, every system stays in agreement. When the brand later adds a teal glaze, they simply add TEA and create DW-MUG-TEA-STD and DW-MUG-TEA-LRG without disturbing anything that already exists. That is what a scalable structure looks like in practice.

Barcodes in picking and packing

Barcodes earn their keep at the moment of physical action. During picking, a scanned barcode confirms the picker has the right item before it leaves the shelf, which dramatically reduces the wrong-item errors that drive returns and refunds. During packing, scanning each item against the order line confirms completeness, so customers receive exactly what they bought. Scanning is also faster and far more accurate than reading and typing a code by hand, which matters when order volumes climb.

To make this work, every shelf location and every product needs a clean, scannable label tied to the correct SKU. Barcode-driven picking and packing also create a reliable audit trail: you can see what was scanned, when and by whom. WhiteBox supports barcode picking and packing against a unified order queue, so the same scan that confirms the item also updates stock in real time. For the wider workflow around receiving, put-away and locations, see our warehouse management basics.

Scaling your system

A SKU system is easy when you have fifty products and one channel. The strain appears as you add variants, warehouses and marketplaces. Three principles keep it stable at scale. First, enforce one master catalogue so every channel pulls from the same SKUs rather than inventing their own. Second, design for growth by leaving room in your structure for new categories and attributes, so adding a product line is an extension rather than a redesign. Third, lean on software to maintain consistency, because manual discipline breaks down once thousands of variants move across several locations.

Scaling also touches bundles and kits. When you sell a gift set made of several components, the set needs its own SKU while still drawing down stock from each component’s SKU. Managing that relationship cleanly is closely related to a bill of materials, and getting it right keeps your available-to-sell figures honest even as your assortment grows complex.

How WhiteBox helps

WhiteBox is Singapore-based inventory and retail-operations software built for brands, retailers and distributors across Southeast Asia, and it is designed to keep your SKUs consistent everywhere they appear. It syncs stock in real time across Shopify, Lazada, Shopee, Amazon and TikTok Shop, so a single SKU stays accurate across every channel. It handles multi-warehouse stock and transfers, barcode picking and packing, a unified order queue, plus forecasting and reporting, all built around the same clean catalogue. With pricing from S$49 (about US$38) per month, unlimited users, an open API and a 14-day free trial, most teams are live within an afternoon. Ready to organise your SKUs once and for all? See pricing or talk to our team.

Frequently asked questions

Should a SKU contain the price? No. Prices change, and a SKU should stay fixed for the life of the item. Keep price in a separate field so you can update it without disturbing the code or your historical reporting.

Can two products share a SKU? No. A SKU must be unique at the variant level. If two items share one code, your systems cannot tell them apart, which corrupts stock counts and order accuracy.

Do I need barcodes if I already have SKUs? SKUs identify items, but barcodes let you scan them quickly and accurately during picking and packing. For anything beyond very low volumes, barcodes save time and cut errors, so most growing operations want both.

How long should a SKU be? Long enough to be meaningful, short enough to read aloud without losing your place. A handful of short segments separated by hyphens usually strikes the right balance and keeps codes easy to sort.

Should I let each sales channel generate its own SKU? No. Maintain one master catalogue and push the same SKU to every channel. Channel-specific codes make reconciliation painful and quietly create duplicates that distort your reporting.

Related reading: Inventory management guide, Warehouse management basics, Bill of materials.