ERP for Variant Manufacturing — software for configure-to-order machinery and plant
DACH machinery builders make their margin in variants. A standard machine becomes a customer-specific configuration once options, sizes, performance classes and country-specific compliance are layered on top, and the variant tree explodes from there. An ERP for variant manufacturing has to handle configure-to-order at scale: a parametric BOM, a working sales configurator (CPQ) in front of it, variant-specific costing, and a clean order-engineering hand-off so the technical clarification does not run on email. Generic discrete-manufacturing ERPs without genuine variant logic collapse once the variant count moves above a few hundred per product family.
Requirements
The defining requirement is parametric BOM and routing. A single product family is described by a set of features and characteristics — size, motor class, voltage, control package, country variant — and the ERP generates the resulting BOM, routing and cost on the fly from a rule base, rather than storing thousands of pre-built variant records. This requires a real configurator engine in the ERP, not a glorified options matrix. In front of the engine sits the CPQ: a sales configurator that lets sales engineers or partners build a feasible configuration, with rules preventing impossible combinations, and that produces a quotation with price and delivery date. Behind it sits engineering: standard variants resolve automatically, edge-case configurations land in an engineering-to-order (ETO) clarification workflow with a defined hand-off, milestones and revision control. Variant costing must support both a planned cost at quotation time and an actual cost rolled up from production, so that pricing decisions are based on realistic margin per variant rather than on a family average.
Mandatory functions
Mandatory features start with a true configurator engine: parametric BOM and routing, characteristic-based rules, dependency graphs and validation. The CPQ on top has to support sales-channel use (B2B portal, mobile sales tablet, dealer logins), generate quotations in the customer's language and currency, and connect to CAD where the configuration drives a customer drawing. Engineering integration links the ERP to PLM (Siemens Teamcenter, PTC Windchill, Aras Innovator, 3DEXPERIENCE) so changes flow through approval into the production BOM with audit trail. Variant costing must roll up materials, purchased components, labour minutes and overheads per characteristic, ideally with a margin-by-variant report. Production planning handles long lead-time purchased parts against shorter assembly windows, with project management for ETO orders alongside. Service and spare-parts management is the second life of every machine: the ERP must keep the as-built configuration for the next 10–20 years.
Vendor landscape
The DACH variant-manufacturing vertical has a strong specialist field. SAP S/4HANA with Variant Configuration (LO-VC, the modern advanced variant configuration) is the de-facto standard at the upper Mid-Market and above. Infor LN, IFS Cloud, abas ERP and proAlpha are the established mid-market alternatives with deep variant capability. ams.erp focuses tightly on project- and variant-heavy Mechanical Engineering and Anlagenbau. Microsoft Dynamics 365 F&O appears in larger groups, often paired with Tacton CPQ or KBMax (now Epicor CPQ) for the configurator front end. For pure CPQ on top of an existing ERP, Tacton, Combeenation and Camos remain strong DACH choices, with Salesforce CPQ taking ground in sales-organisation-driven projects. Selection typically pivots on the existing PLM stack: a Teamcenter-led organisation lands more naturally on SAP, a Windchill-led one on IFS or Infor.
Trends and outlook
Three trends are reshaping the vertical. First, CPQ in B2B self-service: dealers and even end customers are increasingly expected to configure online, which raises the bar for configurator usability and for instant feasibility and pricing. Second, digital twin: the as-built configuration becomes the seed for an IoT-connected digital twin that drives service and predictive maintenance, with the ERP feeding configuration data and consuming telemetry. Third, the new EU Machinery Regulation 2023/1230 (replacing the Machinery Directive from January 2027) tightens documentation and software-update obligations on configurable machines, pushing more compliance metadata into the ERP's configuration record.
Related Topics
Frequently Asked Questions
What is the difference between options-based and rule-based variant configuration?
Options-based configuration multiplies pre-built records (every combination becomes its own SKU); it works for a few dozen variants. Rule-based configuration with parametric BOM derives the BOM and routing from a rule engine at order time and supports millions of theoretical combinations. Above a few hundred active variants, only rule-based configuration scales without exploding master data.
Do we need a separate CPQ if the ERP already configures?
It depends on the sales channel. If sales is in-house and uses the ERP directly, the embedded configurator is often enough. If dealers, distributors or end customers configure online, a dedicated CPQ (Tacton, Camos, Combeenation) delivers the usability, multi-channel reach and partner-portal experience that an ERP configurator rarely matches.
How does engineering-to-order (ETO) sit alongside variant configuration?
Variant configuration handles the standard tree; ETO picks up edge cases that fall outside the rule base. A good ERP routes those to a defined engineering clarification workflow with a fixed hand-off, milestone tracking and a clear conversion back into production once the engineering work is done — rather than letting ETO orders run on email and Excel.
How long does as-built configuration data have to be kept?
For machinery, the answer is typically the operational life of the machine plus statutory product-liability windows — in practice 15–25 years. The ERP must keep the exact as-built BOM, software version and option set per serial number for that period so that spare parts and service work on a 12-year-old machine can be planned against accurate data.