Engineer to order (ETO) manufacturing: managing custom-engineered projects from RFQ to commissioning

What is engineer to order (ETO)

Engineer to order is a manufacturing model in which the design and engineering work happens after the customer order arrives, producing a unique product configuration for that specific order. Unlike make-to-stock, where products are engineered once and manufactured to a warehouse for later sale, and unlike make-to-order and its variants where products are manufactured on demand against a pre-existing design, ETO treats every order as a design event followed by a production event. The customer buys engineering capability as much as production capacity, and the engineering phase is an integral part of the order fulfilment cycle rather than a one-time upfront investment.

The defining characteristics of ETO

ETO orders share four defining characteristics regardless of industry. First, each order produces a unique bill of materials because engineering starts from customer requirements rather than from a catalogued design. Second, each order produces a unique routing through the shop floor because the manufacturing steps depend on what was engineered. Third, lead times are measured in months for smaller ETO products and in years for large capital equipment, because engineering plus procurement of specialised components dominates the schedule. Fourth, the engineering component of cost typically represents a substantial share of total order value, unlike in mass production where engineering cost is amortised across many units and effectively disappears from unit economics.

Where ETO happens

ETO dominates in industries where standardised products cannot meet customer requirements. Heavy machinery manufacturers (mining trucks configured for specific mine conditions, cranes sized for specific construction projects, agricultural equipment tuned for specific crops and terrains) operate primarily in ETO mode. Shipbuilding is almost entirely ETO because each vessel is designed for a specific route, cargo type and operator. Custom industrial equipment (process plants, packaging lines, material handling systems, automation systems, laboratory equipment) is ETO because each installation adapts to the customer’s existing plant and process. Power generation equipment (gas turbines, hydro turbines, generators, transformers above certain sizes) is ETO because units are sized and configured for specific installations. Rail rolling stock, mining equipment, specialised chemical plants, medical devices for specific clinical procedures and defence systems all follow ETO patterns.

Why ETO orders are projects, not manufacturing runs

The single most important operational insight about ETO is that each order is a project, not a manufacturing run. A manufacturing run consumes a known bill of materials through a known routing to produce a known product with known cost and known duration, and the entire management stack (MRP, APS, MES, ERP) is designed around this predictability. An ETO order starts with none of these knowns: the BOM is created during engineering, the routing is determined by engineering choices, the cost is estimated during quoting and revised throughout execution, and the duration is a function of engineering complexity, procurement risk and manufacturing complexity that only becomes fully visible late in the order. Managing an ETO order with tools designed for manufacturing runs consistently underperforms managing it with tools designed for projects.

ETO compared to MTS, MTO, ATO and CTO

Manufacturing strategy classifications describe how much design and engineering is completed before the customer order arrives. The four common alternatives to ETO (make-to-stock, make-to-order, assemble-to-order, configure-to-order) each move the customer decoupling point closer to the finished product, which reduces lead time and engineering effort per order but limits how much the product can be adapted to specific customer needs.

Make-to-stock (MTS)

MTS engineers the product once, manufactures it to inventory based on demand forecasts, and ships from stock when a customer orders. Lead times to the customer are hours to days. Every unit is identical, product engineering happens once and is amortised across all units, and manufacturing runs are optimised for throughput and unit cost. MTS applies to commodity products, consumer electronics, standard tools, packaged food and beverages, standard chemicals and pharmaceuticals. Management stack: forecasting, MRP, APS, MES, warehouse management.

Make-to-order (MTO)

MTO engineers the product once but manufactures it only after receiving a customer order, reducing inventory investment at the cost of longer customer lead times (typically days to weeks). The product design is pre-existing and orders trigger the manufacturing run, not the engineering. MTO applies to products with high configuration variation where holding all variants in stock is impractical: printed materials, specialised chemicals in specific packaging, non-standard steel sections, industrial fasteners in non-standard sizes. Management stack: order management, MRP, APS, MES. Different manufacturing strategies require different scheduling approaches, from PERT and Gantt charts to full portfolio management.

