Variant manufacturing (Variantenfertigung) describes the production of multiple product variants from a common base — combining the cost efficiency of repetitive production with the customer-specific configuration of engineered products. Variant manufacturing dominates DACH machinery, industrial equipment, automotive supply and specialty industrial production. The complexity of managing thousands or millions of possible variant combinations drives specific ERP requirements around variant configurators, BOM resolution and master-data structures.
Variant manufacturing concept
The product structure starts with a configurable material (the base product) plus a defined option space (the choices available). Selecting a specific configuration produces a variant instance with a resolved BOM, routing and price. Example: a configurable industrial mixer has options for size (5 sizes), material (3 options), drive type (4 options), control system (3 options) and country of installation (10 options) — producing 1,800 distinct variants from one base. Without variant tooling, this would require 1,800 separately maintained BOMs. With proper variant configuration, one configurable BOM plus rules generates each variant on demand.
ERP variant configuration
SAP Variant Configuration (LO-VC): the most-mature variant tool, with deep history and broad adoption in DACH machinery and automotive. Object-oriented configuration model with classes, characteristics, dependencies, constraints. SAP Advanced Variant Configuration (AVC): S/4HANA modernisation with simplified architecture. Microsoft Dynamics 365 F&O Product Configurator: capable variant configurator with modern UX. Oracle Cloud Configurator. Mid-market specialist: Tacton (Swedish, strong in DACH machinery), encoway, Camos, In-Mind Cloud, Configit. Mid-market ERP-native: abas Product Configurator, proALPHA Configurator, Infor LN Configurator, IFS Cloud Configurator, Sage X3 Variant Management. Many DACH machinery operations layer a specialist front-end (Tacton, encoway) on top of ERP-native variant configuration for sales-engineering workflows.
Configuration architecture
Variant configuration involves three master-data structures. (1) Configurable material: the base product with its characteristics (which options can be set). (2) Configurable BOM (super-BOM): contains all possible components across variants, with selection rules linking BOM items to characteristic values. (3) Configurable routing: similar structure for production steps. Rules and constraints define valid combinations: which options are compatible, which exclude each other, which imply others. At order time, the configurator resolves the customer's selection into a specific BOM instance and routing instance that drive production. The complexity lives in the master-data design; ongoing variant additions and changes require disciplined master-data management.
Practical considerations
Three patterns characterise successful variant-manufacturing programmes. (1) Match variant granularity to commercial value: not every option deserves a configurable parameter. Options that drive different cost, lead time or supplier need to be in the configuration; pure cosmetic options can stay outside. Discipline here keeps the configuration manageable. (2) Maintain configuration rules rigorously: as products evolve, the rules must evolve too. Stale rules produce invalid orders that crash production. Quarterly or semi-annual rule reviews are standard practice. (3) Integrate with sales-engineering: salespeople need access to the configurator early in the customer dialogue, ideally with pricing and lead-time visibility. CPQ (see CPQ) tools deliver this front-end experience; ERP variant configurators provide the back-end production-side resolution. Tight CPQ-ERP coupling is the differentiator for high-performance variant manufacturers.
How many variants justify a configurable approach?
The rule of thumb: above 50-100 distinct variants of a similar base product, configurable BOM with rules outperforms maintaining separate BOMs. Below that threshold, separate BOMs are simpler. The break-even varies by industry — high-engineering-content products justify configuration earlier; simpler products later.
SAP Variant Configuration versus Tacton — which to choose?
SAP VC for SAP-centric organisations wanting tight integration with S/4HANA-side production execution; depth and maturity, but a less polished sales-side UX. Tacton for organisations prioritising customer and sales-engineering experience; sits as a front-end above various ERP configurators. Many DACH machinery operations use both: Tacton for sales, SAP VC for production.
Does variant manufacturing imply ETO (engineer-to-order)?
Not necessarily. Variant manufacturing covers configure-to-order (combinations of pre-engineered components, no new engineering per order) and engineer-to-order (custom engineering per order). The boundary depends on whether the configuration involves only pre-engineered options or genuinely new engineering. ERP supports both with appropriate setup.
