Tag: configurable BOM

A CPQ rules engine is the decision-making component of a Configure, Price, Quote system. It evaluates a product model, applies configuration rules and constraints, and determines whether a proposed product is valid, manufacturable and commercially quotable. In manufacturing CPQ, the result may include a valid configuration, calculated dimensions, a price, a configurable bill of materials (BOM), engineering parameters, a CAD variant or a handoff to an engineer for further design work.

The rules engine does not simply display product options. It encodes relationships such as which motor is suitable for a pump, which materials are compatible with a chemical application, how frame dimensions affect component selection, and when a configuration must be routed to engineering. It is therefore central to the product model and should be treated as operational manufacturing logic rather than as a collection of sales prompts.

A rules engine is only one part of CPQ. Product configuration determines what can be selected, engineering logic determines how the product must be designed, pricing logic determines what it costs or should sell for, and quoting tools present the result to the customer. Some CPQ platforms also generate BOMs, CAD outputs or manufacturing data; others integrate with specialist engineering, product lifecycle management or enterprise resource planning systems instead.

What is a CPQ rules engine?

A CPQ rules engine is software that evaluates conditions and actions within a configurable product model. It uses inputs such as product options, dimensions, performance requirements, customer selections, production constraints and commercial policies to produce decisions or calculated outputs.

For example, a rules engine for an industrial pump may evaluate:

• fluid type, temperature and viscosity;
• required flow rate and pressure;
• pump family and impeller diameter;
• motor power, voltage and frequency;
• casing, seal and material compatibility;
• installation orientation and connection standard;
• lead time, plant capability and regional compliance requirements.

It may then prevent invalid selections, recommend a suitable pump size, calculate a required motor rating, add components to a configurable BOM, apply a price adjustment and identify whether the order is configure-to-order (CTO) or engineer-to-order (ETO).

A generic sales CPQ application may use rules to control discounts, bundles and quote approvals. Manufacturing CPQ uses those capabilities but extends them into product and engineering domains. The critical question is not only whether a salesperson can sell an option, but whether the selected product can be designed, costed, built and supported.

Where the rules engine fits in a manufacturing CPQ architecture

The rules engine normally sits between the user interface and the systems that hold product, engineering and commercial data. A typical flow is:

1. A salesperson, dealer, customer or engineer starts a configuration.
2. The CPQ application loads the relevant product model, version and context.
3. The user selects options or enters requirements such as capacity, dimensions or material.
4. The rules engine evaluates constraints, dependencies, calculations and recommendations.
5. The configuration interface enables, disables, recommends or rejects selections.
6. Pricing, costing, BOM and engineering services use the validated configuration.
7. Outputs are sent to quoting, customer relationship management (CRM), enterprise resource planning (ERP), product lifecycle management (PLM), product data management (PDM), computer-aided design (CAD) or manufacturing execution systems (MES), depending on the architecture.

These systems have different responsibilities. A CRM system manages customer and opportunity information. An ERP system manages transactions such as orders, inventory, purchasing and production planning. PLM manages product structures, revisions and lifecycle information. PDM focuses primarily on engineering files and related product data. CAD creates or modifies engineering designs. MES supports execution and tracking on the factory floor. CPQ coordinates the commercial configuration process and may use data from all of these systems without replacing them.

More detail on these boundaries is available in the guide to CPQ integrations.

The main components of a CPQ rules engine

1. Product model

The product model describes the configurable product, its structure and its allowable choices. It may contain product families, models, features, options, attributes, components, dimensions, units of measure and default values.

For an industrial air-handling unit, the model might contain:

Model element	Example	Purpose
Product family	Air-handling unit	Defines the overall configurable product
Feature	Cooling section	Groups related choices
Option	Chilled-water coil	Represents a selectable alternative
Attribute	Airflow, width or voltage	Stores a value used by rules and calculations
Component	Fan, filter or control panel	May contribute to the BOM
Revision	Model version 2025.1	Controls which rules and components are valid

The product model is more than a catalogue. It is a structured representation of how the product is sold and engineered. A weak model may contain options without the relationships needed to validate a real product. A strong model connects commercial choices to technical consequences and downstream outputs.

