A LEGO SKU system is a short code you assign to every minifigure or lot so you always know what it is, where it lives, and what you paid, without opening a bag or scrolling through hundreds of photos. In my experience, the sellers who scale past a spare bedroom of bins are the ones who solved this early, not the ones who happened to get lucky on a viral Whatnot show. This guide walks through how to build a SKU format that actually holds up once you have 500, 2,000, or 10,000 figures moving through your inventory.
I started keeping loose notes on sticky pads when I had maybe 40 figures. That fell apart fast. Once you're sourcing from bulk lots, Facebook Marketplace pickups, and BrickLink parts orders in the same week, you need a system that survives chaos, not one that only works when your desk is clean.
Key takeaways:
- A good SKU encodes theme, condition, and a sequential number at minimum, so you can identify an item without unwrapping it.
- Your SKU format should match your storage method, whether that's labeled bins, poly bags, or a mix of both.
- Spreadsheets work fine under a few hundred items; past that, most resellers I know move to a dedicated inventory tool.
- Bulk lots and incomplete sets need their own SKU sub-rules or they'll bottleneck your whole workflow.
What Is a SKU System for LEGO Minifigures?
A SKU (stock keeping unit) for minifigures is a unique alphanumeric code, usually 6 to 12 characters, that identifies one figure or one lot in your inventory, separate from the LEGO element ID printed on the box. It lets you track cost, source, condition, and listing status across every platform you sell on without relying on memory or photos alone.
LEGO already assigns official numbers to sets and elements, but those aren't built for reseller workflows. A set number tells you nothing about which bin a figure is in or what you paid for the bulk lot it came from. Your SKU is a layer on top of the official catalog data, one that reflects how you actually run your business.
Why Do LEGO Resellers Need SKUs Instead of Just Selling by Memory?
You need SKUs because memory and loose piles don't scale past a small side hustle, and every hour spent hunting for a figure is an hour you're not sourcing or listing. Once your inventory crosses a couple hundred pieces, matching a photo to a bin becomes the single biggest time sink in the entire business.
I've seen this play out the same way with almost every seller who reaches out to me. They start strong, selling out of a single tote, and then a good bulk lot buy turns into six totes and a spreadsheet nobody updates. A SKU system fixes the root problem: it gives every item a fixed, searchable identity the moment it enters your inventory, not whenever you get around to labeling it.
It also matters for cross-platform selling. If you're listing the same figure on eBay, Whatnot, and Facebook Marketplace, a consistent SKU is what stops you from double-selling an item or losing track of which platform it's currently listed on.
What Information Should a LEGO Minifigure SKU Actually Encode?
A useful SKU encodes theme or license, condition, and a sequential number, and optionally a source code and a storage location. Keep it to information you'll actually reference weekly, because a SKU with too many fields becomes harder to write consistently than the mess it replaces.
Here's the breakdown I recommend to sellers starting from scratch:
| Field | Purpose | Example |
|---|---|---|
| Theme code | Star Wars, Marvel, Ninjago, CMF, etc. | SW, MRV, NIN, CMF |
| Condition code | Mint, complete, incomplete, damaged | M, C, INC, DMG |
| Sequential number | Unique count within that theme | 0042 |
| Source code (optional) | Where it came from | FBM, EBAY, LOT |
| Location code (optional) | Physical bin or shelf | B3 |
Put together, a figure might read SW-C-0042-FBM-B3: a complete Star Wars minifigure, the 42nd one you've logged in that theme, sourced from Facebook Marketplace, sitting in bin 3. That's enough detail to find it, price it, and relist it fast, without turning every label into a paragraph.
How Do I Build My First SKU Format?
Start with theme and a sequential number only, then add fields as your volume grows past what two fields can handle. Overbuilding your SKU format on day one is one of the more common mistakes I see, because it front-loads complexity before you know which fields you'll actually use.
A practical build order:
- Pick 4 to 8 theme codes that cover most of what you source (you can always add more).
- Decide on a condition shorthand, 3 to 5 states is usually enough.
- Assign sequential numbers per theme, not globally, so you can tell volume by theme at a glance.
- Add source or location codes only once you're managing more than one storage area.
- Write your format down somewhere permanent, not just in your head, so it stays consistent if you ever bring on help.
When I sort a new bulk lot, I assign SKUs the same day I identify the figures, before anything gets mixed back into general storage. Delaying that step is where most inventory systems quietly break down. This matters just as much whether you're selling on eBay, listing on Mercari, or prepping for a live Whatnot show, since a missing SKU slows down every single one of those workflows equally.
Physical Storage: Bins, Bags, and Labels That Match Your SKU
Your physical storage should mirror your SKU logic exactly, so a code on a spreadsheet maps directly to a bin, bag, or drawer without extra translation. If your storage doesn't match your codes, the SKU becomes a second system you have to maintain instead of a shortcut.
Most sellers I know land on one of two approaches: individual poly bags labeled with a printed or handwritten SKU, or theme-sorted bins with a shared location code and per-figure SKUs tracked digitally. Poly bags work better for higher-value figures you're photographing individually. Bins work better for CMF and bulk-lot volume where per-bag labeling isn't worth the time.
Either way, label the outside of the storage container with the SKU range it holds, not just a generic name like "Star Wars bin." That single habit saves real time during a live Whatnot show when you need to grab an item fast.
Digital Tracking: Spreadsheets vs Dedicated Inventory Apps
A spreadsheet is fine for a few hundred items, but most resellers I know outgrow it once they're tracking cost, platform, and status across a few thousand figures at once. The spreadsheet itself isn't the problem, it's that manual data entry doesn't scale with sourcing volume.
In my experience, the tipping point is usually when you start losing track of what's listed where. That's when a dedicated tool that can scan and catalog minifigures in bulk starts paying for itself in time saved, not just organization. If you're still on the spreadsheet stage, that's completely normal, just build your SKU format now so migrating later is a clean import instead of a rebuild. Tools like brick'em's minifigure database can also help you confirm which figure you're actually looking at before you assign a SKU, which matters more than people expect when two similar-looking figures have very different values.
How Do I Handle SKUs for Bulk Lots and Incomplete Sets?
Bulk lots and incomplete sets need a holding SKU the moment they arrive, before you've sorted individual figures out, so nothing gets lost in the gap between purchase and processing. I recommend a simple "LOT" prefix with the purchase date, which lets you trace every figure back to its original source lot later if you need to.
For incomplete sets specifically, don't assign a final SKU until you've decided whether you're parting it out or completing it. If you're completing it, you'll likely be sourcing missing pieces from BrickLink, and it helps to note that status directly in your tracking sheet or app so you don't accidentally sell a piece another set needs.
A lot of sellers I know underestimate incomplete inventory. It's genuinely one of the more overlooked categories in this business, and a clean SKU habit is what makes it profitable instead of a pile of parts you never get back to.
What Are Common SKU Mistakes That Slow Resellers Down?
The most common mistake is adding too many fields too early, which makes the format hard to write consistently and even harder to read at a glance months later. The second most common is skipping labels on storage, which defeats the entire point of having a SKU in the first place.
- Reusing numbers across themes. Keep sequences per theme, not global, or you'll eventually collide.
- Changing the format mid-stream. Pick a structure and stick with it. If you must change it, keep old SKUs valid rather than renumbering everything.
- Not logging source or cost. Even a rough cost field matters when you're calculating margin later.
- Letting bulk lots sit unSKU'd. Unsorted inventory is invisible inventory. It doesn't sell if you can't find it.
I learned most of these the hard way after building a system that worked fine at 100 figures and completely fell apart at 1,000. Building it right the first time is a lot less painful than migrating a few thousand mislabeled items later.
Heads up: This is not financial or legal advice. We're sharing what we've learned from the LEGO reselling community.
Checklist: Setting Up Your LEGO SKU System
- [ ] Choose 4 to 8 theme codes that cover most of your inventory
- [ ] Pick a condition shorthand with 3 to 5 states
- [ ] Decide whether numbering resets per theme or runs globally
- [ ] Add source and location codes only if you manage multiple storage areas
- [ ] Write your format down somewhere permanent, not just in your head
- [ ] Assign SKUs the same day a bulk lot or lot arrives
- [ ] Label physical storage to match your digital SKU ranges exactly
- [ ] Track cost and source alongside each SKU for future margin math
- [ ] Revisit your format once a quarter as volume grows
If you want a head start, you can grab a free copy of our downloadable reseller checklist after you sign up for brick'em, matched to exactly this workflow.
How Does a SKU System Help With Pricing and Valuation?
A SKU system helps with pricing because it lets you track what you paid against what similar items eventually sold for, which is the only reliable way to know your real margin over time. Without that link, you're pricing off gut feeling instead of your own sales history.
I've sold over $100,000 worth of LEGO on eBay, and the pattern I trust most is comparing recent sold listings and BrickLink pricing data against my own cost basis by SKU category, not by guessing at a single item's value in isolation. Tools like brick'em's collection value calculator and investment calculator can help you estimate current worth once your SKUs are organized enough to feed them accurate item lists. If you're evaluating whether a bulk lot is worth buying in the first place, running the numbers through a haul calculator before you commit is a habit that pays for itself.
One more note on sourcing economics worth knowing: larger sellers building out BrickLink stores sometimes acquire entire smaller stores for roughly 30 to 50 percent of market value, according to what I've seen in the community, which is a reminder that organized inventory with clean records is worth more than the same inventory in a shoebox. If you want a second data point beyond your own sales history, BrickEconomy is a solid place to sanity-check general market trends before you finalize pricing.
Frequently Asked Questions
How long should a LEGO minifigure SKU be?
Most working SKUs land between 6 and 12 characters, long enough to encode theme, condition, and a sequential number, but short enough to write on a small label or bag without it becoming illegible or slowing down your sorting process.
Should I use the LEGO element ID instead of my own SKU?
Element IDs are useful for confirming exactly which figure you have, but they don't track your cost, source, condition, or storage location, so most resellers use their own SKU alongside the official ID rather than instead of it.
Can I change my SKU format after I've already started?
You can, but it's smoother to keep old SKUs valid and only apply your new format going forward, rather than renumbering existing inventory. A full renumber is doable, it's just a lot of avoidable work once you're past a few hundred items.
Do I need a SKU for every single loose part, not just minifigures?
Not usually. Most sellers I know reserve individual SKUs for minifigures and sets, then track loose parts in bulk batches or by BrickLink lot, since parts inventory is typically too high-volume to SKU one by one.
What's the fastest way to start if I already have hundreds of unsorted figures?
Pick your theme and condition codes first, then work through your backlog in batches by theme rather than trying to sort everything at once. In my experience, tackling one theme fully before moving to the next keeps the project from stalling out halfway through.
.png)
