Skip to content
Development · What is SKU

What is SKU

Category: DevelopmentRead: 9 minWebLift

SKU sounds like an accounting term until you start counting a catalog. Then it turns out that 500 clothing models become six thousand line items, the platform plan was not sized for them, and the fulfillment provider invoices you for exactly that number. Below we cover what a SKU is, how it differs from a product and an article number, and how to count it correctly the first time.

What a SKU is: the definition

SKU (Stock Keeping Unit) is a unit of inventory accounting: a single catalog line with a unique set of attributes that is counted and stored independently of the others. One T-shirt style in three colors and four sizes gives twelve SKUs, even though the customer sees a single product. Every SKU has its own code, its own stock level and its own price.

The abbreviation is read letter by letter ("S-K-U") or as "skew", and in Ukrainian it is rendered as "unit of inventory accounting". The term came from brick-and-mortar retail, where every shelf slot holds a specific item, and it moved into e-commerce almost unchanged.

The main takeaway from the definition: a SKU answers the question "what exactly is in the warehouse and how much of it", not the question "what product is this". When black T-shirts in size M run out, that specific SKU runs out. The product itself keeps selling.

SKU vs product: why they are different numbers

A product is a model the customer sees on the site as a single card, while a SKU marks each of its individual variations with its own size, color or volume. One product can contain anywhere from one to several dozen SKUs, so the number of items in the catalog and the number of SKUs in the warehouse almost never match.

The difference becomes obvious at the very first count. A clothing store with 500 models, each available in four sizes and three colors, shows the customer 500 products but stores and tracks 6,000 separate line items, while an electronics seller with the same number of cards and no variations stops at exactly 500.

NicheProductsVariations per productSKUs
Clothing50012 (4 sizes × 3 colors)6,000
Footwear2008 sizes1,600
Home appliances5001500
Cosmetics3003 volumes900

Two stores with the same number of products on the storefront can differ twelvefold in how complex their inventory is. That is why the question "how many items do you have" gives nothing to a developer, a fulfillment operator or you yourself when choosing a platform, unless you specify what exactly is being counted. The right question is different. How many rows are in the database?

SKU, article number and barcode

A SKU is the accounting unit itself, an article number is the code that labels it, and a barcode or GTIN is a global product identifier issued through GS1. In Ukrainian practice the article number and the SKU are used as synonyms, and the field in marketplace dashboards is called "article". A barcode, however, cannot be invented, it is purchased.

Strictly speaking, the SKU is the entity and the article number is its name, but in practice nobody holds that distinction: in conversation "add a new SKU" and "create a new article number" mean the same action, and confusion begins only where a barcode joins the pair. We untangled all four codes in the piece on what a product article number is.

One difference is still worth remembering. The barcode is the same for all sellers of the same product, because the manufacturer assigns it through GS1, whereas the SKU is different for every seller: two stores can easily sell the same T-shirt under the codes TS-BLK-M-001 and 45-CHORNA-M, and both are right.

How to count SKUs correctly

The number of SKUs is calculated by multiplication: the number of models times the number of variations of each. Any attribute by which a product is stored and written off independently becomes a separate SKU — size, color, volume, bundle, flavor. Attributes that do not affect stock, such as the country of origin or the material within a single model, do not create separate SKUs.

You can test yourself with one question: can this variation run out in the warehouse separately from the others? If yes, you are looking at a standalone SKU with its own stock and its own code; if not, it is just a line in the card's specifications that adds nothing to inventory accounting.

  • Creates a SKU: size, color, volume or pack weight, bundle, flavor, power rating.
  • Does not create a SKU: material and country of origin if they are the same for the whole model; season; any attribute that is text in the specifications rather than a separate box on a shelf.
  • Debatable: gift packaging and bundles. If a bundle is stored assembled, it is a separate SKU; if it is assembled to order, it is a set of other SKUs.

The last point eats the most time when moving to a new platform. Bundles entered as ordinary products duplicate stock: the system is convinced that you have both the set and each of its components separately, while physically there is one box in the warehouse. Everything sells at once. Then come the cancellations.

How many SKUs your platform can handle

Catalog limits on SaaS platforms are counted in line items, and product variations are usually counted toward the limit. At Horoshop the base limits are 1,000 products on the Basic plan, 20,000 on Standard and 50,000 each on Pro and B2B, with expansion up to 250,000 by arrangement. A clothing catalog of 500 models with twelve variations each will not fit on Basic.

Catalog owners skip this arithmetic regularly. The plan is chosen by the number of models they see in their own price list, while the platform counts rows in the database, and a twelvefold difference calmly turns a confident "the cheapest one will be enough" into a forced upgrade a month after launch. Sometimes sooner.

Before choosing a plan, count not products but the rows that will go into the database. They are different numbers, and you will pay for the second one.

