What Is Engineer-to-Order Manufacturing? The Complete ETO ERP Guide

Engineer-to-order (ETO) is one of the most demanding production models to run, and one of the hardest to support with the wrong software. 

In our conversations with ETO manufacturers across aerospace and defense, industrial machinery and equipment, and metal and steel fabrication, we hear the same frustrations again and again. Their ERP system was built for repeatable production, but their business runs on evolving designs, one-off jobs, and costs that need to be tracked project by project. The two don’t fit.

In this article, we’ll define engineer-to-order manufacturing, walk through the operational realities that make it so difficult to run on generic software, and explain clearly what a purpose-built ETO ERP system needs to do. You’ll find the core capabilities to look for, real cost ranges, our top vendor picks, and case studies from ETO manufacturers who have already made the move. 

What Is Engineer-to-Order (ETO) Manufacturing?

Engineer-to-order manufacturing is a production model where a product is designed and built to a specific customer’s requirements after the order is placed, rather than manufactured from an existing design. The engineering happens inside the order itself, not before it.

You’ll find ETO production across industries where products are highly complex or specialized. Aerospace and defense contractors build systems to precise mission specifications. Industrial machinery and equipment manufacturers design entire custom production lines around a customer’s exact facility and process. Metal and steel fabricators build structural components to a project’s unique drawings.

While these industries have little in common on the surface, what ties them together is that no two orders look the same.

The distinction that separates ETO from every other production model is timing. 

In make-to-stock or make-to-order manufacturing, the design already exists before a customer places an order. In ETO, the design comes after. A customer commits to a project before the bill of materials (BOM) is final, before the routing is set, and sometimes even before the full scope is locked down. Long-lead materials often have to be ordered while engineering is still finalizing the drawings, because waiting for a complete design would blow the delivery schedule before production even starts.

That shifting foundation is what makes an ETO environment fundamentally different than any other manufacturing mode, and it’s the main reason software built for fixed BOMs and predictable timelines tends to fall apart the moment it meets an ETO project.

Where ETO Fits on the Manufacturing Spectrum

ETO sits at the custom end of manufacturing. The spectrum runs from pre-built to designed-to-spec. Make-to-stock, assemble-to-order, and configure-to-order fall at different points along that same line, each handling the bill of materials, lead time, and costing differently.

And many manufacturers don’t run purely in one mode. A shop that builds custom equipment to order might also stock standard fasteners, brackets, or replacement parts under a make-to-stock model, running both systems side by side. An ERP system built for only one mode forces the second workflow into an awkward workaround, which is another reason a system’s flexibility across modes matters as much as its depth in any single one.

Understanding the Operational Reality Behind ETO Manufacturing

In ETO production, the BOM keeps moving long after production starts. Costs need to be tracked project by project instead of by unit. The software also needs to keep up with engineering decisions still being made in real time.

Generic ERP systems, and even many manufacturing ERP systems, are built around the opposite assumption. They expect a stable item master, a finished design, and a predictable cost structure before anything gets scheduled. When that assumption meets a real-life ETO project, the mismatch shows up fast.

Two problems tend to surface right away:

1. Margin erosion creeps in when change orders happen informally, like getting tracked on a spreadsheet. By the time a project closes, nobody can say with confidence where the margin went.
2. Scope creep causes a similar problem from a different angle. A customer’s requirements shift mid-project, the team accommodates it because that’s the nature of the work, but the system never captures the added cost or the schedule impact, so the job’s numbers stop reflecting reality.

The good news is, there’s a simple way to find out whether an ERP system was built for ETO or just adjusted to tolerate it: During your ERP demo, ask the vendor to demonstrate how to buy material for a part that doesn’t have a part number yet, which is a very common scenario in ETO operations.

Systems built around a standard item master struggle here, because nearly everything in them is tied to that master record. The workaround teams end up leaning on is creating placeholder part numbers to force the software to accept the purchase order, which defeats the purpose of traceability in the first place.

An ERP system built for ETO doesn’t have this problem, because the job, not the part number, is the organizing structure. Materials, costs, and change orders all peg back to the project itself, so procurement can move as fast as engineering does instead of waiting on a record that doesn’t exist yet.

This is worth testing directly rather than taking a vendor’s word for it. Asking that one simple question in a demo will reveal more than a full feature walkthrough. Ask to see it in action.

