SKU stands for Stock Keeping Unit. In ecommerce, an SKU is a merchant-assigned code used to identify and track a sellable product or variant inside the merchant's catalogue and inventory management systems.
A navy T-shirt in size M and the same T-shirt in size L normally need different SKUs because their stock is counted separately. An SKU is not automatically a barcode, GTIN, ASIN, model number, or serial number. Those identifiers have different owners and jobs.
What is an SKU in ecommerce?
The practical SKU meaning is a unique reference for something a business needs to stock, sell, pick, return, or report separately. The code can contain letters, numbers, or both. The merchant controls the format inside its own system.
The important word is unit. A product family can contain several products or variants, and each separately stocked variant can have its own Stock Keeping Unit.
A catalogue with 100 SKUs contains 100 separately identified sellable units under that merchant's counting policy. It does not automatically contain 100 product families. One shoe design offered in five sizes and four colours can account for 20 SKUs when every size-colour combination is stocked separately.
An SKU only needs to be unique within the business and connected systems that depend on it. It is not designed to identify the same trade item across every retailer worldwide.
Product, variant and SKU: the catalogue hierarchy
The hierarchy should be clear before a team creates codes.
| Catalogue level | Hypothetical apparel example | What changes at this level? |
|---|---|---|
| Product family | Everyday cotton T-shirts | The broad merchandise group |
| Product | Crew-neck cotton T-shirt | The item design or model |
| Sellable variant | Navy, size M | A stocked combination a customer can buy |
| SKU | TSH-NVY-M-01 | The merchant's reference for that variant |
In this hypothetical example, TSH-NVY-M-01 and TSH-NVY-L-01 belong to the same product but identify different size variants. A warehouse can therefore count, pick, replenish, and return them separately.
The exact hierarchy varies by catalogue. A furniture brand may treat finish and size as variants. A beauty brand may separate shade and pack size. A spare-parts seller may organise products by machine model, part type, and fitment. The SKU architecture should mirror the distinctions the business actually stocks and fulfils.
This is also why “product code” can be ambiguous. A team may use that phrase for an internal SKU, a manufacturer's part number, or a marketplace identifier. Name the identifier instead of assuming every system uses “product code” in the same way.
SKU vs barcode, GTIN, EAN, UPC, ASIN, MPN and serial number
These terms are related, but they are not synonyms.
| Identifier | Usually assigned by | Scope | Main job |
|---|---|---|---|
| SKU | Merchant or seller | The merchant's catalogue and connected systems | Track a sellable product or variant internally |
| GTIN | Issued under the GS1 identification system | Standardised trade-item identification | Identify a trade item across organisations and channels |
| EAN or UPC | Brand owner through the relevant GS1 route | Common GTIN formats used in retail | Carry a standard trade-item number |
| Barcode | Depends on the value encoded | A machine-readable symbol | Let scanners read an identifier or other data |
| ASIN | Amazon | Amazon catalogue | Identify a product detail-page entity in Amazon's catalogue |
Flipkart skuId | Seller | Seller listing context on Flipkart | Identify the seller SKU associated with a listingId |
| MPN | Manufacturer | Manufacturer's product range | Identify a part or model assigned by the manufacturer |
| Serial number | Manufacturer or operator | One physical unit | Distinguish one individual item from another item of the same model |
Barcodes are visual carriers. The underlying identifiers remain separate. A barcode can encode a GTIN, an internal SKU, or another value, depending on the system and use case.
Amazon India describes its seller SKU as a code created by the selling partner for stock tracking and offer association. That seller-controlled code is not the same as an ASIN. Flipkart's API documentation similarly distinguishes the seller's skuId from Flipkart's listingId.
Where an SKU travels through an ecommerce business
An SKU is useful because multiple systems can refer to the same sellable variant without relying on a changing product title.
| System | What the SKU helps connect | Check before relying on it |
|---|---|---|
| Storefront catalogue | Product and variant records | Every stocked variant has one stable value |
| PIM or ERP | Product attributes, purchasing and stock records | Imported values have not been reformatted or truncated |
| Warehouse system | Bin counts and the handling flow from pick to return | Labels and scanners resolve to the correct variant |
| Marketplace listing | Seller offer and channel listing | Channel-specific listing IDs are mapped separately |
| Product feed | Product data sent to another channel | SKU is not being substituted for a required global identifier |
| Order system | Line items, cancellations and refunds | Historical orders retain the identifier used at purchase |
| Reporting | Sales and stock analysis, including returns and margin | The same SKU has not been recycled for another product |
The SKU acts as a join key only when each system agrees on the value. Spaces, leading zeroes, case changes, hidden prefixes, and spreadsheet formatting can break a match even when two codes look similar to a person.
During an ecommerce platform migration, preserve the relationship between the old product or variant record, its SKU, the new record, marketplace listings, and historical orders. Changing every SKU during a migration creates another mapping problem at the moment when the catalogue already has the most moving parts.
How to create a practical SKU system
A useful SKU system is easy for staff to recognise, hard to duplicate, and stable enough to survive catalogue growth.
- Choose the attributes that create stocked variants. Start with the real catalogue structure, such as product type, style, colour, size, material, pack size, or generation.
- Put attributes in one consistent order. When the code uses product type and style followed by colour and size, keep that sequence across the relevant catalogue.
- Create an abbreviation dictionary. Decide whether navy is
NVY,NAV, or another approved code. Record the choice instead of letting each person invent a version. - Test uniqueness before import. Check the proposed values against active records, archived products, marketplace listings, and feed exports. A duplicate can overwrite or misjoin data in some workflows.
- Assign ownership. One role or controlled process should create and change values, retire codes, and document each decision.
TSH-NVY-M-01 is a hypothetical pattern, not a universal template. A short code can be easier to scan, but a code packed with every product attribute becomes difficult to maintain. Store rich attributes in their proper catalogue fields instead of forcing the full product description into the SKU.
Run a one-product-family check: choose one product with at least three variants. Trace each SKU through the storefront, stock record, warehouse label, marketplace listing, order export, and reporting table. If one variant changes identity between systems, fix the mapping before applying the pattern catalogue-wide. For a wider catalogue review, request a free ecommerce SEO audit.
Common SKU mistakes and what they break
Duplicate SKUs
Two active variants sharing one SKU can make stock, order, or feed records ambiguous. Some imports may reject the duplicate. Others may update the wrong record. The result depends on the platform and integration, so test duplicate handling before a bulk upload.
Recycled SKUs
Reusing an old SKU for a new product can make historical orders and reports appear to belong to the new item. Retire an identifier without reassigning its history.
One SKU for several stocked variants
If size, colour, pack, or material changes what the warehouse counts, each stocked combination normally needs its own code. Otherwise, the business can know that a product is in stock without knowing which variant is available.
Silent changes during migration
Changing prefixes, case, separators, or leading zeroes can disconnect a variant from feeds, marketplace offers, warehouse records, and order history. Keep a tested old-to-new mapping whenever a change is unavoidable.
Too much meaning inside the code
An overencoded SKU becomes fragile when an attribute changes. The identifier should support recognition and control, while the catalogue stores the complete product facts.
Do SKUs affect ecommerce SEO?
An SKU is primarily an operational and product-data identifier. It is not a standalone Google ranking tactic.
Accurate SKUs can still support search work indirectly. They help teams connect a product-page record with feed data, structured data, analytics, inventory, warehouse records, and marketplace mappings. That consistency makes audits and catalogue changes easier to verify.
Schema.org defines sku as a merchant-specific identifier. Product structured data can include the value when the visible product and variant data support it. Do not use an SKU as a substitute for GTIN or another identifier required by a specific feed or marketplace.
Putting an SKU in every product title is not a general SEO rule. It may help customers who search exact part references, replacement items, or B2B catalogue codes. For most consumer products, the title should first communicate the product type, brand, variant, and attributes that buyers use.
The product page SEO guide covers search-facing product content. The ecommerce schema guide explains how product identifiers fit into structured data without treating markup as a ranking guarantee.
SKU questions ecommerce teams ask
How do I find my SKU number?
Check the product or variant record in the storefront admin, inventory system, warehouse label, order line, or marketplace seller listing. The location differs by platform. Confirm that the value identifies the same variant in every connected system.
Can I create my own SKU number?
Yes. An SKU is merchant-controlled, so a business can create its own internal pattern. The pattern should be unique, documented, stable, and tested across the systems that will import or export it.
What is the SKU ID on Flipkart?
Flipkart defines skuId as the seller SKU ID associated with a listingId. Its inventory documentation uses SKU IDs in listing and stock operations. Do not treat the seller SKU and Flipkart listing ID as the same field.
Is an Amazon seller SKU the same as an ASIN?
No. The selling partner creates the seller SKU for its offer and stock records. Amazon assigns the ASIN within its product catalogue. A seller offer can therefore have both values serving different jobs.
Should customers see the SKU on a product page?
Show it when the code helps buyers confirm a part, model, replacement, wholesale item, or support request. For a consumer product where buyers do not use the code, the SKU can remain in the page data without becoming prominent sales copy.
Can the same SKU be reused for another product?
Avoid reuse when orders, returns, inventory history, integrations, or reports still depend on the old identity. A retired SKU should remain connected to its historical product rather than being reassigned.
Related ecommerce terms and guides
- The ecommerce glossary contains the controlled definitions used across EcommerceSEO.in.
- Fix search-facing titles, descriptions, internal links, and product information with the product page SEO guide.
- Add Product and BreadcrumbList structured data using the ecommerce schema guide.
- Preserve identifier and URL relationships during platform changes with the ecommerce migration guide.
Reviewed: 21 August 2026
Next accuracy review: 21 September 2026
Deep source recertification: 21 November 2026