Back to media

SKU Mapping for Marketplaces: A Practical Guide for Sellers

SKU Mapping for Marketplaces: A Practical Guide for Sellers

SKU Mapping for Marketplaces: A Practical Guide for Sellers

Seller matching a barcode to inventory

SKU mapping links the internal code you use for each product, your master SKU, to the identifier each marketplace uses for the same item. Done well, one stock pool feeds every channel, and an order on any channel updates the right product. Done badly, you get overselling, orphaned listings and fulfillment errors. This guide shows you how to build a mapping system, which rules to set before your first upload, and how to keep it clean as you add channels and countries.

Moreshores
Keep Marketplace Operations Connected
MoreShores integrates product listings across marketplaces and storefronts, alongside warehousing, inventory management, and cross-border fulfillment.

TL;DR

  • A SKU is your own code. ASINs, Walmart item IDs and similar codes belong to the platform, so you need a table that connects them.
  • Set your naming convention before the first marketplace upload. On Amazon, a SKU on an existing FBA listing cannot be changed later.
  • Keep one master inventory ledger and map every channel alias to it, including separate aliases for FBA and merchant-fulfilled offers.
  • Review “close match” and “no match” lists regularly. Mismapping causes inventory drift.
  • If you sell across borders, mapping has to line up with the warehouse, customs data and couriers too. That is where we help.

Table of Contents

What SKU mapping actually is

A stock keeping unit is an internal alphanumeric code that sellers create to identify, receive and locate inventory. Shopify’s SKU guide explains that SKUs are not required by law and differ from barcodes, but they are best practice for inventory tracking, accurate sales reporting and avoiding stockouts.

The trouble starts when you sell on more than one channel. Each marketplace keeps its own catalog and its own identifiers. Amazon uses ASINs, which are platform-specific and, per the same Shopify guide, are 10 characters starting with “B0” in the example it gives. Walmart uses its own item IDs. Your storefront has product and variant IDs. None of these talk to each other unless you tell them how.

SKU mapping is that instruction. For each product you record a structure like this:

Layer Example Owner
Master SKU TEA-GRN-100-12 You
Amazon FBM alias TEA-GRN-100-12-AMZ You (Amazon also assigns an ASIN)
Amazon FBA alias TEA-GRN-100-12-FBA You (Amazon also assigns an FNSKU)
Walmart alias TEA-GRN-100-12-WMT You (Walmart assigns an item ID)
Storefront variant TEA-GRN-100-12 Your Shopify or WooCommerce store

The codes in this table are illustrative. Use whatever scheme fits your catalog, as long as it is consistent.

Why mapping breaks when you grow

One channel is easy. A spreadsheet works. Problems appear at the second or third channel, for four common reasons.

  1. The same product has different identifiers per channel. A sale on one channel has to reduce stock available on all the others. Without a map, nothing knows which items are the same.
  2. Fulfillment methods count as separate channels. Amazon FBA and merchant-fulfilled listings of one product usually need their own aliases so you can track demand and stock for each.
  3. Old listings leave debris. Per the Amazon seller forum guidance, you cannot change a SKU for an existing FBA listing. If you need a different one, you create a new SKU, and the old record can leave orphaned inventory behind.
  4. Bundles and multipacks behave differently. A two-pack on one channel may draw down two units of a single-unit master SKU. Your map needs a quantity multiplier, not just a pair of codes.

The cost shows up as cancelled orders, late shipments and a seller metric that slides. Fixing it after the fact is slower than designing it up front.

Step by step: building your mapping system

1. Design the master SKU first

Pick the structure before you upload anything. Amazon seller support guidance stresses that planning your naming convention before your first upload avoids long-term rigidity, since an FBA listing’s SKU is fixed once created.

A workable pattern:

  • Product family, variant, size or pack, in that order
  • Short, readable segments separated by hyphens
  • No spaces, no leading zeros that a spreadsheet could strip, and no meaning that will change (such as a supplier name)
  • Never reuse a retired code for a different product

2. Collect your product identifiers

Most marketplace listings need a valid GTIN, the number under a UPC barcode. GS1 US notes that unless your category is exempt, sellers need valid GTINs, and that Amazon checks UPCs against the GS1 database. Codes that are not GS1-licensed can lead to listing rejection or account issues. Get your codes from GS1 or from the brand owner, not from a reseller list.

Store the GTIN in the same row as the master SKU. It is your best secondary signal when matching.

3. Create the mapping table

One row per channel alias. Columns that earn their place:

  • Master SKU
  • Channel name and fulfillment type (for example, Amazon FBA)
  • Channel SKU (your alias)
  • Platform ID (ASIN, Walmart item ID, listing ID)
  • GTIN
  • Pack quantity multiplier
  • Status (live, paused, retired)
  • Date created

4. Link existing listings instead of recreating them

If listings already exist, link them. Shopify’s Marketplace Connect lets you link an existing listing to a Shopify product, and it suggests matches using secondary signals when exact SKUs are missing. Walmart offers Setup by Match, a bulk upload method that matches your items to products already in its catalog.

Treat any automatic match as a suggestion. Check it against the GTIN and the pack size before you accept it.

5. Set one inventory ledger

The master SKU should own the count. Channels receive an allocation or a synced quantity, and every order decrements the master. If you cannot sync in real time, hold a safety buffer on fast-moving items so a slow update does not become an oversold order.

Master SKU inventory allocation and order flow

6. Audit on a schedule

