Can staff change a customer's configuration after submission?

Staff may need to correct or complete a customer configuration, but the change should remain traceable. Define who can amend the record, which changes need customer or technical approval and how the resulting quotation or factory request is updated. Silent editing can leave different teams acting on different understandings.

Distinguish a correction from a new commercial decision

Correcting a misspelled project name is not the same as changing a dimension or substituting an accessory. Classify the changes your process allows and identify the approvals they require. The software should reflect that distinction in its permissions and record history.

Preserve the submitted version where it matters. A salesperson investigating an issue should be able to understand what the customer originally selected and what the company later changed.

Test a change after quotation issue

Submit a product, issue an offer and then change an accessory as a staff user. Inspect the earlier selection, revised specification, price difference and customer communication. Decide whether the existing offer becomes superseded or remains valid for its earlier scope.

Repeat with a role that should not be allowed to make the change. An inactive-looking button is not enough; the operation itself needs the agreed permission check.

Connect reasons to outcomes

A change log saying “updated” is less useful than a record identifying the changed value, actor, time and business reason. Do not collect excessive commentary merely to create a long history. Retain the information needed to understand the decision and its consequences.

If a receiving system has already accepted the order, define an amendment transaction or a review task. Editing the configurator alone does not establish that the factory received the revision.

Scope staff workflows with Configurix

A Configurix order-management implementation can connect role-specific editing, quotation revisions and agreed factory handoffs. Use your real amendment scenarios to define permissions and acceptance tests before launch.

Should staff always create a completely new project?

Not necessarily. A controlled revision can retain the relationship to the original request. Choose a process your sales and production teams can understand and reconcile.

Does recording a change mean the customer accepted it?

No. Approval, notification and acceptance are separate events. Specify which is required for each type of amendment.