- Features > Self Maintained Product Configuration
Self-Maintained Product Configuration
Maintain your product configuration independently. Mercura puts configuration rule authoring, testing, and deployment in the hands of your team — with no vendor involvement required for routine updates.
100%
Configuration ownership with your team
Zero
Vendor dependency for product updates
Same day
From product change to live configuration
The Challenge
Product Configuration Requires Constant Vendor Involvement
Many CPQ implementations are delivered on the assumption that the vendor or implementation partner will remain involved for the life of the system. Every product update, every pricing change, every new constraint is managed through a support ticket or change request — at vendor rates, on vendor timelines.
This model fails to scale. A manufacturing business with an active product portfolio generates configuration change requirements continuously. Routing every change through a vendor creates a permanent dependency that grows more expensive and more constrictive as the product portfolio grows.
Vendor involvement also introduces latency that costs deals. When a new product is not in the configurator yet because the vendor has not completed the configuration work, sales teams either sell incorrectly or cannot sell at all. The gap between product launch and CPQ availability is a recurring revenue leak.
Perhaps most significantly, vendor dependency for configuration means the business never truly owns its CPQ system. It is always one vendor relationship away from being stranded with a system it cannot maintain itself.
How It Works
How Self-Maintained Configuration Works in Mercura
Mercura is designed with the assumption that the customer team will own configuration from day one. The onboarding process includes configuration training for the product and pricing teams who will maintain the system. All configuration interfaces are designed for business users — product managers, sales operations leads, and pricing analysts. Mercura's support model provides access to technical expertise for platform issues and advanced integration questions, but routine configuration — adding products, updating rules, modifying pricing, creating templates — is handled entirely by the customer team without vendor involvement. No change requires Mercura's input unless the customer chooses to request it.
What's Included
Key Capabilities
- Full configuration interface for business users — no vendor involvement required
- Onboarding training programme for customer configuration team
- Comprehensive configuration documentation and knowledge base
- Template library — start from proven patterns rather than blank canvas
- Self-serve configuration testing in staging environment
- Configuration health monitoring — automated checks for rule conflicts and gaps
- Community and peer learning resources for configuration best practices
- Optional Mercura expert review for complex configuration challenges
The Difference
Before and After Self-Maintained Configuration
- Every configuration change routed through vendor — permanent dependency
- Product launches delayed until vendor completes configuration work
- Vendor costs grow with product portfolio complexity and change frequency
- Business never truly owns its CPQ system
- Configuration knowledge concentrated in external team — transfer risk high
- Business team owns all configuration — vendor uninvolved in routine updates
- New products configured and live same day as product launch
- Ongoing configuration cost near zero — internal resource only
- Business owns its CPQ system completely — no dependency risk
- Configuration knowledge built and retained in the business permanently
Real-World Application
Example Use Case: Agricultural Equipment Manufacturer
An agricultural equipment manufacturer had been paying their CPQ implementation partner approximately €8,000 per month for ongoing configuration maintenance — product updates, pricing changes, and constraint modifications. The partner was efficient, but the manufacturer was acutely aware of the dependency. A leadership change at the partner organisation caused a 6-week delay in a product launch when the person who understood their configuration was on leave and no one else at the partner had adequate context. After migrating to Mercura and completing a 3-day configuration training programme, the manufacturer's product team took over full configuration ownership. Monthly vendor spend for configuration dropped to zero. The first product launch under self-maintenance was live in the configurator on the same day as the commercial launch.
Quote turnaround dropped from 3 days to under 4 hours.
Business Impact
Why Self-Maintained Configuration Matters
Self-maintained product configuration is the difference between a CPQ system that the business controls and one that controls the business. When your team can update, test, and deploy configuration changes independently, product launches are faster, change costs disappear, and the CPQ system becomes a genuine competitive advantage rather than an expensive liability. Mercura is built to be owned by the people who understand the products — not by the people who built the platform.
Own Your Product Configuration
Book a demo to see how Mercura puts full configuration ownership in the hands of your team from day one.
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.