Weekly at first, then monthly. Review the close-match and no-match lists that mapping tools produce, and compare channel stock to physical stock. Mismapping lets inventory drift quietly until a customer order cannot be filled.

Mapping rules by marketplace

Rules change, so check each seller portal before you commit. These are the points we see matter most.

Channel What to know
Amazon Your SKU is tied to your seller account. ASIN is Amazon’s catalog ID. FBA and FBM need separate offers. GTIN needs to be valid.
Walmart Sellers must provide a Business Tax ID (an SSN is not accepted) and supporting documents to join, so set up your business details before mapping. Listings use unique product identifiers such as GTIN/UPC.
Your own store Variants carry their own IDs. Keep the storefront SKU identical to the master SKU where you can.
Other marketplaces Each has its own required attributes. Keep those attributes in your product data, not in the SKU.

Common mapping mistakes and how to fix them

  • Encoding too much in the SKU. If the code includes the price or supplier, it breaks when those change. Keep attributes in product data.
  • One SKU for several pack sizes. Give each pack its own code and map it to the master with a multiplier.
  • Deleting a listing to “fix” it. The merchant SKU stays burned. Retire it in your table and create a new one.
  • Accepting every auto-match. A match on title alone can pair a 12-ounce item with a 16-ounce one.
  • No owner. Assign one person to approve new mappings. Ten people adding rows is how duplicates are born.

Our perspective: mapping is a supply chain problem, not just a data problem

Most advice treats SKU mapping as a spreadsheet exercise. In our work with brands selling across borders, we see it as the point where catalog data, stock, customs paperwork and shipping meet.

Our perspective: mapping is a supply chain problem, not just a data problem — overview diagram

When a brand sells into a new market through several marketplaces, the same master SKU has to line up with the pallet in the warehouse, the barcode on the box, the customs record for import and the listing on each channel. If any of these use different codes, someone ends up reconciling by hand, and that is where errors happen. That is why we run catalog, warehousing, fulfillment and compliance in one system rather than as separate contracts with a broker, a courier and an agency.

Our advice is simple. Decide your master SKU on day one. Give every barcode a matching SKU. Map each channel to the master, not to one another. Then let one partner own the physical flow behind it.

— Matt

How MoreShores supports multichannel mapping

We built Marketplace Integration so product listings across marketplaces such as Takealot, Amazon SA, Jumia and Kilimall, as well as Shopify and WooCommerce storefronts, tie back to one catalog. Stock sits in our fulfillment and warehousing operation, and orders go out through a multi-courier network, so the SKU a customer buys is the SKU we pick.

If you are a US or international brand looking at African markets, our cross-border selling model lets you sell without setting up a local entity, with us acting as Importer of Record. Here is what we publish on our pricing page that touches on SKU and catalog work:

Item Published price
Market-entry setup fee 950 USD, one-off
Barcode creation 120.00 ZAR per SKU, one-off
Stock intake 180.00 ZAR per pallet or 24.00 ZAR per box, one-off
Pick, pack and box 18.00 ZAR per order, first item included
Each additional item in an order 6.00 ZAR per order
Storage 180.00 ZAR per pallet per month, or 360.00 ZAR per shelf per month, pro-rated
Stock take From 2400.00 ZAR, one-off
Rush order, same-day dispatch before 12pm 600.00 ZAR per order

The pricing page also lists a cross-border rate of 10%. Open the page for how it applies to your setup. Want to talk through your catalog? Partner with us and we will look at your SKU structure with you.

A worked example

Say you sell a 100 g green tea tin and a three-tin gift pack on Amazon, Walmart and your Shopify store.

  1. Master SKUs: TEA-GRN-100-1 and TEA-GRN-100-3. You keep the gift pack as its own master, or map it to the single tin with a multiplier of 3. Choose one approach and keep to it.
  2. Aliases: the single tin gets an FBM alias and an FBA alias on Amazon, one Walmart alias and one storefront variant. That is four rows for one product.
  3. GTINs: the single tin and the gift pack each have their own GTIN, from GS1 or the brand owner.
  4. Inventory: 500 single tins sit in one ledger. A gift pack sale subtracts 3.
  5. Audit: at month end, you compare channel counts to the shelf count and review any close matches.

The example is simple on purpose. With 300 products and four channels you would hold over a thousand alias rows, which is why a system with a ledger beats a sheet.

Checklist before you add a new channel

  • Master SKU convention written down and shared
  • GTINs verified for every product
  • Mapping table includes pack multiplier and fulfillment type
  • Inventory ledger owns the count
  • Safety buffer set for fast sellers
  • Named owner for mapping approvals
  • Audit date in the calendar

FAQ

What is a SKU on a marketplace listing?

It is the code you assign to an offer in your own inventory. The marketplace stores it with your listing, but it is tied to your seller account and is not the same as the platform’s own product ID, such as an ASIN.

How do I find my SKU number?

Check your seller portal’s inventory or listings page, or your storefront’s product admin. If you never set a scheme, export your listings and build a master SKU table from that export before you add channels.

What is the difference between a SKU and a barcode?

A SKU is an internal code you choose. A barcode, usually a UPC or other GTIN, is a standardized number that identifies the product globally. Marketplaces often require a valid GTIN, and mapping tools use it as a secondary signal to match listings.

Can I change a SKU after I list the product?

Often not. On Amazon, an existing FBA listing’s SKU cannot be changed, and a retired SKU cannot be reused for a different product. Plan the naming convention first, and create a new SKU if you must start over.

Sources

Recommended