Configuration Version Control
A string-sizing rule edit blocked a high-volume inverter combo. Restoring the prior version took a day of spreadsheet diff because CPQ kept no version history.
The challenge
A string-sizing rule edit blocked a high-volume inverter combo. Restoring the prior version took a day of spreadsheet diff because CPQ kept no version history.
A solar racking and inverter OEM maintains module compatibility, string sizing, and mounting rail rules that dealers configure in CPQ. Product logic evolves weekly as new panel wattages and inverter SKUs ship. When a combination stops working, inside sales needs to know exactly which rule version changed and what the previous state looked like, not just that something broke in production.
Without version history, product ops exports rule tables to spreadsheets and compares columns by hand. The engineer who wrote the original constraint left two years ago. Rollback means retyping conditions from an old PDF export and hoping nothing else shifted in the meantime. A single bad edit can block dealer quotes until someone reconstructs logic from email attachments.
Configuration-governance pages separate authors from publishers and keep edits in staging. Audit-log pages record who performed actions after the fact. Access-control pages define login rights. Configuration version control is different: it keeps a timeline of every rule change, lets teams diff any two versions in the editor, and restores a prior state in one action when production behaviour regresses.
Inquiry to config to price to approval to order needs product logic that can evolve quickly and revert safely when a change misfires, not a rule set that only moves forward because nobody can see what changed yesterday.
How it works
How Mercura version control tracks configuration rule history
Every save to a configuration rule in Mercura creates a version record with author, timestamp, summary, and optional change notes. The rule editor shows a timeline of all versions. Select any two versions to open a side-by-side diff of conditions, options, and dependencies that changed. Rollback restores a prior version as the current state; the rollback itself becomes a new version entry. Named snapshots tag major releases such as new panel families or price book updates. Branch-style drafts let teams test rule changes before they affect dealer configurators. Governance and approval pages control when changes publish; version control preserves the history teams need to compare, explain, and undo.
What's included
What configuration version control covers
- Automatic version record on every configuration rule save
- Timeline view with author, date, and change notes per version
- Side-by-side diff between any two rule versions
- One-click restore to a prior configuration state
- Named snapshots for product launches and price book milestones
- Draft branches for testing rule changes before production impact
- Restore events logged as new versions in the same chain
- Version export for engineering documentation and compliance files
The difference
Configuration rule changes before and after version control
- Rule changes overwrite production with no comparable prior state
- Investigations compare manual exports instead of in-editor diffs
- Rollback means retyping logic from old files or email attachments
- Rationale for constraints lost when authors leave the organisation
- Dealer quotes blocked until someone rebuilds the previous rule by hand
- Every edit stored in a searchable version timeline
- Diff view shows exactly which conditions changed between versions
- Restore prior state in one action without manual rebuild
- Change notes capture why a constraint was set that way
- Production regressions corrected in minutes instead of days
Real-world application
Example workflow: inverter string rule regression
An OEM of roof mounting rails, string inverters, and optimizer modules sold through regional dealers. A product manager updated string-sizing compatibility for a new high-wattage panel family. Within hours, dealers reported that a popular three-inverter string configuration was no longer selectable. Product ops opened Mercura version control, compared the latest save against the prior week's version, and found one extended condition that excluded valid combinations. Rollback restored the previous rule state in one action. Dealers resumed quoting the same afternoon. Without version history, the team had spent the previous quarter comparing spreadsheet exports for a similar incident.
Business impact
Why version control is the safety net complex product logic needs
Configuration version control lets product teams evolve CPQ rules quickly because every change is reversible and documented. It complements publish governance, audit trails, access permissions, and approval routing. Mercura does not replace your external engineering document control system or Git workflows outside CPQ. Someone must write change notes when constraints are non-obvious. If the pain is "we changed a rule and cannot get back to what worked last week", version history and diff in CPQ align inquiry, configuration, price, approval, and order with logic teams can inspect and restore on every quote.
Diff rule versions and restore a prior state in one action
Book a demo and walk through version timeline, side-by-side diff, and rollback on a configuration rule your dealers depend on.
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.