Multi-Tenant CPQ
Merger closed Friday. IT inherited a fourth CPQ contract instead of a second tenant. Mercura hosts isolated brand environments on one platform with separate catalogs, rules, pricing, and API keys.
The challenge
Merger closed Friday. IT inherited a fourth CPQ contract instead of a second tenant.
A group that sells industrial and specialty gas equipment across welding supply, medical oxygen, and engineered blend systems completed an acquisition of a regional cylinder and regulator brand. Each legacy division already ran its own CPQ instance from a different vendor. Central IT was asked to connect all four quoting flows to one SAP instance while keeping medical pricing invisible to welding distributors and acquisition-brand discount tables out of legacy rep screens.
Provisioning another full CPQ contract for the acquired brand duplicated vendor fees, user sync jobs, and patch windows. Running everyone on a single instance without tenant walls meant a regional sales manager opened a quote template and saw another division's customer price book. Channel partners for the acquired brand needed their own catalog and approval rules, but spinning up separate infrastructure per partner was not scalable.
API-first CPQ documents REST parity between admin screens and integration code. Headless CPQ runs Mercura logic behind your own UI. The CPQ SDK removes auth boilerplate in typed clients. Developer tools provide sandbox and webhook debugging. Multi-tenant CPQ is different: one Mercura deployment hosts isolated tenant environments, each with its own product catalog, configuration rules, pricing structure, user base, and API credentials, while central platform teams maintain one upgrade cycle, one administration console, and shared ERP connectors.
Inquiry to config to price to approval to order should not multiply vendor contracts every time the group adds a brand, region, or partner program.
How it works
How Mercura multi-tenant CPQ works
Platform administrators create tenant environments inside a single Mercura deployment. Each tenant receives an isolated data store: catalog, rules, price lists, users, roles, and audit history remain invisible to other tenants. Tenant-scoped API credentials let integration teams connect division-specific dealer portals or ERP mappings without sharing secrets across brands. A central console provisions tenants, assigns administrators, configures optional shared reference data, and monitors usage. Platform upgrades apply once and reach every tenant on the same schedule. Your team defines tenant boundaries, maps brands to credentials, and tests cross-tenant isolation before onboarding acquired catalogs. Mercura does not replace corporate IAM design or ERP chart-of-accounts mapping workshops.
What's included
What multi-tenant CPQ covers
- Isolated catalog, rules, pricing, and user data per tenant
- Central administration console for tenant provisioning and monitoring
- Tenant-scoped API credentials for division-specific integrations
- Independent role and permission configuration per tenant
- Shared platform maintenance with one upgrade cycle
- Optional shared reference libraries across selected tenants
- Cross-tenant reporting for enterprise-level quote analytics
- Tenant creation via API for programmatic environment rollout
The difference
Enterprise CPQ before and after multi-tenant consolidation
- New brand means new vendor contract and integration project
- Single-instance workarounds leak pricing across divisions
- Partner portals require duplicate infrastructure or shared secrets
- IT runs multiple patch cycles and user sync jobs
- No group-wide view of configuration and quote activity
- Acquired brand tenant provisioned without a fourth CPQ contract
- Reps and partners see only their tenant catalog and price lists
- Division ERP and portal integrations use tenant-scoped credentials
- One platform upgrade covers welding, medical, and specialty brands
- Central team monitors quote volume across tenants from one console
Real-world application
Example workflow: post-merger gases group on one Mercura deployment
An industrial gases group consolidated four legacy CPQ systems after acquiring a regional cylinder brand. Mercura tenants were created for welding supply, medical oxygen, engineered blends, and the acquired brand, each with isolated catalogs and approval rules. Central IT maintained one SAP connector with tenant-scoped API keys routing order lines to the correct company code. A welding distributor never saw medical tariff tables. Platform patches applied once per quarter instead of four vendor cycles. Group finance opened cross-tenant quote reports without requesting exports from each division IT team.
Business impact
Why multi-tenant CPQ is platform consolidation, not shared login screens
Multi-tenant CPQ gives enterprise groups and SaaS operators division-grade isolation on one maintained platform. It complements API-first integration, headless front ends, SDK clients, and developer sandbox tooling. Mercura does not replace tenant boundary decisions, partner contract terms, or ERP entity mapping. Someone must define which catalogs belong in which tenant and verify isolation in testing. If the pain is "every acquisition adds another CPQ contract", multi-tenant CPQ aligns inquiry, configuration, price, approval, and order across brands without multiplying infrastructure.
Provision a new brand tenant with isolated catalog while central admin keeps one ERP connector
Book a demo and walk tenant creation, division-scoped API credentials, and cross-tenant isolation until acquired catalogs onboard without a new vendor contract.
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.