Assemble-to-order (ATO)

ATO manufactures sub-assemblies to stock and assembles them into finished products only after receiving a customer order. Lead times are days because sub-assemblies are already available and only the final assembly waits for the order. ATO enables mass customisation on a predefined set of options: personal computers configured with specific components, cars configured with specific trim levels and options, home appliances configured with specific feature packages. Management stack: order configuration, sub-assembly MRP, final assembly scheduling.

Configure-to-order (CTO)

CTO is a variant of ATO in which the customer configures the product from a defined option set, typically through a configurator that validates option combinations against a product model. The engineering has been done in advance to establish which options combine with which others, and the customer’s configuration triggers the assembly. CTO applies to enterprise software licences, complex machinery within predefined variant sets, and industrial equipment where the product model constrains customisation to engineered combinations. Management stack: product configurator, ATO tooling, order management.

Engineer-to-order (ETO)

ETO differs from the four models above because the design phase happens after the customer order arrives, and the engineering work is substantial rather than incremental. Lead times run in months to years, engineering cost is a significant share of order value, and the management stack extends beyond MRP and MES to include project portfolio management, product lifecycle management, engineering change management and CRM for the long sales and delivery cycle. Some manufacturers operate across multiple models: an equipment vendor might sell CTO for its standard product line and ETO for specialised installations. Understanding which model a given order belongs to determines which management tools are appropriate and which are not.

The seven-stage ETO order lifecycle

An ETO order typically progresses through seven stages from initial customer contact to final handover. The stages are not always sequential (engineering and procurement often overlap, testing can occur throughout manufacturing rather than only at the end), but the gate criteria between stages are what enforces discipline. Skipping or compressing gate criteria produces cost and schedule impacts that appear later in the lifecycle at multiples of what the discipline would have cost upfront.

Stage 1: Request for quotation (RFQ)

The RFQ stage begins when the customer describes their requirements and requests a price and delivery commitment. For simple ETO products this stage takes days; for complex capital equipment it takes weeks or months of pre-sales engineering. The RFQ output is a formal quotation containing scope description, technical assumptions, price, delivery commitment, commercial terms and validity period. Quote quality drives everything that follows: an underspecified RFQ produces a quote that misses substantial scope, and the missing scope becomes a change order dispute later in the project.

Stage 2: Quote and contract

Once the customer accepts the quote, the contract stage produces the formal purchase order and signed contract. The contract, which functions as an initial project charter, defines scope, commercial terms, delivery schedule, acceptance criteria, warranty terms, liquidated damages for delay and mechanisms for change management. Contract quality determines how disputes are handled throughout execution: a well-drafted contract with clear scope, defined change management and specified acceptance criteria protects both customer and supplier, while a poorly drafted contract makes every disagreement expensive.

Stage 3: Requirements and specification

Requirements and specification translates the contract scope into detailed technical requirements that engineering will design against. This stage often surfaces gaps between what the customer thought they ordered and what the contract actually specified, and resolving those gaps early is far cheaper than resolving them at factory acceptance. The specification output typically includes functional requirements, performance requirements, interface requirements, regulatory and standards compliance requirements, and testing and acceptance requirements. Specification sign-off by the customer is the last low-cost opportunity to align expectations.

Stage 4: Engineering and design

Engineering and design produces the technical solution: mechanical design, electrical design, control system design, software design where relevant, hydraulic and pneumatic design where relevant, bill of materials, routing, manufacturing drawings, assembly instructions, testing procedures. Engineering typically runs in phases from conceptual design through detailed design, with reviews at each phase and formal design freeze at the end. Design freeze establishes the baseline against which change control operates: any change after freeze requires formal impact assessment and customer approval.

Stage 5: Procurement

