Product Bundling
Stop rebuilding the same solution from scratch on every quote. Offer commercial packages with clear scope and package pricing for inside sales and dealers.
Bundling · session
Motion-control commercial offer
Core product selection suggests / adds companion lines.
Core
Accessories
Services
Separate sellable lines · one commercial offer (not one engineered product)
What this controls
As a kit
Pre-defined packages instead of ad hoc line lists
Package price
One commercial price for the agreed scope
On the quote
Bundle lines visible before approval and order
The challenge
You sell solutions. Your quotes still look like spare-parts lists.
Customers ask for a working cell, a treatment skid, or a commissioning-ready set. Sales answers with twelve separate SKUs chosen from memory. One cooler is missing. One torch tip set is wrong. The price looks sharp until the second quote arrives to fill the gaps.
Inside sales knows the usual package by heart. New reps and dealers do not. They under-scope to win the deal, or over-scope and lose it. Marketing publishes starter / standard / complete kits that never appear consistently in the configurator.
Dependency logic pulls technical must-haves when you pick a trigger option. Bundling is different: it is how you package and price a commercial offer. Without bundles in CPQ, package strategy stays in slide decks while quotes stay line-by-line.
Inquiry to config to price to approval to order should carry a clear kit scope, not a scavenger hunt across the catalog.
How it works
How Mercura turns kits into selectable packages
Product and sales ops define fixed or lightly configurable bundles in Mercura: a named package with included lines and a package price (flat, discounted sum, or formula). A rep or dealer selects the kit, sees the included scope on the quote, and can add approved options inside the package rules. Rule-triggered adds can still attach technical companions; the bundle is the commercial wrapper. Dependencies keep configurations complete. Constraints keep them legal. This page is how you sell agreed kits without rebuilding them every time. Bundles need an owner when kits or prices change.
Bundle completeness
Commercial package, not an assembly tree
Incomplete
- ✓ Controller
- ✓ Motor
- ✓ Cable
- ✕ Commissioning
PACKAGE INCOMPLETE
Suggested: Add commissioning service
Complete
- ✓ Servo motor
- ✓ Power + encoder cables
- ✓ Commissioning
- ✓ Support
COMPLETE SOLUTION
What's included
What product bundling covers
Package
- Fixed kits sold as a named commercial package
- Configurable packages with limited option choices inside the kit
Complete
- Package pricing: flat, discounted sum, or formula-based
- Included lines visible on the quote for transparency
Price
- Optional upsell kits surfaced in guided flows
Trace
- Same packages for inside sales, dealers, and portals
- Compatibility checks inside and across packages
- Reusable package templates by segment or region
The difference
Quoting kits before and after bundling in CPQ
Line-by-line assembly
- 01 Reps rebuild the same package from memory
- 02 Dealers miss accessories that belong in the kit
- 03 Package prices calculated inconsistently in Excel
- 04 Starter / standard / complete kits exist only in brochures
- 05 Follow-up quotes fill gaps after the first PDF
With Mercura
- 01 Named kits selectable in the configurator
- 02 Package price and included scope on one quote
- 03 Dealers and reps sell the same published packages
- 04 Approved options added inside package rules
- 05 Kit updates published when commercial packages change
Real-world example
Example workflow: welding system packages
A welding equipment maker sells power sources that are almost always quoted with a cooler, torch, and wear-part starter set. Inside sales used to add those lines by habit and still missed items on busy days. After defining starter and complete packages in Mercura, reps select a named kit, the included lines and package price appear on the quote, and only approved options can extend the package.
Business impact
Why bundling is a commercial layer, not just a BOM trick
Product bundling is how manufacturers turn a catalog into sellable offers: clear scope, package pricing, fewer incomplete first quotes. It complements dependency logic (technical must-haves) and constraints (hard stops). Mercura does not invent your commercial strategy or replace ERP kit masters if those remain the system of record for manufacturing. Someone must own package definitions and prices when offers change. For teams whose channel keeps rebuilding the same solution line by line, putting kits in CPQ keeps inquiry, configuration, price, approval, and order aligned with how you actually want to sell.
Business impact
More complete solutions
Packages keep companion products and services on the quote.
Consistent upsell
Fixed, dynamic, and rule-triggered kits share one commercial path.
Fewer missing package items
Completeness checks surface before approval.
Compare
Modular configuration vs product bundling
Modular
Modules inside one product boundary
[Base + Head + Controls] = MACHINE
Bundle
Multiple sellable products/services · one commercial offer
Machine + Installation + Spare kit + Service = OFFER
Configuration map
Product definition → rules orchestration → commercial packaging → valid configuration, price, and BOM
Product definition
Logic
Commercial packaging
Output
Valid configuration · Price · BOM
Complete package · all lines on quote
See a named kit land on the quote with package price
Book a demo and select a commercial package until included lines and pricing show before approval.
Let’s build together.
We empower manufacturers to master product modeling, streamline quoting process, reduce errors, and ultimately deliver the tailored solutions that customers demand.