A SKU that works at 20 items and breaks at 1,000 almost always fails for the same reason: it was designed to describe the item, not to identify it. A description changes — condition improves after cleaning, a price gets marked down, an item moves shelves. An identifier has to stay fixed for the life of the item, from intake to sale. That single requirement decides most of what follows.
What a SKU should encode
- A short category or intake-batch prefix — enough to make the SKU meaningful to a human at a glance, not a full taxonomy.
- A sequence number, zero-padded to a fixed width (0001, not 1) so numeric sort order matches item order.
- Optionally, a two-digit intake year — useful once inventory spans more than one year, since it keeps sequence numbers from needing five digits early on.
A format that scales without a redesign
Suggested format
[CATEGORY]-[YY]-[SEQUENCE]
Example (illustrative): A vintage furniture flipper acquiring a mid-century dresser in 2026 as their 41st appliance-category intake that year might use APPL-26-0041. The next unrelated item, regardless of category, gets the next sequence number in its own category — not a shared running total.
Example SKUs across categories
| SKU | Item | Category prefix | Notes |
|---|---|---|---|
| APPL-26-0041 | Washer, tested working | Appliances | 41st appliance intake of 2026 |
| FURN-26-0118 | Mid-century dresser | Furniture | 118th furniture intake of 2026 |
| ELEC-26-0007 | Bluetooth speaker, untested | Electronics | 7th electronics intake of 2026 |
Four digits of sequence room (0001–9999) per category per year is generous headroom for almost any single-seller operation; a category running past that threshold usually means the category prefix is too broad and deserves splitting, not a fifth digit bolted on.
SKU vs. storage-location ID — two different jobs
The single most common design mistake is folding a shelf or bin location into the SKU. A SKU identifies the item; a location ID identifies where that item currently sits, and it changes every time the item is moved for cleaning, photography, or a shelf reorganization. Keeping them as two separate fields means moving an item never touches its permanent identifier — see the companion bin-and-shelf article for the location-ID format itself.
Does the SKU change when the item moves or its condition changes?
No. If a SKU has to be reassigned whenever a fact about the item changes, it isn't functioning as an identifier. The SKU is set once at intake and never edited again — everything that legitimately changes (location, condition, price, status) lives in its own field, referencing that same fixed SKU.
Bringing legacy inventory into a new SKU system
- 1
Audit what exists first
Before assigning anything, get a real count of unsold, on-hand items — this is exactly the physical inventory audit covered in the companion article, and doing it first avoids assigning SKUs to items that were actually already sold.
- 2
Assign oldest-first, in batches
Work through existing stock in acquisition order (or by category, if acquisition dates aren't tracked) rather than trying to assign 1,000 SKUs in one sitting. A few categories a day is sustainable; a single all-nighter usually produces mistakes.
- 3
Never renumber sold or archived items retroactively
If an item sold before the new system existed, leave its historical record alone rather than trying to backfill a SKU it never had — the goal is a clean system going forward, not a perfectly retroactive one.
Common failure modes
- Reusing a SKU after the original item sells — always advance the sequence number, even for a near-identical replacement item.
- Inventing prefixes ad hoc at intake time instead of working from a fixed, written prefix list — this is what produces "APP" and "APPL" as two different prefixes for the same category.
- Skipping zero-padding, so SKU-9 sorts after SKU-10 and SKU-89 alphabetically instead of numerically.
- Treating the SKU as a place to store condition or price shorthand — six months later nobody remembers what the code meant, and the item's actual condition has usually changed anyway.
ListNestly's item records don't have a dedicated SKU column today, so most sellers using this format put the SKU at the start of the item name or in the Notes field, where it stays visible on every list view and searchable from Inventory's search box without needing a schema change.