Hey, I’m Ashley, and I’m the CEO and founder of ITequality. Welcome to Bundles Level 1 in Salesforce CPQ. The scenario is, as a merchant, you need to sell a canvas backpack that has room for three different healing potions. There are ten potions for your customers to choose from, but they can only put three in the backpack.
Potions 1-3 are included automatically with the backpack, and there are no additional costs. There are some potions that are available for an additional fee. Lastly, the minor potions, those freebie ones, can allow for three of the same type. So you could have all pink potions, for example.
But the more powerful potions can only be sold at a quantity of two, and the really special potions are limited to just one for safety reasons. This backpack can easily be sold as a bundle of products where your various potions and pricing display when you add the backpack to your cart.
- Step 1: we’re going to build the parent product. (I’ve already done that. When we get to the live demo portion, I’ll show you. We have our canvas backpack.)
- Step 2: we’re going to make all 10 of the child products.
- Step 3: we’re going to add the features to the parent. That’s the backpack.
- Step 4: we’ll create the product options.
So first we’re building the parent product with the parent, if you will, settings. We need to ask, what is the configuration type? Should we always configure this bundle? Should it be required that we configure this bundle? Or maybe it’s optional. Maybe we have the bundle that’s already ready to go and we just want to allow people to change it if they want to.
That’s what the configuration type will be. The configuration event will ask, do you want this to be something where you edit and you go back and change it? Or is this something where you want it to be required in order to get to the next step that you must configure it? Then we’ll talk about the option layout. There’s a few different UI settings that you could have for your bundles.
Build the child products. These child products are going to be associated with different features. Products that are available where you can choose three of the same kind, we’re going to associate those with this one feature. For these other ones, we’re going to say that this is feature B because these ones are additional prices and they just behave a little differently.
And then for this product, where you can only choose one for these special ones, we are going to have that be on a different feature. A little bit about the features, so we’ll have feature A, feature B, and feature C for those different types of products. And these features are just groupings, as you’ll see in the live demo portion. Lastly, we’re going to create the product options. So we’ll go back to our parent product, and then we will configure those product options.
Live Demo
So with no further ado, let’s jump into the live demo portion of this. With Salesforce Revenue Cloud Consulting you may find many situations with bundles. We are on our canvas backpack, and this is our parent product, if you will.
We have our configuration type set to required, so we want to make sure that people are always configuring this bundle, but you can play with the options and see what works best for your particular bundle. For a configuration event, we want this to be always, so we always want people to be configuring this bundle.
We don’t want them to be able to bypass it by accident; we want it to be a required step. Under the option layout, I chose sections, you can have this be like a wizard where you go and you jump to different screens to toggle between the different features. And we have a click, but if you prefer a little plus sign where you click to add, you could change the UI settings.These ones are more for visually appealing purposes and these ones are more functional as to when and why you need to update.
From our parent product, we have a couple options. One, we could go and make our child products by cloning this product. Or two, we could just go to products and we could make a new product from here. So let’s go ahead and make a new product. This product is going to be one of our minor potions. So let me go ahead and fill in these details. All right. Now that I have my details filled out, this is our minor health potion.
We’re going to give this a product code of potion M2 cause this is our minor potion number two. We’ll assign it to the product family for potions. We don’t need any asset behavior right now. So we’re just going to default that to none. Product description – this is a one time health potion and we’re going to make sure that this product is active.
We don’t need to do any of the parent control settings because this one is just a child product. So we’re going to go ahead and save this. Now from our minor health potion, it may make sense for us to go ahead and use the clone feature. So at this point, I’ll go ahead and clone. So I’m going to make the next eight or so potions on my own, and then we’ll jump back in when those are done.
Alright, we’ve got all of our products keyed in, and we can see them all, all of our potions and all of our single backpack right now. Everything’s all filled out. The next thing that we need to do is to make sure that these products are all associated with a price book.
So, in order for them to show up, they have to be active. They can’t be marked as a component and we need to add them to a price book. We’re just gonna use the standard price book, because that one’s available all of the time. Even though these potions, the minor potions, are included as part of the bundle, they can still have a list price that’s non zero.
And, if they’re purchased in some other way they’ll still have a fee associated with them. But when they’re purchased in the bundle, we’ll make sure that these ones are indicated as included. So I’ll go ahead and save this and then I’m going to update the price book entry for all of these products.
Now that we have all of the price book entries created for all of our products, we can go ahead and test this out by navigating to our quotes tab. Even though there may be no other configuration that’s been set at this time, we can always make a new quote from the quotes tab. And for the sake of testing, we can bypass connecting this with an opportunity or an account, and we can just hit save that way.
We look at the products that are available to be added to this quote. In real life, we wouldn’t create a quote in this manner, but for the sake of testing, it just helps speed things up. Sometimes we’re going to go to edit lines. And if you’re in classic, you’ll see that as a button front and center, but in lightning, it’s usually down here somewhere, unless you’ve edited your lightning page layout.
When we go to edit lines, we have to choose a price book, that’s part of Salesforce Revenue Cloud. It’s really critical to make sure that whatever price book you’ve added your products to you’re currently selecting here because if you choose a different price book you won’t see your products unless those products have been added to that price book as well.
We only have one price book so we’re safe and we can go ahead and click on add products. From here this is going to navigate us to see all of our products. I did go ahead and put this little image item in here for the sake of usability. I really like having it.
So at this point we can see all of our products listed here. That means that they’re active and they’ve been assigned to a price book. That’s the price book on this quote. We’re ready to go ahead and move on to our next step of creating our features. So to make our features, we’re going to go back to our products.
We will select our parent product. That is the canvas backpack and we’ll navigate to related, over on our canvas backpack. Then we’ll find our features related list. We’ll go ahead and make our first of three features. So this feature is going to be our minor potions. We’re going to say they could in theory, select zero items if they wanted to, and the maximum number is going to be 3.
This is the first one that’s going to show up in the list, and so we’ll go ahead and save and new. Now we’re going to do our standard potions. Again, we could choose zero if we wanted to, or we could choose as many as three. This is the second one that’s going to show up in our list, and we’ll save and new one more time.
These ones are again, we could have zero of these selected, but, no more than two actually, because we only have two items that are in here. And this is the last one that’s going to show up. This is going to be a lot more clear once we get into making our product options. So for now, consider these placeholders for our product options.
Let’s go ahead and add our product options. So we’re going to, from the product, parent product related list, click on options. This is going to be the first one that shows up. I’m going to number them by tens because it’s easier to adjust your products later that way. The default quantity here, we’re going to leave this empty because people are going to choose them as needed.
This optional skew for the first one, we’re going to have our minor potion number one, and the feature, we’re going to associate this with our minor potions feature. We’ve got our child product, we have the feature that it’s associated with – this is going to be component, because as a component, the quantity is dependent on the parent.
So if we were to buy 5 backpacks, we would need 5 of these potions. If the quantity was going to be independent, we could say it was an accessory and we could buy 4 backpacks and only one of these potions. But because of the way we’re selling them in this bundle, it makes the most sense for us to sell it as a component.
So when you fill your backpack, you’re going to have a total of 3 potions per backpack. And if you buy multiple backpacks, they all have the same potions in them. So we have this set up as a component. It is going to be bundled because by bundling it, the price is zeroed out and it’s just included. So this one is considered bundled.
Here we can specify the minimum or maximum quantity. We can’t choose more than 3, so let’s go ahead and key that in as 3 is the maximum. And we will go ahead and save and make the rest of them. Next, we’ll go ahead and add our minor potion number 2. We’re going to associate that with our minor potions feature.
This too is a component, it is also bundled. This is the second one in the list, so we’ll mark that as 20. And the maximum quantity, again, is going to be 3 for any of these. We will save and new. We’re doing minor potion number 3, associating it with our minor potion. This is the third one. We are going to say that this one is bundled and the maximum quantity is 3.
We’ll go ahead and do this one more time. Our minor potion number 4 is associated with our minor potion feature. This one is the fourth one, so we’ll go ahead and key that in: maximum quantity 4. We’re going to go ahead and say this one is bundled, save and new. Now we’re going to get into our standard potions.
Standard potion number one. We can restart the numbering now because this is going to be associated with a different feature. So I’m going to start back at ten again. And we’re going to have this for our standard potion. It is no longer bundled and again it has a maximum quantity where you can only buy up to two of these.
We’re going to say that the price is two dollars. So we’ll give this a unit price of two dollars, and now we’ll save and new, and we’ll do the rest of the standard potions. Standard potion two, this one’s number 2. Maximum quantity is 2, and our feature – standard potions. We’re going to give this a unit price of 2.
It’s no longer bundled. Save and new. This one is standard potion number 3. This one’s going to be numbered 30. Maximum quantity of this one is 2. This one has a unit price of 2. Standard potions. Save and new.
All right, standard potions 4. We’re going to number this 40. It is going to have a maximum quantity of 2. We are going to give it a unit price of 2. And our feature is standard potions. Alright, we’re going to save and new.
Now, we’re moving on to our next category. So this one is our special potion and this unit price is three and has a maximum quantity of one. We’re starting the numbering over again for our potions in Salesforce CPQ. So click and save and new. This one is our special potion 2, it gets a number of 20 and our maximum quantity here is 1 and over here we’ve got a unit price of 3. It’s associated with our special feature. We’ll go ahead and save that.
Sometimes as we’re going through this I might skip one. I think I skipped over number 3. So, let me get that in there and then we’ll take a look. Now that we’ve keyed in all of our options, we can click on View All to see all 10 of our potions. If we sort them by feature, we can quickly see that all 4 of the minor potions have been included, and these prices are bundled, and we have our special potions as well as our standard potions. Let’s go ahead and add this to a quote and see what our bundle looks like. I’m going to choose quote 17, the one that we made earlier, and I’ll go to edit lines so that I can start to configure this. I’ll click on add products and then choose our canvas backpack.
As soon as I hit select, I’m going to be required to configure this backpack bundle. I can choose no more than three of the following or under the minor or standard potions, and I can choose no more than two of the following under special. So let’s say I wanted to choose a quantity of three for this particular potion.
If I click on save, this is going to tell me that I’ve exceeded the maximum quantity. So, for this one, I’ll go ahead and reset the quantity here to one. Right now we don’t have any additional configuration to tell us not to choose more than three if they cross different areas. But within any particular area we do have the logic set at the product option and feature level.
So, we’ll go ahead and just choose three of these potions, and I’ll go ahead and save. In bundles level two, we’re going to talk about how to restrict these so that you can’t choose more than three, even though some of the potions may mix and match. We’re going to do that with a configuration rule that links to a product rule, and we’re also going to be talking about how to make sure that the special potions are sold together, because right now, technically, you can choose one or the other.
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.