See the product configuration guide for a detailed explanation of product models, features, options and constraints.

2. Rule definitions

Rules describe how the model behaves. Most rules can be expressed as a condition and an action:

IF application_fluid = "corrosive"
THEN require casing_material IN ["316 stainless steel", "duplex stainless steel"]

Rules can require an option, prohibit an option, recommend a choice, set a default, calculate a value, add a component, remove a component, assign a price, trigger an approval or route a configuration to engineering.

A rule may be simple, but manufacturing products often require rules that combine several inputs:

IF flow_rate > 120 m3/h
AND discharge_pressure > 8 bar
THEN require pump_frame = "heavy duty"
AND require motor_power >= 45 kW

Rules should be written so that their purpose, owner, scope and effective date are clear. A rule that exists only as an undocumented expression inside an application is difficult to test and maintain.

3. Constraints

Constraints define combinations that are allowed or forbidden. They are central to configuration validation.

Common constraint types include:

• Compatibility constraints: a 60 Hz motor cannot be selected for a market requiring a 50 Hz electrical system.
• Mutual exclusion: two options cannot be selected together because they use the same physical space.
• Dependency: a high-temperature seal requires a compatible casing material and cooling arrangement.
• Requirement constraints: a particular control module is required when a remote-monitoring option is selected.
• Range constraints: a tank diameter must remain within the manufacturing capability of a selected plant.
• Cardinality constraints: a vehicle may allow one powertrain but several accessory packages.
• Resource constraints: a configuration may be valid technically but unavailable because a component is obsolete or not approved for the target region.

A constraint can be hard or soft. A hard constraint blocks an invalid combination. A soft constraint allows the configuration but displays a warning, recommendation or approval requirement. For example, a pump may technically operate with a selected impeller and motor, but the combination may be outside the preferred efficiency range. The system could warn the user rather than reject it.

4. Dependency and propagation logic

Configuration choices often propagate through the model. Selecting a product family can limit available options. Selecting an option can set dimensions, alter a calculated value or add a component. Changing a dimension can invalidate an earlier choice.

Consider a conveyor configuration:

1. The user selects a belt width of 1,200 millimetres.
2. The rules engine restricts the available drive units to those rated for that width and load.
3. The required motor power is calculated from length, incline, material and throughput.
4. The frame and guarding options are updated.
5. The BOM receives the correct belt, rollers, drive assembly and support members.
6. The price is recalculated from the selected components and length.

This propagation may occur immediately in the user interface or through a server-side validation service. The important design issue is consistency: the same logic must be applied when a configuration is created, edited, recalculated, imported through an API or converted into an order.

5. Calculation and engineering logic

Some manufacturing products cannot be configured using yes-or-no rules alone. They require calculations. Examples include heat exchanger sizing, motor selection, structural capacity, cable sizing, pressure drop, thermal performance, battery capacity and vehicle payload.

A calculation rule may derive an output from several inputs:

required_motor_power = (flow_rate * pressure_rise) / efficiency_factor

In practice, engineering calculations may include unit conversions, safety factors, lookup tables, interpolation, standards and product-specific formulas. The CPQ system may perform the calculation itself, call an external engineering service or pass the inputs to CAD or simulation software.

Calculation results should be distinguished from selections. A motor power of 30 kW may be a calculated requirement, while a specific motor catalogue number is a subsequent selection based on that requirement. Keeping these concepts separate improves traceability and makes rules easier to review.

For CAD, drawings, parametric models and engineering automation, see the CAD and engineering automation guide.

How a CPQ rules engine evaluates a configuration

The exact implementation varies by platform, but a typical evaluation cycle contains the following stages.

1. Load context

The engine loads the product model version and the context of the transaction. Context can include customer, country, currency, sales channel, plant, effective date, language, opportunity type and user permissions.

Context matters in manufacturing. A valve may require different certifications by market. A component may be available from one plant but not another. A dealer may see a different price list from an internal sales engineer. A product revision may be valid for new orders after a release date but not for an existing contract.

2. Accept inputs