What Are the Biggest ETO Manufacturing Challenges, and How Does ERP Solve Them?

ETO manufacturers face a specific set of operational challenges because the environment is constantly changing. Evolving designs, project-based costs, and shifting schedules all come into play. 

A purpose-built ERP system addresses each of these challenges directly.

Dynamic BOMs and Engineering Change Management

ETO BOMs keep evolving throughout the build instead of locking before production starts. Every design change risks updating one part without the rest catching up.

The right ERP addresses this through multi-level, version-controlled BOMs that support staged releases, so long-lead components can be ordered before the full design is finalized. The system then automatically flags every affected purchase order, work-in-progress job, and inventory record.

CAD and PLM Integration

Engineering design is the source of truth in ETO production, but when the design lives in a separate system from the ERP, manual data re-entry leaves the project vulnerable to errors and delays. 

ERP should solve this with a direct, bi-directional link to CAD and PLM platforms. Design changes convert directly into buildable structures, part records, and routings without any manual re-entry.

Project-Based Costing and Margin Visibility

Standard unit costing breaks down when every job is unique. Without a way to track cost against a specific project, margin erosion happens quietly and gets discovered only after the job closes.

ERP for ETO handles this by tracking labor, materials, and overhead against a project’s work breakdown structure, with real-time estimate-vs-actual reporting that surfaces overruns while there’s still time to act. 

Material Planning for One-Off Builds 

Traditional MRP assumes repeat demand and safety stock thresholds, but neither applies to a one-off build, leaving planners working around a system that wasn’t built for the work they’re doing.

The right ERP will address this with project-pegged material planning, so components purchased for one job stay reserved for that job. Staged procurement logic lets you order long-lead materials before the full BOM is complete.

Scheduling Around Concurrent Engineering

On an ETO shop floor, engineering, procurement, and production often happen at the same time, not in a sequence. A schedule built around fixed milestones falls apart the moment a drawing is late or a material shipment slips.

A properly selected ERP solves this with scheduling tools that account for shifting drawing availability and material arrival dates, reflowing the shop floor automatically when needed.

The 3 Core Capabilities Every ETO ERP Needs

The five challenges above are all handled by these three core capabilities. When an ERP system gets these right, it holds up under real ETO conditions. When it doesn’t, teams must build up workarounds to compensate.

1. Engineering and Design Integration

Engineering and design integration keeps design and production in sync as the project evolves. It covers dynamic BOMs that support staged releases, along with bi-directional CAD and PLM sync so engineering changes flow directly into the ERP without manual re-entry. 

2. Project and Financial Control

Project and financial controls track the real cost and progress of a job rather than the cost of a generic unit. It covers job costing against a project’s work breakdown structure, real-time estimate-vs-actual reporting, and milestone billing.

3. Procurement and Production Execution

Procurement and production execution keeps materials and scheduling moving at the pace engineering sets, not the other way around. It covers project-pegged material planning, so components stay reserved for the job they were purchased for, along with advanced planning and scheduling that adjusts automatically when a design change or material delay shifts the timeline.

A few capabilities span all three: Configure-price-quote (CPQ) and estimating tools turn historical project data into faster and more accurate early-stage quotes. Order management for ETO-specific workflows and the real-time data feeding visibility across engineering, procurement, and production round out the list.

Our Top ERP Picks for ETO Manufacturers

We curated these top picks specifically for how well they support engineer-to-order production, not manufacturing in general. A system can be a strong fit for make-to-stock or assemble-to-order work and still struggle badly in an ETO environment.

Our selections came down to a few key factors: depth of dynamic BOM and engineering change management, strength of CAD and PLM integration, project-based costing and margin visibility, and how well each system holds up under the part-number demo test described earlier in this guide. Vendor support through implementation mattered too, since ETO projects tend to surface legacy data issues and workflow gaps fast once a system goes live.

Total ETO

Best for custom machine builders, integrators, and panel shops that want an ERP built exclusively around ETO workflows.

Dynamic BOMs integrate directly with CAD systems, and a hold-and-release feature gives engineering and purchasing granular control over releasing parts, subassemblies, or full BOMs in stages. 

Worth knowing: Larger or more complex operations may outgrow its smaller-shop footprint as they scale.

Genius ERP

Best for small to mid-size manufacturers that want deep production and scheduling tools purpose-built by people who’ve run a shop floor.

