A bill of materials (BOM) in Configure, Price, Quote (CPQ) is the structured list of components, quantities and relationships generated or selected for a specific product configuration. In manufacturing CPQ, the BOM connects what a customer selects with what engineering, purchasing, production and finance need to cost, price, quote and eventually build the product.
The basic flow is:
- A salesperson, dealer, engineer or customer configures a product.
- Configuration rules validate options, dimensions, materials and dependencies.
- The CPQ system resolves the selections into a configurable BOM or product-specific BOM.
- Component quantities and attributes support costing and pricing.
- The approved configuration and commercial data are assembled into a quote.
- Relevant BOM data may be sent to enterprise systems such as an Enterprise Resource Planning (ERP), Product Lifecycle Management (PLM) or Manufacturing Execution System (MES) platform.
Not every CPQ platform generates manufacturing-ready BOMs. Some systems only use product options to calculate prices and produce a proposal. Buyers should therefore verify whether a platform supports BOM generation, which BOM type it produces, how rules are maintained and whether the output is suitable for engineering or production.
This guide explains how BOMs fit into manufacturing CPQ, how they relate to configuration and pricing, how EBOMs and MBOMs differ, and what manufacturers should evaluate during implementation.
What is a BOM in CPQ?
A BOM in CPQ is a structured representation of the parts, assemblies, materials and quantities required for a configured product. The BOM may be generated dynamically from configuration choices or retrieved from predefined product structures. It can support commercial calculations, engineering review, manufacturing planning or several of these purposes at once.
A typical BOM line may contain:
- item number or material number;
- component description;
- quantity and unit of measure;
- parent assembly;
- effective date or revision;
- make-or-buy status;
- cost and price references;
- optional attributes such as material, finish, size or voltage;
- manufacturing or procurement notes;
- links to drawings, specifications or CAD files.
In a simple sales CPQ application, the BOM may be only a commercial bundle used to calculate a price. In manufacturing CPQ, the BOM can be the result of a deeper product model containing constraints, engineering calculations, variant logic and relationships between configured features.
For example, configuring an industrial pump may involve selecting flow rate, pressure, fluid type, motor power, seal material, impeller material, connection standard and enclosure rating. Those choices can determine the pump assembly, motor, coupling, baseplate, seal kit, control panel, fasteners and documentation included in the BOM.
The BOM is therefore not merely a list printed on a quote. It is an output of the product configuration model and a potential input to costing, engineering, ERP, PLM, purchasing and production.
How BOM generation fits into the CPQ architecture
Manufacturing CPQ usually contains several related data and logic layers. The exact architecture varies by product and vendor, but the following pattern is common.
| Layer | Purpose | Manufacturing example |
|---|---|---|
| Product model | Defines products, features, options, components and relationships. | A pump family with available impellers, motors and seal types. |
| Configuration rules | Controls valid, invalid, required and conditional choices. | A high-temperature seal is required for a specified fluid and temperature range. |
| Engineering calculations | Derives technical values from customer or application inputs. | Calculating motor size from flow, head and efficiency requirements. |
| BOM logic | Selects components and calculates quantities or structures. | Adding a reinforced baseplate when motor weight exceeds a threshold. |
| Cost model | Applies material, labor, overhead, supplier and manufacturing costs. | Calculating cost from selected steel grade, machining time and purchased motor. |
| Pricing model | Converts cost and commercial rules into customer prices. | Applying customer terms, currency, margin, freight and volume discounts. |
| Quote document | Communicates scope, price, assumptions, validity and commercial terms. | A proposal showing the configured equipment, options, exclusions and price. |
| Enterprise integration | Transfers approved data to surrounding systems. | Sending an order-ready structure and item references to ERP and PLM. |
These layers should be related but not confused. A configuration rule determines whether a combination is valid. A BOM rule determines which components result from that combination. A cost rule determines what the selected components cost. A pricing rule determines what the customer is charged. A quote document presents the result.
For more background, see the guide to product configuration and configuration rules and the overview of BOM generation, pricing and quote automation.
From customer selections to a configured BOM
1. Capture requirements and configuration inputs
The process begins with inputs such as product family, capacity, dimensions, operating environment, materials, accessories, certifications and delivery requirements. These inputs may be entered by an internal salesperson, sales engineer, dealer, customer or engineering user.
In an industrial enclosure example, the inputs could include width, height, depth, ingress protection rating, mounting method, door arrangement, paint system and electrical components. Some values are discrete options, while others are numerical variables or free-form engineering requirements.
2. Validate the configuration
The CPQ rules engine checks the proposed configuration. Rules may require an option, exclude a combination, recommend an alternative or request engineering review.
There are several related approaches:
- Rules-based configuration uses explicit if-then logic, dependencies and compatibility rules.
- Constraint-based configuration evaluates relationships and limits across variables, such as dimensions, load, capacity, temperature or power.
- Guided selling asks questions and recommends suitable products or options, but may not provide the engineering depth required to validate a complex product.
A guided selling interface can be useful for selecting a suitable product family. It is not automatically a substitute for a constraint solver or engineering rules engine.
3. Resolve components and quantities
After validation, BOM logic determines which components belong in the configured structure. A selected option can add an item, replace another item, change a quantity, alter a component attribute or create a new subassembly.
For example, selecting a dual-pump skid might:
- change the top-level equipment quantity from one pump to two;
- add a common skid frame;
- add two motors and two couplings;
- add a shared control cabinet;
- add isolation valves and check valves for each pump;
- change cable and pipe lengths based on layout dimensions;
- require additional instrumentation.
The result may be a multi-level BOM rather than a flat list. A top-level skid contains pump assemblies, each pump assembly contains a motor and hydraulic components, and the control panel contains electrical subassemblies.
4. Apply calculations and attributes
Some BOM values cannot be selected directly. They must be calculated. A configured conveyor may require belt length based on conveyor dimensions. A heat exchanger may require surface area and tube count. A vehicle body may require material quantities based on length, width and payload.
The CPQ system may also assign attributes to BOM lines. A generic motor item might become a specific motor variant with a defined power, voltage, frequency, enclosure and efficiency class. In other cases, CPQ may pass calculated requirements to an ERP or PLM system that selects the final material number.
5. Calculate cost and price
Once the BOM is resolved, the system can use its lines as inputs to costing. Costing may include component purchase prices, manufacturing operations, labor, setup, subcontracting, freight, tooling, scrap, overhead and engineering effort. Pricing then applies commercial policies such as margin, discount, currency, customer segment and approval thresholds.
However, BOM generation and costing are separate capabilities. A CPQ platform may generate a commercial BOM without calculating detailed manufacturing cost. Conversely, a system may calculate price from a product model without producing a production-ready BOM.
6. Produce the quote and route approvals
The quote normally includes a customer-readable description rather than every internal BOM line. It may show major assemblies, options, quantities, technical specifications, exclusions, lead time, price and terms. Internal users may see a more detailed breakdown for margin analysis, review and approval.
Approval workflows can be triggered by low margin, unusual discounts, non-standard materials, extended lead time, engineering risk or an ETO requirement. Engineer-to-order (ETO) products require new or modified engineering work, so the BOM may remain provisional until engineering completes its review.
EBOM, MBOM and configurable BOM
Manufacturers should distinguish among several BOM concepts.
| BOM type | Meaning | Typical purpose |
|---|---|---|
| EBOM | Engineering Bill of Materials: the product structure from a design or engineering perspective. | Defines designed assemblies, parts, revisions and technical relationships. |
| MBOM | Manufacturing Bill of Materials: the structure used to plan and build the product. | Includes manufacturing assemblies, operations, work-center relationships, consumables or packaging where applicable. |
| Configurable BOM | A rules-driven structure containing alternatives, optional items, quantities or conditions. | Represents a product family before one customer configuration is finalized. |
| Configured or order BOM | The resolved structure for one specific order or quote. | Supports a particular customer requirement, order, build or engineering review. |
A CPQ system may own the configurable product model and produce a configured BOM, while PLM owns the authoritative EBOM and ERP or manufacturing systems manage the MBOM. In other architectures, CPQ may read item and structure data from PLM or ERP and return only configuration selections and commercial information.
These responsibilities must be defined explicitly. Treating an EBOM and an MBOM as interchangeable can create problems with assembly sequence, phantom assemblies, work instructions, bulk materials, packaging and shop-floor reporting.
Read more about manufacturing and CPQ terminology, including EBOM, MBOM, CTO and ETO.
Manufacturing examples
Industrial pump configuration
A pump manufacturer may sell several product families with options for capacity, pressure, fluid, temperature, impeller diameter, seal type, motor, coupling, baseplate and controls.
The configuration model can validate that:
- the selected impeller supports the required flow and head;
- the motor has sufficient power and the correct electrical specification;
- the seal material is compatible with the fluid and temperature;
- the casing material satisfies corrosion requirements;
- the selected flange standard matches the connection requirement;
- the baseplate supports the selected motor and pump arrangement.
The resulting BOM could contain a pump casing, impeller, shaft, mechanical seal, bearings, motor, coupling, guard, baseplate, fasteners, documentation and optional instrumentation. A CAD or engineering system may use the same configuration to generate a drawing or dimensional layout, but that capability is not present in every CPQ implementation.
HVAC equipment
An air-handling unit configuration may include airflow, static pressure, casing dimensions, filters, coils, fans, heaters, dampers, controls and access panels. Dimensions can influence the number of modules, panel quantities, coil size, fan selection and shipping sections.
A quote-only CPQ tool may calculate a price from these choices. A deeper manufacturing CPQ system may generate a variant BOM, calculate performance, create a product-specific drawing and pass an order structure to ERP or PLM. The buyer must verify which of these outputs are actually supported.
Specialty vehicle
A specialty vehicle may be configured with chassis, wheelbase, axle rating, body length, storage modules, electrical systems, hydraulic equipment and safety options. A body length change may affect frame members, floor panels, wiring harnesses, lighting, fasteners and weight calculations.
The BOM may need to reflect both optional content and calculated quantities. It may also need revision control because vehicle programs often evolve while orders remain open.
How BOM data supports costing and pricing
The BOM provides a product-specific basis for cost and price, but it does not automatically make the calculation accurate. The quality of the result depends on item master data, supplier costs, operation rates, labor assumptions, waste factors, currency handling and the date on which values are effective.
Costing inputs
- purchased component cost;
- raw material weight, length, area or volume;
- machine and labor rates;
- setup and changeover time;
- subcontracted operations;
- scrap and yield factors;
- freight, packaging and customs costs;
- engineering or project effort for ETO work;
- tooling and one-time charges.
Pricing inputs
- target margin or markup;
- customer-specific price agreements;
- volume breaks;
- discount authority;
- channel or dealer margins;
- currency and exchange-rate policy;
- tax, freight and surcharge treatment;
- commercial risk and contingency;
- approval thresholds.
Some businesses calculate cost and price in CPQ. Others use CPQ to assemble the commercial structure and rely on ERP for authoritative cost or price data. Integration design should define which system owns each value and how revisions, effective dates and failed transactions are handled.
BOMs and CAD, PLM and ERP integration
BOM-related CPQ architecture commonly involves several enterprise systems with different responsibilities.
| System | Typical responsibility | Possible CPQ relationship |
|---|---|---|
| Customer Relationship Management (CRM) | Accounts, opportunities, contacts and sales activity. | Starts a configuration or stores the quote and opportunity reference. |
| ERP | Items, inventory, purchasing, costing, orders, production and finance. | Provides item and price data or receives an approved order structure. |
| PLM | Product definitions, revisions, engineering changes and lifecycle control. | Provides approved product structures or receives configured engineering data. |
| Product Data Management (PDM) | CAD files, documents and design data management. | Links configured products to models, drawings or controlled documents. |
| CAD | Computer-Aided Design models and drawings. | Uses configuration inputs to generate geometry or documentation where supported. |
| Product Information Management (PIM) | Commercial and technical product content. | Supplies descriptions, images, specifications and channel content. |
| MES | Execution and tracking of manufacturing operations. | Receives production-relevant structures or order data through ERP or direct integration. |
These systems are not interchangeable. A CRM opportunity is not a BOM. A PLM EBOM is not necessarily a manufacturing MBOM. A CAD assembly is not automatically an ERP item structure. CPQ must translate or map data between these contexts when the workflow requires it.
Important integration questions include:
- Which system is authoritative for item numbers and revisions?
- Does CPQ create new items or only select existing items?
- Is the BOM transferred as a flat list, hierarchical structure or both?
- How are configured dimensions and calculated attributes passed downstream?
- How are engineering changes reflected in open quotes?
- What happens when an item, price or revision cannot be found?
- Can the receiving system distinguish a quote BOM from an order or production BOM?
- Are integrations synchronous, asynchronous or manually approved?
See the guide to CPQ integration with ERP, CRM, PLM, PDM, CAD and MES for broader architecture considerations.
CTO, ETO, MTO and ATO BOM workflows
BOM behavior depends on the manufacturing strategy.
| Model | Meaning | BOM implication |
|---|---|---|
| Configure-to-order (CTO) | A predefined product is assembled after the customer selects allowed options. | CPQ can often resolve a known configurable BOM from approved variants. |
| Engineer-to-order (ETO) | Engineering designs or significantly modifies the product for the order. | CPQ may create a preliminary BOM and trigger engineering work before final release. |
| Make-to-order (MTO) | Production starts after an order, using a defined product or specification. | The BOM may be created or released when the order is accepted. |
| Assemble-to-order (ATO) | Standard subassemblies are stocked and combined for the order. | CPQ selects a combination of existing modules and may generate an assembly structure. |
In CTO, the CPQ BOM can be relatively deterministic. In ETO, it may represent requirements rather than a final production structure. A system should make this status visible so that a customer-facing quote is not mistaken for an approved manufacturing release.
These workflows are discussed in more detail in the guide to configure-to-order, engineer-to-order and related manufacturing workflows.
Benefits of BOM-driven CPQ
More accurate configuration and pricing
When price and cost are derived from the actual configured content, the quote is less dependent on manual spreadsheet interpretation. This is especially valuable when options change material, capacity, labor, purchased components or manufacturing effort.
Faster sales-to-engineering handoff
A structured configuration and BOM give engineering a defined starting point. Engineers can focus on exceptions, calculations and new design work instead of re-entering every option from a sales document.
Better visibility of scope
A resolved BOM exposes included components, optional content, exclusions and quantities. This reduces ambiguity during commercial review and helps identify missing accessories or services.
Improved approval control
Approvals can use calculated margin, component cost, non-standard selections, lead time and engineering status rather than relying only on the total quote value.
Reusable product knowledge
Rules and product structures become a governed model that can be reused across direct sales, dealers, ecommerce, internal applications and customer service, subject to the capabilities of the chosen platform.
Limitations and risks
A commercial BOM may not be production-ready
A CPQ-generated BOM may omit routing, operations, work instructions, consumables, packaging, phantom assemblies or shop-floor details. It should not be sent directly to production without confirming its intended use.
Product models become difficult to maintain
Large product families can contain thousands of options and dependencies. Poorly governed rules create contradictions, duplicate logic and unexpected combinations. Ownership, naming standards, version control and automated regression testing are essential.
Data synchronization is complex
Item numbers, costs, prices, revisions and availability change in ERP, PLM and supplier systems. A stale CPQ model can produce an invalid or unprofitable quote even when the configuration logic is correct.
Engineering calculations require validation
Calculations for load, pressure, thermal performance, electrical sizing or structural requirements may require specialist review. A CPQ calculation should not be treated as an engineering approval unless the manufacturer has validated and governed it for that purpose.
Variant explosion can affect performance
When many dimensions, options and conditional components interact, the theoretical number of variants can become very large. The implementation may need modular architectures, constraint solvers, parameterized items or integration with engineering systems rather than storing every possible finished BOM.
Quote and order revisions can diverge
If a customer changes the configuration after approval, the system must show which BOM, cost, price, revision and document version correspond to the change. Otherwise, sales, engineering and production may work from different definitions.
Implementation guidance
Define the purpose of the BOM first
Document whether CPQ needs to produce a commercial BOM, costing BOM, EBOM, MBOM, order BOM or a preliminary ETO structure. One output may not satisfy every downstream process.
Establish data ownership
Assign ownership for products, options, item numbers, revisions, costs, prices, engineering formulas and manufacturing structures. A governance matrix should identify the system of record and the synchronization method for each data object.
Model the product before copying spreadsheets
Existing spreadsheets often mix options, prices, formulas, exceptions and manual judgment. Before migrating them, separate product attributes, configuration rules, BOM logic, cost data and approval policies.
Use stable identifiers
Every component, option, assembly and revision should have a consistent identifier. Descriptions alone are not sufficient for reliable integration because similar descriptions may refer to different materials, revisions or units of measure.
Test combinations, not just individual rules
Testing should include valid configurations, invalid combinations, boundary values, revision changes, quantity calculations, missing data, currency changes, discounts, approvals and downstream integration failures.
Define release states
Useful states may include draft, technically valid, commercially approved, engineering review, order-ready and production-released. The names vary, but the distinction between a quote configuration and a released manufacturing structure should be explicit.
Measure operational outcomes
Relevant measures can include quote cycle time, configuration error rate, engineering rework, margin variance, approval duration, percentage of quotes requiring manual correction, order-entry effort and integration failure rate. The right measures depend on the business process and baseline data.
The broader manufacturing CPQ implementation guide covers requirements, migration, testing, governance, deployment and maintenance.
What to ask CPQ vendors about BOM capability
- Does the platform generate a hierarchical BOM, a flat commercial list or both?
- Can it represent configurable BOMs with optional, alternative, conditional and calculated components?
- Can BOM logic calculate quantities from dimensions, capacity or other variables?
- Does it distinguish commercial, engineering and manufacturing structures?
- Can it import or synchronize items and revisions from ERP or PLM?
- Can it return configured data to CAD or engineering automation tools?
- Does it support BOM versioning and effective dates?
- Can users compare BOM changes between quote revisions?
- How are costs, prices and currencies sourced and refreshed?
- Can the system mark a configuration as requiring engineering review?
- What APIs and integration events are available?
- How are errors handled when an item or downstream transaction is unavailable?
- Can dealers or customers see a simplified view while engineering users see detailed data?
- What testing and rule-governance tools are included?
- Which capabilities are standard, which require configuration and which require custom development?
Vendor evaluation should focus on the manufacturer’s actual product complexity and downstream process rather than on a generic feature checklist. The manufacturing CPQ comparison and selection resources can help structure an evaluation.
Semantic map
The following relationships summarize how BOMs connect configuration, costing, quoting and manufacturing systems:
- CPQ configures configurable products.
- Configuration rules prevent invalid combinations.
- A configured product generates a configured BOM.
- A configurable BOM represents product variants.
- A configured BOM identifies components and quantities.
- BOM components contribute to product cost.
- Costing supports price calculation.
- Pricing determines the commercial quote value.
- A quote communicates configured scope and commercial terms.
- Engineering review validates non-standard or ETO requirements.
- EBOM represents an engineering product structure.
- MBOM represents a manufacturing product structure.
- CPQ exchanges item and order data with ERP.
- CPQ may exchange product structure data with PLM.
- CAD automation generates product-specific drawings when supported.
- Approved configuration data can support production planning.
Frequently asked questions
What does BOM mean in CPQ?
BOM means Bill of Materials. In CPQ, it is the component and quantity structure associated with a configured product and may support costing, pricing, quoting, engineering or production.
Does every CPQ system generate a BOM?
No. Some CPQ systems calculate prices and create quotes without generating a BOM. Manufacturers should verify whether BOM generation is supported and whether the output is commercial, engineering or manufacturing-oriented.
How does CPQ create a BOM?
CPQ applies product rules, constraints, option dependencies and calculations to customer inputs, then selects components, assemblies and quantities for the resulting configuration.
What is the difference between a configurable BOM and a configured BOM?
A configurable BOM contains alternatives, options and conditional logic for a product family. A configured BOM is the resolved structure for one particular customer configuration or order.
Is a CPQ BOM the same as an EBOM?
Not necessarily. An EBOM is an engineering product structure. A CPQ BOM may be a commercial or order structure and may require engineering or PLM validation before it becomes an authoritative EBOM.
Is a CPQ BOM the same as an MBOM?
No. An MBOM is organized for manufacturing execution and may include operations, manufacturing assemblies, consumables or packaging that are absent from a commercial CPQ BOM.
Can BOM data be used to calculate price?
Yes, when component costs, quantities and pricing rules are available. The accuracy depends on current item data, supplier costs, labor and overhead assumptions, margins and commercial policies.
Can CPQ calculate manufacturing cost?
Some manufacturing CPQ systems can calculate detailed or estimated cost, while others use costs supplied by ERP or another system. This capability must be verified for the specific platform and implementation.
How does configuration affect the BOM?
Configuration choices can add, remove or replace components, change quantities, alter attributes or trigger calculated dimensions and subassemblies.
What is an example of a BOM rule?
A BOM rule could add a larger motor, reinforced frame and upgraded coupling when a machine is configured for a higher load or capacity range.
Can CPQ generate a CAD model from a BOM?
Some platforms integrate with CAD or engineering automation tools, but BOM generation alone does not create CAD geometry. CAD automation requires suitable parametric models, mappings and validated engineering logic.
How does CPQ support engineer-to-order products?
CPQ can capture requirements, calculate preliminary values, create a preliminary BOM and route the configuration to engineering. The final BOM may not exist until design work and technical approval are complete.
What happens when an item changes in ERP?
The implementation should define synchronization and error handling. CPQ may refresh the item, block the configuration, use an approved replacement or route the quote for review, depending on governance.
Can a BOM appear on the customer quote?
Sometimes. Customer quotes usually show selected equipment, major assemblies and options rather than every internal component. The visible level should match commercial clarity and confidentiality requirements.
How does a BOM affect quote approvals?
The BOM can provide the component cost, non-standard content, engineering effort and lead-time information used to trigger margin, technical or management approvals.
What BOM data should CPQ send to ERP?
The required data may include item numbers, quantities, units, configuration attributes, revisions, customer references and order status. The exact payload depends on whether ERP creates the order, production structure or only a sales document.
Why are BOM revisions important in CPQ?
Revisions show which product definition, component set, cost basis and rules were used for a quote or order. They help prevent discrepancies when products change during a sales cycle.
What is the main risk of using a CPQ BOM for production?
The main risk is assuming that a commercial or configured BOM contains all manufacturing data. Production may also require routings, operations, work instructions, revisions, quality data and manufacturing-specific structures.
How should manufacturers test BOM generation?
Testing should cover normal configurations, invalid combinations, boundary dimensions, option replacements, quantity calculations, revision changes, price changes, approval paths and failed ERP or PLM transactions.
In practice, BOM capability is one of the clearest differences between generic sales CPQ and manufacturing-oriented CPQ. A quoting tool may tell a salesperson what to charge. A manufacturing CPQ architecture can additionally explain what the customer is buying, which components are required, what it costs, whether it can be engineered and how the data should move toward production.