Procurement sources the components, materials and sub-contracted work required to build the product. Long-lead components (specialised castings, custom electronics, safety-rated controllers, precision instruments) drive the overall project schedule and must be identified during engineering and released for procurement as early as possible. Procurement risk is one of the largest sources of ETO project delay because specialised suppliers often have variable lead times, and a supplier delay on a critical component cascades through the entire project schedule.

Stage 6: Manufacturing and assembly

Manufacturing and assembly executes the routing produced by engineering, using the materials procured. For simple ETO products this stage runs at the manufacturer’s plant. For complex capital equipment it may involve multiple locations: sub-assemblies at supplier plants, module assembly at the manufacturer, final assembly at the customer site. Manufacturing quality determines whether testing passes: defects introduced during manufacturing and not caught early become expensive to fix during factory acceptance or, worse, during site commissioning.

Stage 7: Testing and handover

Testing and handover validates that the delivered product meets the contracted requirements. For complex ETO products this stage often includes factory acceptance testing at the manufacturer’s site, site acceptance testing at the customer’s site, and commissioning under live operating conditions. Handover to the customer requires operator training, documentation delivery, spare parts provisioning, warranty terms confirmation and formal acceptance sign-off. Post-handover support periods (typically 30 to 90 days) allow the manufacturer to address issues that surface only under real operating conditions.

Why ETO orders behave like projects

An ETO order has every characteristic that defines a project rather than a repeatable operation, which is why classical project management principles apply to ETO delivery in ways they do not apply to make-to-stock or make-to-order manufacturing. Understanding the specific characteristics that make ETO orders projects clarifies why the management stack has to be different, and where the largest operational improvements are available.

Unique bill of materials per order

Each ETO order produces a bill of materials that has never existed before and will not exist again in exactly the same form. Even ETO manufacturers with substantial reuse (standard sub-assemblies, catalogued components, engineered options) find that each order combines these elements in a unique configuration with unique interfaces. This uniqueness breaks the assumptions behind MRP, which is designed to explode a known BOM and plan procurement and manufacturing against known consumption. ETO BOMs are not fully known until late in engineering, and procurement often has to start before the BOM is complete based on engineering estimates of long-lead components.

Long lead times with engineering front-loading

ETO lead times run in months for smaller products and in years for large capital equipment. Engineering typically consumes the first substantial portion of the lead time, and manufacturing cannot start until engineering has produced enough drawings and BOMs to release procurement and manufacturing. This front-loading means that the majority of ETO project value is committed during engineering, not during manufacturing, and engineering decisions have amplified impact on total project cost and duration.

Engineering changes throughout the lifecycle

Engineering changes are inevitable in ETO because the design being produced is new. Some changes originate with the customer (revised requirements, discovered constraints, changed operating conditions), some originate internally (discovered infeasibility, better solutions identified during detailed design, supplier constraints), and some originate externally (regulatory changes, component obsolescence). Each change requires impact assessment against schedule, cost and technical feasibility. Change control after design freeze is one of the most important disciplines in ETO delivery, and organisations that treat design freeze as a formality rather than a real gate consistently overrun schedule and cost.

Capacity planning without historical standards

Standard manufacturing capacity planning relies on historical work standards: how long a given operation takes, how much material a given step consumes, how much rework is typical. ETO breaks these standards because each project has unique operations. Engineering hours per order vary widely with complexity, shop floor hours vary with the specific routing that engineering produces, and testing hours vary with the specific acceptance requirements. ETO capacity planning has to work with engineering estimates that are uncertain until well into the project, and portfolio-level visibility is often the only way to identify capacity contention before it becomes schedule slippage.

Cost estimation with substantial uncertainty

ETO quoting is inherently uncertain because the product is not yet designed. Quote-stage cost estimates rely on historical actuals from similar past projects, engineering judgement about complexity relative to those precedents, and margin adjustments for uncertainty. Quote accuracy correlates strongly with quote calibration discipline: ETO organisations that systematically compare quoted cost against actual cost per project, identify systematic biases (usually underestimation), and adjust future quoting produce more reliable margins than organisations that treat each quote as a fresh judgement without feedback from actuals.