CAD2BOM automation converts CAD designs directly into structured bills of materials, and dual scheduling options give manufacturers more flexibility in managing throughput than most competitors offer, including a bottleneck-focused method that paces the whole schedule around the shop’s most constrained resource. 

Worth knowing: Its 150-user ceiling means that fast-scaling or larger multi-site operations may need to evaluate whether the system can grow with them.

Infor CloudSuite Industrial

Best for mid-sized manufacturers running ETO alongside other production modes who want configurability without custom code.

A no-code personalization framework lets teams adjust fields, labels, and entire screens to fit how they actually work. Customizations carry forward through upgrades instead of getting wiped out with each release. 

Worth knowing: Infor CSI is built to flex across several production models at once, so manufacturers running ETO exclusively may find a more specialized system gives them deeper coverage in that one area.

SAP ECC

Best for large, established manufacturers already standardized on SAP’s ECC platform who need enterprise-scale financial and production control.

Production management spans material requirements planning, capacity planning, and multi-level BOM management, with shop floor control that tracks actual output against planned orders in real time. 

Worth knowing: SAP has set 2027 as the end of mainstream support for ECC, so manufacturers still running it should factor migration planning into any long-term ETO commitment.

MIE Trak Pro

Best for job shops and smaller ETO manufacturers that want full ownership of their system rather than a shared multi-tenant setup.

Built from real shop-floor experience, MIE Trak Pro covers the full workflow from RFQs and quoting through scheduling, production, and quality control. Its dedicated-server cloud model means customers own their application and data outright, rather than leasing space on a shared platform. 

Worth knowing: MIE Trak Pro architecture is generally better suited to single-site or modestly scaled operations, so manufacturers running large, multi-site ETO projects should confirm it can scale to meet their needs.

How Much Does an ETO ERP System Cost?

An ETO ERP system typically costs between $5,000 and $500,000 depending on the platform tier, with total implementation running well beyond the software license once configuration, CAD and PLM integration, and training are factored in.

Software licensing usually accounts for a smaller share of the total project cost than most buyers expect. Implementation fees, consulting, and integration work make up the majority of what you’ll actually spend. Connecting CAD, PLM, and shop floor systems to the ERP adds a layer of configuration work that standardized production modes don’t require.

ETO ERP Cost Breakdown

Is an ETO ERP System Worth the Investment?

In our experience working with ETO manufacturers, the answer is almost always yes, provided the implementation is planned well and the team commits to moving off spreadsheets early.

Industry data backs this up. According to Panorama Consulting Group’s 2026 ERP Report, organizations achieving expected benefits from removing operational silos jumped from 55.2% to 77.4% in the past year, a sign that more implementations are delivering the kind of connected, trustworthy data that ETO project costing depends on.

ETO manufacturers often tell us this is where the return shows up. Margins that used to leak quietly on every project now get caught in real time, because costs are tied to the job instead of reconstructed after it closes. 

Engineer-to-Order ERP Case Studies

Reading how other ETO manufacturers put their ERP systems to work is one of the best ways to see how ETO ERPs perform under real project pressures.  Below are several great examples to learn from. 

Automac Engineering, a New Zealand-based designer of conveyors and packaging machinery, came off a record revenue year only to find they’d lost more money than ever, slowed down by missing parts and manual spreadsheet errors. After implementing Total ETO, their missing-part rate dropped substantially. 

Read how Automac dropped fabrication tasks from 300 hours to 65. 

Bold Robotics, an Ontario-based builder of automated equipment for greenhouses and nurseries, was losing full days of engineering time to manual procurement, entering parts into an Excel spreadsheet for a single project. Total ETO eliminated most of the clerical work, giving the sales team real project data to quote from instead of guesswork. 

Learn how Bold Robotics stopped wasting employee hours.

REELEX Packaging Solutions, makers of cable packaging systems, needed an ERP that could handle multi-level BOMs and integrate with their existing accounting software. Genius ERP gave them real-time visibility into job costs and completion timelines, something they’d never had before. 

Read how Reelex scaled and eliminated spreadsheet inaccuracies.

Why Do ETO ERP Implementations Fail?

Most ETO ERP implementation failures trace back to a handful of recurring patterns. According to Panorama Consulting Group’s 2026 ERP Report, more than a quarter of organizations exceed their project budgets, with additional technology needs cited as the leading cause.