Inputs can come from user selections, imported customer requirements, a CRM opportunity, an ecommerce session or an engineering template. The system should identify the source and value of each important input.

For example, “capacity” could be entered directly by a salesperson, derived from flow and pressure, or imported from a previous design. These cases may need different validation and audit treatment.

3. Apply defaults and recommendations

The engine may set safe defaults or recommend common combinations. Defaults accelerate configuration but should not conceal important engineering decisions. A default should have a clear rationale and remain visible when it affects cost, performance or manufacturability.

Guided selling is related but not identical to rules-based configuration. Guided selling asks questions and recommends a product or package based on customer needs. Rules-based configuration validates the detailed product structure. A manufacturing CPQ implementation may use guided selling at the beginning and a deeper constraint model after the product family has been selected.

4. Validate constraints

The engine checks compatibility, dependencies, ranges, quantities and required selections. It may report errors immediately or validate the complete configuration at a checkpoint.

Good validation messages explain what is wrong and how to resolve it. “Invalid configuration” is less useful than “A stainless-steel pump casing is required for the selected corrosive fluid. Select 316 stainless steel or change the fluid classification.”

5. Calculate derived values

The engine calculates values such as capacity, weight, dimensions, motor rating, cable size, material quantity, discount eligibility, cost and selling price. Calculation order matters. A price may depend on a calculated component, while the component may depend on a dimension entered by the user.

6. Generate downstream outputs

After validation, the configuration can be used to produce one or more outputs:

• a configured product summary for the quote;
• a price and cost breakdown;
• a configurable BOM or order BOM;
• engineering parameters for CAD or design automation;
• technical data sheets and customer documentation;
• an approval request;
• an ERP order line or manufacturing request;
• an ETO work item for engineering.

Not every CPQ platform generates every output. Buyers should verify whether an output is native, produced through configuration, or dependent on a separate integration.

Rules, pricing, BOMs and engineering outputs

Configuration rules versus pricing rules

Configuration rules answer questions such as “Can this option be selected?” or “Which component is required?” Pricing rules answer questions such as “What should this valid configuration cost?” or “Which discount requires approval?”

The two rule sets interact but should not be confused. A high-temperature seal may be technically required by a fluid temperature rule. Its price may then be retrieved from a price list or calculated from material and size. If technical validity and commercial pricing are mixed into one opaque rule, it becomes difficult to determine whether an error is caused by product logic or a price policy.

Configurable BOMs, EBOMs and MBOMs

A bill of materials (BOM) is a structured list of components and quantities. A configurable BOM contains alternatives, conditions or rules that allow the final structure to be derived from a configuration.

An engineering BOM (EBOM) represents the product from an engineering design perspective. A manufacturing BOM (MBOM) represents how the product is assembled and produced, including manufacturing-specific groupings, operations or consumables. A CPQ result may resemble an EBOM, an MBOM, an order BOM or a sales BOM, depending on the process.

For example, a CPQ system may identify the selected gearbox, motor and frame. ERP may then use those selections to create an order-specific manufacturing structure. Alternatively, CPQ may generate a complete BOM and send it to ERP. The boundary must be designed explicitly rather than assumed.

Read more in the guide to BOM generation, pricing and quote automation.

CAD and drawing automation

When a configuration includes dimensions or geometry, the rules engine may pass validated parameters to CAD automation. A CAD system can then generate a model, drawing, layout or file for review. The CPQ rules engine should not be treated as a replacement for CAD. It determines which parameters and options are valid; CAD applies geometric and drafting logic.

A useful separation is:

• CPQ determines the commercial and configurable product definition.
• The rules engine validates selections and calculates design inputs.
• CAD generates geometry and drawings from those inputs.
• PLM or PDM controls revisions, files and engineering release status.

Rules-based, constraint-based and guided configuration

Approach	How it works	Manufacturing use	Limitation
Rules-based configuration	Explicit conditions trigger actions or validations	Option dependencies, component selection and approval logic	Can become difficult to maintain if rules are duplicated or poorly structured
Constraint-based configuration	The engine evaluates a network of allowed and forbidden relationships	Complex compatibility, sizing and engineering constraints	Requires disciplined modelling and clear explanations of failures
Guided selling	Questions and recommendations lead the user toward a product or package	Dealer, sales and self-service product selection	May not validate detailed engineering or manufacturing requirements on its own

