eBay SKU / Custom Label Naming for Dropshippers (Unique Codes)

Why dropshippers need a SKU / custom label system

On eBay, the Custom label (SKU) field is your private inventory string—not the buyer-facing title. eBay’s own listing/template Help describes it as a seller identifier; buyers do not see it on the public listing page. For AliExpress, Amazon or Walmart dropshippers, that field (plus matching notes in your order sheet) is how you map a sold eBay child back to the exact supplier option before you click Buy.

Without a naming system you get:

• Duplicate or blank labels that break Seller Hub search and bulk revise
• Wrong colour × size ordered upstream after a multi-variation sale
• Cost or margin codes pasted into public fields (title, description, item specifics) where shoppers—and competitors—can read them
• Tool-generated drafts that look “complete” until fulfilment fails

This guide gives a practical, Trust-safe SKU pattern for dropshippers: unique codes, supplier identifiers, size/colour encoding, and no private cost in public fields. Pair it with variations / MSKUs, the draft vs publish checklist and the title formula. Hero rule throughout: draft ≠ publish.

This is operational listing hygiene, not legal, tax or accounting advice. Confirm Custom label behaviour and any character limits in your site’s Seller Hub / Help on the day you list—UI labels and limits change.

Custom label (SKU) vs title vs item specifics

Keep each field’s job separate:

Practical caution: even when the listing page hides Custom label, do not paste the same string into the description, buyer messages, packing inserts you share, or screenshots you post publicly. Private inventory data stays in seller tools and your own sheet.

Design goals for a dropshipping SKU

A good dropshipping custom label is:

1. Unique across your catalogue (and unique per variation child)
2. Stable — same code from draft → active → sold → reorder
3. Decodable by you in seconds under order pressure
4. Safe — no raw cost, margin %, or personal supplier login clues in any buyer-visible field
5. Compatible with your Chrome lister / spreadsheet / packing process

It does not need to look clever in search. Search lives in the title and specifics—not in the SKU.

A practical naming pattern (segments)

Use short, fixed segments separated by hyphens (or another single delimiter you never use inside a segment). Hypothetical pattern for training only:

[Source]-[SupplierRef]-[Product]-[Colour]-[Size]-[Seq]

Worked hypothetical (not a live offer):

• Parent / shared note: AE-100500-HOOD
• Children: AE-100500-HOOD-BLK-M, AE-100500-HOOD-BLK-L, AE-100500-HOOD-NVY-M

Buyer-facing colour names stay “Black” / “Navy”. The codes live in Custom label and your fulfilment sheet—not in the colour aspect buyers click.

Character space is finite. Prefer short tokens over essays. If Seller Hub rejects a string, shorten supplier refs first—confirm the live limit in Help / the form; do not treat a forum number as gospel.

Unique SKUs: singles and multi-variation (MSKU)

Single-SKU listings

One active listing → one unique Custom label. Reusing the same label on unrelated products makes Seller Hub filters and “find listing” useless when an order lands.

Multi-variation / MSKU

On a colour × size grid:

• Give each offered child its own Custom label
• Keep parent and child labels different if you set both (eBay inventory templates note parent and child SKUs must differ)
• Omit or leave unoffered any combination you will not fulfil—do not invent a SKU for a child you cannot buy

Full grid workflow: how to build eBay variations / MSKUs from AliExpress colour × size grids. Wrong-child orders are usually a matrix problem first and a SKU problem second—fix the matrix, then label the children.

Lots and multi-quantity

If you sell a pack or lot, encode pack shape in the mnemonic (AE-…-STRAP-3PK) and mirror pack count in the title/specifics. Do not use SKU alone to explain unit of sale—buyers never rely on it. See lots vs quantity.

Encoding supplier codes without leaking secrets

What to encode

• Marketplace source (AE / AMZ / WMT)
• Supplier product identifier (AliExpress item ID, Amazon ASIN, Walmart item ID—as applicable)
• Option / SKU fragment the supplier uses for colour or size, if you need it to re-select the child

What to keep only in your private sheet

• Full supplier URL with tracking parameters
• Supplier store admin notes, chat IDs, login hints
• Your landed cost, fee estimate, ad rate, target margin
• Personal address / warehouse notes that do not belong on a shared screen

Truncation rule

If the supplier ID is long, truncate consistently (e.g. leading block) and store the full ID + option IDs in a private spreadsheet keyed by the same Custom label. Consistency beats clever compression.

Brand / VeRO note

Do not put protected brand tokens into Custom labels as a habit if those labels get pasted into shared docs or buyer-facing channels. Brand discipline for titles and images still comes first: VeRO for dropshippers · VeRO brand-list workflow.

Size and colour encoding that stays 1:1 with the grid

Build a small legend once and reuse it:

Rules:

1. One token ↔ one variation value — never reuse NVY for two different navy shades on the same parent
2. Prefer readable abbreviations over numeric colour indexes (C3) unless your sheet maps C3 explicitly
3. Asian vs UK/US sizing: keep the supplier’s true size in the SKU if you show a size chart; do not silently remap “Asian M” to “US M” in the code while promising US M to buyers (variations guide)
4. Put technical option IDs in the Custom label / sheet—not as the only Colour name shoppers see

Do not leak private cost in public fields

Competitors and curious buyers read titles, descriptions and specifics. Common leaks:

Recommended policy: Custom labels may carry source + product + colour + size. They should not carry currency amounts, percentage margins or “break-even at X” codes. Your margin model belongs in a private workbook you update when fees or inbound postage change—not in any field that can be copied into a public listing by mistake.

