SKU Naming for Amazon, eBay and WooCommerce

A useful SKU naming convention gives each sellable product variation one stable internal identity. For a small team selling through Amazon, eBay and WooCommerce, the priority is a reliable connection between the product on the shelf, its channel listings and its stock record.

Start with a short, documented format, a master register and a controlled way to create new codes. Making codes longer will not repair an incorrect listing-to-stock connection.

Design the SKU around the sellable unit

Decide what a customer can actually buy. A blue pouch in two sizes needs two identities. A single pouch and a pack of three also need separate identities, even when the packaging looks similar.

Keep the internal SKU separate from other identifiers. An Amazon ASIN identifies a catalogue entry; a GTIN identifies a trade item; your SKU supports your own catalogue and stock operations. Record the connections rather than expecting one identifier to do every job.

For a manageable catalogue, a proposed format is product family, model, colour and size or pack. Use one separator consistently and document permitted abbreviations. Check compatibility with every connected system before adopting a format.

A SKU naming example

Illustrative example: a shop sells model 210 storage pouches in different sizes and packs.

• PCH-210-BLU-S: one small blue pouch.
• PCH-210-BLU-L: one large blue pouch.
• PCH-210-BLU-S-P3: a pack containing three small blue pouches.

The pack code identifies the offer. A separate component record should explain that selling one pack consumes three single units if the pack is assembled from shared stock. A prepacked product held separately needs its own stock treatment.

Avoid putting the current selling price, supplier name or shelf location into the permanent code. These can change without the physical product changing. Keep them in separate fields. Never recycle an old SKU for a different item: historic orders and returns still need to resolve correctly.

Map Amazon, eBay and WooCommerce explicitly

Create a master register containing the internal SKU, product description, variation attributes, pack quantity, barcode where applicable, and each channel's listing identifier and seller SKU or custom label.

Existing channel codes do not have to be renamed immediately. A verified mapping can connect an older code to the correct master item. Confirm what the integration actually uses as its matching key before changing a live field.

WooCommerce's variable product guidance explains variation-level SKU and stock settings, including inheritance when a variation SKU is left blank. Check the saved variation values deliberately; do not assume the parent product represents every independently stocked size and colour.

For the wider stock-sharing process, use the multichannel overselling guide. Naming and stock synchronisation need separate checks.

Introduce changes in a controlled batch

• Export the existing catalogue and identify duplicate or blank codes.
• Agree one owner for creating new SKUs and approving exceptions.
• Test a small group of simple products, variations and packs.
• Follow a test item through listing, picking, dispatch and a return lookup.
• Check integration logs and stock updates before expanding the change.
• Retain the old-to-new mapping with the change date and reason.

Ask a second person to match a physical sample to the register without relying on product photographs alone. Similar-looking variants are a useful test of whether the naming and shelf information are clear.

Keep naming and physical accuracy connected

Review new codes before creating listings, and investigate mismatches at their source. If the code is correct but the wrong product is in its bin, renaming it will not fix the problem. The inventory discrepancy workflow covers that physical investigation.

For a specialised example of structured eBay variation inputs, see the eBay Price Wizard case study. Its worked example complements a master SKU register; it does not replace catalogue ownership or integration checks.