These approaches are complementary. A dealer portal may begin with guided questions, use rules to narrow the product family, apply constraints to validate the detailed configuration and use calculation logic to produce an order-ready result.

Manufacturing workflow example: configuring a hydraulic power unit

Assume a manufacturer sells hydraulic power units with configurable reservoir size, pump type, motor, valves, filtration, controls and mounting arrangements.

Inputs

• required flow rate and operating pressure;
• fluid type and operating temperature;
• available electrical supply;
• mounting orientation and available footprint;
• control method and communication requirements;
• environmental and enclosure requirements.

Rules and calculations

• Calculate minimum pump displacement from flow and speed.
• Require a suitable motor rating for pressure, flow and efficiency.
• Prevent a reservoir size below the required fluid volume.
• Require a high-temperature seal package above a defined operating temperature.
• Restrict enclosure and coating choices for the selected environment.
• Add a return-line filter when the selected circuit requires it.
• Require an engineering review when the footprint is below the standard mounting envelope.

Outputs

• validated configuration summary;
• calculated pump and motor requirements;
• component-level BOM;
• cost and selling price;
• lead-time estimate based on selected components;
• technical data sheet;
• engineering task if a non-standard mounting or control arrangement was selected.

This example shows why the rules engine is more than a user-interface feature. It connects customer requirements to engineering decisions, commercial results and downstream work.

Maintainability and governance

Rules are product knowledge. They need ownership, version control, testing and release processes comparable to other important product data.

Assign rule ownership

Different rules may belong to different functions. Product management may own option availability. Engineering may own performance and compatibility rules. Manufacturing may own plant and process constraints. Finance or commercial operations may own discount and approval rules. A governance model should define who can propose, approve, test and release each category.

Separate rule categories

Keep technical constraints, calculations, BOM logic, pricing, approvals and user-interface recommendations logically separate where possible. This makes changes safer and allows a technical rule to be tested independently from a sales policy.

Use effective dates and revisions

Products evolve. Components become obsolete, suppliers change materials and new standards apply. Rules need effective dates, revision identifiers and a clear relationship to product model versions. A quote created under one revision should not silently change because a rule was edited later.

Test combinations, not only individual rules

Testing one rule at a time is insufficient. Rules interact, and a change in one product area can create invalid combinations elsewhere. Test cases should include valid configurations, prohibited combinations, boundary values, missing inputs, regional variations, obsolete components, high-volume configurations and transitions between product revisions.

Automated regression tests are useful for large product models. A test can submit a known configuration and verify that validation status, calculated values, BOM lines, price and routing outcome remain correct after a model change.

Measure maintainability

Useful operational measures include the number of manual overrides, engineering escalations, rule defects, configuration rework events, duplicate rules, unresolved warnings and time required to release a product-model change. These measures are more informative than simply counting how many rules exist.

The CPQ implementation guide covers product data, migration, testing, governance and ongoing maintenance in more detail.

Common limitations and failure modes

Rules become an undocumented codebase

When every exception is added directly to the model, the rules engine can become difficult to understand. Similar rules may conflict, and no one may know which rule has priority. Use naming standards, descriptions, ownership, reusable functions and review procedures.

The product model is incomplete

A rules engine cannot validate information that has not been modelled. If engineering constraints exist only in spreadsheets, emails or individual experience, the CPQ result may look complete while still requiring manual review.

Too many hard stops

Blocking every unusual configuration can frustrate experienced sales engineers and encourage workarounds. Distinguish between impossible, unsafe, unprofitable and merely non-standard cases. Use warnings, approvals or ETO routing where appropriate.

Rules are duplicated across systems

Product logic may be copied into CPQ, ERP, ecommerce, CAD automation and custom middleware. Duplicated logic can produce different answers. Define a system of record for each type of data and decide which system owns each calculation or validation.

Performance declines with model complexity

