A useful eBay SKU should help you identify and retrieve inventory without becoming a second product description. The format needs to work on a label, in Seller Hub, in reports, and during a rushed order pull.
This guide provides practical templates. Choose the smallest format that solves your operation’s real identification problem.
Start with the jobs the SKU must perform
Write down what you expect the code to do. Common jobs include:
- Point to the storage location
- Distinguish similar one-of-one items
- Connect a physical tag to a listing
- Preserve an internal catalog or supplier code
- Work across multiple marketplaces
Do not encode information simply because it might be useful someday. Every segment needs a current operational purpose.
Use a stable structure
A basic one-of-one reseller format is:
{LOCATION}-{SEQUENCE}
Examples:
A12-0047R03-0182C14-0082
The location gets you to the right storage area. The sequence confirms the exact item.
Use fixed-width numbers when possible. 0047 sorts more predictably than a mixture of 47, 105, and 9, and a missing digit is easier to notice.
SKU templates by inventory type
One-of-one used goods
Use location plus a permanent sequence:
B07-0314
This works for most thrifted clothing, estate-sale goods, and unique hard goods. Do not reuse the sequence after an item sells; historical orders and reports should continue pointing to the same product.
Clothing
Use a clothing-zone location plus sequence:
C14-0082
Store size, brand, and measurements in structured listing fields and descriptions instead of overloading the SKU. A code such as RL-M-RED-SHIRT-GOOD-2026-08 is difficult to maintain and still does not tell you which similar shirt to pull.
Collectibles
If storage is organized by drawer, box, or binder:
D04-0217
For graded items or products with a durable certification number, you may use that number as the unique item reference, but avoid exposing sensitive acquisition notes in the SKU.
Multi-quantity products
Use a stable product code rather than a unique unit sequence:
CAB-USBC-2M-BLK
All identical sellable units can share one inventory item and quantity count. Variations such as color or size need distinct identifiers when they represent distinct inventory records.
Supplier or manufacturer SKUs
Preserve an established supplier SKU when it is truly unique and useful:
ACME-4821-BLK-M
If your physical storage location is not encoded, keep location in a separate inventory field or storage map. Do not append a frequently changing bin value to a manufacturer code unless your system is designed to update it safely.
Keep it under 50 characters
eBay documents a maximum SKU or custom-label length of 50 characters. The Inventory API uses that SKU as the seller-defined key for the inventory item. See eBay’s InventoryItem documentation.
Treat 50 as a ceiling, not a target. Short codes are easier to:
- Print on small labels
- Type without errors
- Read in narrow Seller Hub columns
- Include in packing workflows
- Compare across systems
Most one-of-one reseller SKUs can stay under 15 characters.
Avoid these common SKU mistakes
Encoding the current price
A12-2499 looks useful until the price changes to $19.99. Keep price in the listing and accounting records.
Encoding listing status
Prefixes such as ACTIVE- or DRAFT- become stale. Status belongs in a live system, not a permanent identifier.
Using a long product description
RALPH-LAUREN-PINK-MENS-XL-SHIRT repeats information already stored in the title and item specifics while failing to distinguish two similar shirts.
Reusing a unique item sequence
Historical orders, returns, and reports may refer to the old SKU. Generate a new sequence for a new physical item.
Depending on memory
A code such as JACKET-BOB may make sense today but not to a helper—or to you six months later. Use documented segments with fixed meanings.
Mixing several formats
Inconsistency creates more friction than an imperfect format. Do not alternate among A-12-47, A12_0048, and BIN12ITEM49. Choose separators and widths once.
Make the format easy to type and read
Prefer:
- Uppercase letters
- One separator, usually a hyphen
- Fixed-width location and sequence segments
- Characters that are visually distinct
Avoid ambiguous pairs when you control the codes: O and 0, I and 1, or S and 5. If labels are scanned, test the exact printer, material, and scanner before converting the entire inventory.
Decide whether the bin code must be unique
The physical bin does not need to be unique per item. Several products can share location A12. The inventory item does need a unique key in eBay’s Inventory API.
You have two options:
- Make the entered SKU unique yourself:
A12-0047. - Reuse
A12as a Custom label in software that creates a separate unique eBay key.
PileZero supports both. When the same Custom label is reused, PileZero appends a stable suffix to the remote eBay SKU while keeping the familiar label visible in the workspace.
Write a one-line SKU policy
Document the format so another person can apply it without asking you:
Our SKU is the uppercase storage location, a hyphen, and the next unused four-digit item number:
A12-0047.
Or, for a reusable-bin workflow:
Our Custom label is the physical bin code. PileZero creates the unique eBay SKU when the label is already in use.
Include who assigns the sequence, where the next number is stored, and what happens when an item moves.
Test before relabeling your whole store
Run 20 items through the complete cycle:
- Create the SKU.
- Label the physical item.
- Publish it.
- Find it from the seller record.
- Simulate a sold-order pull.
- Move one item and document the update.
The test will reveal whether the code is too long, labels are hard to read, or location changes are awkward. Fix the rule before applying it to hundreds of active listings.
The right SKU format is not the one with the most information. It is the one that reliably connects a listing to the correct physical item.