Tracking Owned and Missing Parts
Build projects help you understand what your build needs and what is still missing.
The goal is simple: know what you can build now and what you still need to find.
Required parts
Required parts are the parts the project needs.
Example: if a build needs four red 2x4 bricks, the required quantity is 4.
Owned parts
Owned parts are the parts BrickZap counts as already covered for the project.
Owned quantities may come from your saved inventory or from manual project adjustments.
Missing parts
Missing parts are what remains after owned parts are counted.
If the project requires 4 and you own 1, the missing quantity is 3.
Manual owned overrides
Sometimes you know more than your saved inventory does.
Use manual owned adjustments when you have parts set aside, recently found parts, or pieces that are not yet reflected in your main inventory.
Exact part and color matching
BrickZap matches parts by exact part and color when color matters.
A red brick does not cover a blue brick unless the project specifically allows that part and color.
Progress percentage
Progress is calculated from owned parts divided by required parts.
Example: 75 owned parts out of 100 required parts gives 75% progress.
Owned quantity per item is capped at the required quantity — having more of a part than the build needs does not inflate progress above 100%.
Lot coverage
Alongside the quantity-based progress percentage, BrickZap also tracks lot coverage — where a lot is one unique part and color combination.
- Required lots: how many unique part/color combinations the build needs
- Covered lots: unique combinations where you own at least the required quantity
- Missing lots: unique combinations still short at least one piece
Lot coverage is useful when you want to know how many distinct parts you still need to find, regardless of how many of each piece is required.
Why inventory changes do not rewrite requirements
Your project requirements represent the build plan.
Changing your main inventory may change what is counted as owned or missing, but it should not change what the project originally requires.
Recalculate summaries
Use recalculation when progress, owned counts, or missing counts look out of date.
This refreshes the project summary from the latest available project and inventory information.
Future substitutions
Substitutions may be supported later.
For now, expect BrickZap to use exact matching unless the project or catalog data supports another behavior.