What is the difference between a SKU and a barcode?

A SKU is an internal identifier you create for inventory management. A barcode (UPC, EAN, GTIN) is a universal product identifier used across the supply chain. A product has one barcode but may have different SKUs in different retailers systems. You control your SKU format; barcodes follow universal standards.

How should I structure my SKU codes?

Use a logical format: Category-Product-Attribute1-Attribute2. Example: TOP-POLO-BLK-L (Tops > Polo > Black > Large). Keep it concise (8-12 characters), use consistent separators, and document the convention. Avoid starting with numbers or using easily confused characters. Your SKU should tell you about the product at a glance.

How many SKUs is too many?

The right number depends on your business, but more SKUs means more complexity. Regularly review SKU performance. Use ABC analysis: A-items (top 20% by revenue) get premium management, C-items (bottom 20%) should be evaluated for discontinuation. If dead stock exceeds 15% of SKUs, you likely have too many.

Book Free Assessment Calculator

SKU Management

Stock Keeping Unit

Also known as:stock keeping unit managementproduct SKU systemSKU tracking

The system of creating, organising, and tracking Stock Keeping Units -- unique identifiers assigned to each distinct product variant for inventory management and sales tracking.

In-Depth Explanation

SKU (Stock Keeping Unit) management is the practice of creating and maintaining unique identifiers for every distinct product variant a business sells. A well-structured SKU system enables accurate inventory tracking, sales analysis, and operational efficiency.

SKU system components:

SKU format: Structured code encoding product attributes (e.g., SHT-BLU-M = Shirt-Blue-Medium)
Naming convention: Consistent rules for how SKUs are created
Variant tracking: Separate SKUs for each size, colour, and style combination
Barcode mapping: Linking SKUs to scannable barcodes
Cross-reference: Mapping internal SKUs to supplier SKUs and marketplace identifiers

SKU naming best practices:

Start with a category or brand prefix
Include key differentiating attributes (colour, size, material)
Keep SKUs concise (8-12 characters)
Avoid characters that cause confusion (0 vs O, 1 vs l)
Use hyphens or consistent separators
Document the convention for team reference
Plan for future expansion (leave room for new attributes)

SKU management challenges:

Proliferation: Too many SKUs creating operational complexity
Cross-channel mapping: Different identifiers across marketplaces
Bundle tracking: Managing component-level inventory for bundles
Variant explosions: Colour x size x material combinations
Discontinuation: Properly retiring old SKUs
Data quality: Maintaining accurate SKU data across systems

SKU analysis for business decisions:

Sales velocity by SKU (fast vs. slow movers)
Margin analysis by SKU
Inventory turnover rate per SKU
Stock coverage (days of stock remaining per SKU)
ABC analysis (categorising SKUs by revenue contribution)
Dead stock identification (SKUs with no sales)

Business Context

Effective SKU management prevents the common problem of 80% of revenue coming from 20% of products while the remaining SKUs tie up capital in slow-moving inventory.

How Clever Ops Uses This

Clever Ops helps Australian e-commerce businesses implement structured SKU management systems that connect across all sales channels and inventory locations. We design SKU conventions, set up cross-channel SKU mapping, and build analytics dashboards that reveal which products drive profit and which drain resources.

Example Use Case

"A fashion retailer restructures their SKU system from random codes to a structured format (BRD-CAT-COL-SZ), enabling automated inventory reporting, faster pick-and-pack, and accurate cross-channel stock management."