- Features > Multi Tenant CPQ
Multi-Tenant CPQ
Deploy one Mercura instance across multiple business units, brands, or customer-facing environments. Each tenant operates with complete data isolation while sharing a single maintained platform.
Full isolation
Per-tenant data and configuration
Single admin
One platform, multiple environments
Any number
Business units or customer groups
The Challenge
Enterprise Manufacturers Need CPQ Across Multiple Business Units
Large manufacturers typically operate multiple business units, product divisions, or regional organisations — each with distinct product portfolios, pricing structures, and customer bases. Deploying a separate CPQ instance per business unit creates significant overhead: multiple vendor contracts, separate IT maintenance cycles, separate user management systems, and no shared learnings across the organisation.
Running a single CPQ instance without tenant separation creates different problems: data from one business unit is visible to others, configuration rules from one division can conflict with another, and different pricing structures cannot coexist cleanly without complex workarounds.
For manufacturers operating channel partners or white-label product programs, the same challenge emerges at the customer level — each partner needs their own isolated configuration and pricing environment, but maintaining separate instances for each partner is operationally untenable.
The result is either an underinvestment in CPQ capability for secondary business units, or a costly proliferation of separately managed CPQ deployments.
How It Works
How Multi-Tenant CPQ Works in Mercura
Mercura's multi-tenant architecture allows administrators to create and manage multiple isolated tenant environments within a single Mercura deployment. Each tenant has its own product catalog, configuration rules, pricing structure, user base, and data store — completely isolated from other tenants at the data layer. A central administration console allows platform administrators to manage all tenants, provision new environments, configure shared resources, and monitor usage across the deployment. Tenants share the underlying platform infrastructure and benefit from the same update and maintenance cycle — reducing total cost of ownership compared to separate instances.
What's Included
Key Capabilities
- Complete data isolation per tenant — no cross-tenant data visibility
- Per-tenant product catalog, configuration rules, and pricing structure
- Per-tenant user management with independent role and permission configuration
- Central administration console for cross-tenant management and provisioning
- Shared platform maintenance — all tenants updated simultaneously
- Tenant-level API credentials for independent integration per business unit
- Cross-tenant reporting for enterprise-level aggregated analytics
- New tenant provisioning via API for programmatic environment creation
The Difference
Before and After Multi-Tenant CPQ
- Separate CPQ instances per business unit — high cost and maintenance overhead
- Single-instance deployment requires complex workarounds for data separation
- Channel partner environments require separate deployments or data commingling
- IT team maintains multiple update and patch cycles
- No enterprise-wide CPQ visibility — each unit operates as a silo
- Single deployment supports unlimited business units with full isolation
- Clean data separation per tenant — no workarounds or custom segmentation logic
- Channel partner environments provisioned in minutes from central console
- Single platform maintenance cycle covers all tenants simultaneously
- Enterprise analytics aggregated across all tenants from one platform
Real-World Application
Example Use Case: Diversified Industrial Group
A diversified industrial group with four operating divisions — each selling different product categories to different customer segments — had been running four separate CPQ systems from two different vendors. The IT cost of maintaining four separate instances, managing four separate update cycles, and operating four separate integrations with the group's shared ERP was significant. After consolidating onto Mercura's multi-tenant platform, each division received a fully isolated tenant environment with their own product rules, pricing, and users. Central IT managed a single platform integration with the group ERP. Platform maintenance became a shared overhead rather than a per-division cost. Total CPQ platform cost fell by 38% while each division gained capabilities they had not had in their previous single-vendor deployments.
Quote turnaround dropped from 3 days to under 4 hours.
Business Impact
Why Multi-Tenant CPQ Matters
Multi-tenant CPQ gives enterprise manufacturers the operational efficiency of a shared platform without sacrificing the isolation that each business unit requires. It eliminates the proliferation of separately managed CPQ instances, concentrates administrative overhead in a central function, and provides enterprise-level visibility across the entire organisation's quoting and configuration activity. For manufacturers with channel programs, it enables a scalable approach to partner portal deployment that can grow with the partner network without proportionally growing IT overhead.
Consolidate Your CPQ Deployments
Book a demo to see how Mercura's multi-tenant architecture supports multiple business units from a single, centrally managed platform.
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.