How to Structure SKUs Properly (Before You Print Anything)

If you get your SKU structure wrong at the start, it will cost you — in reprints, relabelling, warehouse confusion, Amazon issues, retailer pushback, and messy data forever.

If you get it right, everything scales cleanly.

This guide walks through how to structure SKUs strategically before you print packaging, labels or barcodes — covering internal SKU logic, variants, carton multiples, GTIN hierarchy and how to avoid painful reprints later.

This is not about naming products nicely.

This is about building infrastructure.

Why SKU Structure Matters More Than You Think

A SKU is not just a code.

It controls:

Warehouse picking accuracy
Barcode assignments
Purchase orders
Carton labelling
Amazon FBA setup
Retail EDI integration
Inventory forecasting
Reorders
Returns handling

Once packaging is printed, changing SKU logic becomes expensive.

So do it properly now.

1. Start With Internal SKU Logic (Your System of Truth)

Your internal SKU should:

Be unique
Be human-readable
Encode meaningful structure
Be future-proof

It should not depend on barcodes.

Barcodes (GTINs) can change. Your internal SKU should not.

A Strong SKU Structure Example

Instead of:

NB001
NB002
NB003

Use something structured:

NB-A5-DOT-BLK-2026
NB-A5-DOT-NAV-2026
NB-A6-LIN-SGE-2026

You instantly know:

Product type (NB = notebook)
Size (A5 / A6)
Format (DOT / LIN)
Colour (BLK / NAV / SGE)
Year (if seasonal)

That structure scales cleanly across hundreds of SKUs.

2. Structure Variants Properly

Variants are where most brands make mistakes.

Common dimensions:

Size
Colour
Format (lined / dotted)
Edition / Year
Language
Binding type
Region (UK / US version)

Rule: One Physical Variation = One SKU

If anything physically differs — even paper colour — it must have:

Its own SKU
Its own GTIN

Retailers and marketplaces expect this.

Trying to "group" variations under one code causes:

Picking errors
Wrong barcode scanning
Returns
Retail compliance failures

Be strict here. See Which Barcode Should I Use? for format guidance.

3. Plan Carton Multiples Before Production

This is where operations and SKU structure meet.

Ask yourself:

How many units per inner carton?
How many inners per outer carton?
Are all variants packed separately?
Are mixed cartons allowed?

If you print packaging before deciding this, you may need:

New carton labels
New ITF-14 codes
New GS1-128 labels
New logistics documentation

Carton Strategy Example

If your A5 notebook comes in:

6 units per inner
24 units per outer

You may need:

Product-level GTIN (EAN-13 or UPC-A)
Carton-level GTIN-14
Optional SSCC for pallet tracking

That hierarchy must be planned before labels are printed.

4. Understand the GTIN Hierarchy

Most confusion comes from not understanding packaging levels.

GTINs come in different formats defined by GS1.

Here's how they typically work:

Consumer Unit

Sold individually
Has EAN-13 or UPC-A
Uses GTIN-13 or GTIN-12

Inner / Case Level

Box of 6 or 12 units
Uses GTIN-14
Often encoded in ITF-14

Logistic / Pallet Level

For shipping & tracking
Uses SSCC
Encoded in GS1-128

If you don't define this clearly before launch, you will:

Duplicate barcodes
Reprint cartons
Break Amazon inbound shipments
Fail retail compliance checks

Plan hierarchy first. Print second. See GTINs Explained for the full picture.

5. Avoid the Classic Reprint Mistakes

Here's what usually forces reprints:

❌ SKU changes after launch
❌ New barcode because of duplicate usage
❌ Retailer demands carton GTINs
❌ Amazon FNSKU conflicts
❌ Language variants not separated
❌ Region-specific packaging added later
❌ Yearly editions not encoded in SKU

Reprints are not just printing costs.

They create:

Write-offs
Warehouse relabelling labour
Confusion in accounting systems
Data corruption across channels

This compounds over time.

6. Design a SKU Structure That Scales to 500+ SKUs

Before production, define:

Naming convention document
Variant order hierarchy (size → format → colour → year)
Abbreviation standards
Region rules
Seasonal logic
Discontinued product handling

Then lock it.

Put it in a shared system.

This is exactly why brands build a centralised SKU library before scaling.

If you don't treat SKUs as infrastructure, you'll eventually have to rebuild it under pressure.

7. Build Around Systems — Not Spreadsheets

Early-stage brands manage SKUs in:

Google Sheets
Shopify only
Amazon only

That works until:

You sell wholesale
You need carton GTINs
You introduce multi-region versions
You attend trade shows
You scale beyond 100 SKUs

At that point, SKU logic must connect:

Product data
Barcodes
Carton structure
Purchase orders
Design assets
Warehouse documentation

Structure first. Print later.

Quick SKU Structuring Checklist (Before Printing)

If you cannot tick every box, do not print yet.

Manage SKUs centrally with SKUWorks

Need to structure SKUs, assign GTINs, generate labels and carton barcodes from one place?

SKUWorks gives you a centralised SKU library, barcode assignment, label generation, and purchase order workflows. No spreadsheets. No duplicate codes. Get started free →

FAQ: SKU Structure

What is the difference between SKU and GTIN?

A SKU is your internal product identifier. A GTIN is a globally recognised barcode number issued under GS1 standards. They serve different purposes and should not replace each other.

Should each colour have its own barcode?

Yes. If the product differs physically (colour, size, format, language), it must have a unique SKU and a unique GTIN. Retailers and marketplaces require this.

Do I need carton-level barcodes?

If you sell wholesale, almost certainly yes. Most retailers expect GTIN-14 on cartons, sometimes GS1-128 labels, and sometimes SSCC for pallets. Check requirements before printing cartons.

Can I change SKU structure later?

Technically yes. Operationally painful. It can cause accounting inconsistencies, EDI mismatches, warehouse errors, and retailer delistings. It's far cheaper to structure properly before production.

What is GTIN hierarchy?

It refers to how different packaging levels are identified: individual unit (GTIN-12 / GTIN-13), case/carton (GTIN-14), pallet (SSCC). Each level may require its own barcode. See GTINs Explained for details.

Should my SKU include the year?

If the product changes annually (e.g. diaries, planners), yes. If it's evergreen, usually no. The key is consistency.

What happens if I reuse a barcode incorrectly?

You risk marketplace suspension, retailer compliance failure, supply chain confusion, and data corruption. Barcodes should be permanently tied to one physical product specification.

Final Advice

Treat SKU structure like you would legal contracts or tax planning.

Do it once. Do it properly.

Every shortcut now becomes operational friction later.

Before you print anything — slow down and structure it strategically.

That single decision will save you thousands over the life of your product range.

Still unsure how barcodes fit in? Read How to Get a GS1 Barcode and Which Barcode Should I Use?.