Configure To Order (CTO)
In Configure To Order (CTO), a product is assembled from predefined options upon customer order — no custom engineering, fast delivery, controlled variety.
Configure To Order (CTO) is a manufacturing and sales strategy in which a product is assembled from a predefined set of options — selected by the customer at order time — without requiring custom engineering work. The product’s variants are fully defined before any order arrives; what changes per order is which combination of options the customer selects, not the underlying product design.
CTO is the order fulfillment strategy that systematic variant management makes possible at scale. Without structured management of options, constraints, and variant BOMs, the CTO promise — fast delivery of a product customized to customer needs — quickly breaks down under the weight of configuration errors, production exceptions, and engineering workarounds.
How CTO works
In a CTO process, the work happens in two distinct phases:
Pre-order (engineering and planning phase) The product family is designed with variation deliberately planned in: variation points are identified, options are defined, constraints between options are captured, and the 150% BOM 150% BOM (ˌwən-ˌfif-tē pər-ˈsent ˌbil əv mə-ˈtir-ē-əlz) n. A 150% BOM lists all possible components across all product variants, serving as the master structure for subtractive configuration in variant management. or configuration model is established. Production processes for all valid combinations are planned and verified.
Order phase When a customer order arrives, the customer selects from the predefined options. A CPQ system CPQ – Configure, Price, Quote (ˌsē-ˌpē-ˈkyü) n. abbr. CPQ stands for Configure, Price, Quote — software that automates sales quoting for configurable products by enforcing product rules, calculating pricing, and generating output. or configurator validates the selection against the constraint rules and derives the specific BOM for that configuration. The order goes directly to production — no engineering review required — because all engineering decisions were made during the pre-order phase.
This separation of “design the variants” from “select the variant” is what allows CTO to deliver both customization and speed.
CTO in the manufacturing strategy spectrum
CTO sits between Make To Stock (MTS) and Engineer To Order (ETO) Engineer To Order (ETO) (ˌen-jə-ˈnir tü ˈȯr-dər) n. Engineer To Order (ETO) is a manufacturing strategy where a product is custom-designed to customer specifications — each order triggers new engineering work before production begins. in the spectrum of order fulfillment strategies:
| Strategy | What is predefined | Lead time | Variety |
|---|---|---|---|
| Make To Stock (MTS) | Product AND inventory | Shortest | Fixed |
| Configure To Order (CTO) | Product variants and options | Short–medium | Controlled |
| Make To Order (MTO) | Product design, not stock | Medium | Limited |
| Engineer To Order (ETO) Engineer To Order (ETO) (ˌen-jə-ˈnir tü ˈȯr-dər) n. Engineer To Order (ETO) is a manufacturing strategy where a product is custom-designed to customer specifications — each order triggers new engineering work before production begins. | Requirements only | Longest | Unlimited |
Many companies operate in multiple modes simultaneously: standard products are MTS, core variants are CTO, and highly specialized orders are ETO.
Role in variant management
CTO is the primary target state for most variant management improvement programs. A company that currently manages each customer order with ad-hoc engineering is, in effect, doing ETO for products that could be CTO — paying the cost and lead time of custom engineering for variation that is actually well-understood and repetitive.
Moving to CTO requires:
- Explicit documentation of all valid options and their constraints (the configuration model)
- A product structure Product Structure (ˈprä-dəkt ˈstrək-chər) n. A product structure is the hierarchical decomposition of a product into components and subassemblies — the engineering foundation for BOM management and variant documentation. that supports variant derivation rather than parallel independent BOMs
- A CPQ or configurator system that validates selections and derives the order-specific BOM
- Production processes that can handle the full range of valid configurations without case-by-case engineering review
The benefit of reaching this state is significant: lead times for configured products can drop from weeks to days, engineering resources shift from reactive order support to proactive product development, and production errors from manual variant handling decrease.
Examples
- Automotive — A car model is offered CTO: buyers select engine, transmission, color, interior, and option packages from a defined menu. The factory builds every order from stock components — no custom engineering per vehicle. The manufacturer’s variant management system ensures every selected combination is valid and derives the production BOM automatically.
- Industrial switchgear — A manufacturer offers configurable switchgear assemblies (CTO) with defined options for breaker rating, bus bar configuration, communication module, and enclosure protection class. Each order is assembled from components that were engineered and qualified in advance.
Frequently asked questions
What is the difference between CTO and MTO (Make To Order)?
In Make To Order (MTO), the product design is fixed but inventory is not held — production starts when an order arrives, using a standard BOM. In Configure To Order (CTO), the product design encompasses multiple options and the BOM is derived from the customer’s selections at order time. CTO implies active variant management; MTO does not necessarily — it may involve a single standard product built on demand.
Can a company do both CTO and ETO?
Yes, and most complex manufacturers do. Standard and common variants are handled CTO — the options are predefined, the configuration model is in place, and orders go straight to production. Highly specialized customer requirements that fall outside the predefined option space are handled ETO — with custom engineering for that order. Good variant management involves actively moving the boundary: expanding the CTO envelope so that fewer orders require ETO treatment.