Choosing an ETO ERP: What Custom Manufacturers Should Look For

Engineer-to-Order (ETO) manufacturers don’t operate on fixed processes. Every job is different, designs evolve, and costs change as work progresses. What starts in engineering needs to carry through to production, purchasing, and finance without friction.

That’s where many ERP systems don’t hold up.

Most are built around stable products and repeatable workflows, which makes it difficult to manage design changes, track revisions, or keep teams aligned without relying on manual workarounds.

If you’re reviewing ERP options for an engineering-led environment, the goal isn’t just to manage operations. It’s to make sure engineering, production, and financial data stay connected in a way that reflects how your business actually works.

Why standard ERP systems struggle with ETO environments

Traditional ERP systems are designed for consistency. They assume fixed bills of materials, predictable routing, and repeatable production processes. That works well in make-to-stock environments, and even in some make-to-order scenarios.

But in ETO, those assumptions don’t hold.

Variability isn’t the exception — it’s the baseline. Bills of materials are often created or adjusted for each job, engineering changes continue throughout production, and costs shift as work progresses. On top of that, each job behaves more like a project than a standard order.

When a system tries to force that into a rigid structure, teams end up relying on spreadsheets and manual fixes. Over time, that creates gaps between engineering and production, limits visibility into real costs, and makes it harder to stay in control of profitability.

What sets ETO manufacturing apart

Before choosing a system, it helps to be clear on what makes ETO different in practice.

Everything starts with engineering. The design defines materials, routing, and timelines, so if that data doesn’t move cleanly into the ERP, issues show up downstream.

At the same time, change is constant. Revisions aren’t edge cases — they’re part of the process. Customers request updates, designs evolve, and priorities shift. The system needs to handle that without losing traceability or creating confusion on the shop floor.

And finally, the work itself is project-based. Each job has its own scope, timeline, and cost structure. You’re not managing repeatable orders — you’re managing projects with moving parts.

An ERP system for ETO needs to support all three realities.

Core capabilities an ETO ERP needs

Some capabilities aren’t optional. Without them, everyday work becomes more manual, and the risk of errors increases.

CAD to BOM integration

One of the most important is CAD to BOM integration. Engineering and production can’t operate in separate systems. A strong ETO ERP connects directly to CAD tools and allows you to:

• Generate bills of materials directly from designs
• Avoid re-entering data
• Reduce errors between teams

Without this, teams often fall back on spreadsheets, which increases risk at every step.

Flexible, multi-level BOMs

BOM management also needs to be flexible, as in engineering-led manufacturing environments, bills of materials are rarely static. They’re often multi-level, built around subassemblies, and adjusted as designs change. That means the system needs to:

• Manage complex assemblies
• Update structures as designs change
• Track differences between similar jobs

This becomes critical when projects share components but aren’t identical.

Engineering change control

Just as important is how the system handles engineering changes. Changes will happen; what matters is whether they’re controlled. You need:

• Version control for drawings and BOMs
• Clear tracking of revisions
• Visibility into what changed and when

Without this, teams risk working from outdated information.

Managing costs in ETO projects

Cost tracking alone isn’t enough in ETO. You need visibility and control throughout the lifecycle of a job.

Each project should be treated as its own financial entity, with labour, materials, subcontracting, and overhead all tracked against it. More importantly, those costs need to be visible as they build — not just once the job is complete.

One of the most common gaps in ERP systems is around committed cost. It’s not enough to know what you’ve already spent. You also need visibility into what you’ve committed to spend, whether that’s open purchase orders, planned labour, or reserved materials. That gives a much clearer picture of where the job is heading financially.

Margins should also be visible throughout the project. In longer-cycle ETO work, small issues can compound quickly. Being able to track margins in real time, spot issues early, and make adjustments before they escalate is key to maintaining control.

Scheduling in an ETO environment

Scheduling in ETO is more complex than simply sequencing jobs. Each project has its own timeline, dependencies, and resource requirements — and those can change as designs evolve or priorities shift.

To manage that effectively, you need a clear view of capacity. That includes available resources, current workloads, and upcoming demand. Without that visibility, it’s difficult to commit to realistic delivery timelines.

You also need to account for how work is connected. ETO projects often involve interdependent tasks, shared resources, and shifting priorities. A scheduling system needs to reflect those relationships rather than treating each job as isolated.

At the same time, what’s happening on the shop floor needs to be visible in real time. Job status, work in progress, and potential bottlenecks should all be easy to track. That visibility allows teams to respond quickly when plans change—which they often do in ETO environments.

Where AI fits in ETO (and where it doesn’t)

AI is getting a lot of attention in manufacturing, but its role in ETO is still fairly grounded.

It’s not a replacement for a well-structured ERP system. In practice, it’s most useful when it works with the same data your team already relies on every day.

Where AI can help today is in analysing historical and real-time ERP data. It can identify patterns across past projects, improve estimating accuracy, and highlight potential risks earlier. For example, looking at past jobs can help teams build more accurate quotes or flag delays before they impact timelines or margins.

At the same time, there are clear limits. AI still struggles with highly customised, one-off designs, complex engineering decisions, and situations where there isn’t much historical data to work from. In most engineering-led environments, many decisions still rely on engineering expertise and context that AI doesn’t fully capture.

What matters most is the foundation. AI only adds value when the underlying data is clean, connected, and reliable. That starts with strong CAD-ERP integration, accurate job costing, and real-time visibility. Without that, AI has very little to work with.

How to properly evaluate an ETO ERP

Choosing an ERP isn’t just about comparing features. It’s about understanding how the system supports real day-to-day work.

The key questions are practical:

• Can engineering data flow directly into production without manual steps?
• How are changes handled mid-project?
• Can you see costs and timelines clearly as work progresses?

These details don’t always show up in a standard demo.

What to ask in a demo

Ask vendors to walk through:

• How a CAD model becomes a BOM
• How revisions are managed
• How costs are tracked during production

If the process relies on manual workarounds, that’s a warning sign.

Other questions worth asking

It’s also worth asking a few direct questions to see how well the system lines up with your business:

• How does the system manage engineering revisions?
• Can we track committed and actual costs?
• How does scheduling adapt to changes?
• What does implementation look like in an ETO environment?

The answers should be specific and grounded in real workflows — not ideal scenarios.

Common warning signs

There are also some clear warning signs to watch for. Heavy reliance on spreadsheets outside the system often points to gaps in core functionality. Weak integration between engineering and production can create disconnects that lead to errors or delays. Static BOM structures make it harder to manage revisions, and limited visibility into project costs reduces your ability to track performance as work progresses.

In practice, these issues tend to compound and are all signs that the system may struggle in a real ETO environment.

Choosing the right system

ETO manufacturing is complex by nature. Your ERP shouldn’t add to that complexity.

The right system helps connect engineering and production, track costs as they change, adapt to revisions without losing control, and maintain visibility across every project.

As your business grows, those capabilities become more important.

When evaluating options, focus on how well the system supports the realities of ETO — not how well it fits a standard model. That’s what ultimately determines whether it works day to day.

See how ERP supports ETO manufacturers

Explore how Genius ERP is built for engineering-led environments to help bring together engineering, production, and costing, so you can stay aligned as projects evolve.

— Get in touch —