Configuration Governance
Six CPQ admins could edit production rules. Staging existed on paper; everyone published directly.
The challenge
Six CPQ admins could edit production rules. Staging existed on paper; everyone published directly.
An industrial UPS and power conditioning OEM maintains voltage, bypass, and battery cabinet rules that dealers configure against in production CPQ. Policy says product managers draft in staging and a small release group publishes on a schedule. In practice, consultants, sales ops, and junior engineers share admin login and save straight to production because staging feels like an extra click.
A contractor adjusted a voltage band constraint on Tuesday to unblock one dealer demo. By Thursday, twelve open quotes used the wrong input range before inside sales noticed mismatched SKUs on the PDF. Nobody could say who published the change or revert without rebuilding the rule by hand from memory.
Approval-workflows pages route edits through named reviewers before publish. Audit-log pages record actions after they happen. Access-control pages manage who can log in. Configuration governance is different: it separates who may author rules in staging from who may publish to production, keeps production logic stable while drafts evolve, and preserves version history for rollback.
Inquiry to config to price to approval to order depends on configuration logic that does not change under every admin login. That requires policy-backed authoring, not a shared production password.
How it works
How Mercura governs configuration rule changes
Product ops assign roles in Mercura: authors create and edit rules in staging where dealers cannot see drafts; publishers move approved changes to production on a schedule or after workflow sign-off. Every save creates a version record with author, timestamp, and summary. Rollback restores a prior production state without manual rebuild. Change preview shows which open configurations would behave differently if a draft publishes. Approval-workflows can gate the publish action; this framework defines where editing happens and who holds publish keys. Someone must keep role assignments current when contractors rotate off projects.
What's included
What configuration governance covers
- Staging environment for rule authoring away from production CPQ
- Separate author and publish permissions by role
- Version history on every configuration rule change
- One-action rollback to a previous production version
- Change impact preview before publish is requested
- Scheduled publish windows for off-hours releases
- Change log with author, time, and summary on each edit
- Works with approval workflows and audit logs on publish events
The difference
Rule changes before and after configuration governance
- Any admin saves rule edits straight to production CPQ
- Staging documented in policy but skipped in daily work
- Bad rule changes affect open quotes before anyone notices
- Rollback means rebuilding logic from memory or old exports
- Investigations start with who had admin access, not what changed
- Authors edit in staging; production CPQ stays stable until publish
- Only publishers release changes on schedule or after approval
- Version history shows who changed which rule and when
- Rollback restores prior production logic without manual rebuild
- Impact preview surfaces affected configurations before publish
Real-world application
Example workflow: UPS voltage rule in staging
An OEM of three-phase UPS modules, static switches, and battery cabinets sold through dealer configurators. A contractor widened allowed input voltage in production to close a demo. Open quotes across two regions picked up the wrong band until product management traced the issue to an unaudited admin save. After Mercura configuration governance, authors edit voltage and bypass rules only in staging. Publishers release on Tuesday maintenance windows after engineering checks diff preview. When a similar request came in, the draft stayed in staging until review, rollback remained one click away, and dealers never saw half-tested logic in production CPQ.
Business impact
Why configuration governance protects the logic quotes depend on
Configuration governance keeps mission-critical CPQ rules from changing under every admin session. It complements approval routing, audit trails, access control, and version-control views. Mercura does not replace your engineering change process or quality documentation outside CPQ. Someone must define author and publisher roles and retire access when staff leave. If the pain is "everyone with admin can break production rules", staging plus publish permissions in CPQ align inquiry, configuration, price, approval, and order with logic sales and manufacturing can trust on every quote.
See configuration rules edited in staging, published on your terms
Book a demo and walk through author versus publish roles with rollback and diff preview on a rule change.
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.