How to Catalog a LEGO Collection Without a Spreadsheet (2026)

A LEGO catalog needs three things a spreadsheet can't hold on its own: a photo tied to every entry, a market value that updates itself, and a way to add items in seconds instead of minutes. Build it that way and it stays alive. Build it as rows you typed in once, and it's dead within a month.

Why does a spreadsheet stop working for a LEGO collection?

It stops working because it demands constant manual upkeep, and nobody keeps up manual upkeep forever. You build a clean sheet on a rainy Saturday: columns for set number, name, theme, piece count, purchase price, current value. Two weeks later you buy three sets at a garage sale and a convention exclusive, and you tell yourself you'll add them later. Later never comes, or it comes six months later when you've forgotten what you paid and have to guess.

The deeper issue is that a spreadsheet is a snapshot, not a system. The value column is only accurate the day you typed it in. Prices move once a set retires and secondary demand kicks in, sometimes by a wide margin, and the sheet has no idea any of that happened. It just sits there quietly wrong until you go to sell something and realize your numbers are a year stale.

• No photos, so you can't tell two similar boxes apart at a glance
• No live pricing, so every value is a guess frozen in time
• Manual entry only, so the sheet reflects what you had patience to type, not what you actually own
• No real separation between sealed, built, and loose-parts inventory without extra columns you'll forget to fill in
• Nothing stopping duplicate rows, typo'd set numbers, or entries that quietly go stale

What should a useful LEGO catalog actually record?

A useful catalog records identity, condition, and current value for every item, not just a name and a guess. Identity means the exact set or piece, down to whether it's sealed, built, or missing a box. Condition means sealed versus built versus parted out, and for minifigs, whether accessories are present. Value means a number that reflects what the item would actually sell for right now, not what a price guide said two years ago.

Skip any of the three and the catalog is only half useful. A list of set names with no condition tells you what you own but not what shape it's in. A list with condition but no live value tells you what you have but not whether it's worth insuring, selling, or holding. The whole point of cataloging is to answer what do I have and what is it worth today, and you need all three fields to get there.

How do you catalog a shelf without typing a single set number?

You scan it. Point a phone camera at a box, a built set, or a pile of loose minifigs, and let image recognition identify the exact item instead of you hunting for a set number in tiny print on the bottom of a box. This is the actual shift that makes cataloging sustainable: typing is the bottleneck, and scanning removes it.

This is where Brickify fits in. It's an AI scanner that identifies sealed sets, built sets, minifigs, and even loose brick piles in under two seconds, with a confidence score so you know when a match is solid versus when you should double check. You can bulk scan an entire shelf or a full bin in one pass and get a running total as you go, which is a different experience than opening a spreadsheet and dreading the data entry.

The practical workflow looks like this: pick one shelf or one bin, scan every sealed box first, then scan built sets, then dump loose minifigs on a table and scan those in batches. You're not trying to catalog the whole collection in one sitting. You're trying to make each session short enough that you'll actually do a second one next weekend.

Should sealed sets and built sets be tracked differently?

Yes, because they behave differently as the collection ages and as you think about resale. A sealed set is a single unit with one condition state and one value. A built set is really a bundle: the model itself, plus whatever minifigs came in the box, and those minifigs often hold value independent of the set they arrived in. If your catalog treats a built set as one flat row, you lose visibility into the fact that a few of the minifigs inside it might be worth more loose than the rest of the set combined.

This matters most for anyone who buys sets primarily for the minifigs, which is a huge share of the hobby. A catalog that only tracks a set as one line, built, one value, hides the real breakdown. One that tracks the set and its individual figures separately tells you whether you're sitting on a built display piece or a small stack of individually valuable characters you could part out.

How often does a LEGO catalog actually need to be updated?

The catalog itself only needs updating when your inventory changes, but the values inside it should update far more often than that, ideally on their own. This is the split people miss: adding a new set is an event, but a set's worth is not a fixed fact, it drifts with the secondary market every week. A catalog that only refreshes values when you remember to look something up is always behind.

A live portfolio view solves this by pulling from real recent sales instead of a static guide, so the value on screen today reflects what similar items actually sold for recently, not a number pulled from memory or an old listing. Brickify's portfolio dashboard does this automatically, tracking value over time across a day, a week, a month, or a year, and breaking out trends by theme or set so you can see which parts of your collection are actually climbing and which are flat.

What's the fastest way to catalog minifigs specifically?

The fastest way is to separate them from their sets and scan them as a batch, not one at a time from memory. Minifigs are the part of a LEGO collection that spreadsheets handle worst, because there's no printed number on most of them the way there is on a set box. People either skip cataloging minifigs entirely or spend hours cross referencing torso prints against reference photos online.

Dump a bin of loose minifigs on a table, spread them out so they're not overlapping, and bulk scan the group. This is exactly the scenario where collectors discover their pile is worth more than they thought. One App Store reviewer, Cape4me, put it this way: "I had a 54lb tote of Legos sitting in my attic forever and I was going to sell it by the pound... Thank God I didn't. Brickify helped me identify and re-assemble hundreds of mini-figures... Turns out my childhood collection is worth over $2000!" That's the gap a real catalog closes, the difference between guessing a pile is worth scrap value and knowing what's actually in it.

What does a working catalog actually look like day to day?

A working catalog is something you check the way you'd check a bank balance, not something you dread opening. Every item has a photo so you recognize it instantly. Every value reflects recent sales, not a guess from last year. New items take seconds to add because you scanned them instead of typing them. And the whole thing syncs across your phone and any other device you check it from, so there's no risk of losing the file or working off two versions that disagree with each other.

The test is simple: if adding a new set feels like a chore, the system will fail eventually, no matter how well designed the columns are. If adding a new set takes a few seconds because you just scanned it, you'll actually keep doing it, and a catalog you keep doing is the only kind that stays accurate.

Is it worth cataloging a small collection, or only a big one?

It's worth it at any size, because the value of a catalog isn't proportional to how many sets you own, it's proportional to how much you'd lose by not knowing what you have. A collection of twenty sets that you can't accurately value is just as exposed, relative to its size, as a collection of two hundred. Insurance claims, moving house, selling off part of a collection, all of these go smoother when you have an accurate, current record rather than a memory and a guess.

Start with whatever shelf is closest to you right now. Scan it, watch the running total build, and decide from there whether you want to keep going. That's a lower bar than opening a blank spreadsheet and trying to remember every set number you've bought since you got back into the hobby, and it's the reason a scan first catalog tends to actually get finished.