Welcome to another Salesforce CPQ Revenue Cloud tutorial. We’re going to talk about nested bundles. In our last video we did a product option to exclude our special potion from our other special potions so that you can only choose one. But let’s say that instead you wanted to, when you select the special potion number one, always select another potion. One of the ways to do that would be to have a nested bundle.
And the way that we have nested bundles, you start it out like a regular bundle where you have your canvas backpack as your parent. And then you have all of your child products, these options down here. And in this case, your child option for your special damage potion is also going to be a parent itself.
So let’s take a look at what that’s going to look like in Salesforce CPQ. We have our canvas backpack and we have all of these options. So I can view these options and we can see we have all ten of our different potions. And for our special potion special damage, if I go to this product – right now it doesn’t have any parent settings, so there is no configuration type configuration event.
We’re going to go and edit this child product, and turn it into a parent as well as being a child. Revenue Cloud has a ton out very customizable options. So here, for the configuration type, we’re going to say that perhaps it’s allowed or even disabled, because we want this to be smart enough to just auto select and have the person move on from what they’re doing.
So let’s say that it’s allowed and then the configuration event will just say maybe on edit, so that you really bypass that screen. You don’t get prompted. It’s just gonna automatically select it. We can keep the option layout if we only have one child. The option layout doesn’t matter as much, but we’ll say sections.
In Salesforce CPQ we could include some other features like disable reconfiguration, but we’ll just go ahead and continue. So I’m going to save this now and now we’re going to add a child to this product. So under related, we can see that this is optional for the Canvas Backpack because it’s a child itself. Now we’re going to add an option.
So let’s find our special AoE potion. We don’t have any features associated with this right now because this isn’t as big of a bundle. You could make a feature if you want. I’m still going to give it a number of 10. I like to number by 10s so they’re easy to arrange. This is going to have a quantity of 1.
Salesforce CPQ lets you specify if the quantity is editable. We’re going to say no, this quantity is not editable because we just want 1 to be automatically applied all of the time. We’re going to say this is selected and it’s required, and the quantity is not editable. We’re just going to say the quantity of 1, and you cannot change it. So, I think we have everything we need here. This is a situation you might run into with Salesforce Revenue Cloud Consulting where you need to place limits for some items.
As far as the type goes, this could be done in a few different ways with Salesforce Revenue Cloud. If you want the price to be included, which we currently don’t, we could have it be bundled. The quantity is going to be dependent on the parent, so component is the best option. If you wanted this to be independent, where you could buy as many of these as you’d like, you could say accessory. Revenue Cloud lets you customize accordingly.
And if it’s just a related product and it doesn’t need to be bundled together, but it just needs to be available for perhaps, a related product. We’re going to say component and not bundled. As far as the price goes, let’s call this 2 because the list price is actually more. So when you buy it as part of the bundle, it’ll save you a little bit.
So let’s go ahead and save that. Now we have our both child and parent product. Let’s see what this looks like when we go to our quote editor. I’m going to cancel it up here. All right, and then let’s go ahead and select this backpack.
It’s simple in Salesforce CPQ – I’m going to click on this box, and you’ll notice right away there’s a little wrench right there, just like there was on the previous screen when we selected the backpack. So this wrench is allowing us to configure, but it’s not requiring us to configure. Had we selected required at the parent level, this would have a little red bar next to it, and we would be forced to configure this before we could move forward.
At this point, I’m just going to go ahead and save, and when my screen loads, you can see that we have two potions that have been added automatically. This other one kind of looks like it came out of nowhere, but really, this came from selecting this potion, and this is what we just did in creating that nested bundle. When you do Salesforce Revenue Cloud Consulting you may need to create many types of nested bundles.
If you’ve enjoyed this tutorial, please like and subscribe and if you’d like to learn more about this or any other Salesforce CPQ, Revenue Cloud, or Salesforce Revenue Cloud Consulting items – you can work with us. Thank you so much!
Note: The information in this blog post is still applicable to Salesforce CPQ; however, as of Q1 2025, Salesforce CPQ has been officially deemed End of Sale and Salesforce’s new lifecycle management product has been rebranded to Revenue Cloud (previously named RLM). To view the timeline of CPQ and Revenue Cloud history, click here.
If you’d like to know more regarding the differences between Salesforce CPQ and Salesforce’s new offering, Revenue Cloud (RLM), please click here.
