Engineer to order vs configure to order: what changes in your software?

Start with the approved product family

Configure-to-order generally describes selecting a permitted combination from an established product model. That model may still contain many dimensions, options and dependencies. Complexity alone does not mean every order requires a new design. The important question is whether the chosen specification falls within approved rules.

For a fictional industrial cabinet maker, customers choose dimensions, material, access panels and accessories. If engineering has already approved the relevant combinations and limits, the sales process can guide those choices. The software should identify the resulting specification without asking somebody to redesign the cabinet from first principles.

Recognise an engineering exception

Engineer-to-order work involves customer-specific engineering beyond the existing approved configuration scope. The precise operating model varies by manufacturer. Treat these terms as a way to clarify responsibility rather than a universal software classification.

For the cabinet maker, a request for a new mounting arrangement may require review of drawings, components and production steps. The salesperson needs a route to request that assessment. A configurable interface should not silently accept the new requirement as buildable merely because a free-text field can hold the description.

Expect hybrid workflows

SAP’s ETO production-model guidance describes a scenario in which standard configuration does not cover every requirement and additional customer-specific changes follow. This illustrates why configuration and engineering review can coexist in one sales process.

For the cabinet maker, most of the specification may remain standard while one section needs an engineering decision. Preserve the standard selections and clearly identify the exception. Avoid rebuilding the entire enquiry in disconnected documents when only one unresolved requirement needs review.

Define the status of each output

These are suggested states, not a claim about any vendor’s default workflow. Agree the labels with the people using them. A price estimate should remain distinguishable from an approved quotation, and neither should automatically imply production release.

Build the exception demonstration into procurement

Give suppliers an ordinary configuration, a boundary case and a request outside the existing rule set. Ask how the user learns that review is required, what information the engineer receives and how the answer returns to the saved specification. Inspect the document revision used for the final quote.

Configurix describes custom software for complex products. For any proposed implementation, request a scoped demonstration using your product family. A bespoke project should be evaluated against the actual engineering and sales handover, rather than assumed to support every factory process without further work.

Assign rule ownership and change control

Engineering should identify the approved product boundaries, while commercial owners define quoting and approval conditions. Name who can change each rule and who verifies the resulting behaviour. Keep representative configurations with expected outcomes for future regression review.

When a repeated exception becomes an approved option, decide how it enters the standard product model. Record the effective revision and what happens to earlier saved enquiries. Without that process, sales staff may continue using informal workarounds long after the underlying product rules have changed.

Preserve the unresolved commercial commitment

When engineering review is still open, make that condition visible in the customer handover. Define whether the current amount is an estimate, a quotation awaiting approval or another agreed state. The system should help staff explain what remains undecided, rather than allowing a saved configuration to imply a delivery commitment the business has not approved.

Choose the appropriate first scope

Start with a product family whose rules and exception owners can be described. Include the outputs the receiving team actually needs: specification, approved drawing reference, quote or structured order information. Keep unsupported downstream integrations explicit in the proposal.

Use the rule-dependency guide and project-cost guide for the implementation brief. The Configurix profile provides vendor context. The objective is a controlled path from a customer requirement to an approved order, including the cases that still need engineering judgement.

Frequently asked questions