One product, three codes, zero answers? You need SKU mapping.
List the same kurti on two marketplaces and each panel gives it a different style code — neither matches the other, or your own stock sheet. This guide explains why that happens, what quietly breaks without a master SKU (misrouted returns, settlements you can't reconcile per product, reorders on gut feel), and how to build a mapping sheet that survives catalog changes.
- Every marketplace assigns your product its own identifier, and none of them coordinate. The only stable name your product has is the one you give it — a master SKU that every panel code maps back to.
- Without the map, three things break quietly: returns get matched to the wrong stock, settlement files can't be reconciled per product, and restock decisions run on gut feel instead of true cross-channel velocity.
- The fix is a boring sheet — master SKU, panel, panel code, EAN, weight, cost — kept alive by one rule: no listing goes live and no catalog change lands without its row being updated the same day.
Your product has more names than you think
Take one product — a navy rayon kurti, size M. In your own head and on your shelf, it's “the navy kurti”. In your purchase records it might be KRT-NVY-M. List it on AJIO and the catalog process assigns it a style code. List it on Meesho and it gets a different product ID inside a catalog of variants. Add a barcode for your own scanning and that's yet another identifier. Five names, one product — and every document each marketplace ever sends you will use its name, never yours.
This is not sloppiness on anyone's part. Each platform's catalog system generates identifiers for its own search, logistics and cataloging needs; no marketplace knows or cares what another one calls your product. Which means the join — the knowledge that AJIO's code and Meesho's ID are the same physical kurti — exists in exactly one place: with you. Either it is written down in a mapping you maintain, or it lives in someone's memory and leaves when they are on holiday.
A master SKU is simply the decision to make your internal code the anchor. Panel codes change when catalogs are relisted; your master SKU never does. Every other system — stock counts, costing, reorder maths — hangs off that one stable name.
The mapping sheet, in seven steps
One spreadsheet, one row per product-panel pair. An afternoon to build for a 50-product catalog — and it pays for itself the first settlement you reconcile.
- 01
Fix your master SKU format first
Pick a scheme you can read at a glance — category, colour, size: KRT-NVY-M. Keep it short, uppercase, no spaces, and never reuse a code even after a product is discontinued, because old settlement lines and returns will still reference it months later.
- 02
Lay out the six core columns
Master SKU · panel · panel style code / catalog ID · EAN or barcode · packed weight · unit cost. Weight is there so a weight-discrepancy dispute can be answered per product in seconds; cost is there so reconciliation can say what each product actually earned.
- 03
Pull each panel's codes from its own reports
Don't copy codes from the listing screen — export them from the reports the panel actually generates (order exports, settlement files), so the code in your sheet is character-for-character the code that will appear in every future document you need to decode.
- 04
One row per product-panel pair
A 50-product catalog on two panels is a 100-row sheet, not a 50-row sheet with extra columns. Rows per pair means a third marketplace later is just more rows — and a product delisted from one panel loses one row, not its whole record.
- 05
Wire the map into daily work
The sheet earns its keep only if it's the lens for everything: returns get matched by looking up the panel code before restocking, settlement lines get a master-SKU column added via lookup, and weekly sales-per-product views are built on master SKU, never on panel code.
- 06
Update on every catalog change — same day
Relists, catalog refreshes and variant edits can issue new panel codes. The rule that keeps the map alive: no listing goes live and no relist lands without its row updated that day. Keep the old code in a note column — documents referencing it keep arriving for weeks.
- 07
Audit monthly, ten minutes
Export active listings from each panel and cross-check: every live code has a row, every row has a live listing, weights and costs still current. Drift caught monthly is a two-line fix; drift caught at year-end is a forensic project.
What “we'll sort the codes later” costs
The damage arrives on three fronts, and none of them announce themselves. Returns first: a courier bag comes back carrying a panel code, whoever opens it matches it to the wrong variant, and the wrong stock count ticks up. Multiply by a normal fashion-category return rate and within a quarter your sheet says you have stock you don't — which is how oversells happen on products you thought were safe.
Settlements second: payout files itemise by panel code. Without the map you can check the total but not the composition — so a wrong deduction on one line hides inside an otherwise plausible total. Illustratively, a seller doing ₹2–3 lakh a month who cannot reconcile per product has no way to notice a few hundred rupees of miscoded deductions per file; across two panels and a year, that is thousands of rupees that were never even visible enough to dispute.
Reordering third, and largest: restocking runs on per-product velocity, and velocity needs sales from both panels summed under one name. Without the map, the sum is a guess — so the bestseller goes out of stock while the slow mover gets reordered. No penalty line ever shows up for that one; it just compounds in your working capital.
Robnu speaks every panel's dialect, so you keep one name
The mapping sheet works, but it is manual translation — every return, settlement line and report still passes through a human with a lookup. Robnu builds that translation into the pipeline itself. Orders, returns and settlement files from AJIO and Meesho arrive speaking each panel's code language, and Robnu resolves them to your products automatically: sales roll up per product across channels, returns match the right stock, and every settlement is reconciled line-by-line under one product identity.
That is what makes the Understand side of Robnu possible — per-product, cross-channel answers to “what is actually making money?” — and it is what arms the Protect side: when a settlement line doesn't match what the product should have earned, the dispute is raised with the evidence attached. As fully-autonomous claim filing rolls out, the rare claim still asks you for one approval click.
SKU mapping, answered
SKU mapping is the discipline of keeping one internal master code per product and recording which listing it corresponds to on every marketplace. Each panel assigns your product its own identifier — a style code on one, a catalog or product ID on another — and none of them match each other or your own naming. The mapping sheet is the translation table: one row per product-panel pair, connecting your master SKU to each panel's code. Without it, every report a marketplace sends you speaks a language your stock sheet does not.
Because each platform's catalog system generates its own identifiers when you list — they are built for the marketplace's internal needs (search, cataloging, logistics), not for your bookkeeping. Two panels will never coordinate codes with each other, and neither knows what you call the product internally. That is not fixable on their side; the only place all the codes can meet is a mapping you own. Your master SKU is the one identifier that stays stable while panel codes come and go.
Three things, in escalating order of cost. Returns: a return arrives labelled with a panel code, gets matched to the wrong product, and your stock counts drift silently. Settlements: payout files reference panel codes, so you can total the payout but cannot say which product earned or lost money — per-product reconciliation becomes impossible. Reordering: with sales split across code systems, you cannot see true per-product velocity, so restock decisions run on gut feel. Each failure is quiet; together they mean you are running a catalog you cannot actually measure.
Six as the working minimum: master SKU (your internal code), panel (which marketplace), panel style code or catalog ID (exactly as it appears in that panel's reports), EAN or barcode if you use one, packed weight, and unit cost. Weight earns its place because weight-discrepancy disputes need the correct figure per product instantly; cost earns its place because per-product profit is the whole point of reconciling per product. One row per product-panel combination — a 50-product catalog on two panels is a 100-row sheet.
Make the sheet a mandatory step of the listing workflow, not a document you tidy later: no listing goes live before its row exists. Relist or refresh a catalog and the panel may issue a new code — update the row the same day, keeping the old code noted, because settlement files and returns can reference the old code for weeks afterwards. A monthly ten-minute audit — pull each panel's active listings, check every code has a row and every row a live listing — catches the drift before it compounds.
Robnu keeps the translation layer for you. Orders, returns and settlement lines from AJIO and Meesho arrive tagged with each panel's own codes, and Robnu resolves them against your products so everything lands under one identity — sales per product across channels, returns matched to the right stock, settlements reconciled line-by-line per product rather than as one blended total. When a deduction doesn't match what the product should have earned, Robnu flags it and raises the dispute with evidence attached; as autonomous filing rolls out, the rare claim still asks you for one approval click.
Where this comes from
- AJIO and Meesho supplier documentation on cataloging, style codes and settlement report formats: seller panels and learning hubs, current formats as published on each panel.
- Recurring seller accounts of misrouted returns, unreconcilable settlement lines and catalog-code drift: public seller community threads (Reddit r/IndiaBusiness, seller Facebook and Telegram groups), 2024–2026.
- All rupee figures and timings in charts and examples are illustrative.
Related guides & pages
Sell on multiple marketplaces
The full ops reality of running two or more panels.
Settlement cycles
When each marketplace pays, and what its file looks like.
Inventory sync & overselling
Why unmapped, unsynced stock ends in seller-fault cancellations.
Payment reconciliation
How Robnu checks every settlement line against what you're owed.