Stock Keeping Unit (SKU)

Quick answer — Stock Keeping Unit (SKU)

An SKU is an internal identifier that represents one distinct product variant in your catalog, for example a red medium t-shirt versus a blue large. It describes what the item is, where it lives in inventory, and how systems and people track stock, fulfillment, and sales across channels.

Why it matters

• Revenue accuracy — Correct SKUs ensure sales map to the right items so revenue, margins, and profitability per product are accurate.
• Conversion and availability — Misassigned SKUs cause stock errors and lost sales when customers attempt to buy items that appear available but are not.
• Customer experience — Fast, correct fulfillment depends on clear SKU labeling and warehouse location mapping.
• Marketing and segmentation — SKUs let you track which specific variants respond to campaigns and which need different creative or pricing.
• Operational efficiency — Barcode scanning, pick/pack accuracy, and reorder triggers depend on clean SKU structures.
• Decision making — SKU-level sales and inventory data drives assortment planning, SKU rationalization, and forecasting.

What is a Stock Keeping Unit (SKU)?

SKU stands for Stock Keeping Unit and is an internal code created by a merchant to identify a distinct sellable item. An SKU typically encodes a combination of attributes such as product family, color, size, and sometimes location or season. Unlike standardized barcodes such as UPC or EAN, SKUs are defined by each seller and are not globally unique.

What an SKU includes

• Product family or style identifier
• Variant attributes such as size, color, material
• Optional attributes like warehouse location or pack size when used operationally

What an SKU does not include

• Universal supply chain identifiers like UPC, which are manufacturer assigned and global
• Sales metrics by itself — SKU is an identifier, not a performance metric

When businesses use SKUs

• From startup to enterprise: SKUs are used as soon as inventory or variants exist
• When tracking stock levels, forecasting demand, creating purchase orders, and reconciling sales vs inventory

What high or low SKU counts indicate

• High SKU count can indicate broad assortment, higher complexity, and greater carrying costs
• Low SKU count often means simpler operations but may miss niche customer needs

Formula / Calculation

Because SKU is an identifier rather than a metric, it does not have a single calculation. Instead, merchants measure SKU-related performance using several SKU-level metrics. Below are the common formulas and examples for those metrics.

Metric	Formula
Sell-through rate	Sell-through = Units sold during period / Starting inventory during period
Inventory turnover (SKU-level)	Inventory turnover = Cost of goods sold for SKU during period / Average inventory cost for SKU during period
Days of inventory	Days inventory = 365 / Inventory turnover (or Average inventory / Daily COGS)

Sell-through example

1. Starting inventory for SKU A on January 1: 100 units
2. Units sold during January: 60 units
3. Sell-through = 60 / 100 = 0.60 or 60%

Inventory turnover example (simple)

1. COGS for SKU B in a year: $12,000
2. Average inventory cost for SKU B: $3,000
3. Inventory turnover = 12,000 / 3,000 = 4 turns per year

How it works

1. Define SKU structure

   What happens: Choose a consistent naming convention that encodes key attributes like style, size, color, and optionally warehouse. What to do: Document the format and rules. Why it matters: Consistency prevents duplicates and supports automated parsing for reporting.

2. Assign SKUs at creation

   What happens: New products and variants are given SKUs when added to the catalog. What to do: Enforce SKU generation via your PIM, ERP, or Shopify app. Why it matters: Ensures every sellable item is traceable from order to fulfillment.

3. Link SKU to barcodes and locations

   What happens: Map SKUs to UPC/EAN/GTIN when applicable and to warehouse bin locations. What to do: Print labels or use mobile scanning. Why it matters: Speeds picking and reduces mispicks.

4. Track SKU-level inventory

   What happens: Inventory counts update per SKU on sales, returns, transfers, and receive events. What to do: Use real-time inventory systems or daily reconciliation. Why it matters: Accurate stock prevents oversells and stockouts.

5. Analyze and act

   What happens: Monitor SKU performance, sell-through, and markdown needs. What to do: Run ABC analysis and rationalize slow movers. Why it matters: Frees capital and reduces carrying cost while focusing assortment on profitable SKUs.

Key components / factors

