Engineer-to-order Project-based manufacturing Bill of materials from engineering

Custom ETO ERP development

With engineer-to-order, the design only starts after the order has been signed. There is then no item number, no complete bill of materials and no routing, while purchasing already has to start on long-lead-time components. Standard ERP assumes the opposite. Appfront builds ERP software for companies that engineer per order: machine building, shipbuilding, special vehicles, process installations and custom interior fit-out.

What makes engineer-to-order different

Make-to-stock produces based on forecasts: item, bill of materials and routing are fixed. Make-to-order makes that same known item only after the order, at most with choices within a predefined range of options. In both cases, the system knows at order intake what needs to be made. Not so with engineer-to-order: the specifications are not yet known in detail when the order is received, and the design work is part of the lead time. Every order is an engineering project, so the quote is a calculation based on a concept, and purchasing has to start before engineering is finished.

Is this the right page for you? This page is about project-based engineering per order. If you combine discrete manufacturing with process manufacturing, with bills of materials alongside recipes and batch tracking in the same system, you belong with ERP for mixed manufacturing. There, two production logics have to coexist; here, the product does not yet exist at the moment it is ordered.

Design time is part of the lead time

Drawing hours are not preparation but a phase of the project. While they last, the material requirements keep changing.

The bill of materials grows as you go

At the time of the order there is only a rough outline. Mechanical, electrical and control engineering fill it in at their own pace.

Margin only shows afterwards

There is no cost price per item to send across. Only comparing the estimate with reality shows whether this type of order is profitable.

Purchasing against a bill of materials that doesn't exist yet

This is where most ETO companies get stuck with their ERP. Classic requirements planning runs from item to bill of materials to routing to requirements; remove the first element and the rest of the chain has nothing to calculate on. Yet purchasing has to get started, because the main drive, the casting or the control cabinet has a lead time that exceeds the engineering phase. Waiting for a complete bill of materials means those parts dictate your delivery date.

Companies therefore work with a provisional bill of materials with line items such as "drive, type to be determined", with an estimated amount and a lead time from the quote calculation. As soon as mechanical engineering chooses the drive, the actual item has to replace that line without the project losing its history: the purchase order, the commitment and the variance against budget must remain correct. If your system only knows fully specified items, the buyer works around it: the bill of materials lives in a spreadsheet and nobody knows any more how much of the budget is committed.

Phased release goes hand in hand with this. If engineering only releases once the entire design is finished, purchasing has to wait. Releasing per assembly solves that, provided the system accepts partial releases and recalculates later without upending the first tranche.

And then engineering changes something that has already been ordered

Take a frame that has already been cut and welded when mechanical engineering moves the motor flange. The system then needs to show more than the new bill of materials: that four units of the old version are still in stock, that a purchase order is open for fasteners that will no longer fit, that welding hours were booked against the previous revision, and whether the supplier can still amend the order. In ETO, an engineering change order is therefore a core process. For each affected item, it should be clear where the costs land: a customer-requested change as an extra-work line with approval, a design error as an internal cost item.

What an ETO ERP needs to do

These components are interdependent: a growing bill of materials without change management leads to chaos, and change management without project costing is just administration.

Project structure with partial deliveries

Sections or modules with their own schedule, budget and delivery milestone, to which hours, purchasing and invoicing are linked.

Budget lines without an item number

Lines with an amount and a lead time, later replaced by the final item while retaining the purchase order and booked costs.

Release per assembly

Engineering releases part by part; the system schedules accordingly and recalculates as soon as the next tranche comes in.

Change management with impact overview

Every change order shows, per affected component, its status, costs and the consequences for the schedule.

Estimate and actual costing side by side

Quote calculation and actual costs in the same structure, so the variance can be read per component.

Extra work with customer approval

A change request gets a price and a status; only once approved does it flow through to the budget and invoicing.

Where the margin becomes visible or disappears

With ETO, the comparison between pre-calculation and post-calculation is the most important report in the system, and at the same time the report that is unusable in most companies. The cause is structural: the quote is built per functional block (drive, frame, controls, assembly), while the accounts are kept per cost type (materials, subcontracted work, hours). If those structures don't match, you can establish that the project became more expensive, but not where.

Engineering hours deserve separate attention. Booked as overhead, the project on which the design engineer spent extra weeks disappears into the average. In ETO, those hours are product costs, and together with commissioning hours they are the items where overruns show up first. Extra work is the third leak: changes are the norm here, most are small enough to do quickly without paperwork, and together they make the difference. See also software for the manufacturing industry.

  • Engineering hours as project costs, not overhead
  • Estimate and actual costing structured the same way
  • Hours, purchasing and subcontracting under one project number
  • Commitments visible as soon as the purchase order is open
  • Extra work with status, amount and customer approval
  • Variance per functional block, not just on the project total
Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

CAD, PDM and the two bills of materials

Engineering and production look at the same components but organise them differently. The engineering bill of materials follows the functional structure and the disciplines: drivetrain, frame, hydraulics, controls. The production bill of materials follows the assembly sequence and the work orders. An integration that only transfers item numbers produces an unusable list.

