What maintenance is needed when products change every week?
Specify configurator maintenance for frequent catalogue changes, distinguishing editable data, application changes, tests and emergency corrections.
Table of contents
- Which changes can your team make?
- How should an update be tested?
- What happens to existing quotes and orders?
- What should a support agreement cover?
- Preparing a catalogue for Configurix
- Frequently asked questions
- Does every catalogue update need a developer?
- Does an annual support fee cover every update?
- How often should a configurator be updated?
Frequent catalogue changes need more than a reliable website. Before buying a configurator, agree who maintains product data, which changes need development, how updates are tested and what happens to existing quotes and orders. Ask suppliers to demonstrate the process using a real change from your range.
Which changes can your team make?
The answer depends on the project and its administration tools. Ask to see how an authorised user edits a description, adds a material option or updates a price. Establish who approves each change, whether translations need review and when an update becomes visible to customers.
A new 3D model, compatibility rule or integration mapping may require specialist work. Do not assume every change is editable in the same interface: record the agreed responsibilities and test them before launch.
| Catalogue change | Decision to agree |
|---|---|
| Description or material name | Editor, language review and publication |
| Price | Commercial approval, effective date and effect on open quotes |
| Compatibility rule | Product owner and tests for valid and invalid combinations |
| Frame profile or geometry | 3D asset preparation, visual review and affected components |
| ERP product code | Mapping owner and verification of downstream data |
How should an update be tested?
Choose a representative product and prepare the old and new data. In a test environment, check a valid configuration, a prohibited combination and a boundary case. Compare the visual result, price and data intended for the quotation or order system. Test on mobile too if customers or salespeople use it.
Agree who signs off and when changes are published. If a mistake reaches customers, the team needs a reporting route and a way to restore correct data. Test environments and rollback arrangements should be defined for the particular implementation.
What happens to existing quotes and orders?
Ask how saved projects, issued quotes and accepted orders are treated after a catalogue change. A new price or discontinued accessory should not silently become the original terms accepted by a customer. Agree when a revised quote is needed and who can approve a change to an order.
Discuss these decisions alongside configured-order management and the system holding the accepted record. Request a demonstration with your own product rather than relying on a general promise of version control.
What should a support agreement cover?
Compare included services, separately charged work and how changes are estimated. Agree the reporting channel, contacts and priorities: an error allowing an unsupported order may need a different response from a description correction.
A first response and a resolution are different commitments. Ask about escalation, data access and training for catalogue administrators. The actual support scope depends on what is agreed for your project.
Preparing a catalogue for Configurix
Gather your current product and option list, price rules, compatibility constraints, visual assets and examples of quotations. Identify the owners of technical data, pricing and integrations. Bring several recent changes to a discussion of the custom project so the team can define which tasks you want to perform internally and which need development.
Ask to follow one change from request through review and publication. This makes permissions, training and ongoing responsibilities easier to assess.
Frequently asked questions
Does every catalogue update need a developer?
Not necessarily. Trained administrators may be able to edit simple data if the implementation provides appropriate tools and permissions. Changes to logic, 3D models or integrations may need specialist work.
Does an annual support fee cover every update?
Not automatically. Check the service scope, limits, exclusions and pricing for new features and catalogue changes.
How often should a configurator be updated?
Match the schedule to your product changes and their commercial impact. Prices, availability and rules affecting valid orders may need a prompt response; less urgent edits can be grouped with your team’s agreement.
Book a private Configurix demo
Bring your product range, price list and a representative quote. We can define the configuration and sales workflow around your business.
Book a private Configurix demo →Related articles

Can you launch a configurator before your BOM is ready?
Plan a phased configurator launch when material data is incomplete, separating visual enquiries, quotations and approved factory outputs.

What should a configurator proof of concept prove?
Define a configurator proof of concept around a risky rule, saved revision and receiving-system output, with clear pass conditions.

Can a configurator run in your company's cloud account?
Evaluate company-owned hosting for a configurator by assigning deployment, monitoring, backups, access, incident response and integration responsibilities.

Does available stock in a configurator mean it is reserved?
Distinguish stock visibility from reservation when connecting a configurator to inventory, including stale data, competing orders and acknowledgements.
