Guide
Seller SKU vs ASIN: What a Seller SKU Is and How to Create One
A seller SKU is the one identifier in your catalogue you fully control — and the one most brands get wrong. Here is what a seller SKU actually is, how it differs from an ASIN, UPC and FNSKU, how to build a naming scheme that survives growth, and the mistakes that quietly break inventory and reporting.
A SKU (stock keeping unit) is an identifier a seller assigns to a distinct, sellable item so that its inventory, orders and performance can be tracked separately. Field names, character rules and behaviours differ between platforms and change over time — always confirm the current rules in the marketplace’s own documentation rather than relying on a blog post, including this one.
What a seller SKU actually is
A SKU is an internal tracking code you create. It is not a product identifier the marketplace issues — it is the label you attach to a specific sellable variant so that everything downstream can tell it apart from its neighbours. Three properties define it:
- You own it. You choose the value. No catalog team assigns it, and no GS1 registry issues it.
- One SKU per sellable unit. A T-shirt in three sizes and two colours is six sellable units — six SKUs, even if it is one product page.
- It is the thread through your operations. Inventory, purchase orders, shipments, returns, ads and reports all reconcile against it.
A SKU identifies your item in your systems. A UPC/GTIN identifies the product globally, and an ASIN identifies it inside Amazon’s catalog. Mixing the two is the root of most catalog confusion.
SKU vs ASIN vs UPC vs FNSKU
These four are frequently used as if interchangeable. They are not. Availability and exact behaviour vary by platform and region, so treat this as the shape of each identifier, not a substitute for the marketplace’s own documentation.
| Identifier | Who assigns it | What it identifies | You control it? |
|---|---|---|---|
| Seller SKU (MSKU) | You, the seller | Your specific sellable variant | Yes |
| ASIN | Amazon | A product variant in Amazon’s catalog | No |
| UPC / EAN / GTIN | GS1 (the barcode authority) | The trade item at retail | No — licensed |
| FNSKU | Amazon | Units Amazon holds and fulfils (FBA) | No — assigned |
The practical consequence: you can change or rebuild a SKU scheme on your side, but you do not get to choose an ASIN or re-issue a UPC. Plan your SKUs around the identifiers you cannot change.
Why SKUs matter more than sellers expect
A SKU looks like admin until something breaks. Where it earns its keep:
- Inventory accuracy. Stock counts are per-SKU. Duplicate or reused SKUs make the numbers lie.
- Multi-channel reconciliation. The same physical item sold on Amazon, Walmart and eBay needs a consistent internal key.
- Reporting. Profit and sell-through analysis only works if every sale is attributable to one unit definition.
- Bulk feeds. Catalog uploads update rows by SKU; a malformed SKU fails the row.
- Variation structure. Parent/child relationships are built on the child SKUs.
- Returns and chargebacks. Disputes are argued with an identifier the platform recognises.
How to create a seller SKU
Creating the SKU is the easy part; deciding it well is the work. A sequence that holds up as a catalogue grows:
- Decide the unit of tracking first. What is the smallest thing you sell and stock separately? That is one SKU.
- Apply a naming convention (next section) before you create the first one — retrofitting later is painful.
- Treat it as permanent. Once a SKU is live with stock or sales history, changing it breaks the link to that history.
- Create it in the platform catalogue and, for variations, as the child of the correct parent.
- Record it in your own source of truth. A spreadsheet or ERP that mirrors the platform — never the platform alone.
- Map it across channels if you sell more than one place, so one physical unit has one internal identity.
Allowed characters, length limits and reserved formats vary by marketplace and can change. Confirm them in Seller Central (or the equivalent) before you build a scheme around a specific format — we do not state limits here because they are platform-controlled.
A SKU naming convention that survives growth
There is no single correct scheme, but a good one is short, human-readable and stable. A practical pattern is:
| Segment | Example | Why |
|---|---|---|
| Brand | ACME | Separates your lines if you sell more than one brand. |
| Category / product | TSHIRT | Makes the item identifiable at a glance. |
| Variant | BLK-M | Encodes colour and size — the reason the unit exists. |
| Pack | 2PK | Distinguishes multipacks from singles. |
So a product becomes ACME-TSHIRT-BLK-M-2PK. Keep it uppercase, avoid spaces and punctuation that platforms dislike, and do not encode price, season or channel in the SKU — those change while the product does not.
Common SKU mistakes
- Changing a SKU after launch. It severs the listing’s link to its own history and stock.
- Reusing a SKU for a different product. Reports silently blend two products forever.
- Duplicate SKUs across parent and child. Variations collapse or fail to build.
- Spaces, symbols or very long values. Feeds reject the row or truncate the value.
- Encoding temporary details. Price or campaign codes in a SKU guarantee a migration later.
- Keeping the master list only in the platform. If the catalogue breaks, so does your only record.
SKUs across marketplaces
Each marketplace keeps its own catalogue and its own field for your seller-assigned identifier — Amazon’s MSKU, Walmart’s SKU, eBay’s custom label. They will not match by default, and that is fine, as long as you keep one internal SKU as the single source of truth and map each channel to it.
This is one of the operational reasons marketplace expansion goes wrong: brands add a second channel, invent a second set of SKUs, and lose the ability to answer “how much of this product do we actually have, and where?” before the first reorder. Getting the identifier layer right first is what makes the rest of marketplace expansion tractable.
Where SKUs sit in your catalogue work
SKUs are the foundation the rest of the catalogue is built on:
- Creating products and variations correctly — see Amazon product listing services.
- Improving titles, attributes and content once the structure is right — see listing optimization.
- Making items discoverable in search — see marketplace SEO.
- Running the catalogue day to day — see marketplace account management.
Fix the identifiers first. Optimisation applied to a messy catalogue just makes the mess rank.
Related services
Explore the services this guide supports.
Frequently asked questions
What is a seller SKU?
A seller SKU is an internal code a seller assigns to a distinct, sellable item or variant so its inventory, orders and performance can be tracked separately. You create and control it; it is not issued by the marketplace.
Is a seller SKU the same as an ASIN?
No. A seller SKU is your own internal identifier, while an ASIN is a catalog identifier assigned by Amazon to a product variant. You can change your own SKU scheme; you cannot choose or re-issue an ASIN.
Can I change my seller SKU after listing a product?
You generally can change it, but you should not do so casually: the SKU is the link between the live listing and its stock, orders and history. Changing it mid-life can orphan that history, so change it deliberately and update your own records at the same time.
How do I create a seller SKU on Amazon?
You choose the value yourself when you create the product or variation in Seller Central or a bulk feed. Amazon applies its own field rules and character limits, which can change — confirm the current requirements in Amazon’s documentation before creating a scheme.
What is a good SKU naming convention?
Short, uppercase, stable and descriptive — typically brand, product, variant and pack, such as ACME-TSHIRT-BLK-M-2PK. Avoid spaces and symbols, and do not encode price, season or channel, because those change while the product does not.
Do I need a different SKU for each marketplace?
Each marketplace has its own field for your seller-assigned identifier, so the values often differ. Keep one internal SKU as your single source of truth and map each channel to it, rather than inventing an unrelated identifier per platform.
Get the identifier layer right before you scale
Get a free Ecommerce Growth Audit and we will review your catalogue structure, SKU consistency and listing foundations.