What does work is an explicit mapping between the two structures, maintained per revision, with a list of differences for each release: which items have been dropped, which added, and which quantities changed. Without that list, comparing revisions becomes a source of errors that only surfaces during assembly. BOM data usually flows through the PDM system's API; for geometry, ISO 10303-242 is often used, better known as STEP AP242, which has combined the AP203 and AP214 protocols since 2014.

On the documentation side, the project-based nature makes the difference. Anyone placing machinery on the European market compiles a technical file per machine; in ETO, that means a file per order containing the drawing revisions, material certificates and test reports for that one specific build. Document management tied to the item number doesn't work here. The framework is also changing: the Machinery Regulation (EU) 2023/1230 becomes mandatory from 20 January 2027, replacing the Machinery Directive 2006/42/EC. In steel construction, EN 1090 also applies: part 1 governs the CE marking of structural components, and execution classes EXC1 to EXC4 determine how heavy the burden of proof is per project.

Phased release EBOM to MBOM Change orders Budget lines Requirements calculation per project Post-calculation PDM API integration ISO 10303-242 Project file

When an off-the-shelf package is the better choice

Engineer-to-order is not a blind spot in the ERP market. Mature packages with genuine ETO functionality exist, including Dutch suppliers that explicitly name machine building and vehicle body building as their target group, with data exchange between CAD, PDM and ERP and projects divided into phases. For some readers of this page, such a package is the wiser route, and we would rather say so now than halfway through a quoting process.

If your process follows the pattern of project, engineering, release, purchasing, production and post-calculation, you buy that off the shelf, including maintenance and updates for changing regulations. Your effort shifts from building to configuring.

Custom development pays off in fewer situations than vendors suggest. The strongest case is a configuration or calculation logic that is genuinely your own: a calculation model that derives the main components, the engineering effort and the price from a customer specification. Forcing that model into a package's forms destroys precisely the part that sets you apart. The second case is a package that only allows purchasing for a fully specified item; the third is being stuck on a supplier's roadmap.

The downside comes with the territory: when you build it yourself, keeping up with changing standards is your own organisation's responsibility. Often the middle road is the best answer: a package as the administrative core, custom development for the configurator or the calculation. You can read how we weigh that up under a custom ERP system.

  • Package if your process follows the common ETO pattern
  • Package if BOM discipline still needs to develop
  • Custom if you have your own configuration or calculation logic
  • Custom if the package demands a complete BOM
  • Middle road: package as the core, custom front end

Frequently asked questions about ETO ERP

With make-to-order, the product already exists: item number, BOM and routing are fixed, and the order sets production in motion. With engineer-to-order, the specifications are not yet known in detail when the order is received, and design only starts after the order. The engineering work is therefore part of the lead time, and the BOM takes shape along the way.

By releasing in phases and working with budget lines. Long-lead-time components, such as drives, castings or control cabinets, are entered early in the project as a line with an estimated amount and an expected lead time, still without an item number. As soon as engineering specifies them, the actual item replaces the line, with the purchase order and booked costs carried over.

In engineer-to-order this is not an exception but a core process. The change is recorded as an engineering change order, and for every affected item the system shows its status: not yet ordered, ordered, received or already processed. Then comes the decision: cancel, keep or write off. Equally important is who bears the cost: a customer change should become an additional-work line that needs approval, while your own design error remains an internal cost.

Often yes, and for some companies that is the wiser route. Mature packages with genuine engineer-to-order functionality exist, including Dutch suppliers focused on the manufacturing industry. If your process follows the pattern of project, engineering, release, purchasing, production and post-calculation, you can buy that off the shelf. Custom becomes interesting only if you have your own calculation logic, or if the package demands a complete bill of materials before you are allowed to purchase.

The source code and documentation belong to the client and are kept in a repository you have access to yourself. Handover includes a description of the architecture, the data models, the integrations and the deployment, so that another party can take over without having to reverse-engineer anything first. We work with mainstream technology, because that determines how many parties can pick up the maintenance.

The machine manufacturer remains responsible for this, regardless of which system manages the documentation. The ERP makes that obligation workable by linking the technical file to the project number, so certificates, material certificates and drawing revisions can be traced per order. The framework is also changing: the Machinery Regulation (EU) 2023/1230 becomes mandatory from 20 January 2027. With a self-built system, building that in is down to you.

Related services

ERP for mixed-mode manufacturing

For companies that combine discrete and process manufacturing: BOMs alongside recipes, with batch and lot registration in the same system. See ERP for mixed-mode manufacturing.

Custom ERP system

If the question goes beyond manufacturing, covering purchasing, sales, service and administration, then a custom ERP system is the broader starting point.

Software for manufacturing

Production control, shop-floor registration, quality files and machine integrations alongside the ERP itself: software for the manufacturing industry.

Your ETO process under the microscope

Tell us what your quote calculation looks like, when engineering releases, and what currently happens when a change comes in for a component that has already been ordered. Those three answers usually show whether a package, custom software or a combination fits best.

Does this topic also apply within your own organisation? Read more on applatenmaken.com about building an ERP system.

Edit content