Configure-to-order vs engineer-to-order
CTO or ETO? Define your product boundary.
Configure approved product choices. Route exceptions to the right person. Keep customer-specific engineering connected to the quote, bill of materials and accepted revision. Complexity alone does not decide whether your workflow is CTO or ETO.
Discuss your workflowThree connected operating models
Configure-to-order
Released product identities, characteristics and rules
A governed core with exceptions
Standard-path rules and structured exception reasons
Engineer-to-order
Structured customer requirements and reusable subsystems
What must the factory receive?
Configure-to-order software turns a selection made against approved options into a record the next team can use. A signed quote tells you what the customer accepted. Production also needs the model and option codes, dimensions with units, quantities, revisions and a named owner for any outstanding technical decision.
Take a glazed enclosure with four panels. The customer approves quote revision 2, then asks to change one opening. Sales should save revision 3 and regenerate the affected lines and bill of materials. Ask production which detail changes the order: a panel code, a cut length or a hardware kit. Check the new version against the accepted order and make sure the superseded file cannot be released by mistake.
Test an order that the ERP refuses
Use one line with a missing item mapping. The order should show as waiting for correction, with the rejected line and its owner visible. After fixing the mapping, have the team retry the same order and confirm that the ERP creates one order record. Agree who can promote a corrected export to factory release.
For configure-to-order software, bring a signed quote and its corresponding order and materials list. Configurix can scope product rules, documents and receiving-system fields around that example.
Reusable knowledge or new engineering?
Configure-to-order
The product comes from an approved model, characteristics, modules and constraints. A complex product can be CTO when its permitted choices and outputs are governed. Routine review or manufacture after an order does not by itself create a new design.
A governed core with exceptions
Released rules cover repeatable work. A named exception enters technical review, then its decision returns to the same configuration, price, quote and customer approval. Only accepted reusable knowledge becomes a new standard rule.
Engineer-to-order
The requirement needs customer-specific design or engineering changes beyond the released model. Reuse the standard subsystems, capture the unresolved work and connect the engineering result to the commercial and production revisions.
Map your order workflow
Answer four questions about one product family. The result separates reusable product knowledge, new design, review responsibility and the output you need. Assess another family separately if its process differs.
Answers and notes stay in this browser unless you download them. They are not included in the enquiry form.
Compare responsibilities across CTO and ETO.
- Product knowledge
- CTOReleased model, characteristics, modules and constraints
- ETOOrder-specific requirements and engineering decisions
- Solution space
- CTODefined before the order and testable with representative fixtures
- ETONot completely enumerable before the customer requirement is known
- Sales role
- CTOSelects and prices within a governed product boundary
- ETOCaptures requirements and coordinates technical feasibility
- Engineering role
- CTOModels and maintains reusable rules and approved structures
- ETODesigns, calculates, reviews or releases the individual order
- Validity
- CTORules can prove accepted normal and boundary cases
- ETOValidity depends on new order-specific engineering evidence
- 3D experience
- CTOShows a structured product state tied to accepted choices
- ETOMay begin as concept or requirement visualisation before final release
- Pricing
- CTOCan use approved formulas, components, services and account context
- ETOMay require estimates, risk allowances and revision after engineering
- BOM or routing
- CTOCan resolve from approved rules, mappings or ERP variant logic
- ETOMay be copied and changed, or created specifically for the order
- Quote status
- CTOCan be order-permitted when commercial and technical conditions pass
- ETOShould distinguish budgetary, technically reviewed and released states
- Change control
- CTOCatalogue, rules and effectivity govern repeatable change
- ETOOrder-specific engineering change and renewed acceptance govern the project
- Lead time
- CTODriven by configured scope, availability, capacity and services
- ETOIncludes engineering effort, review and release before execution
- Best automation target
- CTOHigh-frequency product decisions with reusable knowledge
- ETORequirement capture, reuse, exception routing and controlled handoff
Eight boundaries worth defining.
Product identity
- Inside the governed model
- An approved family or model exists and remains the order identity.
- Technical review trigger
- The requested product cannot be represented by a released model or permitted extension.
Geometry and dimensions
- Inside the governed model
- Ranges, increments, formulas, module counts and derived dimensions cover the result.
- Technical review trigger
- Novel geometry, interfaces, loads, tolerances or site conditions need calculation or design.
Rules and compatibility
- Inside the governed model
- Dependencies, exclusions, required selections and valid combinations are accepted in advance.
- Technical review trigger
- The requirement falls outside tested constraints or introduces a new dependency.
Components and materials
- Inside the governed model
- Selections map to approved components, quantities, units and effectivity.
- Technical review trigger
- A new part, material substitution, custom fabrication or unapproved supplier is required.
Commercial result
- Inside the governed model
- Price, service, discount, tax and approval logic can reproduce accepted fixtures.
- Technical review trigger
- Cost depends on unfinished design, uncertain scope or order-specific procurement.
Evidence and compliance
- Inside the governed model
- Approved product data supports the promised description within a defined market and use.
- Technical review trigger
- Performance, structural, electrical, safety or regulatory evidence must be created or assessed.
Operational release
- Inside the governed model
- The configuration maps into an accepted order, BOM, routing or production-review contract.
- Technical review trigger
- Engineering must change or release order-specific BOM, drawings, routing or work instructions.
Change after acceptance
- Inside the governed model
- A change creates a new governed configuration, price and document revision.
- Technical review trigger
- A change invalidates engineering evidence and requires rework, reapproval or re-release.
Keep the exception connected to the configuration.
- Qualify
- Capture application, site, account, market, target outcome and known technical conditions.
- Configure
- Use the released catalogue and rules to complete everything that is safely reusable.
- Classify
- Mark the project valid, incomplete, invalid or review-required with reason codes.
- Estimate
- Separate accepted price lines from allowances, estimates and pending engineering scope.
- Review
- Give engineering the configuration, exception, evidence, customer context and required decision.
- Release
- Attach the accepted technical result, responsible reviewer and released revision.
- Reconcile
- Update price, quote, configured order and customer acceptance after the technical decision.
- Learn
- Decide whether a repeated exception should become governed catalogue knowledge or remain ETO.
One project. Versioned decisions.
Configuration identity
Stable configuration ID and revision linked to the customer, opportunity and quote
Product context
Family, model, catalogue revision, market, account and channel
Selected state
Characteristics, option IDs, dimensions, derived values, quantities and services
Classification
CTO, hybrid or ETO path plus rule, reason code and classification timestamp
Validity
Complete, invalid, review-required, technically accepted or order-permitted
Commercial state
Price source, currency, lines, allowances, tax, discount, approval and validity date
Exception record
Requested deviation, affected subsystem, evidence, owner, priority and due date
Engineering result
Decision, assumptions, calculations, attachments, released revision and approver
Operational mapping
Configured item, component, BOM, routing, drawing, survey or work-package references
Change history
Who changed what, previous and new state, impact, reapproval and downstream acknowledgement
Build a repeatable operating model.
Choose representative orders
Use frequent standard work, boundary cases, accepted exceptions and truly novel projects from the same product family.
Map the current decision chain
Document who decides product fit, price, technical feasibility, quote status, BOM, release and change today.
Define the governed solution space
Name released models, characteristics, ranges, modules, constraints, components and reusable calculations.
Create exception reason codes
Replace free-text escalation with specific triggers such as size, load, interface, material, compliance or unsupported component.
Assign system authority
Separate catalogue, rule, price, customer, order, engineering, BOM, routing and production ownership.
Design the hybrid state model
Make incomplete, invalid, review-required, approved and released states visible to users and integrations.
Build and reconcile outputs
Connect visual state, price, quote, review packet and configured-order data to the same revision.
Accept and improve
Test normal and exception paths, observe rework and promote only stable repeated knowledge into governed CTO rules.
Measure coverage and rework from your own baseline.
CTO coverage
Share of representative demand completed inside the accepted solution space
First-pass classification
Projects routed correctly without later CTO-to-ETO or ETO-to-CTO correction
Engineering touch rate
Orders requiring technical work, segmented by exception reason and product family
Review cycle time
Time from review-required state to accepted decision, excluding clearly named waiting time
Quote revision rate
Quotes changed because technical scope, component mapping or price assumptions changed
Order clarification rate
Accepted orders returned for missing, ambiguous or inconsistent information
Rule reuse
Frequency with which released rules and components resolve repeatable customer demand
Exception promotion
Repeated reviewed conditions intentionally converted into governed product knowledge
Twelve checks before you accept the workflow.
- 1
A standard order inside the approved solution space reproduces accepted product, price and output fixtures while retaining the agreed review responsibilities.
- 2
Minimum, maximum, increment, dependency, exclusion and derived-value boundary cases behave exactly as the approved product model specifies.
- 3
A request outside the solution space cannot be represented as a valid or production-ready CTO result by changing free text or hidden fields.
- 4
Every review-required state includes a structured reason, affected product area, responsible role and the evidence needed for a decision.
- 5
The visual, dimensions, specification, price, quote, review packet and configured order reference the same configuration revision.
- 6
Accepted price lines, estimates, allowances and technically pending values are distinguishable in the interface, document and integration payload.
- 7
Engineering can accept, reject or revise the request without overwriting the customer state or losing the original exception.
- 8
A technical decision that changes product or price creates the agreed new revision and requires the appropriate commercial and customer reapproval.
- 9
A released result records the responsible approver, timestamp, evidence and engineering or operational revision used for fulfillment.
- 10
Unknown and retired product, component, rule and engineering references are rejected rather than silently mapped to a convenient substitute.
- 11
Repeated submission or retry does not create duplicate reviews, quotes, configured items or sales orders.
- 12
A downstream rejection remains visible, retains the full project and can be corrected and reconciled to the originating configuration.
Avoid false confidence at the product boundary.
Everything custom is called ETO
Reusable product knowledge remains inside individual engineers' projects, so sales cannot automate frequent decisions.
Everything is forced into CTO
Unmodeled technical uncertainty is hidden behind a valid-looking interface, price or render.
A warning replaces a workflow
The configurator displays “contact us” but creates no owner, reason, evidence packet, due date or return path.
The quote outruns engineering
A precise-looking total and delivery promise are issued before unresolved design and procurement scope is known.
The picture becomes the specification
A convincing 3D scene is treated as proof of component, structural, compliance or production validity.
Engineering changes a separate copy
The customer configuration, technical design, quote and order diverge because revisions cannot be reconciled.
Every exception becomes a rule
Rare or poorly understood cases make the product model fragile, untestable and difficult to maintain.
No exception ever becomes a rule
The same engineering decision is repeated order after order without becoming reusable governed knowledge.
Custom configurators and software for complex products.
Configurix specializes in complex products. We build custom configurators and business or factory software around your product model, with scoped qualification, CRM, calendars and appointments, pricing, quotes, materials and BOMs, orders, jobs, invoices and integrations. Your responsible team retains authority over engineering evidence and production release.
Custom software for manufacturers
A configurator up front. Your business connected behind it.
We specialize in complex, configurable and made-to-order products. We build custom software around your catalogue, calculations, permissions, sales process and factory workflows.
Custom configurators and software for complex products.
Configurix specializes in complex products. We build custom configurators and business or factory software around your product model, with scoped qualification, CRM, calendars and appointments, pricing, quotes, materials and BOMs, orders, jobs, invoices and integrations. Your responsible team retains authority over engineering evidence and production release.
CRM and qualified leads
Capture the selected product, dimensions and options with each enquiry. Qualify by product fit, project requirements and commercial readiness, then assign the next action to the right salesperson.
New enquiry
Configure-to-order vs engineer-to-order
Product fitQualified
Configure-to-order vs engineer-to-order
RequirementsProposal
Configure-to-order vs engineer-to-order
Next actionCalendars and appointments
Let a configured project continue into a sales consultation, technical review, survey or installation appointment. Connect calendars, responsibilities and reminders to the same customer record.
- 09:00Project review
- 11:30Technical review
- 14:00Production planning
Bill of materials and factory data
Map product selections to component codes, quantities, materials and cut lengths. Build the sales or manufacturing BOM your team needs, with revisions and production review rules defined for your products.
| Component | Quantity |
|---|---|
| FRM-01Configured components | 1 |
| PNL-02Materials and quantities | 1 |
| KIT-03Agreed operations | 1 |
Mapped to your product codes
Live prices and branded quotes
Apply your own formulas, price lists, dealer margins and approval rules. Generate a quote containing the saved specification, product images, commercial terms and a clear customer approval step.
Quote revision
Orders, jobs and production
Carry accepted choices into order lines and assigned jobs. Keep product revisions, required approvals, documents and delivery tasks together so sales and the factory work from the same specification.
- Accepted quote01
- Configured order02
- Production job03
- Installation04
Invoicing and accounting
Connect accepted orders to deposits, invoice drafts, payment terms and your accounting workflow. Agree which system issues the invoice and how references and confirmed payment status return to the project.
Configure-to-order vs engineer-to-order
Built for your website. Connected to your systems.
Launch a branded configurator in your existing website or a custom sales portal. Connect CRM, ERP, PIM, ecommerce, calendars and accounting through available APIs, webhooks or agreed imports. We define the data, permissions and responsibilities for each connection with your team.
- 01Your website
- 02Configurator
- 03CRM & calendar
- 04ERP & accounting
Choose the workflows your implementation needs. We build and validate them against your products, documents and target systems.
Discuss your workflowCTO and ETO questions, answered.
Configure-to-order vs engineer-to-order
Bring one standard order and one exception.
We will map product rules, technical review, pricing, BOMs and the sales-to-factory handoff around your actual product family.