How should I set up SKUs so every channel and supplier matches?

What is SKU management in ecommerce?

It is the job of creating, naming and tracking the codes that identify each version of each product, so that every system you use agrees on what is being sold. Your store platform (Shopify, an online store builder), your marketplaces (Amazon, Etsy, Walmart Marketplace), your supplier sheets and your stock tool all use SKUs to join their records. If the same item has a different code in each, the join fails.

One thing to separate early. A SKU is yours. A barcode (such as a UPC or EAN) is a product number assigned outside your business, and Shopify's help page treats SKUs and barcodes as separate fields with different purposes. A supplier part number is theirs. An Amazon ASIN is Amazon's own listing ID. They look alike and they are not the same. A healthy setup stores all of them against one master SKU. Shopify lets you add up to 20 barcodes to one product or variant, so codes from different suppliers, regions or marketplaces can sit against the same item, and it notes that some sales channels require a barcode (a GTIN) before a product can be published.

Why it matters more with more channels

With one channel, a messy code is an annoyance. With three or four, it is a daily error source. Many sync tools match products between systems by SKU, and Shopify's help page names missing or mismatched SKUs as the usual cause of app sync problems. When they do not match, you get oversells, duplicate listings, wrong prices and missing stock. I cover that failure in Shopify and Amazon integration not working and Shopify and Etsy sync not working.

A naming pattern that works

Build the SKU from parts that mean something, in a fixed order, separated by hyphens. A common pattern:

BRAND or LINE - PRODUCT - OPTION1 - OPTION2

Example (made up): MUG-CER-BLU-12 for a ceramic mug, blue, 12 ounce.

Rules I use:

• Capital letters, numbers and hyphens only. Shopify's help page says to avoid special characters, symbols and spaces because they can cause search problems, and that its SKUs are case-sensitive, so ABC123 and abc123 count as different SKUs.
• Keep it short. Shopify's help page suggests no more than 16 characters, and says a format of 4 to 8 characters is enough for many catalogs. Etsy's help page recommends 4 to 8 characters. Other channels may set hard limits of their own, so design for the shortest one, and check the current limit in Amazon's and eBay's listing tools before you set your pattern.
• Never reuse a SKU, even for a discontinued product.
• Do not put changeable facts in it, like price or supplier name. The supplier can change. The SKU should not.
• Avoid leading zeros. Spreadsheets drop them, so 00123 silently becomes 123.
• Avoid letters that look alike, like O and 0, or I and 1.

Channel rules to check before you commit

Channel	What to check
Shopify	SKU is set per variant and should be unique. Shopify's help page says duplicate SKUs can cause problems with third-party integrations and inventory tracking (it shows a warning, which you can ignore for bundles), and that unique SKUs are required for each variant if you use Shopify Fulfillment Network. It also says sync issues are most often caused by SKUs that are missing or do not match exactly.
Amazon	Your SKU is the code you give each offer, called the "seller SKU". Check Seller Central's help for the current rules on length and characters. I treat it as fixed once listed, so decide before you list.
Etsy	You add a SKU in the "Inventory and pricing" part of a listing, and Etsy's help page says SKUs can be numbers, letters or a mix. It recommends 4 to 8 characters, advises against symbols such as commas or slashes, and suggests avoiding the letters O and I. For listings with variations, you can give each option its own SKU. Etsy allows unique SKUs, prices and quantities for up to 400 option combinations per listing, so a very large variation set needs a different plan.
Walmart Marketplace	Check its item setup guide for current SKU rules.

Step by step: clean up an existing catalog

1. Export every channel and your supplier sheets into one workbook.
2. Make a master SKU column with one row per sellable version.
3. Add a mapping table: master SKU, Shopify SKU, Amazon seller SKU, Etsy SKU, Walmart SKU, supplier part number, barcode.
4. Find the orphans. Items that exist on one channel but not in your master, or the reverse.
5. Decide: rename or map. Renaming live Amazon SKUs can break history, so often you keep the channel's code and map it to your master. Rename where it is safe.
6. Lock the pattern for all new products and write it on one page.
7. Feed the map to your sync tool or stock system, and test with one product before all.

Bundles and variants

Bundles are where SKU plans break. A 3-pack sold as one SKU should deduct three units of the single item. Many sync tools cannot do that, so stock drifts. I explain the fix in Shopify bundle inventory. Variants need their own SKUs, never one SKU for the whole product family. Shopify treats each combination of option values, such as small and blue, as its own variant, and each combination is a separate line to count.

How bad SKUs cause sync errors (made-up example)

A seller lists a kettle as KETTLE-RED on Shopify and Kettle_Red on Amazon. A stock tool treats them as two products. A customer buys the last one on Shopify. Amazon still shows 1 in stock and sells it too. The seller cancels and refunds one order, has a cancellation that counts against the Amazon account, and loses time. One mapping row prevents all of it.

Suppliers and SKU mapping

Your supplier has its own part numbers, and you should not use them as your SKUs. Suppliers rename products, merge them or drop them. If your SKU is their code, every change forces a rename across all your channels. Keep your SKU fixed and keep the supplier code in a mapping column. When you add a second supplier for the same item, you add a row to the map, and nothing on your channels changes.

Watch pack sizes too. A supplier code might mean a case of twelve while your SKU means one piece. Store the pack size next to the code, so cost per piece is always worked out the same way. This is the same matching problem described in automating supplier price lists.

Common SKU mistakes

• Using the product title as the SKU. Titles change with every SEO tweak.
• Different SKUs for the same item on each channel. Fine if mapped, a trap if not.
• Using the barcode as the SKU. Barcodes are public and supplied by others. They belong in their own column.
• Letting staff invent codes. Give one person the job of creating new SKUs, or a short form that builds them from the pattern.
• Forgetting returns and kits. A returned item needs to go back under the same SKU it left under.

SKU management software

Several tools help: inventory systems with SKU mapping, listing tools, and PIMs. The question is which fits your size. Start with a sheet and a mapping table. Move to a tool when you have many channels, many suppliers or warehouse staff. See inventory management systems, multichannel inventory software and the multichannel inventory spreadsheet. Prices change often, so check each vendor's pricing page.

How I'd approach this

Fix the SKUs before buying any tool. The tool cannot repair a mapping you have not made. Build the master list and the mapping table in a sheet, lock one naming pattern, and run it for a month. If you then have supplier feeds changing weekly or many channels, a small custom tool that holds the map and updates stock and prices for you is cheaper than juggling it by hand. I build those, and you own them. Pair this with product data management.