A manufacturing product configurator is software that converts customer requirements and selected options into a valid definition of a configurable industrial product. It uses a structured product model, configuration rules, engineering constraints and calculations to determine which combinations are allowed and what components are required.
Depending on its scope, the configurator may also calculate price and cost, create a quote, generate a bill of material (BOM), select engineering components, produce CAD outputs or exchange data with enterprise systems. These capabilities are not present in every product configurator, so buyers should distinguish core configuration from related configure, price, quote (CPQ), engineering automation and manufacturing functions.
For example, a pump configurator might accept flow rate, head pressure, fluid type, temperature, motor voltage, materials and connection standards. It can prevent an unsuitable impeller from being paired with a motor, select compatible seals and materials, calculate a duty point and produce a valid configuration for pricing, engineering review or production.
This makes a manufacturing configurator different from a simple online product selector. It represents how an engineered product is built, what constraints apply, which components are needed and what downstream information must be created.
What a manufacturing product configurator does
The central purpose of a configurator is to resolve product variability in a controlled way. Instead of allowing salespeople or customers to choose every possible option independently, the system models relationships between features, dimensions, components, calculations and processes.
A typical configuration process contains these steps:
- Collect requirements: The user enters product parameters such as capacity, dimensions, environment, voltage, material or performance requirements.
- Present valid choices: The system displays relevant options and hides or disables choices that do not apply.
- Apply rules and constraints: Dependencies, exclusions, ranges and engineering conditions are evaluated as selections change.
- Calculate the result: The system may calculate dimensions, performance, quantities, costs, prices or lead-time factors.
- Resolve product data: Components, assemblies, operations, documents and attributes are selected for the configured product.
- Pass the result downstream: The configuration may be sent to a quote, customer relationship management (CRM) system, enterprise resource planning (ERP) system, product lifecycle management (PLM) system, computer-aided design (CAD) tool or manufacturing process.
The output can be as simple as a validated option set or as detailed as a manufacturing-ready product definition. The appropriate output depends on the product, the company’s operating model and the capabilities of the selected software.
Manufacturing product configurator versus generic CPQ
CPQ means configure, price, quote. Generic sales CPQ software often focuses on selecting products, applying discounts and producing commercial proposals. A manufacturing product configurator can include those functions, but it must also represent physical products and engineering relationships.
| Area | Generic sales CPQ | Manufacturing product configurator |
|---|---|---|
| Primary output | A commercial quote or orderable product selection | A valid product definition that may support quoting, engineering and production |
| Product structure | Products, bundles, options and commercial attributes | Features, components, assemblies, dimensions, materials, variants and manufacturing relationships |
| Rules | Option dependencies, eligibility, discounts and approvals | Engineering constraints, compatibility rules, dimensional limits, performance calculations and manufacturing conditions |
| Downstream data | Quote, order and customer information | Potentially BOMs, CAD parameters, drawings, routings, specifications, costs and ERP or PLM records |
| Typical users | Sales, account management and commercial operations | Sales engineering, application engineering, product management, design engineering, manufacturing and operations |
These categories overlap. A manufacturing CPQ platform may include a product configurator, pricing engine, quote generator and workflow tools. Conversely, a product configurator may validate selections without calculating prices or generating quotes. Buyers should evaluate the actual product model and outputs rather than treating all CPQ products as equivalent.
See the guide to CPQ software for manufacturing for a broader explanation of how configuration, pricing, quoting and engineering fit together.
The product model behind a configurator
The product model is the structured representation of how a configurable product is organized. It defines the product’s features, options, components, attributes, values, relationships and outputs. A weak product model may produce a system that is difficult to maintain even if its user interface looks simple.
Product features and options
A feature is a decision area or characteristic, such as drive type, mounting arrangement, enclosure rating or frame size. An option is a selectable value within that feature, such as electric motor, wall mount, IP65 enclosure or 7.5 kW motor.
Some features are discrete. Others are numeric or conditional. A tank configurator may allow a diameter between defined minimum and maximum values, while a conveyor configurator may use length, belt width and incline angle as input parameters.
Components and assemblies
The model can associate selections with physical components and subassemblies. Selecting stainless steel wetted parts in a pump configuration may replace several components, change fasteners and require a different seal arrangement. Selecting a larger motor may also change the baseplate, coupling, guard and electrical documentation.
Attributes and technical data
Attributes describe products and components. Examples include voltage, pressure rating, temperature range, material grade, weight, dimensions, efficiency class and certification. These values can be used for filtering, rules, calculations, documentation and integration.
Versions and applicability
Manufacturing products change over time. A configurator may need effective dates, revision control, regional applicability, market-specific options and product lifecycle states. A rule that is correct for a new motor family may be wrong for an older product revision. The model therefore needs governance, ownership and release processes.
More detail on product models, dependencies and validation is available in the manufacturing product configuration guide.
Rules, constraints and configuration logic
Rules determine how the configurator responds to selections. They can prevent invalid combinations, automatically select related values, calculate results or route unusual configurations to engineering.
Rules-based configuration
Rules-based configuration uses explicit logic such as:
- If the pump handles abrasive slurry, require a specified wear-resistant material.
- If the motor voltage is 480 V, use the compatible starter and electrical enclosure.
- If the platform length exceeds a threshold, require an additional support assembly.
- If a vehicle has a refrigerated body, require the corresponding power and insulation package.
Rules can be expressed as required options, exclusions, defaults, substitutions, conditional visibility, value ranges or formulas.
Constraint-based configuration
Constraint-based configuration focuses on relationships and permitted states. Instead of only listing predefined bundles, it evaluates conditions such as capacity, geometry, load, material compatibility or operating environment.
For example, a pressure vessel configurator may need to consider design pressure, temperature, diameter, wall thickness, material and code requirements together. A selection is valid only when the combined result satisfies the applicable constraints.
Guided selling
Guided selling asks users questions and recommends suitable products or options. It is useful when customers know their application but not the technical product terminology. Guided selling can sit on top of a rules engine, but it is not the same as engineering validation. A recommendation may identify a suitable product family, while a deeper configurator validates the exact dimensions, components and manufacturing result.
Hard stops and warnings
Not every issue must block configuration. A hard stop prevents completion, such as an impossible voltage and motor combination. A warning may allow the user to continue but require engineering review, such as a non-standard operating point or a request outside the normal product envelope.
Industrial examples
Pump configuration
A pump configurator can capture flow, head, liquid properties, temperature, solids content, materials, seal type, motor, voltage and connection standard. Rules may constrain impeller diameter, casing material, seal selection and motor size. Engineering calculations may determine whether the selected pump meets the duty point.
The result might include a product code, selected components, performance data, price, lead-time classification and a configurable BOM. If the company uses CAD automation, the configuration may also drive a pump baseplate or piping arrangement drawing.
Industrial HVAC equipment
An air-handling-unit configurator may use airflow, external static pressure, casing dimensions, insulation, filters, coils, fans, controls and environmental conditions. Changing airflow can affect fan selection, coil size, casing dimensions and electrical requirements.
A valid configuration may produce a technical schedule for the quote, a BOM for engineering, a manufacturing configuration for ERP and a drawing package. The same product model must be carefully governed because changes to one option can affect many downstream outputs.
Material handling equipment
A conveyor configurator may accept conveyor length, width, elevation, belt type, load, speed, drive arrangement and guarding requirements. Rules can determine support spacing, drive size, pulley selection and safety components. A non-standard length may require a warning or an engineer-to-order workflow rather than automatic release.
Electrical equipment
A switchgear or control-panel configurator may manage enclosure size, busbar ratings, incoming supply, breaker types, protection devices, control voltage and communication modules. It must account for compatibility, space, thermal limits and applicable documentation. Configuration alone does not replace electrical design verification, but it can standardize repeatable product families and reduce manual selection errors.
How the configurator fits into the manufacturing technology stack
A product configurator is usually part of a broader information flow. It may operate inside CPQ, as a dedicated configuration service, within an engineering application or as a module connected to enterprise systems.
| System | Typical responsibility | Possible relationship with the configurator |
|---|---|---|
| CRM | Customer, opportunity and sales activity management | Provides account and opportunity context and receives quote status or configured deal information |
| CPQ | Configuration, pricing and quoting | Hosts or invokes the product model and creates commercial outputs |
| ERP | Items, inventory, purchasing, orders, production and finance | Receives orderable products, BOMs, prices, configurations or manufacturing instructions |
| PLM | Product lifecycle, revisions, approvals and engineering product data | Provides released product structures, revisions and engineering metadata |
| PDM | Product data and document management | Stores CAD files, drawings and related technical documents |
| CAD | Computer-aided design and geometry | Receives parameters and may return models, drawings or engineering outputs |
| PIM | Product information for distribution and digital channels | Supplies descriptions, attributes, images and channel content |
| MES | Manufacturing execution and shop-floor operations | May receive production-relevant configuration, instructions or genealogy data |
These systems are not interchangeable. PLM is not simply a larger product configurator, ERP is not a rules engine, and CAD geometry is not the same as a manufacturing BOM. The integration architecture should define which system owns each type of data and how revisions are synchronized.
The CPQ integration guide covers these system relationships in more detail.
From configuration to BOM, CAD and quote
Configuration and the BOM
A bill of material (BOM) lists the components, subassemblies and quantities required for a product. A configurator may resolve a configurable BOM by adding, removing or substituting components based on the selected options.
An engineering BOM (EBOM) represents the product from an engineering perspective. A manufacturing BOM (MBOM) represents how the product is assembled or produced. These structures may differ. A configurable product model may need to produce or help reconcile both, rather than assuming that one list serves every department.
BOM generation requires reliable item identifiers, revision data, quantities, effectivity, units of measure and clear ownership. A configuration engine that only returns text descriptions is not necessarily generating a manufacturing-ready BOM.
Configuration and CAD automation
CAD automation can use configuration values to select models, set dimensions, suppress features, create assemblies or generate drawings. For a pump skid, the configured pump, motor, base, piping and connection arrangement may drive a layout drawing.
CAD automation has additional dependencies: parametric models must be stable, naming conventions must be controlled, geometric conditions must be tested and the resulting files must be managed with appropriate revisions. A configurator can provide parameters without being a CAD automation system.
Configuration and pricing
Price is related to configuration but is not the same thing. A price engine may use component prices, quantity breaks, labor, material costs, freight, currency, customer agreements, margins and approval thresholds. Engineering calculations may affect price when dimensions, ratings or materials change.
Costing and pricing logic should be traceable. Users should be able to understand whether a price came from a component, formula, surcharge, discount, project cost or manual adjustment.
Configuration and quoting
A quote can include commercial terms, delivery assumptions, technical descriptions, exclusions, approvals and attachments. A configuration supplies technical content, but quote generation requires separate document and workflow logic. The two functions often work together in CPQ, but they should not be treated as identical.
See BOM, pricing and quoting in manufacturing CPQ for the relationship between these outputs.
Manufacturing workflows supported by configurators
Configure-to-order
In configure-to-order (CTO), the company sells a product assembled from predefined and validated options. The configurator can select the correct components and pass the result to order processing or production. CTO works best when product boundaries, options and manufacturing data are well defined.
Make-to-order and assemble-to-order
Make-to-order (MTO) products are produced after an order is received, often using a defined product structure. Assemble-to-order (ATO) products are assembled from stocked or prepared modules. A configurator can resolve the required modules and options, but inventory and production planning remain ERP or manufacturing responsibilities.
Engineer-to-order
In engineer-to-order (ETO), the final product requires new or substantially changed engineering work. A configurator may capture requirements, validate the standard envelope, calculate preliminary values and identify a standard starting point. It should then route non-standard requirements to engineering rather than pretending that every result can be generated automatically.
A practical design often uses a threshold: standard configurations proceed automatically, while out-of-range dimensions, unapproved materials or unusual duty conditions create an engineering task.
Read more about these patterns in the manufacturing CPQ workflow guide.
Benefits of a manufacturing product configurator
- Fewer invalid combinations: Rules prevent incompatible motors, materials, ratings, dimensions or accessories from being selected together.
- Faster technical sales: Sales teams can resolve repeatable applications without waiting for an engineer to rebuild the same logic manually.
- More consistent quotes: Standardized configuration and pricing inputs reduce variation between sales channels.
- Lower engineering workload: Routine selections, calculations, component resolution and document generation can be automated where the product model supports it.
- Better handoff to operations: A validated configuration can carry technical information into ERP, PLM, CAD or production workflows.
- Preserved product knowledge: Rules and calculations make some engineering knowledge explicit and reusable rather than keeping it only in spreadsheets or individual expertise.
- Improved change control: Versioned models can help organizations manage product revisions and effective dates.
Limitations and risks
A configurator does not automatically make a product configurable. The product must have sufficiently understood options, constraints and outputs. Common limitations include the following:
- Incomplete product knowledge: If rules exist only in informal practices or spreadsheets, modeling them requires discovery and validation.
- Rule conflicts: Overlapping or contradictory rules can create unexpected outcomes and difficult troubleshooting.
- High maintenance effort: New components, suppliers, regulations, prices and engineering revisions can require frequent model updates.
- Unclear ownership: Product management, engineering, sales and IT may disagree about who can change rules and approve releases.
- ETO complexity: Highly novel products may not fit a fixed option model and still require engineering judgment.
- Integration mismatch: Different item numbers, revisions, units, structures and lifecycle states can make ERP, PLM and configurator synchronization difficult.
- False confidence: A valid software configuration is not necessarily a complete safety, regulatory or engineering approval.
- Technical debt: Hard-coded exceptions and duplicated logic can make the model fragile over time.
These risks are reasons to establish model governance and testing, not reasons to assume that configuration software is unsuitable.
How to design a maintainable product model
Start with product families and boundaries
Define which products are genuinely configurable and where a new model, product family or engineering process is required. Avoid placing unrelated products into one large rule set simply because they share a sales screen.
Separate concerns
Keep product selection, engineering constraints, pricing, document text and integration mappings distinct where the platform allows it. A motor compatibility rule should not be hidden inside a quote paragraph, and a discount rule should not determine whether an impeller is technically valid.
Use reusable rules
Common constraints should be represented once and reused where possible. For example, an enclosure-rating rule may apply across several electrical product families. Reusable logic reduces duplication but must still account for product-specific exceptions.
Make rules explainable
Users need useful messages such as the selected motor is below the calculated power requirement, not only a generic invalid configuration error. Explainability helps sales users, engineers and administrators correct problems.
Control ownership and releases
Assign owners for product data, rules, calculations, pricing and integrations. Use approval and release states so that changes are reviewed before they affect live quotes or orders.
Test realistic combinations
Testing should include normal configurations, boundary values, invalid combinations, obsolete components, regional variations, revisions, missing data and integration failures. Automated regression tests are particularly valuable when a product family contains many interacting options.
The CPQ implementation guide discusses requirements, migration, testing, governance and maintenance.
How to evaluate configurator software
Manufacturers should evaluate a product configurator against the complexity of their products and the outputs they require. Useful questions include:
- Can the system model numeric parameters, ranges, dependencies, exclusions and calculations?
- Can rules distinguish warnings from hard stops and route exceptions to engineering?
- Can product models be versioned, tested, approved and maintained by appropriate users?
- Can the system represent configurable components, subassemblies and quantities?
- Does it generate a true BOM, or only a product code and description?
- Can it support EBOM, MBOM or configurable BOM requirements?
- Does it integrate with the company’s ERP, PLM, PDM, CAD, CRM or MES systems?
- Can it support standard CTO products as well as controlled ETO exceptions?
- Are calculations, assumptions, units and engineering formulas traceable?
- Can dealers, distributors, internal sales teams and customers use different views or permissions?
- Are APIs available for ecommerce, portals or headless configuration experiences?
- How are revisions, effective dates, regional rules and discontinued items handled?
- What tools exist for debugging rules, comparing model versions and analyzing configuration errors?
Feature checklists are not enough. Ask vendors to demonstrate a representative product family using real constraints, real component structures and realistic downstream outputs. Vendor claims should be separated from capabilities that have been verified in the proposed deployment.
Implementation approach
- Document the current process: Map how requirements are gathered, how engineers validate them, how prices are calculated and how data reaches production.
- Select a representative product: Choose a product family with meaningful configuration complexity but defined boundaries. Avoid starting with the easiest brochure product or the most chaotic ETO project.
- Build the product model: Define features, options, parameters, components, calculations, constraints and outputs.
- Clean source data: Reconcile item numbers, descriptions, units, revisions, costs, prices, drawings and lifecycle states.
- Define system ownership: Decide whether ERP, PLM, CAD, CPQ or another system owns each data object and how updates are exchanged.
- Test with users: Use sales engineers, product managers, design engineers, manufacturing and operations staff to test realistic scenarios.
- Release incrementally: Start with a controlled product scope, measure results and expand after the model and governance process are stable.
- Maintain continuously: Treat the product model as operational software. Review rule changes, regression tests, release notes and user feedback.
Semantic map
The following relationships summarize the entities discussed in this guide:
- Manufacturing product configurator → applies → product rules and engineering constraints
- Product model → represents → configurable product structure
- Configuration rules → prevent → invalid component combinations
- Constraint-based configuration → validates → combined product requirements
- Guided selling → collects → application requirements
- Configured product → resolves → components and subassemblies
- Configured product → can generate → configurable BOM
- Engineering BOM → represents → product design structure
- Manufacturing BOM → represents → production assembly structure
- CAD automation → generates → product-specific models and drawings
- Pricing engine → calculates → configured product price
- CPQ → produces → technical and commercial quote
- Configurator → exchanges data with → ERP
- Configurator → can use → PLM product revisions
- ETO workflow → routes → non-standard requirements to engineering
- Product model governance → controls → rule releases and revisions
Frequently asked questions
What is a manufacturing product configurator?
It is software that converts product requirements and selected options into a valid definition of an engineered product. It may also produce prices, quotes, BOMs, drawings or system data, depending on its capabilities.
Is a product configurator the same as CPQ?
No. CPQ means configure, price, quote. A configurator handles product selection and validation, while CPQ usually adds pricing, quoting and commercial workflows. Some CPQ platforms include manufacturing-grade configuration, but not all do.
What is the difference between a product configurator and a product selector?
A selector usually filters products or recommends a suitable model. A configurator resolves a specific combination of options, parameters, constraints and components and may create downstream engineering or manufacturing data.
Can a configurator generate a BOM?
Some can, but this is not universal. Buyers should verify whether the system creates a structured configurable BOM with item identifiers, quantities, revisions and effectivity, or only returns a configuration code and description.
Does a configurator replace engineering?
Usually not. It can automate repeatable engineering decisions and identify invalid selections, but safety reviews, regulatory approval, novel designs and non-standard requirements may still require qualified engineers.
What types of manufacturing products benefit most from configuration?
Products with repeatable option combinations and meaningful technical constraints are strong candidates. Examples include pumps, valves, industrial machinery, HVAC units, electrical equipment, conveyors, vehicles and material handling systems.
What are configuration rules?
Configuration rules define allowed, required, excluded or calculated relationships between product options and parameters. They can specify compatibility, ranges, defaults, substitutions, warnings and engineering review conditions.
What is constraint-based configuration?
Constraint-based configuration evaluates whether a combination of values satisfies technical relationships and limits. It is useful for products where dimensions, capacities, materials, loads or performance requirements interact.
What is guided selling in a configurator?
Guided selling asks application questions and recommends products or options in terms users understand. It can improve product selection, but it does not by itself prove that a detailed engineering configuration is valid.
Can configurators support engineer-to-order products?
They can support the front end of an ETO process by capturing requirements, validating standard limits and identifying exceptions. Fully novel designs generally still require engineering work outside the standard configuration model.
How does a configurator connect to ERP?
It may send product codes, configuration attributes, BOMs, prices, order details or production-relevant data to an ERP system. The exact integration depends on system ownership, data structures, APIs and the configurator’s documented capabilities.
What is the difference between an EBOM and an MBOM?
An EBOM, or engineering bill of material, represents the product from a design perspective. An MBOM, or manufacturing bill of material, represents how the product is assembled or produced. They can contain different structures and information.
Can a configurator automate CAD?
Some platforms integrate with CAD automation tools or can drive parametric models. This is a separate capability from basic configuration and requires stable CAD templates, parameter mappings, revision control and testing.
How are product configurator rules maintained?
Rules should have owners, documentation, version control, approval steps, release states and regression tests. Maintenance includes updating components, prices, calculations, product revisions, regulations and integration mappings.
What happens when a user selects an invalid option?
The system may prevent the selection, remove an incompatible option, display a warning, suggest an alternative or route the configuration to engineering. The correct response depends on the severity and business process.
Can customers use a manufacturing configurator directly?
Yes, some organizations expose a simplified configurator through ecommerce, dealer portals or customer self-service. Complex or safety-critical products often restrict advanced choices to trained sales or engineering users.
What data is needed to implement a configurator?
Typical inputs include product structures, options, parameters, component identifiers, compatibility rules, calculations, prices, revisions, documents, workflows and integration mappings. Data quality and ownership are as important as software functionality.
How should a manufacturer choose a configurator?
Evaluate the system using a representative product and real rules. Test configuration depth, calculations, BOM behavior, CAD or PLM integration, pricing, ETO handling, governance, APIs, implementation effort and downstream outputs rather than relying on generic feature counts.
What is a configurable BOM?
A configurable BOM is a product structure that resolves into different component lists or quantities according to selected options and parameters. It may serve engineering, manufacturing or order processing, but its intended use must be defined.
Is a configurator useful if a company does not generate automatic CAD?
Yes. A configurator can still validate options, capture requirements, calculate prices, create quotes, resolve components and support ERP or engineering workflows without generating CAD. CAD automation is an optional capability.