- Features > Configuration Version Control
Configuration Version Control
Maintain a complete version history of your product configuration rules. Compare any two versions, understand what changed and why, and restore any previous state with a single action.
Every version
Saved automatically on every change
One click
Rollback to any previous state
Zero
Configuration state ever permanently lost
The Challenge
Configuration Rule Changes Are Irreversible Without Manual Backup
Product configuration rules evolve continuously as products are updated, new variants are added, and manufacturing constraints change. Every change is an opportunity for error — and without version control, every error in a live rule set is difficult to reverse.
When a configuration change causes unexpected behaviour — a previously valid product combination becomes blocked, or a new invalid combination becomes selectable — the first task is to identify exactly what changed. Without version history, this requires manual investigation: comparing current rules against previous states reconstructed from memory or informal notes.
Rolling back a problematic change without version control is itself a manual process — re-entering the previous rule state, hoping that nothing else changed in the intervening period, and re-testing to confirm the previous behaviour has been restored.
For manufacturers with complex rule sets built up over years, the lack of version control also means that institutional knowledge about why rules were structured in a particular way is lost when the person who created them moves on. The rule set is opaque — it can be read but not understood in context.
How It Works
How Configuration Version Control Works in Mercura
Every change to a configuration rule in Mercura creates a new version record automatically. Version records include the content of the rule before and after the change, the identity of the user who made the change, the timestamp, and any notes added by the author to explain the change rationale. The version history for any rule is accessible from the rule editor interface — showing a timeline of all versions with author and date. Any version can be compared against any other to produce a structured diff showing exactly what changed. Rollback to any previous version is a single administrative action, with the rollback event itself captured as a new version record.
What's Included
Key Capabilities
- Automatic version creation on every configuration rule change
- Full version history with author, timestamp, and change notes
- Side-by-side version comparison with structured diff display
- One-click rollback to any previous version
- Rollback events logged in version history — full chain of changes preserved
- Named versions for major milestones — product launches, price book updates
- Branch-based authoring for testing rule changes before production deployment
- Version export for external documentation and compliance records
The Difference
Before and After Configuration Version Control
- Configuration changes irreversible without manual backup process
- Identifying what changed after an error requires manual investigation
- Rolling back requires re-entering previous state — slow and error-prone
- Rationale for rule structure lost when authors leave the organisation
- No comparison between current and previous configuration states
- Every change versioned automatically — rollback always available
- Error investigation completed in seconds — diff shows exactly what changed
- Rollback completed in one action — previous state restored instantly
- Change notes capture rationale — institutional knowledge preserved in the system
- Any two versions comparable in seconds — changes transparent and traceable
Real-World Application
Example Use Case: Precision Instrumentation Manufacturer
A precision instrumentation manufacturer updated a set of compatibility rules for a new sensor variant. Within 24 hours of the change going live, the sales team reported that a high-volume product combination was no longer selectable. The product team investigated using Mercura's version control, identifying the exact rule change that had caused the issue within five minutes — a condition had been accidentally extended to exclude configurations that should have remained valid. A rollback to the previous version restored correct behaviour within ten minutes of the problem being identified. Total impact: one blocked sales session. Without version control, the investigation and manual restoration would have taken several hours and introduced further risk of additional errors during the manual correction process.
Quote turnaround dropped from 3 days to under 4 hours.
Business Impact
Why Configuration Version Control Matters
Version control for configuration rules is the safety net that makes confident evolution of complex product logic possible. Without it, every rule change carries the implicit risk of an unrecoverable error. With it, every change is reversible, every decision is traceable, and the history of the rule set is a permanent record that survives team changes, product updates, and system migrations. Mercura's configuration version control gives product and IT teams the confidence to evolve rules quickly — knowing that any mistake can be corrected in seconds.
Never Lose a Configuration State Again
Book a demo to see how Mercura version control makes every configuration change safe, traceable, and reversible.
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.