What maintenance is needed when products change every week?

When your products change frequently, buy a defined update process as well as the configurator. Maintenance must explain who can change product data, which changes require development, what gets tested and how an incorrect update is withdrawn. A promise to keep the website running does not settle these questions.

Classify actual changes from your catalogue

Review the last few updates your business made. A new material description, a changed accessory restriction and a revised price formula are different jobs. Ask the supplier to classify each one and show the administrative interface or development process involved.

Check visual dependencies too. A new finish may need an approved material representation; a new frame profile may change geometry and related components. Calling both tasks “add an option” hides important differences in effort and review.

Run a controlled correction exercise

Publish a change in a test environment and identify a saved project that it affects. Verify the current catalogue, earlier offer and new offer independently. Then ask how the update would be reversed if the manufacturer discovered an error after publication.

Reversal should not erase the history of orders accepted while the change was active. Agree which projects require review and how the responsible person finds them. The operational problem is bigger than restoring an older picture.

Define normal and urgent service

Some corrections can wait for a scheduled release. A product rule allowing an unsupported order may require a different response. Record the route for reporting each issue and who decides its priority. A response time is not necessarily a resolution time; ask suppliers to distinguish them.

Also agree the source information needed for a change request. A marked-up screenshot rarely explains every affected component, price rule and document. A short structured change record can reduce repeated clarification.

Give Configurix a maintainable product brief

For a custom Configurix project, define your internal catalogue owner and the changes that owner should perform. Connect updates to order and revision management, particularly where earlier configurations remain commercially relevant. Ask for training using a real change from your range.

Should all catalogue updates require a developer?

Not necessarily. Decide which edits can be safely delegated to trained administrators and which need changes to application logic or models. Test those boundaries before launch.

Is an annual support fee enough detail?

No. Request the included services, exclusions, change process and escalation route. Your company needs to know how its actual catalogue work will be handled.