SKU ID in Meesho, explained for real sellers.
A Seller SKU ID is your own code for each product variation, the constant underneath every listing. Here is what it means, why every variant needs one, and how to structure SKUs that scale across marketplaces.
SKU ID in Meesho means your own code for one sellable variation of a product, a specific size or colour, typed into the Seller SKU ID field when you upload a catalog. SKU stands for Stock Keeping Unit. Meesho assigns the product ID and variation ID; you assign the SKU ID, one per variation, so inventory, orders and settlements all point to the exact unit on your shelf.
- SKU ID = your internal code for one physical, sellable variant (size, colour, etc.).
- Every variation needs its own SKU, shared codes break inventory and reconciliation.
- Structure them short, uppercase, readable: e.g. TSHIRT-RED-M. No spaces, never reuse.
- Keep one SKU per physical unit across Meesho, AJIO and Amazon to prevent overselling.
- Meesho's product ID is not your SKU, its ID names the listing, yours names the stock.
How a listing splits into stock-keeping units
The listing is what the buyer sees. The SKUs beneath it are what your warehouse and your settlement actually track.
What a good SKU scheme looks like
A few rules separate a scheme that scales for years from one you have to rebuild in six months.
| Rule | Good SKU | Bad SKU |
|---|---|---|
| Readable | TSHIRT-RED-M | 8843920011 |
| Encodes variant | SHOE-BLK-42 | SHOE1 (no size/colour) |
| No spaces/symbols | KURTA-GRN-XL | Kurta Green / XL! |
| Consistent order | product-colour-size everywhere | colour-size on some, size-colour on others |
| Never reused | retire SKU with the product | reuse an old code for a new item |
The single most valuable rule is consistency. A scheme that always reads product-colour-size, in uppercase, with no spaces, stays sortable and mappable as your catalogue grows into the hundreds.
What clean SKUs buy you
SKU hygiene is unglamorous, but it is the foundation everything else in operations stands on.
Building an SKU scheme that lasts
Pick a pattern once
Decide product-colour-size (or whatever fits) and apply it everywhere. The value is in never breaking the pattern, so a new variant is obvious at a glance.
Map to every marketplace
Attach the same internal SKU to each marketplace's listing. Your SKU is the constant; the platform ID is the variable. This is what makes cross-channel sync work.
Sync stock on the SKU
Let one stock count per SKU drive every channel, so the last unit cannot sell twice. That is the whole point of a shared key.
SKUs are the least glamorous part of a catalogue and the part that quietly decides whether your operations hold together as you grow. A little discipline now saves a painful rebuild later.
Why one product needs several SKUs
A buyer sees a single listing, a t-shirt, say, and chooses a size and colour. But your warehouse does not stock “a t-shirt.” It stocks a size-M red one, a size-L blue one, and so on, each with its own count on the shelf. Those are genuinely different physical items, and each needs its own Stock Keeping Unit so you can answer the only question that matters operationally: how many of this exact variant do I have left? Collapse them into one code and you lose that answer, which is how sellers end up cheerfully selling a variant that ran out three orders ago.
This is also why the marketplace’s own product identifier is not a substitute. Meesho generates an ID for the listing on Meesho; that ID is about the listing, not about your stock. Your SKU is the code you control, and because you control it, it can be the same across Meesho, AJIO and Amazon, one physical unit, one SKU, listed in several places. That shared key is what lets a single stock count serve every channel.
Designing a scheme you will not regret
The goal is a code that a human can read and a system can sort. Encode the attributes that distinguish variants, typically product, colour and size, in a consistent order, in uppercase, with no spaces or special characters. TSHIRT-RED-M tells you exactly what it is; 8843920011 tells you nothing. Keep the order identical across every product so the scheme stays predictable, and never, ever reuse a retired SKU for a different item, because that is how two unrelated products end up looking identical to your reconciliation. When you are ready to sell in more than one place, our guide on selling across marketplaces and the multi-marketplace daily workflow both lean on exactly this SKU discipline.
Inventory and SKU ID in Meesho: what the two fields mean
Sellers search for “inventory and SKU ID” together because the two sit next to each other in the catalog upload sheet and on the inventory page, and the panel asks for both on every variation. Inventory is the number of units you have available for that one variation: the count Meesho sells against, reduces with every order, and marks out of stock when it reaches zero. Seller SKU ID is your own code for that same variation. The important word is per variation. A kurti in three sizes is three rows in the sheet, each with its own SKU ID and its own inventory number. Give all three the same code and Meesho typically cannot tell which size an order is for, and your stock counts stop meaning anything. When you later update stock, you will usually do it against the SKU ID, which is exactly why the code has to be unique and readable.
Variation ID, Product ID and Style Code: how they differ from SKU ID
Four identifiers show up around a Meesho listing and they are easy to confuse. Two are assigned by Meesho, two are assigned by you, and only one of them names a single sellable unit you control.
| Field | Who assigns it | What it identifies | Where you see it |
|---|---|---|---|
| Seller SKU ID | You | One sellable variation (a specific size or colour) | Catalog upload sheet, inventory page, order and payment sheets |
| Variation ID | Meesho | Meesho’s own ID for each size or colour inside a listing | Catalog and inventory views in the Supplier Panel, some exports |
| Product ID | Meesho | The listing as a whole, across every variation beneath it | Catalog page, product URL, order details |
| Style Code | You | One design, grouping all its sizes and colours into one product | Bulk catalog upload sheet |
The practical rule: style code answers “which design is this?”, SKU ID answers “which exact unit is this?”, and the two Meesho-assigned IDs are Meesho’s bookkeeping, useful for support tickets and matching exports but not something you should build your own stock system on. Field names in the panel and the upload template change from time to time, so treat the labels above as the usual ones rather than a guarantee.
Seller SKU ID example: a scheme you can copy
Here is a complete set for one product, a kurti set sold in two colours and three sizes. Six variations, six SKU IDs, one pattern:
KURTISET-BLU-S(blue, small)KURTISET-BLU-M(blue, medium)KURTISET-BLU-L(blue, large)KURTISET-PNK-S(pink, small)KURTISET-PNK-M(pink, medium)KURTISET-PNK-L(pink, large)
Product, then colour, then size, always in that order. The product part can be a short word or a number you assign (KS01 works as well as KURTISET), as long as every product gets a different one. If the same kurti set is listed on AJIO or Amazon, use the identical six codes there, so one stock count serves every channel.
How to create SKU ID in Meesho, step by step
- Decide your pattern before you upload anything: product code, colour code, size code, joined with hyphens, uppercase, no spaces or special characters.
- In the Supplier Panel open Catalog Uploads and choose a single catalog upload or the bulk upload sheet for your category.
- For a single catalog upload, add each size or colour as its own variation and type your code into the Seller SKU ID field for that variation. For a bulk upload, fill one row per variation and put the code in the Seller SKU ID column on every row.
- Enter the inventory for each variation on the same row, so every SKU ID has its own stock count from day one.
- Check that no two rows share a code, then submit. Once the catalog goes live, use the same SKU ID whenever you update stock, so the code and the shelf never drift apart.
SKUs and the money side of your business
The payoff most sellers underrate is reconciliation. When a settlement report lands, every line refers to a sale, a return or a deduction, and the only way to check whether each one is correct is to trace it back to a specific product. If your SKUs are clean and unique, that trace is instant: the line names the SKU, the SKU names the exact variant, and you can see at a glance whether the amount is right. If your SKUs are duplicated or inconsistent, the same line becomes ambiguous, two products look identical to your records, and reconciliation quietly becomes guesswork. That is how wrong deductions slip through, because you cannot dispute a charge you cannot even attribute to the right item. A tidy SKU scheme is, in that sense, the backbone of payment reconciliation.
The same logic extends to restocking and demand signals. Because each SKU carries its own sales history, a clean scheme tells you which exact variant is moving and which is dead stock, the size that always sells out, the colour that never does. Roll those signals up and you can buy inventory to match real demand instead of averages, which is one of the quiet advantages larger sellers have and smaller ones can copy for free. It costs nothing but discipline, and it compounds: the longer your SKU scheme stays clean and consistent, the more trustworthy every downstream number becomes.
Sources & further reading
Your SKU is the key, Robnu keeps every lock aligned
A clean SKU scheme is your responsibility to design. Keeping it consistent across a growing catalogue, matching every settlement line back to the right variant, and not overselling the last unit is where a system helps. Robnu is an agentic OMS for Meesho and AJIO sellers: it runs your daily order processing on the SKU as the shared key, so stock, sales and settlement all speak the same language. It is not a warehouse management system, it does not run your shelves, but it keeps the order and money side aligned to your SKUs.
Free for every seller right now, and forever free under 25 orders a day when paid pricing launches. See it on Meesho order management or the full order management system guide. Amazon is live; Flipkart and Myntra are coming soon.
Seller SKU ID, answered
A Seller SKU ID is your own internal code for a specific, sellable version of a product, a particular size, colour or variant. SKU stands for Stock Keeping Unit. It is how you, not Meesho, identify exactly which unit sits on a shelf, ships in a parcel, and needs restocking. One product listing can contain several SKUs, one per variation.
Because a size-M red shirt and a size-L blue shirt are different physical items with different stock levels. If they share one code, you cannot track inventory accurately, you cannot tell which variant is selling, and you risk overselling one while sitting on another. A distinct SKU per variation is what makes accurate stock and reconciliation possible.
Use a short, consistent, human-readable pattern that encodes the attributes that matter: a product code, then the variant dimensions like size and colour. For example a scheme such as TSHIRT-RED-M keeps it readable and sortable. Keep it uppercase, avoid spaces and special characters, and never reuse a retired SKU for a different product.
Yes, and you should. A single internal SKU per physical variant that you map to each marketplace's listing is exactly what prevents oversell and reconciliation chaos when you sell in more than one place. The marketplace has its own listing ID; your SKU is the constant underneath that ties them all to one real unit of stock.
Messy SKUs cause real money problems: you oversell a variant that is actually out of stock, you cannot reconcile which product a settlement line refers to, and your inventory counts drift from reality. Duplicate or reused SKUs are worse, because two different products then look identical to your system. Cleaning it up later means re-mapping every listing.
No. Meesho generates its own product and catalog identifiers for the listing on its platform. Your Seller SKU ID is the internal code you assign to the physical variant. They serve different jobs: Meesho's ID identifies the listing on Meesho, your SKU identifies the real unit of stock that could be listed on several marketplaces at once.
The SKU is the shared key. When the same physical variant carries the same SKU everywhere, a system can decrement one stock count as sales come in from any channel, so you do not sell the last unit twice. Without a clean SKU scheme, cross-marketplace inventory sync is guesswork. See our guide on inventory-sync-overselling.
They are two columns that sit side by side in the Meesho catalog upload sheet and on the inventory page. Inventory is the number of units you have available for one variation, the count Meesho sells against and reduces with every order. Seller SKU ID is your own code for that same variation. Both are per variation, so a kurti in three sizes has three SKU IDs and three inventory numbers, not one.
Variation ID is the identifier Meesho itself assigns to each size or colour option inside a listing. You do not choose it. It appears in the Supplier Panel's catalog and inventory views and in some exports, and it is what Meesho uses internally to tell one variation from another. Your Seller SKU ID is the code you assign to the same variation, so the two usually map one to one.
Product ID is Meesho's identifier for the listing as a whole, covering every size and colour beneath it; you will usually see it in the catalog page and in the product URL. Style code is a code you provide, typically in the bulk upload sheet, to group all the variations of one design into a single product. Neither replaces the SKU ID, which is the only one that names a single sellable variation you control.
You create it while uploading a catalog. In a single catalog upload, there is a Seller SKU ID field for each size or colour you add. In a bulk upload, the sheet has one row per variation and a Seller SKU ID column on every row. Type your own code, uppercase with no spaces, one per variation, and keep it unique across your whole catalog. Meesho does not generate it for you.
Take a kurti set sold in two colours and three sizes. A clean scheme reads KURTISET-BLU-S, KURTISET-BLU-M, KURTISET-BLU-L, KURTISET-PNK-S, KURTISET-PNK-M and KURTISET-PNK-L. Product, colour, size, always in that order, always uppercase, no spaces. Anyone in your team can read a code and know exactly which unit it is, and the codes sort neatly in any spreadsheet.
SKUs is simply the plural of SKU, Stock Keeping Unit. When the panel or a report says a catalog has six SKUs, it means the listing contains six distinct sellable variations, each with its own Seller SKU ID and its own inventory count. Counting SKUs is counting variations, not counting products.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Variation ID, Product ID, Style Code and SKU ID in Meesho
Variation ID in Meesho is Meesho's ID for one size or colour; product ID names the listing; style code and SKU ID are yours. Who assigns each, where you see it.
Meesho Order On Hold Meaning: Why an Order Is Held and What to Do
Meesho order on hold means Meesho paused the order before ready to ship, usually for a payment, address or risk check. Why, how long it lasts, and what to do.
Multi-Marketplace Order Management for Indian Sellers (2026)
Selling on Meesho, AJIO and Amazon at once means three panels, three SLAs, three settlement formats and three label rules. Learn why juggling tabs breaks at scale and how a unified order plus reconciliation system fixes it.
Meesho Branded Packaging Code: Policy & Support 2026
Meesho's branded packaging policy lets eligible sellers ship in their own brand identity within the rules. Here is what the branded packaging code covers, who qualifies, and how it sits alongside mandatory BP-TP.
Meesho orders stuck in pending: what it means and how to clear them
Blocked does not mean paused, the dispatch clock usually keeps running. The four causes, which two you can fix yourself, and what to document when you cannot.
Bulk Label Cropping on Meesho: Save Hours a Day (2026)
Bulk label cropping on Meesho turns a full download of shipping labels into clean, print-ready slips in one pass. Learn how it works, how barcodes stay intact at scale, and how to keep buyer data private.
Meesho Manifest: How to Generate and Hand Over (2026)
A Meesho manifest is the handover list that proves you gave your packed parcels to the courier. Learn how to generate it after labels are ready, scan parcels onto it, hand it over, and use it to protect disputes.
Meesho Order Processing: From Order to Handover (2026)
Meesho order processing explained end to end: new order, accept, label and invoice, pack, ready to ship, manifest, courier pickup, delivery or RTO, and settlement. Learn each SLA stage and where sellers lose time and money.