Question: spares #128

New Issue

2025-12-26T11:54:33+01:00

dilbert commented

2025-12-26 11:54:33 +01:00

Just a quick question - how do spares work within the application? A lot of sets have a handful of spares and I'm not too sure how they can be represented? I think I am missing something obvious.

Cheers! 🍻

Just a quick question - how do spares work within the application? A lot of sets have a handful of spares and I'm not too sure how they can be represented? I think I am missing something obvious. Cheers! 🍻

FrederikBaerentsen commented

2025-12-26 18:34:00 +01:00

Great question! Spare parts in BrickTracker work as follows:

Spare parts are imported from Rebrickable along with regular parts when you add a set
They appear in parts lists with a yellow "Spare" badge (with a loop icon) next to the part name
They're tracked separately in the database (the spare field distinguishes them from regular parts)
The same physical part can appear twice in your set's inventory: once as a regular part and once as a spare

Configuration options: You have two environment variables to control spare parts behavior:

BK_SKIP_SPARE_PARTS (default: false)
- Set to true to skip importing spare parts entirely when downloading sets from Rebrickable
- Use this if you don't want spares in your database at all
BK_HIDE_SPARE_PARTS (default: false)
- Set to true to hide spare parts from parts lists (they stay in the database but don't display)
- Use this if you want spares tracked but not cluttering your views

These can be configured via your .env file or through the Admin > Live Settings panel. Tracking spares:

Spares are fully tracked like regular parts. You can mark them as checked, missing, or damaged
They're counted separately in your inventory (e.g., if you have 2x regular + 1x spare of the same part, they're distinct entries)

It is currently not possible to manually add spares or loose parts, see #68 for that feature request.

Hope this helps!

Great question! Spare parts in BrickTracker work as follows: - Spare parts are imported from Rebrickable along with regular parts when you add a set - They appear in parts lists with a yellow "Spare" badge (with a loop icon) next to the part name - They're tracked separately in the database (the spare field distinguishes them from regular parts) - The same physical part can appear twice in your set's inventory: once as a regular part and once as a spare [Configuration options](https://bricktracker.baerentsen.space/configuration/core.html#spare-parts): You have two environment variables to control spare parts behavior: - `BK_SKIP_SPARE_PARTS` (default: false) - Set to true to skip importing spare parts entirely when downloading sets from Rebrickable - Use this if you don't want spares in your database at all - `BK_HIDE_SPARE_PARTS` (default: false) - Set to true to hide spare parts from parts lists (they stay in the database but don't display) - Use this if you want spares tracked but not cluttering your views These can be configured via your `.env` file or through the Admin > Live Settings panel. Tracking spares: - Spares are fully tracked like regular parts. You can mark them as checked, missing, or damaged - They're counted separately in your inventory (e.g., if you have 2x regular + 1x spare of the same part, they're distinct entries) It is currently not possible to manually add spares or loose parts, see #68 for that feature request. Hope this helps!

dilbert commented

2025-12-27 11:27:39 +01:00

Perfect, thank you Fred! It was only that we added a set that didn't have spares listed that I wasn't sure. Just added Concorde which my son got for Christmas and there are spares showing.

Thank you 😁

Perfect, thank you Fred! It was only that we added a set that didn't have spares listed that I wasn't sure. Just added Concorde which my son got for Christmas and there are spares showing. Thank you 😁

dilbert closed this issue

2025-12-27 11:27:41 +01:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#128