SKU Management Guide

Create, name, and govern SKUs so catalogs stay searchable, counts stay accurate, and purchasing does not drown in duplicates.

SKU Management Guide

By Tibeau De Grauwe, FounderUpdated July 2026

  • 25 products free
  • No credit card
  • 10-min setup

Key takeaways

  • Strong SKU management means unique IDs, clear naming, attribute standards, and a process to add or kill SKUs.
  • Duplicate and zombie SKUs destroy reporting and cause overbuying.
  • Review the catalog on a schedule; do not let every one-off purchase become a permanent SKU.

Build a clean SKU foundation

A stock keeping unit (SKU) uniquely identifies an item you track. Good SKUs are unique, stable, and never reused for a different product. Names should be human-readable and consistent: brand, description, size, color, pack quantity in a fixed order. Attributes like category, supplier, cost, and barcode belong in fields—not crammed inconsistently into the name.

Decide units of measure carefully. If you buy by the case and issue by the each, configure conversion factors so receiving a case does not look like receiving one unit. Ambiguous UOM is one of the top causes of 'mystery' variances.

Document who can create SKUs. Uncontrolled creation is how catalogs explode. A simple request form with approval prevents duplicates when someone cannot find an existing item and invents a new code.

Governance and rationalization

Run SKU rationalization quarterly: flag items with no movement, overlapping substitutes, and near-identical variants. Merge duplicates carefully after reconciling quantities. Discontinue true dead stock with a sell-down plan rather than letting it occupy bins forever.

Variant strategy matters for retailers and manufacturers. Too many similar SKUs dilute demand signals; too few frustrate customers. Use data—attach rate, returns, and turns—not only sales opinion.

StockFlow is free inventory software with phone barcode scanning, multi-location stock, reorder alerts, and real-time counts built for small businesses that outgrew spreadsheets.

  • Unique, never-reuse SKU codes
  • Consistent naming and attribute fields
  • Controlled SKU creation workflow
  • Quarterly rationalization of dead and duplicate items

SKUs in daily operations

Barcode every active SKU before it reaches a pick face. When suppliers change packaging, map new barcodes to the same SKU rather than creating a new item unless the product truly changed. Kits and assemblies need clear parent/child SKUs so depleting a kit hits components correctly.

Train purchasing to search before creating. Train receiving to question unlabeled goods instead of inventing codes on the dock. Small habits keep the catalog trustworthy.

Export a SKU master periodically as a backup and for analysts. The master should include status (active/discontinued), preferred supplier, and reorder parameters so planning is not tribal knowledge.

Sustaining the practice

For SKU Management Guide, schedule a standing thirty-minute weekly focus on label durability. Short rituals outperform rare heroic cleanups. Capture decisions in the SOP the same day so the improvement does not live only in someone's memory after a busy season.

Translate the takeaway into floor behavior: 'Strong SKU management means unique IDs, clear naming, attribute standards, and a process to add or kill SKUs.' Is that enforced by a required scan, a checklist, or a KPI on the weekly review? If the behavior is neither measurable nor required, it remains a poster. Assign an owner and an escalation path when the metric trends the wrong way for two consecutive weeks.

Lean on related playbooks (What are the 4 types of inventory, Best barcode generator) for depth instead of bloating a single document—link them from your internal wiki. Export item masters and on-hand balances monthly. That turns SKU Management Guide into an operating system rather than a one-time software install, and it keeps onboarding sane when you hire before peak season. Also revisit 'Duplicate and zombie SKUs destroy reporting and cause overbuying.' whenever suppliers, channels, or locations change, because static parameters silently decay even when the UI still looks fine.

Trusted by small businesses

What our customers say

Super Kind! Quick replies from their support and very easy fixes, changed the dashboard a bit and customized it. Also gave me 450 items extra on the free plan just for me. Highly recommend and again great service!

Erasable Trading AU

Best customer service! Stockflow's customer support is fast and extremely helpful. They assisted me with customization of the software to improve my experience as a user.

Justin M.

Co-Owner, Consumer Goods

Frequently asked questions

Should SKU codes be meaningful or arbitrary?
Either works. Meaningful codes help humans; arbitrary codes avoid breaking when attributes change. Many teams use arbitrary IDs plus rich names.
How many SKUs is too many?
When staff cannot find items, duplicates multiply, and turns collapse under complexity—rationalize.
What about supplier part numbers?
Store them as attributes. Do not make the supplier number your only SKU unless you will never change suppliers.