A bundle is a product sold as a set of component products and services, some required and some optional, priced on the quote as one line or as the sum of its members.
A worked example
An illustration with round numbers. A starter kit has three members: a device at $400 and a setup service at $200, both Required, and a mount at $100 that is Optional. The admin has three ways to price it in Kugamon. Kit/Bundle Price Only: one $600 price on the kit and $0 on the members, whether or not the mount is chosen. Member Prices Only: the kit line is $0 and the total is the sum of the members chosen, $600 without the mount or $700 with it. Kit/Bundle + Member Prices: a kit price, say a $50 kitting fee, plus each member's own price, so $750 with the mount. Same products, three different totals, decided once by the admin rather than deal by deal by the rep.
Kit/Bundle or configuration, and the mistake to avoid
Use a Kit/Bundle when the set is fixed and the rep only toggles optional members. Use Configuration Options when the rep chooses among alternatives, such as one of three support tiers (a group with Minimum and Maximum Option both set to 1) or up to four add-ons. The common mistake runs the other way: a separate SKU for every combination and term, which multiplies the catalog and the price book entries behind it. A Kugamon implementation often cuts the SKU count; with subscriptions, for example, you don't need separate one-year and two-year SKUs. If you're leaving Salesforce CPQ, expect to rebuild bundles rather than import them; the data migration guide maps each object.
In Salesforce
Sales Cloud on its own has no bundle structure: each Opportunity Product is a single line with no parent or children. Salesforce CPQ adds it with SBQQ__ProductFeature__c (the features on a parent product) and SBQQ__ProductOption__c (the options inside each feature), plus product rules for validation and selection. Revenue Cloud Advanced moves from SKU-based bundles to an attribute-based catalog (ProductClassification, ProductRelatedComponent) and a constraint-based configurator. Conga uses Product Option Groups and Components. None of these structures carries over to another platform as-is: moving between them means rebuilding the bundles in the new platform's terms.
How Kugamon handles it
Kugamon has two ways to build one, both set on the product's Additional Product Info record. A Kit/Bundle is a simple grouping of Products and Services whose members are Required or Optional, managed with [Manage Kit/Bundle]; Kit/Bundle Pricing is Kit/Bundle Price Only, Kit/Bundle + Member Prices, or Member Prices Only, and Print Kit/Bundle Members decides whether members show on the PDF. Configuration Options cover the more complex case: Configuration Groups with a Minimum and Maximum Option, and per-option Selection Behavior (Unselected, Selected, Required), Quantity Behavior (Bundled, Defined, Related) and Price Behavior (Included, Discounted, Related). A Product Kit/Bundle can hold Products and Services; a Service Kit/Bundle holds only Services.
Related terms
Source: help.salesforce.com