ETO, MTO, CTO: Why Your CPQ Software Should Know the Difference

October 19, 2026

How flexible is your business when it comes to meeting changing customer requirements?

Many customers now expect products to meet their own requirements. For manufacturers of complex equipment, that expectation means managing a large number of customization options on every quote. So, they rely on one of the three manufacturing strategies:

Manufacturers often deploy one model or a combination of models based on how the products are designed, configured, and manufactured. However, the main question here is: Does your CPQ solution know the difference between ETO, MTO, and CTO?

ETO, MTO, and CTO are sound ways to build products, and the complexity they bring is real. This article looks at how these models differ from each other, how standard CPQ solutions fall short when used with these models, and how adopting modern CPQ software can help your enterprise address those gaps.

Differences Between ETO, MTO, and CTO

ETO

The design is developed for each order. Engineering begins once the customer’s request arrives, and the product takes shape from those requirements. The final price can be set only after that work is complete. 

MTO

In the make-to-order model, production starts when the order is received by the client. The customer chooses from the available range, and the product is made for that order.

CTO

Engineers define the product structure and its options in advance. The customer selects a combination of those options, and each selection produces its own bill of materials and routing.

Here is the key difference between the three models:

Make-to-order (MTO) Configure-to-order (CTO) Engineer-to-order (ETO)
Product definition at quoting Predefined product, built for each order Predefined options, with customer selections defining the configuration Product shaped around customer requirements
Engineering involvement Minimal or fixed Limited to the rules set in advance Engineering team is involved at every stage of product design and development
Main challenge for CPQ Accurate scheduling, purchasing, and material availability Well-defined product structures and rules Quotes are harder to produce accurately, and costs change over the project
Typical demand Product availability and production schedule Many variations within defined limits Highly specific requirements, such as industrial machinery and aerospace
Coordination needs Visibility across the production process Alignment between sales, engineering, and production Coordination across departments is critical

Where Do Standard CPQ Solutions Fall Short?

Standard CPQ tools handle fixed catalogs well. The gaps appear when a model needs pricing, configuration, or scheduling logic that the tool was not built to carry. 

Pricing Management in Real-Time

Under ETO, the price is built from materials, configurations, customizations, and margins. Each input changes the pricing of the final product. Under CTO, the price of a configured product depends on which options are chosen together. Bundles, quantity breaks, and option dependencies all affect the total. Standard tools struggle to update pricing in real time and highlight the same pricing updates to sales reps and clients.

Invalid Configurations

A CPQ solution that does not have rule-based or constraint-based configuration may allow invalid production configurations into the quote. If not caught earlier, invalid configurations can lead to delays and rework for the sales team.

Rules That Stop at Validation

Under CTO, each valid selection must produce a bill of materials and a routing for that one unit. Standard tools usually check the selection but do not generate production records. Those records are then rebuilt by hand, which introduces delay and the risk of mismatch.

Approvals Based Only on Discount

Discount approvals often depend on thresholds recorded in decade-old sheets. An unusual bid may have no large discount but still carry weak margin or need engineering review. Standard tools route every quote through the same discount-based path, so these bids reach the customer without the right review.

Engineering Changes That Stay in Separate Records

A single change in the product configuration can affect the price, quote, and delivery timeline, especially in the ETO environment. A standard CPQ tool often keeps these records separately, which have to be updated manually every time a configuration is changed.

Quote Data That Stops at the Order

Once a quote is accepted, its configuration, pricing basis, and revision history should move to the ERP or production system. Standard tools often transfer only line items, so option selections and revision details stay behind. Engineer-to-order projects then begin without the budget and the assumptions the quote was based on. 

Separate Systems for Data Records

When configuration, quoting, customer data, and sales data run on separate systems, IT must maintain every system and manually enter the data, which increases the chances of errors and delays in sales. 

Choosing CPQ Software That Understands Your Production Model

ETO, MTO, and CTO models pose different requirements in the quote-to-order process. They impact product configuration, pricing, and quoting at different stages. On top of that, manufacturers often manage more than one model, which standard CPQ solutions struggle to handle. A modern CPQ platform supports these requirements by integrating different systems and departments working together. 

A modern CPQ orchestration tool integrates sales, engineering, and operations to work from a single source of data, which minimizes the need for manual data entry and rework.

When evaluating CPQ software, your enterprise must test it against your existing quote-to-order process and check whether it can handle changing requirements, prevent invalid configurations, maintain pricing accuracy, and carry the approved specification into production. The right solution does more than generate quotes faster. It helps ensure that what the customer approves is consistent with what the business can deliver.


Tags


You may also like

{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}