Large product models, extensive constraint networks, external calculations and real-time integrations can make configuration slow. Performance should be tested with realistic product structures and concurrent users, not just a small demonstration model.

Human engineering judgment is overlooked

Not every ETO decision can be reduced to a deterministic rule. A good architecture supports controlled handoffs, engineering review, assumptions, attachments and revision of the configuration after review. Automation should remove repetitive work without pretending that every design decision is already known.

How to evaluate a CPQ rules engine

Manufacturers evaluating a CPQ engine should ask questions about product complexity rather than rely on feature counts.

Evaluation area	Questions to verify
Product modelling	Can the system represent nested products, options, attributes, revisions, units and configurable components?
Constraints	Can it express dependencies, mutual exclusions, ranges, cardinality and context-specific restrictions?
Calculations	Can it handle formulas, lookup tables, units, rounding, external services and engineering approvals?
Explainability	Can users understand why a selection is blocked, required or recommended?
BOM output	Does it generate a configurable BOM, order BOM, EBOM or MBOM, and how is ownership divided with ERP or PLM?
Engineering automation	Can it provide parameters to CAD or engineering tools, and what file or revision controls are available?
Versioning	Can the organisation test, approve, release and retire product-model revisions?
Integration	How are CRM, ERP, PLM, PDM, CAD, PIM and MES data exchanged, and which system owns each value?
Performance	How does evaluation perform for large models, complex constraints and concurrent users?
Governance	Can product, engineering, manufacturing and commercial teams manage rules without uncontrolled duplication?

Documented capability should be separated from roadmap claims or assumptions. A vendor may support pricing rules but require a separate product configurator for engineering constraints. Another may support BOM generation but rely on ERP for the final manufacturing structure. The implementation architecture matters as much as the feature list.

Relationship to CTO, ETO, MTO and ATO

Manufacturing process types influence how the rules engine is used:

• Configure-to-order (CTO): the rules engine selects from predefined, validated options and produces repeatable order data.
• Engineer-to-order (ETO): the rules engine captures requirements and identifies where engineering must create or approve a unique design.
• Make-to-order (MTO): the product is made after the order, often using a defined product model with order-specific values.
• Assemble-to-order (ATO): standard modules are assembled after the order; the rules engine validates module compatibility and assembly choices.

A single manufacturer may use all four approaches across different product families. The CPQ model should therefore identify which decisions are automated, which outputs are standard and which cases require engineering intervention. See the guide to manufacturing CPQ workflows.

Implementation principles

1. Start with a representative product family. Choose a product that exposes meaningful configuration, engineering and manufacturing complexity without attempting to model the entire catalogue immediately.
2. Document the current decision process. Capture spreadsheets, selection charts, engineering checks, price logic, BOM rules and approval paths.
3. Define the target output. Decide whether the first release must produce a quote only, a validated configuration, an order BOM, CAD parameters or an engineering request.
4. Establish data ownership. Identify whether CPQ, ERP, PLM, PDM or another system owns each product, component, price, revision and status value.
5. Model standard paths first. Automate repeatable CTO and ATO cases before encoding every rare ETO exception.
6. Design for explanation. Users need actionable reasons for warnings, blocked options and engineering escalations.
7. Build a release process. Treat rule changes like product changes, with review, testing, effective dates and rollback procedures.
8. Monitor the live model. Track overrides, defects, escalations, abandoned configurations and downstream corrections.

Semantic map

The following relationships summarize how a CPQ rules engine connects product configuration with engineering and manufacturing systems:

• CPQ uses a product model to represent configurable products.
• Configuration rules prevent invalid combinations.
• Constraints validate technical and commercial relationships.
• Configuration inputs drive engineering calculations.
• Engineering calculations determine required product parameters.
• A validated configuration generates a quote.
• A configured product can generate a configurable BOM.
• An EBOM represents an engineering product structure.
• An MBOM represents a manufacturing product structure.
• CAD automation generates product-specific models and drawings.
• CPQ exchanges customer and opportunity data with CRM.
• CPQ exchanges order and item data with ERP.
• PLM manages product lifecycle and revision information.
• PDM manages engineering files and related product data.
• ETO routing sends non-standard configurations to engineering.
• Rules governance controls product-model changes.