Common pitfalls in ETO delivery

Five failure patterns recur across ETO delivery regardless of industry. Each is preventable with specific counter-measures, and naming the patterns makes them recognisable earlier in future projects, when they can be intercepted at a fraction of the cost of dealing with them at delivery.

Underestimated quotes based on optimistic engineering assumptions

The first pattern is quoting based on optimistic assumptions about engineering complexity, and discovering during detailed design that the actual complexity is substantially higher. The consequence is margin erosion or loss for the quoted project, and the risk of losing the customer relationship if scope has to be renegotiated. The counter-measure is quote calibration against historical actuals: at every project closure, compare quoted engineering hours against actual engineering hours, identify systematic biases, and update the quoting methodology so that future quotes reflect what similar projects actually consumed rather than what they were hoped to consume.

Undisciplined scope changes without price renegotiation

The second pattern is accepting customer requests for scope changes without formal change orders and price renegotiation. The engineering team accommodates the changes because they seem small, no formal record is created, and the cost impact accumulates invisibly across multiple small changes. By project delivery the accumulated scope changes have consumed substantial engineering hours that were not in the quote, and the customer is unprepared for a change order invoice at the end. The counter-measure is formal change control from the start of engineering: every scope change is documented, priced and approved by the customer before engineering executes it.

Engineering changes without full impact assessment

The third pattern is making engineering changes after design freeze without full impact assessment across the interconnected engineering deliverables. A change to a mechanical dimension propagates to fixture design, procurement lists and assembly instructions, and if each downstream deliverable is not updated the change surfaces during manufacturing or testing at multiples of the cost of updating it in engineering. The counter-measure is disciplined engineering change management with configuration control: every change after design freeze requires formal impact assessment covering all affected deliverables, cost and schedule impact, and customer approval where relevant.

Procurement planned as if suppliers were reliable

The fourth pattern is planning procurement of specialised components as if suppliers deliver on their quoted lead times, when in practice specialised suppliers have variable lead times that depend on their own order load, material availability and technical challenges. A supplier delay on a critical long-lead component cascades through the entire project schedule and cannot be recovered by working harder elsewhere. The counter-measure is buffer planning against supplier variability: long-lead components are ordered with buffer time against quoted lead time, supplier delivery risk is tracked on the risk register, and alternative suppliers are pre-qualified where possible so that a delay on one supplier does not stop the whole project.

Capacity contention across concurrent orders

The fifth pattern is capacity contention across multiple concurrent ETO orders that is invisible at the individual order level and only becomes visible at the portfolio level. Engineering hours, shop floor capacity, specialised skills and testing facilities are shared across orders, and a single order manager cannot see how their order competes with others for the same resources. Capacity contention shows up as unexplained delays, resource escalations that get resolved by moving people between projects, and quality issues from overloaded teams. The counter-measure is portfolio-level capacity planning that shows all concurrent orders competing for shared resources, and offer decisions that are made against actual portfolio capacity rather than against optimistic assumptions about how much the organisation can absorb.

Why ETO cannot be managed by ERP alone

Manufacturers frequently attempt to manage ETO operations through ERP and MRP alone, on the assumption that these systems handle all manufacturing including ETO. In practice ERP handles the transactional layer of ETO effectively (purchase orders, invoices, cost postings, stock movements, payroll allocation) but leaves the project management layer of ETO to spreadsheets, personal knowledge and improvisation. This gap between what ERP does and what ETO requires is where most operational improvement opportunities in ETO manufacturers are found.

What ERP handles well in ETO

ERP does specific things well for ETO: it holds the master data (customers, suppliers, materials, cost centres), it records transactions (purchase orders raised against orders, receipts and invoices matched, cost postings applied to project accounts, revenue recognition against milestones), it produces financial reports (project profitability, working capital, backlog analysis), and it integrates with accounting so that project financials aggregate correctly into company accounts. Modern ERP systems also increasingly support project accounting extensions that add project-level cost tracking and revenue recognition, which addresses the financial view of ETO orders.

