Product bundles
On this page
Product bundles let you sell a curated group of products as a single offering. Customers select their options and add the bundle to their cart from the bundle product page on your storefront.
StoreConnect’s native bundle system does not require Salesforce CPQ. If you are using CPQ, see Product bundles with Salesforce CPQ instead.
How bundles work
A bundle consists of:
- An anchor product — the bundle itself (e.g., “Gaming Laptop Bundle”). This is the product your customers visit and purchase.
- Components — the individual products that make up the bundle (e.g., a laptop, keyboard, monitor). Each component has quantity and pricing rules.
- Component groups (optional) — logical groupings of components that let you apply additional selection and quantity constraints (e.g., “Choose your accessories”).
When a customer adds a bundle to their cart, the anchor product and each selected component appear as separate line items, grouped together under the bundle.
Set up a bundle
Step 1: Create the anchor product
Create a standard product to represent the bundle (e.g., “Gaming Laptop Bundle”). This is the product customers will visit on your storefront — it acts as the bundle container, not as a purchasable item in its own right.
Configure the product with these settings:
| Field | Value | Notes |
|---|---|---|
| Product Name | The name of the bundle | Displayed as the bundle title on the storefront |
| Is Master | Checked | Default for standalone products. Do not create the anchor as a variant of another product. |
| Track Inventory | Unchecked | Bundle availability is determined by component stock, not anchor stock. Leave this off. |
| Active | Checked | Required for the product to appear on the storefront |
| Virtual | Optional | Check this if the bundle contains no physical items requiring shipping (e.g., all digital downloads). Leave unchecked if any component requires shipping. |
:::note The anchor product itself is never sold or shipped directly — it is just the entry point for the bundle. There is no need to assign a SKU or manage stock for the anchor. :::
Add the anchor product to a category so it appears on your storefront. Customers navigate to it and configure the bundle from the product page.
Step 2: Add a pricebook entry and set the pricing strategy
The anchor product must have an active Pricebook Entry in your store’s pricebook. The pricing strategy controls how the bundle total is calculated.
On the Pricebook Entry for the anchor product, set:
| Field | Description |
|---|---|
| Bundle Price Strategy | Choose flat_price or component_price (see table below) |
| Price | For flat_price: the fixed bundle price. For component_price: set to $0 — the total is calculated from components. |
| Bundle Only | Leave unchecked on the anchor. (This field is used on component products — see Step 3.) |
| Strategy | How pricing works |
|---|---|
flat_price |
The bundle total is the anchor product’s price only. Component prices are ignored. |
component_price |
The bundle total is the sum of all selected component prices × quantities (less any free quantities). |
Step 3: Create your component products
Create or identify the products you want to include as components. If a product should only ever be sold as part of a bundle (never standalone), check Bundle Only on its pricebook entry.
:::note If a component is a variant product, set the price on the variant’s price book entry, not the master product. The price used is the selected variant’s price. :::
Step 4: Create Product Component records
For each component, create a Product Component record linking it to the anchor product. Set the following fields:
| Field | Description |
|---|---|
| Anchor Product | The bundle anchor product |
| Component Product | The product to include as a component |
| Required | If checked, the component must be included. The customer cannot remove it. |
| Default Quantity | The quantity pre-selected when the customer opens the bundle page |
| Minimum Quantity | Minimum quantity the customer must select (0 = none required) |
| Maximum Quantity | Maximum quantity the customer can select |
| Free Quantity | Quantity included in the bundle price at no extra charge (applies to component_price strategy) |
| Position | Display order — lower numbers appear first |
| Component Group | (Optional) Assign to a group for additional constraints |
Step 5: Create Component Groups (optional)
Use component groups to organize components and apply group-level selection rules. For example, an “Accessories” group where customers must choose at least one but no more than three items.
On the Component Group record, set:
| Field | Description |
|---|---|
| Display Name | The group heading shown to customers on the storefront. If left blank, the storefront shows the group Name instead. |
| Position | Display order of the group |
| Minimum Components | Minimum number of different components from this group the customer must select (0 = none required) |
| Maximum Components | Maximum number of different components the customer can select from this group |
| Minimum Group Quantity | Minimum total quantity across all components in this group |
| Maximum Group Quantity | Maximum total quantity across all components in this group |
Then assign each component to its group by setting the Component Group field on the Product Component record.
:::tip Minimum Components and Minimum Group Quantity serve different purposes. For example: Minimum Components = 2 means the customer must pick at least 2 different items from the group. Minimum Group Quantity = 4 means the combined quantities of all items in the group must total at least 4. :::
:::note At least one product component must not be assigned to a component group, otherwise the bundle cannot be added to the cart. Groups are for organizing subsets of components — they cannot contain all components in a bundle. :::
Quantity constraints
The bundle page checks quantity and group rules as the customer makes selections. StoreConnect checks the same rules again when the bundle is added to the cart, including the contents of any nested bundle. The second check catches a selection that reaches the cart some other way, such as from a custom front end or from a page loaded before you changed the rules.
If a selection breaks a rule, nothing is added and the cart stays as it was. The customer sees a message naming the component or group. For example, if a group has a Display Name of Accessories and a Minimum Components of 1, a customer who selects no accessory sees “Accessories requires at least 1 component(s)”.
If a customer edits a bundle already in the cart and the new selection breaks a rule, the original bundle stays in the cart unchanged.
- Required component with matching min/max/default: The component cannot be removed.
- Min Quantity = 0, Required = false: The component is optional and can be excluded entirely.
- Free Quantity: For the
component_pricestrategy, the first N units of a component are included in the bundle price. Units above the free quantity are charged at the component’s price.
Nested bundles
A component product can itself be a bundle. This lets you build hierarchical bundle structures.
Example:
Ultimate PC Bundle
├── Gaming Laptop Bundle (nested)
│ ├── Gaming Laptop (required)
│ └── Keyboard Cover (optional)
├── 4K Monitor (optional)
└── HD Webcam (optional)
Customers set up the nested bundle in a pop-up window before adding the parent bundle to the cart. In the pop-up, the customer also chooses how many of the nested bundle they want.
To work out how many of an item inside a nested bundle reach the cart, multiply three numbers:
- The quantity of the item in one nested bundle
- The number of nested bundles the customer chooses
- The number of parent bundles the customer orders
For example, each Gaming Laptop Bundle includes 2 Keyboard Covers. A customer chooses 2 Gaming Laptop Bundles and orders 3 Ultimate PC Bundles. The cart gets 2 × 2 × 3 = 12 Keyboard Covers.
A nested bundle that comes to $0 is still added to the cart with the rest of the bundle. A nested bundle can come to $0 when the parent bundle price already covers the nested bundle’s contents.
Each different nested bundle selection makes a separate bundle in the cart. If a customer adds the Ultimate PC Bundle twice, once with the Keyboard Cover and once without, the cart shows two Ultimate PC Bundles. Adding the same bundle again with identical selections, including identical nested bundle selections, combines with the matching bundle already in the cart.
To set up a nested bundle, create a Product Component record where the Component Product is itself a bundle anchor product. The nested bundle’s own Product Component records define its contents.
:::note Bundles support a single level of nesting. A bundle can contain a sub-bundle, but that sub-bundle’s own components must be regular products, not bundles. StoreConnect blocks the creation of a three-level bundle chain when you save the Product Component record, because deeper nesting cannot be priced, displayed, or edited on the storefront. :::
If older Product Component records still form a deeper chain, the storefront refuses to add that bundle to the cart and shows “This bundle cannot be added to the cart: bundles can only be nested one level deep”. To fix the bundle, remove the extra level from the Product Component records.
Bookable product bundles
A component product can be a bookable or rental product. When included in a bundle, customers select booking dates, times, and location for that component directly on the bundle page.
Each bookable component in a bundle can have a different booking period. Availability is validated per component when the bundle is added to the cart.
For more on configuring bookable products, see Sell bookable events and services and Configure rental products.
Customer experience
- The customer visits the bundle product page on your storefront.
- The bundle page shows required components (pre-selected) and optional components.
- The customer adjusts quantities, selects optional components, chooses variants, sets up any nested bundles, and selects booking details for any bookable components.
- The total price updates in real time as selections change.
- The customer adds the bundle to the cart. The anchor product and each component appear as grouped line items.
- To edit a bundle in the cart, the customer selects Edit. The bundle page reopens with their previous selections pre-filled.
- Removing the bundle from the cart removes all component line items together.
Component pricing overrides
By default, a component’s price comes from its standard pricebook entry. If you need per-pricebook pricing for a component — or different pricing when the same component appears in different anchor bundles — use Component Pricing (Component_Pricing__c) records.
Priority order when determining a component’s price:
- Component Pricing record matching both the anchor product and the pricebook (most specific)
- Component Pricing record matching the pricebook only (general)
- Standard pricebook entry for the component (default)
To create a Component Pricing override:
- In Salesforce, navigate to Component Pricing in the App Launcher.
- Create a new record and set:
| Field | Description |
|---|---|
| Component Product | The component product to override pricing for |
| Anchor Product | (Optional) The bundle this override applies to. Leave blank to apply to all bundles. |
| Pricebook | The pricebook this price applies to |
| Unit Price | The overridden price for this component |
See Component Pricing Object Reference for the full field reference.
POS behavior
Bundles set up this way can also be sold at the register, where operators configure them in a bundle screen and the bundle sits in the cart and on the receipt as one group. A few settings behave differently at POS:
- Bundle Price Strategy decides how operators discount the bundle. There is no discount for the bundle as a whole: in a
flat_pricebundle operators adjust the anchor line, and in acomponent_pricebundle they adjust the component lines. - Virtual on the anchor also tells the POS the anchor has nothing to prepare, so it never routes to a fulfillment station.
- Bundle Only components appear in POS search and the product grid but cannot be added to the cart on their own.
- A bundle is added with a quantity of one and cannot be reopened once it is in the cart. A whole-bundle quantity above one is a storefront behavior.
To prepare a bundle for the register, see set up bundles for POS. For what operators do at the register, see sell a bundle at POS.
CPQ coexistence
StoreConnect’s native bundle system and Salesforce CPQ can coexist in the same org. However, a single product cannot use both approaches simultaneously — a product is either a StoreConnect native bundle or a CPQ bundle, not both.
Salesforce object reference
The bundle system uses these custom Salesforce objects:
- Product Component Object Reference — defines each component’s relationship to the anchor, quantities, and group assignment
- Component Group Object Reference — defines component group display and selection rules
- Component Pricing Object Reference — defines per-pricebook and per-anchor pricing overrides for components
The Bundle Price Strategy and Bundle Only fields are on the Pricebook Entry record for each product.
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.