Frequently asked questions

1. What does a CPQ rules engine do?

It evaluates product selections and requirements against configuration, engineering, pricing and process rules. It can validate a product, calculate values, select components, produce outputs and route exceptions to engineering.

2. Is a CPQ rules engine the same as a product configurator?

Not exactly. A product configurator is the broader application or capability used to define a product. The rules engine is the logic layer that evaluates selections, constraints and calculations within that configurator.

3. How is a manufacturing CPQ rules engine different from a sales CPQ engine?

Sales CPQ commonly focuses on bundles, pricing, discounts and approvals. Manufacturing CPQ also addresses product constraints, dimensions, materials, engineering calculations, BOMs, CAD inputs and production or engineering handoffs where supported.

4. What is a configuration rule?

A configuration rule defines a condition and an action, such as requiring a high-temperature seal when a pump operates above a specified temperature.

5. What is a configuration constraint?

A constraint defines an allowed, forbidden or conditional relationship between product choices, values or resources. It may prevent incompatible options or restrict a value to a valid range.

6. Can a rules engine calculate engineering values?

Some can perform formulas, lookup logic and unit conversions. Others call external engineering or calculation services. The specific capability must be verified for the CPQ platform and product domain.

7. Can CPQ rules generate a BOM?

Some manufacturing CPQ systems generate configurable or order-specific BOMs. Others send validated selections to ERP, PLM or a separate BOM service. The resulting structure and system of record should be defined during design.

8. Does a configurable BOM equal an EBOM?

No. A configurable BOM describes how a selected configuration resolves into components. An EBOM represents the engineering structure, while an MBOM represents the manufacturing structure. They may share data but serve different purposes.

9. Can a CPQ rules engine generate CAD drawings?

It may provide validated parameters to CAD automation, which then creates models or drawings. Not every CPQ platform includes CAD generation, and CAD, PLM or PDM may remain responsible for files and revisions.

10. How does the engine handle engineer-to-order products?

It can capture requirements, validate known constraints, calculate preliminary values and route non-standard cases to engineering. It should not claim a complete design when engineering work is still required.

11. What happens when rules conflict?

The platform may use priorities, rule dependencies, evaluation order or explicit conflict handling. The implementation should define how conflicts are detected, explained and resolved rather than relying on undocumented precedence.

12. Should every warning block configuration?

No. Safety or impossible combinations may require a hard stop. A non-preferred but technically feasible choice may be better handled through a warning, approval or engineering review.

13. Who should own CPQ rules?

Ownership depends on the rule type. Engineering may own technical constraints, manufacturing may own plant rules, product management may own options, and commercial teams may own pricing and approvals. Shared governance is usually required.

14. How are CPQ rules versioned?

Rules should be associated with product-model revisions, effective dates and release status. This allows the organisation to reproduce an earlier quote and prevent later edits from changing historical transactions.

15. What data does a CPQ rules engine need?

It may need product structures, options, attributes, component data, engineering formulas, constraints, prices, costs, plant capabilities, customer context, revisions and integration mappings.

16. Can a CPQ rules engine replace ERP?

No. CPQ and ERP have different responsibilities. CPQ creates and validates the commercial configuration, while ERP commonly manages orders, inventory, purchasing, production planning and financial transactions.

17. Can rules be reused across products?

Reusable rules or functions can reduce duplication, especially for common materials, voltage standards or approval policies. Reuse must be controlled so that a change does not unintentionally alter unrelated product families.

18. How should a company test a CPQ rules engine?

Test valid and invalid configurations, boundary values, regional contexts, product revisions, pricing outcomes, BOM results, integrations and engineering escalations. Regression testing is important after every major model change.

19. What is the biggest maintainability risk?

The main risk is uncontrolled growth of undocumented exceptions and duplicated logic. Clear ownership, modular rules, versioning, explanations and automated tests reduce that risk.

20. How does guided selling relate to a CPQ rules engine?

Guided selling helps users identify a suitable product or package through questions and recommendations. The rules engine may then perform the deeper technical validation required to configure the final manufactured product.