- Features > Configuration Governance
Configuration Governance
Protect your product configuration rules with structured governance. Control who can author changes, require review before publication, and maintain a full change history for every rule in the system.
Zero
Unreviewed changes to production rules
Full history
Every configuration change versioned
Role-based
Authoring and publishing permissions
The Challenge
Configuration Rules Can Be Modified Without Review or Traceability
Product configuration rules are mission-critical business logic. A rule that permits an invalid product combination — or blocks a valid one — has immediate downstream consequences: incorrect orders shipped, valid deals lost, or manufacturing disruptions caused by configurations the factory cannot build.
In most CPQ deployments, configuration rules can be modified by any user with administrative access, with changes taking immediate effect in the production environment. There is no review gate, no change preview, and no rollback mechanism if a change introduces unintended behaviour.
When a configuration error is discovered — a customer has been able to select a combination that cannot be manufactured — tracing the root cause requires manual investigation of who made changes and when. Without structured change history, this investigation is slow and often inconclusive.
For manufacturers with complex, interdependent rule sets, the risk of uncontrolled modification grows with every person who has editing access. A well-intentioned change to one rule can have cascading effects on others that are not immediately apparent.
How It Works
How Configuration Governance Works in Mercura
Mercura's configuration governance framework separates authoring from publishing. Users with authoring permissions can create and modify rules in a staging environment where changes are visible but not yet live. Publishing a change to production requires a separate permission and, optionally, a formal approval from a designated reviewer. All changes are versioned — every modification creates a new version record with the author's identity, the timestamp, and the content of the change. Production rules can be rolled back to any previous version with a single administrative action. A change preview function shows authors the impact of a proposed rule change on existing configurations before it is submitted for review.
What's Included
Key Capabilities
- Staging environment for rule authoring — changes not live until published
- Separate authoring and publishing permissions by role
- Change approval workflow for publication to production
- Full version history for every configuration rule
- One-click rollback to any previous version
- Change impact preview — see affected configurations before publishing
- Change log with author, timestamp, and change summary for all rule modifications
- Scheduled publication — stage changes for off-hours deployment
The Difference
Before and After Configuration Governance
- Rule changes go live immediately with no review — errors affect live customers
- Any admin can modify production rules — change risk grows with team size
- No version history — rolling back requires manual reconstruction
- Change investigation slow and inconclusive without structured logs
- Impact of rule changes on existing configurations unknown before publishing
- All changes staged and reviewed before production — errors caught before they affect customers
- Authoring and publishing permissions separated — change risk controlled
- Full version history — any previous state restorable in seconds
- Every change attributed and timestamped — investigation takes minutes not days
- Change impact preview surfaces downstream effects before publishing
Real-World Application
Example Use Case: Aerospace Component Manufacturer
An aerospace component manufacturer experienced a production disruption when a CPQ rule change inadvertently permitted a material combination that violated a manufacturing constraint. The change had been made by an engineer who did not realise the rule was connected to a downstream validation. There was no staging environment, no review process, and no version history — the change was live within seconds of being saved. The incident prompted the adoption of Mercura's configuration governance framework. All subsequent rule changes were made in staging, reviewed by a second engineer, and published on a controlled schedule. In the 18 months following adoption, zero production-impacting rule errors were recorded.
Quote turnaround dropped from 3 days to under 4 hours.
Business Impact
Why Configuration Governance Matters
Configuration rules are the most consequential business logic in a CPQ system. They determine what can be manufactured, what can be quoted, and what reaches the customer. Uncontrolled modification of this logic is a source of commercial and operational risk that scales with the complexity of the product portfolio and the size of the team with editing access. Mercura's configuration governance framework reduces this risk to near zero by ensuring that every change is staged, reviewed, approved, and versioned before it affects production.
Protect Your Configuration Rules
Book a demo to see how Mercura's governance framework prevents uncontrolled changes from reaching your production configurator.
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.