[Feature] Add Sold feature #122

New Issue

2025-12-22T19:41:41+01:00

101br03k commented

2025-12-22 19:41:41 +01:00

Could there be an functionality for sold sets?
There is currently a function to fill in the date, price & location, for the purchase, could this also be an option to log the sold "status"

Could there be an functionality for sold sets? There is currently a function to fill in the date, price & location, for the purchase, could this also be an option to log the sold "status"

FrederikBaerentsen commented

2025-12-22 19:48:00 +01:00

Could you give a usecase for this? If you sold the set, then wouldn’t you delete it from your set collection?

You can technically use custom tags for this, or a status.

In my Project Overview I say that BrickTracker won’t support marketplace/seller features, as it is meant solely for personal collections.

Could you give a usecase for this? If you sold the set, then wouldn’t you delete it from your set collection? You can technically use custom tags for this, or a status. In my [Project Overview](https://bricktracker.baerentsen.space/project-scope/#target-audience) I say that BrickTracker won’t support marketplace/seller features, as it is meant solely for personal collections.

101br03k commented

2025-12-22 19:54:53 +01:00

If you are a collector of sets, would you not like to know which sets you did own at some point? I mean collecting is not only about what you currently have in your inventory but also about what you may have sold or traded but once had?

I get that you could use both tags and statuses (I would like to point out that you can filter on something not having a certain status but that that does not goes for tags but that is another story. ) to keep an inventory.

An alternative I could think of, and that would catch most of these kind of feature request, would be an notes field; where you are free to put what ever you want to "note" about an item.

If you are a collector of sets, would you not like to know which sets you did own at some point? I mean collecting is not only about what you currently have in your inventory but also about what you may have sold or traded but once had? I get that you could use both tags and statuses (I would like to point out that you can filter on something not having a certain status but that that does not goes for tags but that is another story. ) to keep an inventory. An alternative I could think of, and that would catch most of these kind of feature request, would be an notes field; where you are free to put what ever you want to "note" about an item.

FrederikBaerentsen commented

2025-12-25 05:25:40 +01:00

Thank you for the explanation! I understand the desire to track your collecting history. However, I have to respectfully disagree with this approach for BrickTracker.

Here's why:

Sold sets would still appear in parts and minifigures aggregations, showing inventory you no longer own
We'd need "exclude sold" filters across every page (sets, parts, minifigures, statistics, etc.)
Parts from sold sets would mix with your actual collection, making it unclear what you actually have

BrickTracker is designed as an active inventory manager for your current collection, not a historical record. Adding "sold" status would blur this focus and create confusion about what's actually in your collection versus what used to be.

Better alternatives:

Use the (upcoming) export functionality to save a CSV/XML record of the set before removing it from BrickTracker. You can maintain a separate spreadsheet of your collecting history. Export feature can be tested on the docker label pre-1.4.
As mentioned, you could tag sets as "To Sell" while they're still in your possession, then delete them once sold. I'll look into filtering on 'not'-tags.
Keep periodic backups of your database as historical snapshots.

Regarding the notes field: This is actually a good suggestion! A general notes/comments field per set could be useful for many purposes (storage notes, condition notes, special memories, etc.) but would require a new database field. Would you like to open a separate feature request for that? I hope this makes sense. I want to keep BrickTracker focused on what it does well: tracking your current collection accurately.

Thank you for the explanation! I understand the desire to track your collecting history. However, I have to respectfully disagree with this approach for BrickTracker. Here's why: - Sold sets would still appear in parts and minifigures aggregations, showing inventory you no longer own - We'd need "exclude sold" filters across every page (sets, parts, minifigures, statistics, etc.) - Parts from sold sets would mix with your actual collection, making it unclear what you actually have BrickTracker is designed as an active inventory manager for your current collection, not a historical record. Adding "sold" status would blur this focus and create confusion about what's actually in your collection versus what used to be. Better alternatives: - Use the (upcoming) export functionality to save a CSV/XML record of the set before removing it from BrickTracker. You can maintain a separate spreadsheet of your collecting history. Export feature can be tested on the docker label `pre-1.4`. - As mentioned, you could tag sets as "To Sell" while they're still in your possession, then delete them once sold. I'll look into filtering on 'not'-tags. - Keep periodic backups of your database as historical snapshots. Regarding the notes field: This is actually a good suggestion! A general notes/comments field per set could be useful for many purposes (storage notes, condition notes, special memories, etc.) but would require a new database field. Would you like to open a separate feature request for that? I hope this makes sense. I want to keep BrickTracker focused on what it does well: tracking your current collection accurately.

FrederikBaerentsen added the Kind/Feature label 2025-12-25 05:25:49 +01:00

101br03k referenced this issue

2025-12-25 16:20:16 +01:00

[Feature] general notes/comments field #124

101br03k commented

2025-12-25 16:21:43 +01:00

That does make sense.
I created an feature request for the notes field, would you also like a separate feature request for the filtering on 'not'-tags?

That does make sense. I created an feature request for the notes field, would you also like a separate feature request for the filtering on 'not'-tags?

FrederikBaerentsen commented

2025-12-25 18:20:22 +01:00

Yes please, that would be great. I already have an idea for the implementation, so if you could make a separate feature request for that, ill close this one.

FrederikBaerentsen closed this issue

2025-12-25 18:20:22 +01:00

101br03k referenced this issue

2025-12-25 18:55:24 +01:00

[Feature] filter on sets not having a tag #126

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#122