If you’re trying to boost your average order value and make your sales team’s life easier, product bundles are one of the simplest tactics in the book. But actually setting them up—especially in a complex CPQ system like Experlogix—can be more tedious than it should be. This guide is for admins, sales ops, or anyone who’s tasked with wrangling Experlogix to make upselling smoother.
We’ll go step-by-step through bundle configuration, flag the gotchas, and share some blunt advice: don’t overcomplicate things. Let’s get into it.
What Are Product Bundles in Experlogix?
Let’s get clear on terms first. In Experlogix, a product bundle is a collection of related products or services that you sell together, often at a discount or with extra features, to encourage customers to buy more. The idea is to make buying easy, add value, and—frankly—raise your deal size.
Bundles can be: - Static: Same group of products every time (like a “Starter Kit”). - Configurable: Customer (or rep) can pick and choose from a set of options (like a computer with pick-your-RAM).
You can use bundles to upsell by suggesting high-margin add-ons or nudging customers toward pricier packages.
Before You Start: Prep Work That’ll Save You Headaches
You’ll move a lot faster if you do a bit of homework upfront:
- Get your product data clean: If your catalog is a mess, bundles will be a mess. Name things consistently.
- Know your upsell targets: What do you actually want customers to buy more of? Don’t bundle random junk just because you can.
- Map out bundle logic: Draw it on a whiteboard. What’s required? What’s optional? Any dependencies?
- Double-check pricing rules: Bundles can break your pricing if you’re not careful.
Pro tip: If you’re inheriting an existing Experlogix setup, review any current bundles first. It’s common to find zombie bundles no one uses.
Step 1: Set Up Your Bundle Parent Product
This is the anchor for your bundle. In Experlogix, you’ll need to create a “parent” product that represents the whole bundle.
How to do it: 1. In Experlogix Admin, go to Product Maintenance. 2. Create a new product. - Give it a clear name (“Premium Laptop Bundle,” not “Bundle 1”). - Set the product type to “Bundle” if available; otherwise, flag it in the description. 3. Add a description. Be specific about what’s included and who it’s for. 4. Set pricing. Decide if the bundle price is fixed or calculated from the sum of parts.
Honest take: Resist the urge to make fifteen bundles at once. Start with your top seller and see how it performs.
Step 2: Add Child Products (Bundle Components)
Now, link the products or options that belong in the bundle.
How to do it: 1. Open your bundle parent product. 2. Navigate to the Bundled Products, Child Items, or similar tab (naming varies by version). 3. Add each product you want in the bundle. - You’ll usually search and select existing products in your catalog. - Set quantity defaults if needed.
Required vs. Optional: - For static bundles, set all as “required.” - For configurable bundles, mark optional items and set any selection rules.
Reality check: Only bundle products that actually make sense together. “Printer + Pool Float” isn’t a bundle, it’s a clearance rack.
Step 3: Define Bundle Rules and Constraints
Here’s where most people either make bundles magic—or totally over-engineer them. You can add logic that guides what can be picked together, sets minimums/maximums, and steers the user.
Common rules to set: - Required selections: E.g., customer must pick a charger with a laptop. - Maximum allowed: E.g., only one extended warranty per device. - Dependencies: E.g., if they pick Product A, Product B becomes available.
How to do it: 1. In the Bundle Rules or Constraints section, start adding rules. 2. Use plain logic: “If [Option] is selected, then [Other Option] is required/disabled.” 3. Test as you go. Don’t assume you got it right—actually run through a quote.
Heads up: Don’t go wild with rules unless you have a real business reason. Every new constraint is a future support ticket.
Step 4: Set Up Pricing for the Bundle
Pricing is where bundles can get tricky. You’ve got a few choices:
- Fixed Price: The bundle always costs the same, no matter which options are chosen.
- Roll-up Price: The bundle price is the sum of the selected child items.
- Discounted Price: The bundle applies a discount to the total of the parts.
Best practices: - Decide if discounts are visible: Will reps see how much the bundle saves the customer? - Avoid “mystery math”: If no one can explain how pricing works, you’ll get complaints. - Watch for double-discounting: If both parent and child items have discounts, Experlogix can stack them unless you specifically block it.
How to do it: 1. Head to the Pricing section of the bundle parent product. 2. Set the pricing method. 3. If discounting, enter the percentage or dollar amount. 4. Preview pricing with sample selections.
Pro tip: Run a few test quotes with edge cases—like maxing out every optional add-on or picking no options at all.
Step 5: Fine-Tune the User Experience
Upselling only works if the bundle is easy to understand and quick to configure. Don’t bury users in options or make them click through 12 screens.
Tips: - Use clear labels: “Add a Mouse ($15)” not “Option 2b.” - Group related options: Accessories, warranties, etc. - Add tooltips or descriptions: Briefly explain why someone would want this add-on. - Set smart defaults: Pre-select the most popular or high-margin options if it makes sense.
Pitfall: Don’t require users to pick something for every single option unless it’s truly needed. Decision fatigue kills upsell rates.
Step 6: Test Your Bundle (and Have Others Test, Too)
This is the step most people rush—and regret later.
Checklist: - Can you add the bundle to a quote without errors? - Does the pricing make sense? Do discounts apply as expected? - Are the required/optional rules working? - Can a salesperson easily understand what they’re offering?
What to watch for: - Edge cases: What if someone tries to pick every option? None? - Mobile/tablet usability: If your sales team works on the go, test there too. - Reporting: Make sure bundles show up correctly in sales reports.
Reality: You will find something broken. That’s normal. Fix it, then move on.
Step 7: Train Sales (But Keep It Simple)
Salespeople are not going to read a 20-page manual. Give them a short cheat sheet:
- What’s in each bundle
- Who should get offered which bundle
- How to tweak options (if allowed)
- What to say about savings or value
If you see reps ignoring bundles, ask why. Often, it’s because the configuration is confusing or takes too long.
What Works, What Doesn’t, and What to Ignore
Works: - Bundling logical add-ons (warranties, accessories, setup services) - “Good/Better/Best” tiered bundles - Pre-selecting the most popular configurations
Doesn’t Work: - Bundling stuff nobody actually wants together - Forcing too many required choices - Making pricing a black box
Ignore: - Overly complex dependency logic unless you really need it - Bundling just for the sake of having more bundles
Wrapping Up: Keep Bundles Simple, Iterate Often
You don’t need to launch with every possible bundle or rule. Start with one or two solid, logical bundles that make buying easier and upselling more natural. Watch how they perform, talk to your sales team, and tweak as you go. The less friction you put between your customer and a “yes,” the better.
If you keep the setup straightforward—and avoid the urge to build a bundle for every scenario—you’ll save yourself a ton of pain, and you’ll actually see results faster.