What Is a SKU?
A SKU (Stock Keeping Unit) is a unique internal code a business assigns to each distinct product or variant it sells, used to track inventory, sales, and stock levels. Pronounced "skew," a SKU is created by the retailer for its own systems, unlike a universal barcode. It identifies a specific item, size, color, and style, so the business knows exactly what it has, what sold, and what to reorder.
- Stands for
- Stock Keeping Unit (retail/inventory standard term)
- Created by
- The individual retailer, for internal use (unlike UPC/EAN barcodes)
- Identifies
- A specific product variant, e.g. size and color combination
- Format
- Alphanumeric code, structured by the seller (industry-typical)
What is a SKU and what is it for? #
A SKU, or Stock Keeping Unit, is a unique code a business gives to each distinct item it sells so it can track that item through its systems. Pronounced "skew," a SKU is typically a short alphanumeric string, and it identifies a specific sellable variant, not just "a t-shirt" but "the blue medium crewneck t-shirt." Every time that exact item is stocked, sold, counted, or reordered, the SKU is how the business refers to it precisely. SKUs power inventory management, sales reporting, order fulfillment, and reordering: when a sale is recorded against a SKU, stock for that unit decreases, and when it runs low, the SKU tells staff exactly what to reorder. Because each business designs its own SKUs, they can encode useful information, category, size, color, in a structure that makes sense internally. For any store selling more than a handful of products, SKUs are the backbone of keeping track of what you have and what is selling. They connect directly to inventory systems, see /wiki/what-is-inventory-management and /services/ecommerce-development.
How is a SKU different from a barcode or UPC? #
This is the most common point of confusion. A SKU is internal and unique to your business: you create it, you control its format, and it means something within your systems. A UPC (Universal Product Code), the barcode you see on retail packaging, is external and universal: it is assigned through a global standards body and is the same everywhere that product is sold, so a can of a specific soda has the same UPC in every store nationwide. In short, SKUs are yours; UPCs are shared across all sellers. A single product might have one UPC from the manufacturer but different SKUs at every retailer that stocks it, each store coding it to fit its own catalog. SKUs are also more flexible, they can identify things without a manufacturer barcode, like your own custom bundles or services. Both can coexist: many stores record a product's UPC for scanning and its own SKU for internal tracking. Understanding the distinction prevents data mix-ups when importing products or integrating systems, something we handle carefully on /services/ecommerce-development and /services/database-services.
How do you create a good SKU system? #
A well-designed SKU system is logical, consistent, and human-readable enough to be useful at a glance, while staying unique for every variant. The common approach is to build SKUs from meaningful segments: a category or product-type code, then attributes like style, size, and color, often separated for readability. For example, a shirt SKU might combine a code for the product line, a size, and a color, so staff can partly interpret it without a lookup. Keep the format consistent across the whole catalog so codes sort and filter cleanly. Avoid a few pitfalls: do not start SKUs with a zero if your spreadsheet software will strip it, avoid characters that clash with your systems, keep them a reasonable length, and never reuse a retired SKU for a different product, which corrupts historical sales data. Plan the structure before you have thousands of products, because retrofitting a scheme later is painful. A clean SKU system pays off in faster fulfillment and clearer reporting. We help stores design sensible SKU structures as part of catalog setup on /services/ecommerce-development.
Why do SKUs matter for inventory management? #
SKUs are the foundation of inventory management because they let a business track stock at the exact level it matters, the individual sellable unit. Without unique SKUs, you cannot accurately know how many blue mediums you have versus red larges; you only know you have "some shirts," which is useless for reordering and forecasting. With SKUs, every stock movement, receiving, selling, returning, transferring, is tied to a specific unit, so stock counts stay accurate per variant. This enables automatic reorder alerts when a SKU runs low, prevents overselling by knowing precise availability, and reveals which specific items sell fast and which sit unsold. For stores selling across multiple channels, a website plus a physical location or marketplace, SKUs keep inventory synchronized so the same unit is not sold twice. In short, granular, accurate inventory is impossible without SKUs, which is why they and inventory systems are inseparable, see /wiki/what-is-inventory-management. We connect SKU-level tracking to real inventory workflows on /services/ecommerce-development and /services/database-services.
How do SKUs relate to product variants on a website? #
On an ecommerce site, a single product page often offers multiple variants, sizes, colors, styles, and each distinct variant is typically its own SKU behind the scenes. So a t-shirt product with three sizes and four colors is one product page but twelve SKUs, one for each size-color combination that a customer can actually order. This matters because inventory, pricing, and availability are tracked per SKU: when a shopper selects "large, navy," the store checks that specific SKU's stock and price. Good ecommerce platforms manage this automatically, tying each selectable option combination to its SKU so the right variant is added to the cart and the correct unit is decremented from inventory. Poorly structured variant-to-SKU mapping causes real problems, overselling out-of-stock combinations, or wrong items shipped. Getting this architecture right is part of building a reliable store, connected to how product pages present options, see /wiki/what-is-a-product-page. We design variant and SKU structures deliberately during store builds on /services/ecommerce-development.
How are SKUs used in sales reporting and analytics? #
Because every sale is recorded against a SKU, SKUs are the key that unlocks meaningful sales analytics. Reporting by SKU shows exactly which specific products and variants sell best, which underperform, and which sizes or colors move fastest, insight that "total shirts sold" can never provide. This granularity drives smarter decisions: what to reorder and in what quantities, which variants to discontinue, how to price, and what to promote. SKU-level data also reveals patterns like a popular color selling out repeatedly while another gathers dust, prompting inventory adjustments. Over time, SKU sales history supports demand forecasting, predicting how much of each unit you will need next season. For multichannel sellers, consistent SKUs across channels let you consolidate reporting into one accurate picture. Essentially, SKUs turn raw sales into structured, actionable data. Building the reporting and data infrastructure to make use of this is part of serious ecommerce operations, see /services/ecommerce-development and /services/database-services, and it complements the conversion insights from /services/conversion-optimization.
Do SKUs affect SEO or the customer experience? #
SKUs are primarily internal, so they usually have little direct effect on SEO or what customers see, and that is by design, shoppers care about the product, not your internal codes. That said, SKUs sometimes appear on product pages as a reference ("Item #: ABC-123"), which can help customers and support staff identify an exact item, and some shoppers even search by a manufacturer part number that functions like a SKU. Where SKUs matter more indirectly is in the accuracy of the storefront: correct SKU-to-variant mapping ensures customers see accurate stock status and pricing, which is a real experience factor. In structured data for product pages, a SKU or product identifier can be included in the markup, which supports rich results, see /wiki/schema-markup-guide and /tools/schema-generator. But you would not, for instance, put SKU codes in your URLs or optimize pages around them for search. The customer-facing SEO work belongs to titles, descriptions, and images, while SKUs quietly keep the operational side accurate. We keep the two concerns properly separated on /services/ecommerce-development.
When does a business need a formal SKU system? #
Any business selling more than a few distinct products, or products with variants, benefits from SKUs, and the need grows sharply with catalog size and complexity. A seller with three simple items can track them informally, but once you have dozens of products across multiple sizes and colors, or sell through more than one channel, informal tracking breaks down fast, you lose track of what is in stock, oversell, and cannot tell what is selling. That is the point at which a structured SKU system becomes essential rather than optional. Local businesses expanding online, a boutique, an auto parts seller, a gym selling apparel, typically adopt SKUs as they move from a handful of products to a real catalog. The good news is that modern ecommerce platforms build SKU handling in, so you mostly need to design a sensible coding scheme and apply it consistently. Setting this up correctly from the start avoids painful cleanup later. We help growing local sellers establish SKU systems and inventory workflows on /services/ecommerce-development, /web-design-for-salons, and /web-design-for-auto-repair-shops.
FAQ
How do you pronounce SKU?
It is pronounced "skew," like the word meaning to slant. SKU stands for Stock Keeping Unit, a unique internal code a business assigns to each distinct product or variant it sells. The single-word pronunciation is standard across retail and ecommerce, even though it is technically an abbreviation of three words.
What is the difference between a SKU and a UPC?
A SKU is internal and unique to your business, you create and control its format. A UPC is the universal barcode assigned through a global standards body and is the same across every retailer that sells that product. One product can have one shared UPC but a different SKU at each store that stocks it.
Does every product variant need its own SKU?
Yes, each distinct sellable variant, every unique size-and-color combination, should have its own SKU so inventory, price, and availability can be tracked precisely. A single product page with three sizes and four colors typically represents twelve SKUs behind the scenes. This granularity is what makes accurate stock tracking and reporting possible.
How should I format my SKUs?
Build them from consistent, meaningful segments, such as a category code plus attributes like size and color, so they are partly readable at a glance. Keep the format uniform across your catalog, avoid leading zeros that spreadsheets strip, keep them a reasonable length, and never reuse a retired SKU for a different product, which corrupts historical data.
Can two different products share a SKU?
No. A SKU must be unique within your business, that is its entire purpose. If two products shared a SKU, your inventory and sales data would be meaningless, since the system could not tell them apart. Each distinct product and variant gets its own unique code, and retired SKUs should never be reassigned.
Do I need SKUs for a small online store?
If you sell only a few simple items, informal tracking may suffice, but once you have dozens of products or variants, or sell across multiple channels, SKUs become essential to avoid losing track of stock and overselling. Modern ecommerce platforms include SKU handling, so you mainly need to design a consistent coding scheme.
Was this helpful?