How to organise a LEGO collection
A useful collection record separates what you own from what you want and from what is already set aside. BrickzBack keeps sets, minifigures, loose parts and wishlist entries in connected but distinct workspaces.
Add confirmed items to the appropriate collection area, record condition and quantity, and keep wanted items on the wishlist. Loose-piece availability remains separate from pieces committed to a build.
Choose the right place for each record
Use owned collection records for sets and minifigures you have confirmed, and track loose pieces with their part, colour, condition and quantity. Put an item you hope to acquire on the wishlist instead of counting it as owned.
Keeping these states separate makes later searches more meaningful. A wanted set is not a set in your collection, and a piece reserved for a project is not available stock.
- Record an item's identity and condition only after checking it.
- Use wishlist records for planned purchases and collection records for confirmed ownership.
- Review loose quantities and their available or committed state before using them.
Use projects and builds without losing ownership context
A selected set or custom project can be checked against loose pieces marked available. This is a focused check against a parts list you choose, not an automatic search of every possible build.
Collection progress, projects, value history and Trader drafts can support different jobs without turning planned, committed and owned quantities into one ambiguous total.
Keep the record maintainable
Add items in manageable groups and correct uncertain identities before relying on them in another workflow. You can also use supported collection imports for applicable files, then review unresolved items instead of assuming every row matched.
Value estimates can help with a high-level view, but they do not replace item condition notes or a sale record. Keep your own values where that is more useful.
Frequently asked questions
What can I keep in a BrickzBack collection?
Sets, minifigures and loose pieces can be recorded separately, alongside wishlist entries, builds, projects, value history and Trader drafts.
Does a wishlist item count as owned?
No. Wishlist entries represent items you want; confirm an item and add it to the collection before treating it as owned.
Are loose pieces always available for a project?
No. A piece must be marked available; quantities committed to other work should not be treated as free stock.
Put the workflow into practice
Use the current BrickzBack workspace to review your own records. Confirm identities and changes before relying on a parts list or value.
Create a BrickzBack account