• SKU naming convention — Impacts human readability and ease of parsing for automation.
• Variant attributes — Size, color, material affect SKUs and inventory complexity.
• Channel mapping — Different marketplaces may require mapping SKUs to external IDs like ASINs or merchant SKUs.
• Warehouse location — Location in the SKU or a linked location field reduces pick time and errors.
• Barcode integration — Scannable labels linked to SKUs are essential for speed and accuracy.
• Forecasting and seasonality — Demand patterns change SKU stocking priorities and safety stock levels.
• Price and promotions — Promotions can change turnover rates and should be tracked at SKU level.
• Payment, returns, and bundles — Bundles and returns affect SKU inventory differently than single units.
• Analytics and attribution — Accurate SKU tracking is necessary for per-item ROI and lifetime value analysis.

Example

Scenario

• Small DTC apparel brand sells a hoodie style in three colors and four sizes producing 12 SKUs.
• Average selling price per SKU: $50. COGS per unit: $20. Gross margin per unit: $30.
• One SKU, Hoodie-Blue-M (SKU HB-M), has inventory errors because two different SKU codes were used in the warehouse. Available stock appears as 50 but actual pickable stock is 30.

Diagnosis

• During a weekend promotion, observed 20 lost orders attempted for HB-M but failed due to stock discrepancy resulting in 20 lost sales.

Action taken

• Consolidated duplicate SKUs into a single SKU HB-M, relabeled inventory, and updated the WMS to prevent duplicate creation.
• Cost to relabel and reconfigure: $400.

Result and impact

• Recovered 20 immediate lost sales: 20 x $50 = $1,000 revenue.
• Gross profit recovered: 20 x $30 = $600.
• Net impact after cost: $600 - $400 = $200 net gross profit increase in the short term, plus ongoing reduction in future stockout losses and labor savings from no longer chasing duplicate SKUs.

Business takeaway

• Fixing SKU hygiene is low-cost with measurable returns — reduced stockouts, more accurate revenue attribution, and better fulfillment speed.

Benchmark / What is a good metric

There is no single universal benchmark for SKU counts or SKU performance because results depend on category, business model, channel mix, seasonality, and price points. Instead:

• Use relative comparisons within your catalog: identify top 10% revenue-generating SKUs and slowest 20% by sell-through.
• For inventory metrics, compare SKU-level sell-through and turnover against category peers within your business and across comparable time periods.
• If seeking external benchmarks, consult industry reports specific to your vertical and geography; treat them as directional, not absolute.

How to improve / optimize SKUs

1. Standardize SKU naming first

   What to change: Create a short, documented format (for example: STYLE-COLOR-SIZE). Why it works: Prevents duplicates and enables automated parsing. How to implement: Update PIM or Shopify product import templates. What to monitor: Number of duplicate SKUs and time spent on SKU-related support tickets.

2. Integrate barcodes and scanning

   What to change: Link each SKU to a scannable barcode and bin location. Why it works: Reduces picking errors and speeds fulfillments. How to implement: Print new labels and deploy handheld scanners. What to monitor: Pick accuracy rate and average fulfillment time.

3. Run SKU rationalization

   What to change: Identify slow movers and decide to delist, bundle, or mark down. Why it works: Frees working capital and reduces carrying costs. How to implement: Use 90/180-day sell-through thresholds and ABC classification. What to monitor: Inventory carrying cost and sell-through improvements.

4. Use SKU-level forecasting

   What to change: Forecast demand at SKU level rather than product family in high-variance catalogs. Why it works: Prevents under/overstock of specific variants. How to implement: Add SKU-level historical sales into your forecasting model or demand planning tool. What to monitor: Forecast accuracy and stockout rate.

5. Version control and change management

   What to change: Never repurpose an SKU for a different product. Why it works: Preserves historical reporting accuracy. How to implement: Create new SKUs for new products and maintain deactivation records. What to monitor: Instances of changed SKU meaning in analytics.

Best practices

• Keep SKUs short and structured for parsing by scripts and humans. Avoid embedding price information into SKUs.
• Always link SKU to a single canonical product record in your PIM or ecommerce platform.
• Use barcodes for physical inventory events and require scans for receiving and shipping.
• Implement daily or weekly reconciliation for high-turn SKUs and monthly for slow movers.
• Perform ABC analysis quarterly: focus replenishment and forecasting effort on A SKUs that drive most revenue.
• Map external marketplace IDs to your SKUs to avoid channel mismatches and prevent oversells.
• Log changes to SKUs in a change register so analytics teams can adjust historical reporting when necessary.
• Track SKU-level KPIs in dashboards: sell-through, stockouts, days inventory, and gross margin.

Common mistakes to avoid

