One Yoda, Three Catalog Numbers: Why This Collection Has Its Own Numbering System

Every serious collection needs a way to name its pieces. Ours had to be built from scratch — because the rest of the hobby can’t agree on what to call them.

A look under the hood at how this collection assigns catalog numbers, why we don’t just borrow them from the big databases, and how one little Yoda made the case for doing it ourselves.

Every item in this collection has a number. It’s how we identify a piece across the whole catalog — how an article links to the right record, how a photo gets filed, how we tell two near-identical boxes apart. For a collection built around promotional and event exclusives, that number does a lot of quiet work — and getting it right turned out to be harder than it sounds.

The Trouble With Borrowing

The obvious move is to use a number that already exists. LEGO prints one on most boxes, and the big catalog sites — BrickLink, Brickset, BrickEconomy — assign their own to nearly everything. For an ordinary retail set, any of those works fine; they all agree, and the number on the box is the number everyone uses.

For the things this collection actually documents — the giveaways, the raffle prizes, the convention exclusives — that consensus falls apart. These items often never got an official LEGO number at all, and the catalog sites each handle them differently. They disagree on what to call an item, on how to categorize it, and sometimes on basic facts like which event it came from. Pick any one site as your master source and you inherit its mistakes along with its numbers.

One Yoda, Three Numbers

Here’s the example that settled the debate. In 2013, LEGO handed out a small Yoda diorama — a brick-built New York City street-corner scene in a clear display case — to the press at the New York Toy Fair, celebrating the launch of The Yoda Chronicles. Roughly 150 were made. A genuinely rare little thing. Now watch what happens when you try to look it up.

Brickset lists it, but files it under a New York Comic-Con code and tags it as a Comic-Con item — even though it was a Toy Fair giveaway from February, months before that year’s Comic-Con. The event is simply wrong. BrickLink doesn’t catalog it as a set at all; it lives in their “Gear” section under one code, while the 1999 promotional Yoda statue sits in the same section under a nearly identical one. BrickEconomy, meanwhile, uses yet another code — but for a different Yoda entirely, the white-haired version given away at a Times Square event that same year, which is a separate figure with its own hair color and its own backstory.

So: three databases, three different numbers, three different ways of categorizing the same little statue — and one of them has the event flat-out wrong. If we’d crowned any single source as our authority, we’d have copied its error straight into our catalog.

Our One Rule

If LEGO printed a number on it, we use that — no questions. If they didn’t, we assign our own, and we make it obvious the number is ours.

That’s the whole philosophy. The catalog sites don’t disappear — they become cross-references, not the source of truth. Every record points back to whatever BrickLink, Brickset, and BrickEconomy call the item, so you can still follow the trail. But the number we hang our own documentation on is one we control, and one we can keep accurate even when the rest of the hobby doesn’t.

The Four Kinds of Numbers

In practice, every item falls into one of four buckets:

1. Official LEGO numbers. If the box carries one, that’s the number, full stop. The Darth Vader Bust is 75227; the Celebration BrickHeadz are 40547. We don’t reinvent what LEGO already named.
2. Recurring events. Items from the conventions we document year after year get an event code plus the year — SDCC2013, NYTF2013, CELEB2007. Read the code and you know the show and the year at a glance.
3. Make & Take builds. The build-it-at-the-booth models are their own species — not boxed sets, not quite giveaways — so they get their own prefix, a venue, and a year: MNTCELEB2015.
4. Everything else. One-off promos, store giveaways, contest prizes, the genuine oddities — these get a plain in-house code, BMS for BringMeSolo, and the year: BMS2013. The BMS tag is deliberate. It announces, right in the number, “this one is ours — don’t go looking for it on BrickLink.”

Anatomy of a Code

The four kinds above describe the front of the code — its base. Riding behind that base are two small pieces that do the unglamorous work of telling near-identical records apart.

The first is the sequence number — a -N that follows the base. On an official LEGO number it’s almost always -1 and stays there: LEGO already made that number unique, so there’s nothing to pull apart. In full, the Darth Vader Bust isn’t just 75227 — it’s 75227-1, with the -1 usually going unspoken. (When an official set shows up in more than one box, that’s the variant letter’s job below, not the sequence’s.) Where the sequence actually earns its keep is on the codes we assign ourselves, because an event prefix plus a year isn’t unique on its own — a single show can put out a whole row of exclusives in one year. The 2009 San Diego Comic Con exclusives are the clearest case: six Collectable Display Sets that share one SDCC2009 base and are told apart only by the sequence — SDCC2009-1 through SDCC2009-6 — with that year’s other two booth exclusives carrying on at -7 and -8. The in-house BMS codes work the same way: BMS2013-1, BMS2013-2, and so on.

The second is the box variant — a trailing letter, a, b, c, tacked on after the sequence. It marks the same item turning up in genuinely different packaging: a new box format, a reissue with redesigned art, a release distinct enough that a collector handling both would see two different objects. So 75188-1a and 75188-1b are one set in two boxes. Only a meaningful box difference earns a letter — a trivial reprint doesn’t. The full shape, then, reads base, sequence, variant: 75188-1a.

The year baked into the event and in-house codes is our best estimate, not a sworn affidavit. When we can’t pin a date precisely, we make the most informed call we can and revise it if better information turns up later — and when we do change a code, the old one doesn’t vanish, which brings us to the next part.

Keeping the Receipts

The catch with running your own system is the risk of cutting yourself off from everyone else’s. So we don’t. Every record carries cross-reference fields for the database codes, and a legacy field for anything the item used to be called in our own catalog before we corrected it. Nothing gets thrown away.

That means our Yoda diorama can be filed under our own accurate code and still point you to Brickset’s number, BrickLink’s gear code, and the label we gave it before we caught the mistake. Old links keep resolving, nothing gets orphaned, and — this is the part we care about most — the contradictions stay visible on the record instead of getting quietly smoothed over. If a database is wrong, we’d rather show our work than hide it.

Why Bother

It would be less work to pick a database and copy it. But the entire reason this collection exists is to document things the databases get wrong or skip entirely — and a numbering system that just mirrored those databases would mirror their errors right along with them. Building our own is more effort, and yes, it means our numbers are ours alone. That’s the trade we made on purpose. It keeps the catalog honest, and honest is the whole point.

---

This is a living system, refined as the collection grows and as we run into the next item the databases can’t agree on. When an official LEGO number exists, we use it; when one doesn’t, we assign our own and keep every other name the item has ever gone by.