[feature request] better handling of sets that contain other sets / complete CMF series. #157

Open
opened 2026-05-01 19:45:45 +02:00 by commenter · 0 comments

There are many lego sets that are just bundles of other sets. Some are actual bundles, which put multiple sets in a single retail package, and some are collections that are multiple sets sold separately (CMF series.) Rebrickable does track which sets constitute the collection, if that helps.

An example of a real retail bundle would be 66808-1 https://rebrickable.com/sets/66808-1/lego-star-wars-epic-battle-set/?inventory=1#comments, which contains 75431-1, 75435-1, and 30708-1.

A CMF complete series would be 71050-13 https://rebrickable.com/sets/71050-13/spider-man-across-the-spider-verse-complete-all-sets/?inventory=1#parts, which is not a 'real' set sold by lego, but logically, it contains sets 71050-01 through 71050-12.

It'd be nice to be able to add the parent set and have bricktracker pull down the constituent set details to add to the inventory, and (optimally) allow the sub-sets to be grouped under the parent set, sort of how duplicate sets can be grouped?

This might be a pretty big change on the DB backend, so don't worry too much if it's too much of a pain to add.

There are many lego sets that are just bundles of other sets. Some are actual bundles, which put multiple sets in a single retail package, and some are collections that are multiple sets sold separately (CMF series.) Rebrickable *does* track which sets constitute the collection, if that helps. An example of a real retail bundle would be 66808-1 https://rebrickable.com/sets/66808-1/lego-star-wars-epic-battle-set/?inventory=1#comments, which contains 75431-1, 75435-1, and 30708-1. A CMF complete series would be 71050-13 https://rebrickable.com/sets/71050-13/spider-man-across-the-spider-verse-complete-all-sets/?inventory=1#parts, which is not a 'real' set sold by lego, but logically, it contains sets 71050-01 through 71050-12. It'd be nice to be able to add the parent set and have bricktracker pull down the constituent set details to add to the inventory, and (optimally) allow the sub-sets to be grouped under the parent set, sort of how duplicate sets can be grouped? This might be a pretty big change on the DB backend, so don't worry too much if it's too much of a pain to add.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#157