Make-to-order and engineer-to-order manufacturers operate under constraints that standard ERP systems handle poorly. Every order is a project with its own bill of materials, routing, cost estimate, and delivery timeline. There is no stable master production schedule, no repetitive demand signal, and no finished goods inventory to buffer against delivery commitments. The ERP system either manages this complexity natively or becomes the bottleneck that prevents scaling.
The distinction matters at the system level. Make-to-order manufacturers produce known products configured to customer specifications. Engineer-to-order manufacturers design and build unique products where engineering is a significant portion of the project scope. Both require project-centric ERP, but ETO demands tighter integration between engineering, manufacturing, and commercial functions than any other manufacturing model.
This guide evaluates the strongest ERP systems for MTO and ETO manufacturing in 2026, assessing five critical capabilities: project-based manufacturing, BOM management, engineering change orders, shop floor control, and estimating and quoting.
Why MTO and ETO Manufacturing Breaks Generic ERP
Project-Based Cost Structures
Repetitive manufacturers track costs by product line or work center. MTO and ETO manufacturers track costs by project, and every project is a unique cost entity. A single customer order for a custom industrial heat exchanger might involve 400 hours of engineering, 12 purchased components with different lead times, 6 fabrication operations across 4 work centers, and 3 subcontracted processes. The ERP must accumulate all of these costs against the project in real time and provide margin visibility before the project ships rather than after the accounting period closes.
Generic ERP platforms approximate this with workarounds, but approximation creates latency, and latency in project-based manufacturing means margin erosion goes undetected until it is too late to correct.
Multi-Level, Non-Standard BOMs
A repetitive manufacturer might maintain 500 active BOMs that change quarterly. An ETO manufacturer might create 500 new BOMs per year, each unique to a specific customer order. These include custom-designed components, customer-specified materials, one-off fabrication routines, and assemblies that will never be built again. The ERP must support rapid BOM creation from templates or configurators without requiring formal product lifecycle management overhead for every one-off item.
MTO and ETO BOMs are also living documents. They evolve as engineering refines the design, procurement identifies substitutions, and the shop floor discovers that the specified process does not work as planned. A system that treats the BOM as a frozen reference document will generate constant friction between engineering and production.
Engineering Changes Under Active Production
In repetitive manufacturing, engineering changes follow a controlled release process with effective dates. In ETO manufacturing, changes happen while affected components are already in production or partially assembled. The change process must handle mid-stream revisions without losing traceability or creating phantom inventory records.
This is where most generic ERP implementations fail. The engineering change module assumes a product-centric model where revisions apply to all future production. ETO requires an order-centric model where revisions apply only to the specific project or serial number that triggered the change. Supporting both models simultaneously is an architectural challenge that few platforms handle well.
Critical ERP Capabilities for MTO/ETO Manufacturing
1. Project-Based Manufacturing
Project-based manufacturing treats each customer order as a self-contained project with its own budget, timeline, resource allocation, and margin calculation. The ERP must create a project structure when the order is confirmed, link all subsequent purchasing, production, and engineering activity to that project, and provide real-time cost accumulation against the original estimate.
The strongest platforms support work breakdown structures, resource leveling across concurrent projects, and earned value metrics. For ETO manufacturers with projects spanning 6 to 18 months, this level of project visibility is not optional.
Revenue recognition adds another dimension. MTO and ETO manufacturers frequently bill on milestone completion, percentage-of-completion, or cost-plus arrangements. The ERP must support these billing models natively, including progress billing, retainage, and ASC 606 requirements for recognizing revenue over time.
2. BOM Management
BOM management in MTO and ETO environments requires capabilities that repetitive manufacturing platforms rarely provide. The system must support configurable BOMs where standard structures are modified per order, full ETO BOMs where every component is defined from scratch, and hybrid approaches where some assemblies are standard and others are engineered.
Template-based BOM creation is essential for efficiency. Engineers should be able to start from a reference BOM for a similar past project, copy it, modify the components and routings that differ, and release it to production without rebuilding the entire structure. Multi-level BOM management must handle deep nesting without performance degradation. Complex ETO products like packaging machinery, industrial boilers, or custom automation systems can have BOMs with 8 to 12 levels and thousands of components.
Where-used reporting is particularly critical. When a supplier notifies you that a raw material is being discontinued or a component lead time has doubled, you need to know immediately which active projects are affected. The BOM module must provide instant cross-project where-used lookups across all active revisions and open orders.
3. Engineering Change Order Management
Engineering change orders in MTO and ETO manufacturing are the primary mechanism for managing the gap between what was quoted, what was designed, and what can actually be built. A mature ECO process must capture the change request with full context, route it through approval workflows involving engineering, production, quality, and often the customer, and then execute the change by updating affected BOMs, routings, purchase orders, and work orders without corrupting the audit trail.
The order-specific dimension is critical. When an engineer changes a component on Project 4471, that change must propagate only to Project 4471 without affecting Project 4385, which uses the same base design but has already passed that production stage. Generic ECO modules that apply changes globally by part number will create chaos in an ETO environment.
Cost impact tracking is equally essential. Every engineering change carries a cost consequence: different materials, additional labor, scrapped work-in-process, or expedited purchasing. The ERP must capture these impacts at the time of the change so that project managers can decide whether to absorb the cost, negotiate with the customer, or redesign the solution.
4. Shop Floor Control
Shop floor control for MTO and ETO manufacturers must handle variability as the default condition. Job sequences change as engineering releases revised drawings. Priority shifts as customer delivery dates move. Work center loading fluctuates because the product mix is never the same from one month to the next.
The ERP shop floor module must provide real-time work order status visibility. Production supervisors need to see which operations are in queue, in progress, and completed for every active project without waiting for end-of-shift data entry. Barcode or RFID-based labor and operation tracking enables this, but only if the system processes transactions in real time rather than batching them for overnight posting.
Finite capacity scheduling is more important in MTO/ETO than in repetitive manufacturing because the work is less predictable. The scheduler must account for operation sequences that vary by order, setup times that depend on the previous job, and resource constraints spanning multiple work centers. Non-conformance and rework tracking complete the picture: when a fabricated component fails inspection, the system must capture the non-conformance, link it to the project, and update the cost and schedule accordingly.
5. Estimating and Quoting
Estimating is where MTO and ETO manufacturers win or lose business and margin simultaneously. An accurate estimate wins the order at a sustainable margin. An inaccurate estimate either loses the bid or wins it at a margin that disappears during execution. The ERP must support the full workflow from initial inquiry through detailed estimate to formal quotation.
The strongest platforms allow estimators to build estimates from historical project data. When a new inquiry arrives for a custom conveyor system, the estimator should be able to pull up a similar past project, use its actual costs as a baseline, and adjust for specification differences. This requires a searchable repository of completed project costs linking actual material, labor, and subcontract costs back to the estimate line items that predicted them.
Parametric estimating extends this capability for semi-standard product lines. If primary cost drivers are dimensions, material gauge, number of cutouts, and finish type, the module should support rules-based cost calculation from input parameters without building the BOM and routing manually.
Quote-to-order conversion is the critical handoff. When the customer accepts the quote, the ERP should convert the estimate directly into a project structure with a preliminary BOM, routing, and budget. Re-keying estimate data into a separate order entry module is a source of errors that compounds through the entire project lifecycle.
Top ERP Systems for MTO and ETO Manufacturing in 2026
Epicor Kinetic
Epicor Kinetic is the platform most frequently deployed in MTO and ETO environments across the mid-market. Its project-based manufacturing module treats each sales order as a job with its own BOM, routing, and cost bucket. The estimating module pulls from historical job data and supports multi-level quote BOMs that convert directly to production orders.
Strengths: Deep job-based manufacturing with native MTO, ETO, and mixed-mode support. The Advanced MES module provides real-time shop floor tracking with barcode-based labor reporting. The configurator handles rule-based product configuration for parametric product lines. Built-in APS accounts for material and capacity constraints simultaneously.
Limitations: The transition from legacy Epicor 10 to the Kinetic web interface is ongoing, and some advanced functions still require the classic client. Implementation complexity is moderate to high for ETO manufacturers needing tight CAD-to-BOM integration.
Best for: Mid-market MTO and ETO manufacturers ($20M to $750M revenue) in industrial equipment, custom machinery, and fabricated products.
Infor CloudSuite Industrial (SyteLine)
Infor CloudSuite Industrial, built on the SyteLine foundation, supports configure-to-order, make-to-order, and engineer-to-order workflows within a single instance. The platform is well-suited for manufacturers that operate across multiple fulfillment models.
Strengths: Full work breakdown structure support with earned value tracking, cost-to-complete forecasting, and milestone billing. BOM management handles multi-level configured and engineered structures with order-level revision control. The APS scheduling engine is among the strongest in the mid-market, providing finite capacity scheduling with constraint-based optimization.
Limitations: Cloud migration from on-premise SyteLine has been uneven, with performance issues reported on heavily customized legacy instances. The user interface does not match modern usability standards. Pricing for the full CloudSuite bundle can be opaque.
Best for: Mid-market to upper-mid-market manufacturers ($50M to $1B revenue) with complex scheduling requirements and mixed manufacturing modes.
SYSPRO
SYSPRO balances manufacturing depth with implementation speed, providing project-linked production orders, multi-level BOM management with engineering change control, and quote-to-order conversion.
Strengths: Integrated job-based costing, shop floor data collection, and quality management. BOM management supports template-based creation and order-specific customization. The engineering change module handles both product-level and order-level changes. Lower implementation complexity makes it accessible to manufacturers that cannot absorb 12-month timelines.
Limitations: Advanced project management capabilities like earned value tracking are less developed than in Epicor or Infor. Shop floor control depends on partner solutions for real-time MES functionality. ETO-specific workflows are less mature than in purpose-built project manufacturing platforms.
Best for: Smaller MTO manufacturers ($10M to $200M revenue) who need solid job-based manufacturing without enterprise-grade implementation overhead.
Microsoft Dynamics 365 Finance and Supply Chain Management
Dynamics 365 delivers project-based manufacturing through its Project Operations and Supply Chain Management modules, combining project costing, BOM management, production control, and advanced planning under Microsoft’s cloud infrastructure.
Strengths: Tight integration with Microsoft 365, Power BI, and Azure AI services. The project module supports work breakdown structures, cost tracking, and milestone billing with ASC 606 compliance. The platform scales from mid-market to enterprise without architectural changes. A large ISV ecosystem provides specialized add-ons for engineering change management and advanced shop floor control.
Limitations: Manufacturing depth requires careful configuration and often ISV extensions to match purpose-built platforms. BOM and routing management for complex ETO products is functional but less intuitive than dedicated manufacturing systems. Implementation costs and learning curves are higher than mid-market alternatives.
Best for: Upper-mid-market to enterprise MTO and ETO manufacturers ($100M+ revenue) already invested in the Microsoft ecosystem.
Genius ERP
Genius ERP is purpose-built for engineer-to-order manufacturers. Unlike general-purpose platforms adapted for ETO, Genius was designed from the ground up for companies that engineer and build unique products, with ETO workflows as the default.
Strengths: The estimating module is among the strongest available, supporting parametric estimation, historical cost referencing, and direct quote-to-order conversion that creates project BOMs and routings automatically. Native CAD integration with SolidWorks and Autodesk Inventor enables BOM import directly from engineering models. Engineering change management operates at the order level by default. Visual dispatch boards are designed for high-mix environments.
Limitations: Optimized for small to mid-market ETO and may not scale to enterprise requirements. The financial module is less comprehensive than Tier 1 platforms for multi-entity, multi-currency operations. The partner ecosystem is smaller, which can limit geographic availability.
Best for: Small to mid-market ETO manufacturers ($5M to $150M revenue) in custom machinery, industrial equipment, and specialty fabrication.
Cetec ERP
Cetec ERP is a cloud-native SaaS platform targeting small manufacturers with a focus on job shop and make-to-order environments. No on-premise option exists, which keeps infrastructure costs low.
Strengths: Clean web interface with strong job-based workflow. The quoting module supports multi-level assemblies and converts directly to production orders. Pricing is transparent and significantly lower than mid-market competitors. Implementation timelines are measured in weeks rather than months.
Limitations: Engineering change management is less formal than in larger platforms. Advanced project management features like earned value tracking are not available. The shop floor module lacks MES-level granularity. Not suited for complex ETO manufacturers with deep engineering integration requirements.
Best for: Small MTO manufacturers and job shops ($2M to $50M revenue) that need an affordable, cloud-native ERP with solid job-based fundamentals.
Evaluation Framework: Matching the System to Your Manufacturing Model
Selecting between these platforms requires honest assessment of where your organization falls on the MTO-to-ETO spectrum.
If engineering drives your business and changes are daily, prioritize Genius ERP or Epicor Kinetic for first-class engineering integration. If scheduling complexity is your primary constraint, Infor CloudSuite Industrial and Epicor Kinetic lead with advanced planning engines. If estimating accuracy determines your margins, Genius ERP and Epicor Kinetic offer the strongest historical cost referencing and parametric estimating.
For enterprise-scale project manufacturing with multi-entity consolidation and global operations, Dynamics 365 and Infor CloudSuite Industrial are the strongest candidates. For fast time-to-value without a 9-month implementation, SYSPRO and Cetec ERP offer the most direct path.
Conclusion
MTO and ETO manufacturing ERP selection is a decision about whether your system architecture will support or constrain how your business creates value. Every project generates data that should make the next project more predictable and more profitable. The right ERP captures that data, connects it across estimating, engineering, production, and finance, and transforms it into organizational knowledge that compounds over time. The wrong platform fragments it across spreadsheets and tribal knowledge. Choose the system that matches your actual manufacturing model, and hold it accountable for delivering the project visibility and cost accuracy that MTO and ETO manufacturing demands.