What is the best way to name SKUs when the same item is listed on several marketplaces?

Why a SKU is not a listing title and not a platform ID

Every marketplace assigns its own listing number, and none of those numbers mean anything to the other marketplaces. If the same jacket is live on three platforms, you have three listing IDs and no built-in way to say they refer to one physical object. The SKU is the identifier you own. It lives on the tag attached to the item, in your inventory record, and in the custom label or SKU field of each listing, and it is the only thing that ties the three listings together. For one-of-a-kind resellers, one SKU equals one physical item. For people who buy in quantity, one SKU equals one product with a count attached. Related: The Oversell Problem for Resellers

The title is a different job entirely. Titles are marketing text you will adapt per platform, shorten when a character limit bites, and rewrite when an item stalls. A SKU should never change once assigned. That is also why the SKU should not carry information you might later want to correct. If the code encodes brand, size, and color and you later discover the size tag was wrong, you now have a choice between a misleading SKU and a renumbered item that breaks every link you built. Keep the meaning in the record, keep the code stable.

Keep reading: The Oversell Problem for Resellers, Selling on Multiple Platforms, Keeping Prices in Sync. See how RelistSync helps you multi-platform price and inventory sync for resellers.

A scheme that stays unique past item two hundred

The scheme that survives growth is a short prefix plus a running number that never resets. A prefix can identify the intake batch, such as the year and month you sourced the item, so 2609-041 reads as the forty-first item from the September 2026 intake. That gives you the item's age at a glance without encoding anything that could turn out to be wrong. Six to ten characters is typically enough. Avoid characters that are easy to misread on a handwritten or thermal-printed tag, especially the letter O next to zero and the letter I next to one, and skip punctuation other than a single hyphen, since some marketplace SKU fields strip or reject special characters.

Never reuse a SKU, even when the same product comes back through a return or you source an identical piece later. A returned item keeps its original code, because the history attached to that code (photos, original price, the return reason) is exactly what you want to see. A second identical piece gets its own new code if you sell one-of-a-kind, or is added to the quantity on the existing code only if it is truly interchangeable and you are comfortable shipping either unit against any sale. The moment two different physical objects share a code, a sale of one will delist the other. Related: What should a reseller do when a returned item needs to go back up for sale everywhere?

Putting the code in every place it needs to be

The SKU needs to appear in three places, and a missing one is where problems start. First, on the physical item: a hang tag, a masking-tape label, or a small sticker on the poly bag. Second, in the inventory record next to the storage location. Third, in the SKU or custom label field of every marketplace listing. Where a platform offers no such field, put the code at the very end of the description or in a private seller note, never in the public title, where it looks like noise to buyers and can get truncated.

When a sale notification arrives, you search by SKU rather than by title. Titles differ per platform because you adapted them, and searching for a blue sweater returns a dozen candidates. The SKU returns one. A sync tool pairs listings across platforms the same way, by matching the SKU field, so a listing with a blank or mistyped code is a listing the tool cannot pair. That is the quiet failure mode: the sale goes through on one platform and the unpaired listing elsewhere simply stays live, because nothing knew they were the same item. Related: Selling on Multiple Platforms

Cleaning up a messy history without relisting everything

Most resellers arrive at a SKU system after a period of no system, then a period of descriptive nicknames, then numbers. Do not try to renumber the past. Freeze the old items under whatever they have, start the new scheme from today, and backfill an old item only when you touch it anyway for a photo refresh, a price cut, or a relist. If old codes carried meaning, keep a one-page key so you can still read them. A partial migration that is accurate beats a full migration that stalls halfway through.

Set aside one session to find the dangerous cases. Export active listings from each marketplace, which most platforms allow as a spreadsheet, sort by the SKU column, and look for blanks and repeats. Blanks get filled by locating the physical item and copying the tag. Repeats across two different items are the ones to fix immediately: give the second item a suffix such as -B, update its tag, its record, and its listings, and confirm the pairing in your sync tool. Duplicated codes across different objects are the single most common cause of a delist landing on the wrong listing. Related: Faster Relisting Across Platforms