We actually read these.
Ideas submitted here go to the product team, not into a void. Add yours, vote on others, and comment on what matters to your business.
Talk to our Product Managers live: every other Monday, 1:00–2:00 PM ET → https://www.d-tools.com/cloud-product-office-hours
I think you should make a variation of packages for "assemblies". I think it is the correct term (as already used in manufacturing) to do what we are looking to do much of the time when wanting a package to be an accessory. If you can think of group of items as it's own entity you describe as one thing to sell the customer (ie. speaker rough in) and not as multiple things to sell the customer at the same time. (ie. TV + Mount). Assemblies would present as a single item, not be able to show the parts within on a proposal, and end up with its own brand / model / vendor, etc... I add vendor there, because you may be writing PO's to a subcontractor for rough in work!
Hi @Guest as we consider this, the key question is what an Assembly needs that a Package can't be configured to do. You mentioned: presents as a single line item, hides the component parts on the proposal, and carries its own brand/model/vendor for POs (e.g., subcontracted rough-in). Are there other behaviors — like its own price independent of the sum of parts, or its own labor — that matter? And should the components still drive procurement (POs for the parts inside) or does the assembly itself become the purchasable thing?