The same applies to fulfillment: storage and handling are billed by the number of SKUs, not the number of models, because every variation physically takes up its own bin. We compared the platforms themselves by limits and cost in our overview of ecommerce platforms, and a detailed breakdown of the Horoshop pricing grid is in the piece on Horoshop plans.

SKU in the feed and on marketplaces

In a product feed every SKU must get its own unique identifier. The Google Merchant Center specification requires a separate id for each product variant, forbids reusing identifiers, and recommends basing them on the seller's SKU. An identifier is 1 to 50 characters long.

On marketplaces the logic is the same, with local specifics. A product that is not split by size arrives there as a single row, the customer sees only one variant in the card, and the remaining stock simply never goes on sale and lies dead until the end of the season. The opposite mistake is just as common: variations entered as separate, unlinked products multiply cards and compete with each other in the marketplace's results.

The right solution is in the middle. Variations stay separate SKUs in accounting and in the feed, and on the site they are gathered into one card with a size switcher, so the customer sees exactly what they should see while the warehouse keeps counting every box separately. How this looks in the fields of each marketplace is described in our in-depth guide on how to fill in a product card.

Why count SKUs in analytics

SKU-level analytics shows which exact variations bring in money and which sit as dead weight. The classic ABC analysis ranks items by their contribution to revenue, and in most catalogs a small share of SKUs delivers most of the sales. The rest take up warehouse space, use up the plan limit and dilute attention.

At the product level this picture is not visible at all. A model looks successful right up until you look inside and see that one size out of four is selling while the other three have been sitting since purchase. The decisions differ, from changing the size grid in the next order to dropping a variation from the range, but the problem itself is visible only at the SKU level.

The second practical metric is turnover, that is, how many days on average a unit of a specific SKU sits before it sells. Items with a turnover of several months eat the money frozen in purchasing. They are also the first to go on sale.

Common SKU mistakes

The most frequent mistakes: counting SKUs as products and getting the plan wrong, entering variations as separate unlinked products, giving one SKU to several variations and losing control of stock, and changing the code of an already created item. Each of them is noticeable not immediately but months later, when the catalog has already grown.

  1. One SKU for several sizes. Stock shows the total quantity, and the store sells a size it does not have. Then comes an order cancellation and a hit to the seller rating.
  2. Variations as separate products. The catalog bloats, cards compete with each other, and the customer does not see that the size they need exists at all.
  3. A code with meaning baked in. A supplier or purchase date built into the SKU ages faster than the product itself, and the code can no longer be changed.
  4. No single source of truth. When SKUs live separately in a spreadsheet, separately on the site and separately in the marketplace dashboard, a mismatch appears with the very first delivery.

The last one is cured not by discipline but by architecture: the catalog is maintained in one place and distributed to marketplaces through feeds. Then a new SKU is created once and arrives everywhere it should on its own. If the catalog has already sprawled, we usually start with consolidating it into one database as part of product card content work.

What is a SKU in simple terms?

It is a separate item in the warehouse with a unique set of attributes. One T-shirt style in three colors and four sizes gives twelve SKUs, even though on the site it is a single product card. Every SKU has its own code and its own stock level.

What does SKU stand for?

Stock Keeping Unit, in Ukrainian "unit of inventory accounting". The term came from brick-and-mortar retail, where every item has a specific storage location, and moved from there into e-commerce.

How is a SKU different from a product?

A product is a model the customer sees as one card. A SKU is each of its variations by size, color or volume. One product can contain from one to several dozen SKUs, so the number of cards in the catalog and the number of SKUs in the warehouse almost never match.

How is a SKU different from an article number?

In practice it is not: both words mean a separate accounting item of the seller. Strictly speaking, the SKU is the accounting unit itself, while the article number is the code that labels it. In the dashboards of Ukrainian marketplaces the field is called "article".

How do you count the number of SKUs?

Multiply the number of models by the number of variations of each. The check is simple: if a variation can run out in the warehouse separately from the others, it is a standalone SKU. If not, it is just a specification in the product card.

Does the number of SKUs affect the cost of a platform?

Yes. Catalog limits are counted in line items, and variations are usually counted toward the limit. At Horoshop that is 1,000 products on Basic, 20,000 on Standard and 50,000 each on Pro and B2B. A clothing store with 500 models and twelve variations will not fit on Basic.

Does every SKU need its own code in the feed?

Yes. The Google Merchant Center specification requires a unique identifier for each product variant, forbids using the same identifier twice, and recommends basing it on the seller's SKU. The length is 1 to 50 characters.

How many SKUs should an online store have?

There is no universal number, it depends on the niche: in electronics 500 products mean 500 SKUs, in clothing several thousand. It is more practical to look not at the total but at the sales distribution: in most catalogs a small share of SKUs brings in most of the revenue, while the rest take up space and plan limit.

Related WebLift services

If the article answered your question, this is where people usually go next.

Has your catalog outgrown the platform?

We'll count the real number of SKUs, choose a platform for your catalog and move the products over without duplicates or lost stock. Free quote within 24 hours.

Discuss the project