What ERP does not handle well in ETO

ERP does not handle the engineering coordination layer of ETO: which engineers are working on which drawings, what stage each drawing is in, when design reviews are scheduled, which changes have been approved and which are still under review. ERP does not handle the schedule layer with the visibility that ETO requires: the critical path across engineering, procurement and manufacturing, the impact of a supplier delay on downstream activities, the resource contention across concurrent orders. ERP does not handle the risk register with owners, mitigation plans and review cadence. ERP does not handle structured gate reviews with evidence-based go or no-go decisions. Attempting to force these functions into ERP through customisation typically produces expensive systems that neither the finance team nor the engineering team fully trusts.

Where project portfolio management fits

Project portfolio management (PPM) fills the gap between ERP’s transactional layer and the operational needs of ETO delivery. PPM handles the project charter, the schedule, the risk register, the gate reviews and the portfolio view across concurrent orders, while ERP continues to handle the transactional layer. The two systems integrate at defined interfaces: cost data flows from ERP into PPM for variance analysis, project progress flows from PPM into ERP for revenue recognition, procurement releases flow from PPM triggering ERP purchase orders. Neither system tries to do the other’s work, and the operational effectiveness of the whole is the product of both systems doing their part well.

The transition from ERP-only to ERP plus PPM

The transition from ERP-only ETO management to ERP plus PPM is typically the biggest single operational improvement an ETO manufacturer makes. Before the transition, engineering coordination happens through email and spreadsheets, schedule visibility exists only in the heads of individual project managers, risks live on informal lists that are not systematically reviewed, and portfolio-level decisions are made against optimistic assumptions rather than actual capacity data. After the transition, coordination happens in a shared system, schedules are visible with critical path and variances, risks have owners and are reviewed on cadence, and portfolio decisions are grounded in actual data. The transition is not a technology project alone: it requires standardising project management practice across the organisation, which for many ETO manufacturers is the more difficult part.

Managing an ETO portfolio at scale

An ETO manufacturer rarely has a single order in flight. More typically the portfolio includes multiple orders at different stages: some in RFQ, some in engineering, some in procurement, some in manufacturing, some in testing. Managing the portfolio effectively is where ETO manufacturers move from delivering individual projects to running a reliable operation, and where the largest gains in throughput and margin are available.

Portfolio dashboard by stage

A portfolio dashboard for ETO shows all active orders categorised by lifecycle stage, with visibility into which orders are approaching gate reviews and which are blocked. The dashboard surfaces patterns that individual order views hide: RFQ queues building up when sales capacity is short, engineering bottlenecks when specific skills are contended across multiple orders, procurement backlogs when specialised suppliers have variable delivery, testing queues when facilities are constrained. Portfolio-level pattern recognition drives operational improvements that per-order management cannot see.

Resource contention across specialised skills

ETO manufacturing depends on specialised skills that are often thin in supply: senior mechanical engineers with specific product experience, control system programmers, safety system specialists, commissioning engineers with sector experience. Shared resources become the largest source of unplanned delay across a multi-order portfolio. The same senior engineer appearing on three project schedules simultaneously is invisible at the project level but obvious at the portfolio level, and effective portfolio management makes this contention visible early enough to sequence orders differently, add capacity, or make explicit decisions about which orders take priority.

Offer decisions grounded in actual capacity

ETO manufacturers make offer decisions continuously: which RFQs to bid on, what delivery dates to commit to, when to accept new work and when to decline. Firms without portfolio-level capacity data typically over-commit during optimistic phases (winning bids on the assumption that the organisation can absorb them) and under-commit during conservative phases (losing bids when actual capacity was available). Firms with portfolio-level capacity data can bid grounded in actual forecast utilisation, commit delivery dates that reflect real capacity, and improve win rates and margin simultaneously by matching bids to capability rather than to hope.

Standardisation across orders

