CPQ Product Bundle

 CPQ Product Bundle 

Bundle:

• A bundle is simply a group of products we know should be sold together ( A bunch of products sold together as a set. ) or  A bundle is a product with optional features or components that you want to include on a single quote line.
• A bundle product contains several records.
  
  
• A bundle parent: The parent product is the bundle itself.
  
  
• Options: These products in the bundle contribute to the bundle price. You can consider these children of the bundle parent. An option doesn’t contribute to the bundle price if you select its Bundled checkbox.
  
  
• Features: A feature is a group of options. You can use the Min Options and Max Options fields to define selection restrictions for objects in the same feature, such as “pick one or more” or “pick 3 of 5.”. or A feature is a group of product options within a bundle. Use features if you want to organize options into set groups, such as hardware and software.
  
  
• Option constraints: Use constraints to control how users select options together.
• 
  
• Configuration attribute: A field and picklist shown above or below the list of product options. This field targets all options containing the same field and applies its value to all those fields.

• There are three types of bundles. 

• Static bundle:  These bundles always have the same products together, in the same quantities, with no changes allowed

• Configurable bundle: This bundle can be customized to your liking, with some limits to prevent impossible configurations.

• Nested bundle: This is a bundle inside another bundle.   

 

Control When Sales Reps Can Configure Bundles

•  Change a product’s configuration event, Configuration Type  fields to control when Salesforce CPQ allows sales reps to configure a bundle.
  
  
• Configuration Event field With the following values.
  
  
• Always: Salesforce CPQ opens the configurator when the sales rep adds the bundle product. The quote line item always displays the configuration link as well.
  
  
• Add: Salesforce CPQ opens the configurator when the sales rep adds the bundle product. After initial configuration, the quote line item doesn’t display the configuration link.
  
  
• Edit: Salesforce CPQ doesn’t open the configurator when the sales rep adds the bundle product. However, they can select the configuration link on the quote line. This value saves time if you have a bundle that always or frequently uses its default configuration.
• Configuration Type the following values.
  
  
• Allowed: The sales rep can configure the bundle at any point. Since they’re not required to configure it, they can leave the initial configuration page without making any changes.
  
  
• Disabled: Sales reps can’t configure the bundle. Salesforce CPQ doesn’t prompt them to choose options after adding the bundle product. And it doesn’t show a Configure link next to the bundle’s quote line item. Use this value when your bundle automatically selects options.
  
  
• Required: The sales rep can’t leave the initial configuration page until they choose at least one product option.
  
  
  

• Global attributes. Global attributes are reusable, so admins can attach them to as many options as they’d like (even across multiple bundles)
  
  
• Configuration attributes: cannot be reused in another bundle. Configuration attributes have a few additional behaviors we can set up to make them easier to use, which we can see throughout this project. Sometimes configuration attributes are found in specific bundle features.
  
  
• it’s important to understand that configuration attributes are not actually fields, but are visible manifestations of fields.
  
  
• To create a new configuration attribute you’ll go through the three steps
  
  
• Create a field on the Product Option object.
  
  
• Add the API name of the field to the Target Field field on the Configuration Attribute object.
  
  
• Create a configuration attribute record on the bundle product.


• Both configuration and global attributes are meant to gather information you can use later in the sales and fulfillment process.
  
  

•  Global attributes are like configuration attributes, with a few important distinctions.

  Differences	Configuration Attributes	Global Attributes
  Appearance	Visible above, below, or inside features.	Visible in an expandable drawer on the option.
  Reusability	May be related to a single bundle.	May be related to as many options as you’d like, even across bundles.
  Construction	Requires only one record related to the product.	Requires four records across four objects.
  Behavior	May be configured to use a default value, show or hide picklist values, be required, and more.	Currently, cannot be configured with any of the special behaviors such as default values.

 

• Attribute sets are collections of global attributes that have something in common. 
  
  
• Global attributes are related to attribute sets through a junction object called an attribute item, which has lookups to each of the other objects.
  
  
  
  
• This kind of relationship allows you to create more than one attribute set from the same collection of global attributes.
  
  
• An attribute item does more than just connect a global attribute to an attribute set. It also determines which should appear first from left to right 
  
  
• Product Attribute Set :To associate the Attribute set to both Product band product options. We need to use another junction object named Product Attribute Set.
  
  
  
  
  

Mapping Custom Fields Between Objects

• Certain pairs of CPQ objects pass custom field values from the first object to the second object when the second object is created. The values pass if the custom fields are editable, have matching field types, and have matching API names. We call these field pairs “twin fields.”
  
  
  
• Reference Link Here