When a Chrome tool pre-fills drafts, scan title, specifics and description for accidental cost strings before List (draft checklist).

Hypothetical map (labelled)

Hypothetical example — not a live supplier offer:

On eBay: Colour = Black, Navy; Size = M, L; offer only the three in-stock, brand-safe children. Cost columns never leave the sheet.

Draft review: SKU gate before publish

Whether you fill the form by hand or with a non-API / session-based Chrome extension, treat Custom label as a checklist item, not autofill theatre.

Before List / Publish:

• Every offered single or variation child has a unique Custom label
• Parent label ≠ child labels when both are set
• Colour/size tokens match the variation values 1:1
• Supplier ref is enough (with your sheet) to reorder the correct child
• Title follows the brand-safe formula—no cost codes
• Description and item specifics contain no COGS / margin / supplier admin strings
• Fee worksheet still clears your floor (fees · profit pricing)
• Full pre-List pass: draft vs publish checklist

draft ≠ publish. A filled SKU field does not make a branded or dishonest listing safe.

Non-API Chrome path (optional)

A non-API / browser-session lister fills the eBay form from your open Chrome session—no API keys, no OAuth for that flow—then you review the editable draft. Connection method ≠ policy immunity. Tool context: best AliExpress → eBay Chrome extensions.

Extension path (example — DS Lister Pro):

1. Install or open the Chrome Web Store listing
2. Sign in to the tool and eBay in the same Chrome profile
3. Open one carefully chosen supplier product (prefer unbranded / clear options)
4. Start list-on-eBay; let the extension capture images, variations and fee-aware estimates
5. In the editable eBay draft, set or correct Custom labels per child; strip any cost strings from public fields
6. Publish only when labels, matrix, title and price all match what you can fulfil

Bulk habit: after a multi-tab draft session, sort drafts by Custom label in Seller Hub (customise columns) and fix collisions before you schedule or List (schedule listings).

After publish: revise labels with the matrix

When stock or options move:

• Revise or end the affected variant; do not leave a sold-out child clickable “hoping it restocks”
• Keep the Custom label stable when you only change price or quantity—change the code only when the supplier identity truly changes
• On reorder, search Seller Hub / orders by Custom label, then open the matching sheet row for the full supplier URL and option IDs
• If you migrate the same grid from AliExpress to Amazon or Walmart, update the Source segment and supplier ref; do not recycle an old code for a different upstream child

Common SKU mistakes

• Blank Custom labels on every draft “to save time”
• One shared label across an entire colour × size grid
• Using supplier colour codes as the only buyer-facing Colour name
• Putting landed cost or margin % in the title, specifics or description
• Encoding sell price and cost so anyone can reverse the margin
• Inventing sizes in the SKU that AliExpress does not offer
• Changing SKUs every revise so order history no longer matches the sheet
• Treating tool auto-fill as reviewed—always open the draft
• Skipping VeRO / brand checks because the SKU “looks organised”

How DS Lister Pro helps (short)

DS Lister Pro (Alpine Adverts LLC) scrapes AliExpress (also Amazon; Walmart on About + CWS), builds fee-aware editable eBay drafts—including variation / MSKU grids—from the open browser session without API keys or OAuth, and flags brand/VeRO-style risk. You still assign or correct Custom labels, keep cost data out of public fields, and remain the publisher of record.

• Soft path: install · Chrome Web Store · select plan (paid trial, not free—confirm live terms)

Also comparing draft-focused tools: AutoDS alternative · SaleFreaks alternative · Dropeex alternative · KalDrop alternative · SuperDS alternative · Ecomli alternative · DSM Tool alternative

DS Lister Pro is not affiliated with eBay Inc., AliExpress, Amazon or Walmart.

FAQ

Do buyers see the Custom label (SKU) on the listing?

eBay’s listing/template Help states the Custom label is your unique identifier and that the buyer does not see this information on the item. Still keep cost and margin out of titles, descriptions and specifics—and out of any channel you share with buyers.

Should every variation child have its own SKU?

Yes, if you offer that child. Unique per-child labels make wrong-option fulfilment far less likely when colour × size grids get busy. See the MSKU guide.

Can I put my cost in the Custom label if buyers cannot see it?

Better not. Raw cost/margin codes leak through screenshots, team spreadsheets, packing workflows and accidental paste into public fields. Keep economics in a private worksheet; keep the SKU to source + product + colour + size.

Does a “smart” SKU improve Best Match or sales?

This guide does not invent ranking, CTR or conversion claims. Custom labels are fulfilment hygiene. Search and clarity live in title, specifics, photos and honest logistics (Best Match overview for process context only).

Does DS Lister Pro offer a free trial?

No. DS Lister Pro uses a paid trial model—not a free trial. Confirm live terms on select plan.

Soft CTA

If you want supplier pages turned into reviewable eBay drafts—where you can set unique Custom labels, fix colour × size rows and strip cost strings before publish—try one carefully chosen product end-to-end:

1. Install or open the Chrome Web Store listing
2. Same Chrome profile for the tool and eBay
3. Capture → assign unique SKUs → check public fields for cost leaks → verify the matrix → publish once
4. Continuing? Plans (paid trial, not free): select plan

Next step

Pick one unbranded AliExpress (or Amazon / Walmart) product with a small colour × size set. Build the segment legend, assign unique Custom labels per child, keep COGS only in your sheet, rewrite the title with the title formula, and run the draft checklist before List. Keep variations / MSKU, AliExpress how-to, fees, profit pricing, VeRO and non-API explainer open while you build the habit. Soft path when you want session-based draft fill: DS Lister Pro install.