Mature ETO portfolios standardise repeatable elements: project charter templates by order type, engineering deliverable checklists, gate review criteria, procurement processes, testing protocols, handover documentation. Standardisation prevents reinvention of routine elements on every order and frees engineering attention for the parts that genuinely differ between orders. Standardisation also enables cross-order learning: a lesson learned from one project’s engineering change control updates the templates so that subsequent projects benefit. ETO manufacturers with mature standardisation deliver orders faster and with less variability than firms where each order reinvents its own approach.

Operating practices of ETO organisations that deliver reliably

Certain operating practices consistently appear in ETO organisations that deliver on time and on margin, and consistently absent in organisations that overrun. Naming these practices makes them adoptable rather than intuitive, and gives ETO manufacturers a checklist against which to assess their current maturity and identify improvement opportunities.

A project charter for every order

Reliable ETO organisations create a project charter for every order at the point of contract signature. The charter defines scope, deliverables, milestones, acceptance criteria, budget, risks, sponsors and the project manager. The charter is not a formality: it is the reference document against which scope changes are assessed, delivery is measured, and disputes are resolved. Organisations that skip the charter (or reduce it to a contract signature) discover during execution that scope was never truly aligned, and the cost of retroactive alignment is much higher than the cost of front-loading it.

Baseline schedules with critical path visibility

Reliable ETO organisations produce a baseline schedule at project start showing engineering, procurement, manufacturing, testing and handover activities with dependencies and critical path. The baseline is approved at project start and used as the reference against which actual progress is compared throughout execution. Variances are visible immediately, root causes are analysed and mitigations are planned before variances become losses. Organisations without baseline schedules operate on rolling estimates that make variances invisible until they are irrecoverable.

Risk register with named owners

Reliable ETO organisations maintain a risk register from project start through handover, with named owners for each risk, mitigation plans and review cadence. Common ETO risk categories include engineering complexity risks (design assumptions that may not hold), supplier delivery risks (specialised components with variable lead times), customer decision risks (approvals that delay downstream work), testing risks (acceptance criteria that may reveal issues) and commercial risks (change orders that erode margin). Risks are reviewed at gate reviews and mitigations are updated as project reality evolves.

Structured gate reviews

Reliable ETO organisations conduct structured gate reviews at defined lifecycle transitions: after specification (before engineering starts), after conceptual design (before detailed design starts), at design freeze (before procurement release), at manufacturing release (before shop floor loading), at factory acceptance (before shipment) and at site acceptance (before handover). Each gate has defined evidence, defined criteria and defined decision authority. Gate reviews are not status meetings: they are formal go or no-go decisions with the option to remediate before proceeding.

Change control from design freeze onwards

Reliable ETO organisations enforce change control from design freeze onwards. Every change is documented on a change request, impact-assessed across schedule, cost and technical feasibility, priced where it affects commercial terms and approved by the customer where it affects contracted scope. Change control is often uncomfortable in the customer relationship: it forces conversations that both parties might prefer to defer. But the alternative (informal accommodation of changes without price impact) consistently produces margin erosion that reliable organisations do not accept.

How FlexiProject supports ETO delivery

FlexiProject supports the execution layer of ETO delivery with project portfolio visibility, schedule management, risk tracking, structured gate reviews and standardised templates. The engineering discipline that produces reliable technical solutions, the procurement discipline that manages specialised suppliers, and the manufacturing discipline that executes the routing are all responsibilities of the ETO organisation. FlexiProject provides the operational infrastructure that makes disciplined ETO delivery workable across a portfolio, not a substitute for the engineering, procurement and manufacturing expertise that ETO success depends on.

Portfolio view across concurrent ETO orders

FlexiProject provides a portfolio dashboard showing all active ETO orders categorised by lifecycle stage, with visibility into which orders are approaching gate reviews and which are blocked. The portfolio view surfaces patterns that individual order views hide, such as engineering bottlenecks on specific skills, procurement backlogs with specific suppliers, testing queue congestion at specific facilities. Steering committees making portfolio-level decisions work from the same portfolio view rather than reconciling different order reports.