• Duplicate SKUs across warehouses

  Why it happens: Multiple teams create codes independently. Harmful because it fragments inventory and causes stock inaccuracies. Correct approach: Centralize SKU creation and enforce uniqueness in your system.

• Embedding volatile data in SKUs

  Why it happens: Teams include price or promotion codes to make SKUs descriptive. Harmful because price changes require SKU changes and break history. Correct approach: Keep SKUs stable and store mutable attributes in fields, not codes.

• Changing SKU meaning

  Why it happens: Reusing SKUs to avoid creating new ones. Harmful because historical analytics become misleading. Correct approach: Always retire an SKU and create a new SKU for different products or significant changes.

• Relying on manual counts without barcode verification

  Why it happens: Cost pressure or legacy processes. Harmful because manual counts are error-prone and slow. Correct approach: Implement barcode scanning workflows for receiving and picking.

• Not pairing SKU data with financial metrics

  Why it happens: Operational teams track units only. Harmful because decisions ignore profitability. Correct approach: Combine SKU sales with COGS and margin in reports.

Stock Keeping Unit (SKU) vs related concepts

SKU vs UPC / EAN

• SKU: An internal identifier created by the seller for inventory and operations.
• UPC / EAN: Manufacturer or brand-provided barcodes that are globally unique and used in retail scanning.
• Key difference: UPC is external and universal; SKU is internal and flexible.

SKU vs ASIN

• SKU: Your internal code for a specific variant.
• ASIN: Amazon Standard Identification Number assigned by Amazon to catalog items on Amazon.
• Key difference: ASIN is marketplace-specific; SKUs map your internal items to marketplace listings.

SKU vs Product ID / Variant ID

• SKU: Often used as the merchant-visible code for operations and fulfillment.
• Product ID / Variant ID: Platform-generated identifiers used internally by systems like Shopify; may not be human-friendly.
• Key difference: Use SKU for human processes and cross-system mapping; use Product/Variant IDs for API-level references.

When should you track SKUs

• Who: Everyone with inventory — founders, merchants, inventory managers, finance, and marketing teams.
• Stage of growth: From day one when you have more than a handful of items or any variants; SKUs prevent chaos as you scale.
• Review frequency: Daily for fast-moving SKUs, weekly for medium-turn items, and monthly for slow movers and catalog health reviews.
• Segments to analyze: By product family, channel, warehouse location, season, and promotion.
• Metrics to pair: Sell-through, inventory turnover, stockout rate, gross margin per SKU, and days of inventory.

Related ecommerce metrics

• Sell-through rate — Shows how quickly a SKU sells relative to starting stock.
• Inventory turnover — Indicates how many times SKU inventory cycles in a period.
• Days of inventory — Estimates how many days current stock will last for a SKU.
• Stockout rate — Frequency a SKU is unavailable when customers try to buy it.
• Fill rate — Percentage of orders fulfilled from available SKU inventory without backorders.
• GMROI — Gross margin return on inventory investment, useful at SKU level for profitability decisions.

FAQs

What exactly does SKU stand for and who creates it?

SKU stands for Stock Keeping Unit and is created by the merchant or retailer to uniquely identify a sellable variant. It is not assigned by a standards body.

Can SKU be used across different sales channels?

Yes. You should map your SKU to channel-specific identifiers like ASIN or marketplace item ID to keep inventory synchronized and avoid oversells.

Do I need a barcode if I use SKUs?

Yes. Barcodes linked to SKUs enable fast and accurate receiving, picking, and shipping. SKUs without barcodes are more error-prone operationally.

How do I measure if an SKU is profitable?

Calculate gross margin per SKU by subtracting SKU COGS from net revenue for that SKU, and then assess GMROI by comparing margin to average inventory cost.

How often should I audit SKUs?

Perform cycle counts daily or weekly for top-selling SKUs and full physical inventory reconciliations quarterly or biannually depending on catalog size and error rates.

What causes duplicate SKUs and how do I prevent them?

Duplicates usually result from decentralized SKU creation and inconsistent naming. Prevent them with a centralized SKU registry and enforced templates in your product management tools.

Is it okay to change an SKU after products are sold?

No. Reusing or repurposing an SKU breaks historical reporting. Create a new SKU and mark the old SKU as inactive with notes explaining the change.

How are SKUs different from barcodes like UPC?

SKUs are internal codes used for operations and analytics; UPCs are standardized barcodes intended for retail scanning and are globally recognizable.