- HOME
- CPQ (Configure, Price, Quote)
- Product bundling strategies in CPQ: Best practices in the B2B landscape
Product bundling strategies in CPQ: Best practices in the B2B landscape
This seemingly modern concept is centuries in the making.
Before economists tried to map out the pricing strategies, merchants of past understood a fundamental truth about human psychology: People love a packaged deal. During the Industrial Revolution, bundling evolved from a survival tactic into a calculated strategy to capture the market. The most iconic example was King Camp Gillette’s "razor and blades" strategy where, by selling safety razors at a steep discount, Gillette practically gave away the handle so they could lock consumers into buying proprietary replacement blades for the rest of their lives.
Fast forward to the modern market where bundling has become so deeply embedded in our daily lives that it is the norm, making it incredibly hard to notice and separate it. When you buy a value meal at McDonald's, open Microsoft Office 365, or pay your annual Amazon Prime subscription, you are buying ecosystems instead of individual products. In the SaaS and subscription era, near-zero digital shipping costs have made the "invisible bundle" the ultimate engine for customer retention.
Today, there have been multiple dedicated studies around this to understand customer behavior, market preferences, buying trends, and other opportunities to increase sales and revenue. The results are the clear strategies built with plenty of data engineering, that businesses can experiment with in no time. With technology introducing solutions for CPQ and billing, the opportunity has only broadened.
The popular bundling models businesses use today
Fixed bundles
Everything is predecided, which makes this one of the simplest bundles to create and manage. The components, the quantities, and the price are all locked at the catalog level, so the rep/the customer selects the bundle and the purchase process begins. The buyer either takes the package as designed or looks at a different one altogether. This works when you start noticing a particular combination of purchases happening a hundred times over.
Pros | Cons |
|---|---|
Quotes go out in minutes because there is nothing to decide | Buyers who need eight of the ten components feel they are paying for padding |
Can be priced publicly and sold in self-serve models | Weak components hide behind strong ones, so you learn little about what customers actually value |
Example: In Microsoft 365 Business Standard, the apps, the mailbox, the storage, and the collaboration tools come as one fixed package at one per-user price. You cannot drop Teams and pay less for it.
Configurable bundles
Here, the parent element stays fixed while the sub-contents flex. The system holds a frame, and the rep fills it in within boundaries your team has already defined.
A telecom offer is the clearest illustration. The connectivity plan is mandatory because nothing else works without it. The router is optional, since plenty of customers already own one. The managed firewall is available at a per-site rate, so it scales with how many locations the customer is running. Three different decisions, one parent product, one price that recalculates as the rep moves through it.
The reason mid-market and enterprise deals lean heavily on this format is simple: Buyers almost never fit the catalog as written. A 60-person company and a 6,000-person company want the same product in meaningfully different shapes. Configurable bundles let you serve both without maintaining two catalogs, provided the rules underneath are kept current.
While flexible for the customers, setting them up can take loads of planning and correct configuration. Mandatory versus optional, minimum and maximum quantities, and mutual exclusions once codified will off load the time-consuming task from sales reps.
Pros | Cons |
|---|---|
Option-level data tells you which components are genuinely wanted | Rule maintenance grows fast |
Upsell paths are built into the structure rather than bolted on later | Discount control gets harder when every quote looks different |
Example: In Dell's server configurator, the chassis is the parent, while processors, memory, storage, and the support tier are selected within limits the system enforces. Pick an incompatible combination and it simply won't let you proceed.
Nested bundles
This is a bundle inside a bundle. Rather than one parent holding a flat list of components, the parent also holds other bundles that are complementary. Nested bundles prevent confusion among purchasers and lets you provide a complicated offering in a neat package.
Pros | Cons |
|---|---|
Provides users a clear path to purchase services with complex choices | Debugging a pricing error can become a maze |
Sub-bundles can be reused across several parent offers, saving catalog work | Partial cancellations get messy when a child bundle is shared across parents |
Example: In Cisco's Enterprise Agreement, a single agreement holds separate suites for networking, security, and collaboration, and each suite contains its own set of licenses and services underneath it.
Best ways to use bundles
The models above describe how a bundle is built broadly. And there are different ways to leverage them.
New product promotion
You pair a new release with an established product so the newcomer borrows trust it hasn’t earned yet. A security vendor folding a new threat intelligence module into the existing endpoint subscription for two renewal cycles is doing this. The one thing to settle before launch is the end date, because a temporary bundle with no expiry becomes a permanent one by accident, and unpicking it two years later is an unpleasant conversation with both finance and the customer.
Buy one get one
In B2B this seldom looks like a supermarket aisle. It shows up as a second license block at no charge, an extra environment for staging, or an additional region thrown in for the first year. It is a promotion layered on top of a bundle rather than a bundle of its own, and it is time-boxed so the renewal price doesn’t come as a shock.
Attachment or complementary
The bundle exists to pull a second product along with the first, and keeping them complementary is key to natural cross-sell or up-sell pathway — implementation services attached to a platform subscription, a data add-on attached to an analytics tier, an extended warranty attached to equipment.
Best practices while configuring the bundles in a CPQ system
Keep the components visible underneath the parent
The customer should see one clean figure on the quote. Your system, though, needs to carry every component separately behind that figure. This is the detail that saves you a lot of time later. When the customer drops the training component in month four, or doubles their seat count in month six, the billing engine needs something specific to prorate against. Without that breakdown, your finance team is calculating credit notes by hand, and nobody can answer which part of the bundle was actually making money.
Codify the rules while the reasoning is still fresh
Every bundle carries a set of conditions that someone in your organization already knows. Component A cannot ship without Component B. The premium tier is unavailable below 50 seats. Two of these four add-ons are mutually exclusive. When those conditions are embedded in the system, it moves the correction to the earliest possible point. A rep who is blocked at the configuration screen loses 30 seconds, at worst. But a rep who is corrected after sending the quote is renegotiating with a customer who has already seen a number, and that conversation costs a lot.
Decide discount limits bundle by bundle
A blanket discount ceiling across the catalog feels tidy on paper and hides quite a lot in practice. Twenty percent off a service-heavy bundle and twenty percent off a licence-heavy one land very differently on your margin, because the cost structures underneath them have almost nothing in common.
Version your bundles rather than editing them
There are customers still being invoiced against the package you built 18 months ago, and they'll renew it too. If someone edits that bundle in place to fix a price or swap a component, you have just changed the terms of live contracts without meaning to.
Create a new version, point new deals at it, and let the old one run until its last renewal passes. Slightly more housekeeping, but still considerably fewer awkward emails, which is more important.
Review attach rate and discount depth together
Teams tend to report these separately, and separately they both look encouraging. A bundle taken by 70% of new accounts reads as a win until you notice the attached component is being discounted to nothing in order to get it there.
Looking at the two numbers side by side each quarter will tell you which bundles are genuinely wanted and which ones are only being used to get deals over the line. Both are useful to know, provided you know which is which.
A solution right here for you: Zoho Billing
A bundle that's configured beautifully will still cause trouble if the billing system underneath it can't handle a customer with wild customization expectations. The configuration logic and the billing logic need to agree on what a bundle is, otherwise the sales and finance teams' synchronization takes a hit.
So when you are mapping out your next bundling experiment, trace a sample deal all the way through: quote, order, invoice, change order, renewal. If the trail breaks anywhere after signature, you know the next step and our experts are here to assist you.
Zoho Billing handles bundled products, hybrid pricing, mid-cycle changes, and revenue recognition in one place, so what your sales team configures is what your finance team sees clearly the day a purchase happens.
Talk to our experts today who can walk you through setting up various bundles in Zoho Billing.
Frequently Asked Questions
The three common models are fixed bundles (components, quantities, and price all locked), configurable bundles (a fixed parent with flexible sub-components within set rules), and nested bundles (bundles contained inside a parent bundle).
Use a fixed bundle when the same combination sells repeatedly and speed matters. Choose a configurable bundle when buyers need different shapes of the same product, such as different company sizes. Go nested when you need to package a complex offering with reusable sub-bundles, accepting that pricing errors become harder to debug.
Bundles let you sell an ecosystem instead of a single item, which makes the purchase simpler for buyers and builds natural cross-sell and up-sell paths. They also improve retention, since customers are tied into a broader offering, and they speed up quoting. That said, it should be a case-to-case analysis. If buyers want only one component or your products have little in common, individual selling can serve you better.
A CPQ system lets you codify bundle rules such as mandatory versus optional items, quantity limits, and mutual exclusions, so errors are caught at the configuration screen rather than after the quote is sent. It shows the customer one clean price while tracking each component separately, which makes mid-term changes and proration easier. It also supports bundle-level discount limits and versioning, so edits don't alter live contracts.
Start with purchase patterns: If a particular combination is already being bought together repeatedly, it's a strong candidate for a bundle. Keep the components complementary, so one product naturally pulls the other along, such as implementation services with a platform subscription or a data add-on with an analytics tier. Then review attach rate and discount depth together to confirm that customers genuinely want each component and that none is being given away just to close deals.