Project schedule with Gantt, task list and Kanban views

The FlexiProject schedule combines a Gantt chart view for milestone tracking and dependency visualisation, a task list view for detailed execution work and a Kanban view for workflow discipline within stages. ETO orders benefit from the combination: the Gantt view handles the lifecycle structure with dependencies between RFQ, engineering, procurement, manufacturing, testing and handover, task lists handle the detailed engineering and manufacturing work within stages, and Kanban tracks the flow of specific deliverables through review and approval. Warning icons flag budget or risk issues without requiring separate reports.

Budget tracking against baseline

FlexiProject tracks project budget against baseline with forecast to completion, so that budget variances are visible early rather than at project closure. For ETO orders where the initial quote is the commercial commitment, the ability to see actual cost trending against quoted cost throughout execution is the difference between margin protection and margin surprise. The forecast to completion updates as engineering, procurement and manufacturing consume actuals, giving project managers early warning when a project trends toward margin erosion so that mitigation actions have time to work.

ERP integration for transactional data

FlexiProject integrates with ERP systems so that cost data flows into FlexiProject for variance analysis and project progress flows into ERP for revenue recognition and reporting. The integration means that FlexiProject and ERP are consistent without double entry, and financial data in ERP matches project data in FlexiProject. ETO manufacturers with existing ERP investments do not have to replace ERP to add project portfolio management: FlexiProject sits alongside ERP and handles the project layer while ERP continues to handle the transactional and financial layer.

Risk register linked to project stages

The FlexiProject risk register tracks ETO-specific risks with owners, mitigation plans and review cadence. Stage-specific risks (specification gaps during requirements, design assumptions during engineering, supplier delivery during procurement, quality issues during manufacturing, acceptance failures during testing) are linked to the relevant stage milestones and reviewed at the corresponding gate. The linkage between risks, tasks and the schedule means that a materialising risk visibly affects the associated timeline rather than sitting in a separate register that nobody consults during scheduling decisions.

Gate reviews as structured decisions

Project reviews in FlexiProject can be structured as formal ETO gate reviews with defined criteria, structured evidence presentation and formal go or no-go decisions recorded in the project record. The review cadence is scheduled (typically at specification sign-off, design freeze, manufacturing release, factory acceptance and site acceptance), and the review outputs feed into standardised templates for subsequent projects. Gate criteria configured in the templates apply consistently across projects, so that a design freeze gate for one order uses the same criteria structure as a design freeze gate for another.

What FlexiProject does not do

FlexiProject does not perform engineering (that is the work of the engineering organisation), does not execute procurement (that is procurement’s work with ERP support), does not run manufacturing (that is shop floor’s work with MES support) and does not substitute for the discipline of enforcing gate criteria (that requires management commitment). It provides the visibility, structure and traceability that make disciplined ETO delivery workable across a portfolio, but the engineering, procurement and manufacturing expertise, and the discipline itself, are organisational.

Frequently asked questions

What is the difference between ETO and MTO?

MTO (make-to-order) manufactures a pre-existing design after receiving a customer order. The engineering was completed once, and orders trigger manufacturing runs against the existing design. ETO (engineer-to-order) engineers the product after receiving a customer order, producing a unique design for that order. MTO lead times are days to weeks; ETO lead times are months to years. MTO can be managed largely through MRP and MES; ETO requires project portfolio management alongside ERP because each order is a project.

What industries use ETO?

ETO dominates in heavy machinery (mining trucks, cranes, agricultural equipment), shipbuilding (each vessel is designed for specific operations), custom industrial equipment (process plants, packaging lines, material handling, automation systems), power generation equipment (turbines, generators, transformers above certain sizes), rail rolling stock, specialised chemical plants, medical devices for specific procedures and defence systems. Common characteristics across these industries: customer requirements are too specific to be met by standardised products, engineering is a substantial share of order value and delivery timelines are long.

