Guidelines and Considerations for Using Nested Bundles

To create a nested bundle, assign a bundle product to the Optional SKU field of an option record. When users configure the top-level bundle, they’ll see a configuration icon on the quote line for the option containing the second bundle.

For easy user navigation, we recommend keeping your nested bundles one to three levels deep. As of Spring ‘20, product bundles can be set as expanded or collapsed by default. To save screen space. In your installed package settings, on the Line Editor tab, check Enable Expand/Collapse Bundles,. If this setting is unavailable, ensure that you also check Enable Large Quote Experience, Visualize Product Hierarchy, and Keep Bundles Together. After the feature is enabled, you can choose the Default Bundle Setting.

“Parent bundle” means the configured SKU of the product option represented by the nested bundle. It’s not always the top level. It’s always the immediate parent of a “child bundle.”

Nested bundles can’t be upgraded.

Contracting by subscription start date isn’t supported end to end for bundled subscriptions with different start dates than their parent product has.

Example Your top-level product in a bundle is a customizable laptop, where the first level of options lets you select the brand of hard drive for the laptop. Create two sets of features on each hard drive brand so you can set the brand’s memory size and warranty after a user selects it in the laptop bundle. These hard drive sizes and warranties represent the second level of options in your bundle.