In ETO environments, we’ve seen that pattern show up again and again: a system chosen because it looked flexible enough during the demo, but required a patchwork of workarounds once a real, evolving BOM entered production.

Several causes show up again and again in struggling ETO implementations:

1. Treating a catalog-built system as flexible enough for ETO. A platform that handles configuration or make-to-order work well can still fall apart under the demands of an ETO environment. 
2. Underestimating legacy data. ETO shops tend to carry years of informal job costing, inconsistent part numbering, and engineering records that live outside their system. Moving that clutter into a new ERP without cleaning it up first just moves those errors to a new location.
3. Informal engineering workarounds surfacing post-launch. Spreadsheets, side conversations, and tribal knowledge often fill the gaps in an old system, and that informal layer usually stays invisible until go-live, when the team suddenly can’t fall back on it anymore.
4. Missing input from the people running projects day to day. Implementations driven only by IT and finance, without input from engineers, project managers, and shop floor leads, tend to produce a system that doesn’t match how ETO  production actually flows 
5. Underinvesting in change management. ETO implementations reshape how engineering, purchasing, and production coordinate day to day, which makes the human side of the rollout as important as the technical one. Treating training and change management as an afterthought inevitably lets old workarounds creep back in within weeks of go-live.

How to Prepare for a Successful ETO ERP Rollout

A well-planned rollout can prevent most of the failure patterns above before they take hold. A few practices consistently separate ETO implementations that succeed from the ones that stall.

1. Test for ETO fit before you sign anything. We cannot stress this enough! Ask the vendor to walk through buying material for a part that doesn’t have a part number yet. That single scenario will reveal a system’s ETO readiness more than any full-feature demo.
2. Clean up legacy data before it moves. Job costing records, part numbers, and engineering files that have drifted out of sync for years won’t fix themselves during migration. Budget real time for data cleanup rather than assuming it will happen automatically as part of the technical rollout.
3. Bring engineering and shop floor leads into the selection process early. The people running projects day to day will spot gaps in how a system handles concurrent engineering or change orders long before IT or finance execs will notice. Their input during selection, not just during training, will produce a system that actually fits how work moves through the shop.
4. Surface informal workarounds before go-live, not after. Ask project managers and engineers where they currently rely on spreadsheets, side conversations, or tribal knowledge to get work done. Those gaps need a real solution in the new system, or they’ll simply resurface.
5. Budget for change management. ETO implementations carry more organizational risk than most because they affect how engineering, purchasing, and production coordinate day-to-day. Training and change management deserve a real line item in the project budget.

Not Sure Where to Start? We Can Help You Find the Right ETO ERP for Your Manufacturing Business

No two ETO shops evaluate ERP the same way. What matters most for a panel builder running lean might barely register for an aerospace fabricator managing ITAR compliance and multi-site production. 

Our side-by-side comparison tool lets you weigh systems against the criteria that matter to your operation, and our ETO ERP Selection Guide picks up from here once you’re ready to move from research into an actual vendor decision.

We also have an extensive white paper library you can explore by vendor, or you can schedule a free call with one of our ERP experts if you’d rather talk it through.

FAQs for ETO ERP Buyers

What makes ETO manufacturing different from other production models?

In ETO manufacturing, the product design happens after the customer places the order, not before. That timing difference is why ETO needs an ERP system built around evolving designs, not a fixed BOM.

What’s the difference between ETO and configure-to-order (CTO)?

ETO starts from a blank design built to a customer’s exact specs. CTO starts from a set of predefined options a customer selects from.

Can an ETO ERP system also handle standard or repeat production?

Many ETO shops mix custom builds with repeat work like standard parts or fasteners. Most modern ETO ERP systems support this, though the depth varies by vendor.

How does ERP handle engineering changes that happen mid-project?

A purpose-built ETO ERP system triggers a formal change order workflow, automatically flagging affected purchase orders, jobs, and inventory. Without that, changes tend to get tracked informally, and that’s where cost visibility breaks down.

Should ETO manufacturers choose cloud or on-premise ERP?

Cloud ERP fits most ETO manufacturers today, with faster implementation and easier scaling. On-premise still makes sense though for manufacturers with strict data residency requirements, like ITAR compliance.

How is ETO different from custom manufacturing in general?

Custom manufacturing can include configuration-based work where a base design already exists. ETO starts from scratch, with no existing design to modify.