Can ERP alone manage ETO?

ERP handles the transactional layer of ETO (purchase orders, invoices, cost postings, financial reporting) effectively, but leaves the project management layer of ETO (engineering coordination, schedule with critical path, risk register, gate reviews, portfolio view) to spreadsheets and personal knowledge. Attempting to force project management functions into ERP through customisation typically produces expensive systems that neither the finance team nor the engineering team fully trusts. The more effective architecture is ERP for transactional data and project portfolio management for the project layer, integrated at defined interfaces.

How long does a typical ETO project take?

ETO project duration varies widely with product complexity. Smaller custom industrial equipment (packaging machines, specialised material handling systems) delivers in 6 to 12 months. Mid-scale ETO products (industrial process equipment, custom automation systems, mid-size turbines) delivers in 12 to 24 months. Large capital equipment (large turbines, custom ships, specialised chemical plants) delivers in 24 to 60 months. Engineering typically consumes 20 to 40 percent of total lead time, procurement of long-lead components dominates the remaining lead time, and manufacturing and testing complete the schedule.

How do ETO manufacturers handle engineering changes?

Mature ETO manufacturers use formal engineering change management with configuration control. Every change after design freeze requires a change request with impact assessment across schedule, cost, technical feasibility and affected engineering deliverables, priced where it affects commercial terms and approved by the customer where it affects contracted scope. Configuration control ensures that all affected drawings, BOMs, procurement lists and manufacturing instructions are updated together. Organisations without formal change control accumulate hidden scope changes that erode margin invisibly until project closure.

Can ETO deliveries follow Agile methods?

ETO deliveries have physical dependencies that limit the applicability of pure Agile methods: hardware needs procurement lead time, manufacturing requires shop floor capacity, testing follows physical processes that cannot be iterated over. Elements of Agile thinking apply well, particularly iterative refinement of specification with the customer before design freeze and iterative debugging during testing and commissioning. But the lifecycle structure from RFQ through handover is a stage-gate backbone because physical and commercial constraints enforce it, and attempts to apply pure Agile methods to ETO delivery typically underperform the disciplined stage-gate approach.

Engineer to order is a manufacturing model in which each customer order triggers a new engineering and production cycle, producing a unique bill of materials, unique routing and often unique tooling for that one order, sitting at the opposite end of the manufacturing strategy spectrum from make-to-stock. Every ETO order is a project rather than a manufacturing run, which is why ETO organisations manage their work through project portfolio management alongside ERP rather than through ERP alone. The seven-stage lifecycle from RFQ through handover, with structured gate criteria between stages, provides the framework, and engineering changes after design freeze are the single largest source of ETO project overruns without formal change control. Five failure patterns (underestimated quotes, undisciplined scope changes, engineering changes without full impact assessment, procurement planned as if suppliers were reliable, capacity contention across concurrent orders) are preventable with named counter-measures. ERP handles the transactional layer of ETO effectively but leaves the project management layer to spreadsheets, and the transition from ERP-only to ERP plus PPM is typically the biggest single operational improvement an ETO manufacturer makes. Portfolio-level visibility across concurrent orders enables the resource, standardisation and offer decisions that ETO firms make continuously. Reliable ETO organisations operate a project management standard applied to every order: charter with scope and acceptance criteria, baseline schedule with critical path, risk register with named owners, structured gate reviews and change control from design freeze onwards. FlexiProject supports the execution layer of ETO delivery with portfolio visibility, schedule management combining Gantt, task list and Kanban views, budget tracking against baseline, ERP integration for transactional data, risk register linked to stages, structured gate reviews and standardised templates. The engineering, procurement and manufacturing expertise, and the discipline of enforcing gate criteria, remain organisational responsibilities. If an ETO manufacturer’s order portfolio has grown beyond spreadsheets and needs a system supporting discipline across multiple concurrent orders, thirty days of full access with no credit card is a practical way to test the fit.