SKU Full Form: Stock Keeping Unit, Explained
The SKU is the smallest unit of truth in e-commerce. Get SKU discipline right and every other report starts making sense. Get it wrong and nothing does.
- SKU full form is Stock Keeping Unit, a unique code for each distinct product variant a seller stocks.
- A SKU is your internal code. It is not the barcode, not the marketplace listing ID and not the product name.
- Every SKU you add ties up working capital. Catalogue width is a cost decision, not just a growth decision.
SKU full form: Stock Keeping Unit, a unique code a seller assigns to each distinct product variant so it can be tracked through inventory, listings, orders and returns. One style of shoe in four sizes and two colours is not one product. It is eight SKUs.
What SKU actually measures
A SKU is not a metric in itself. It is the unit of record that every real metric stands on. Sales, stock levels, returns, margins and reorder points are all counted per SKU. If the SKU layer is messy, every report built on top of it is fiction.
A SKU is internal. You create it, you own the naming logic, and it needs to mean something to your team. It is not the barcode on the packaging, which is a global standard, and it is not the listing ID a marketplace generates. A good SKU code encodes the essentials: category, style, colour, size. Anyone in the warehouse should be able to read BLK-TSH-CRW-M and know roughly what they are holding.
The formula
There is no formula for a SKU itself. The formulas start once SKUs exist. Sales per SKU = total sales divided by active SKUs. Sell-through rate per SKU = units sold divided by units received. Inventory turns per SKU = cost of goods sold divided by average inventory. These are the numbers that separate a working catalogue from a warehouse full of regret.
Where you meet it
- Marketplace dashboards. Amazon and Flipkart seller panels report sales, returns and stock health at SKU level. Their listing IDs map to your SKUs, and that mapping is your responsibility.
- Inventory and ERP systems. Unicommerce, Zoho Inventory and similar tools treat the SKU as the primary key. Duplicate or inconsistent SKUs break syncing across channels quietly and expensively, and in India the printed MRP on each batch is tracked against the SKU as well.
- Investor conversations and board decks. SKU count is shorthand for operational complexity. A founder who knows which twenty SKUs drive most of the GMV reads as an operator. One who only knows the total count reads as a tourist.
- India context. Multi-channel selling is the norm here: your own store plus two or three marketplaces plus quick commerce. Without one clean SKU master across all of them, stock counts drift and oversells follow.
How operators misread it
The first misread is treating SKU count as a growth trophy. Every SKU you add ties up working capital in inventory, occupies storage and demands management attention. Wide catalogues with thin depth are how cash disappears into shelves.
The second misread is ignoring the tail. In most stores a small share of SKUs produces most of the revenue, while the long tail produces stock audits. Look at contribution margin per SKU, not just sales, because a fast mover with heavy returns can still be a net loss.
The third misread is renaming SKUs casually. Change a code mid-season and you cut the thread of its sales history. Your AOV analysis, reorder logic and cohort views all lose memory at once. SKU codes should be boring and permanent.
Discipline at the smallest unit
Set a naming convention, document it and never improvise. Keep one SKU master across every channel. Review sales and margin per SKU monthly, kill the tail without sentiment, and let the winners take the working capital. The unit economics of the whole business are just the unit economics of your SKUs, added up.