How Product Bundles Work
How Do Combo Bundles Work?
Combo Bundles are presented and processed as a parent-child hierarchy across the shopping experience:
Dynamic Store: Product Bundles are displayed a new Product Type, including a pill icon to designate them:
Product Item Details (LWC): Product Bundles will be displayed as a main “Parent” product with “Children” (the bundled products) listed below in a table. Images, Names and Prices (if configured based on Bundle Subtype) will be displayed
Shopping Cart & Checkout: Bundled items are displayed hierarchically. Configuration-required products (e.g., size selection for a T-shirt) are flagged, and checkout is blocked until all configurations are complete
Order Confirmation & My Orders: The bundle structure is preserved, showing both parent and child items. Bundles can be collapsed for easier viewing.
Pricing & Taxation (Based on Subtype)
Assembled Bundles: Priced, taxed, and shipped at the parent level. Only the Parent Bundle product will be used for calculations. Children are treated as $0 line items.
Unassembled Bundles: Priced, taxed, and shipped at the child level. Only the Children “Bundled” products will be used for calculations. The parent Bundle product is treated as a $0 line item.
Data Structure
Combo Bundles are built using a structured data model:
Parent Product: Represents the bundle as a whole. This is the main product displayed in the Dynamic Store or in the Order Processor
Child Products: Linked via
ProductLinkrecords with attributes like quantity, price override, and GL Account.Bundle Subtype: Specifies financial handling (Assembled vs. Unassembled).
Wizard Setup: Staff can use the Bundle Wizard to easily add products to a bundle with specified quantities and discounted prices, and define main bundle properties, including name, GL codes, and price.
Data Processing
Triggers are responsible for the addition of bundled products into a cart/proforma order. When a parent Bundle product is added. triggers active and will add all the linked children products to an order as specified in the Product Link (Price, Quantity, GL Account), depending on the Bundle Sub Type. For products that have logic to determine the start or end dates, the default order processor logic is used. The end result should mimic a process where a Staff User selects the individual products and adds them 1 by 1, overriding the quantities and prices.
Examples
Example 1
Name: Membership Bundle
Type: Combo Bundle
Subtype: Unassembled
Children (Specified by Product Link(s))
Annual Membership (Membership Product)
List Price: $100
Bundle Link Price: $50
Accounting Handbook (Merchandise Product)
List Price: $50
Bundle Link Price: $0
Quantity: 2
ISEN 2026 Full Pass (Registration Product)
List Price: $300
Bundle Link Price: $150
Adding Products Individually
Total Order Price: $500
Adding Products as a Bundle
Total Order Price: $200
Example 2
Name: Membership Bundle
Type: Combo Bundle
Subtype: Assembled
List Price: $200
Children (Specified by Product Link(s))
Annual Membership (Membership Product)
List Price: $100
Bundle Link Price: $0
Accounting Handbook (Merchandise Product)
List Price: $50
Bundle Link Price: $0
Quantity: 2
ISEN 2026 Full Pass (Registration Product)
List Price: $300
Bundle Link Price: $0
Adding Products Individually
Total Order Price: $500
Adding Products as a Bundle
Total Order Price: $200