Tag: configurable products

  • Price Books and Product Configuration in Manufacturing CPQ

    In manufacturing CPQ, a price book is a controlled set of prices, discounts, surcharges, costs, currencies and commercial conditions that a Configure, Price, Quote (CPQ) system applies to a valid product configuration. Product configuration determines what can be sold; the price book determines how that valid configuration is valued for a particular market, customer, channel or date.

    The two functions must work together. A configured industrial pump may require a specific motor, seal, impeller material and control panel. Configuration rules confirm that the combination is technically valid. The price book then assigns prices to the selected options, applies quantity or customer terms, adds engineering or freight charges where appropriate and produces a quote. In manufacturing CPQ, the same configuration may also generate a bill of materials (BOM), engineering outputs and data for enterprise systems.

    This is different from a generic sales CPQ application that simply selects products from a catalogue and applies discounts. Manufacturing price management often depends on dimensions, materials, capacity, regional conditions, production costs, engineering effort and downstream manufacturing data.

    What is a price book in manufacturing CPQ?

    A manufacturing CPQ price book is a structured pricing model containing the commercial values and rules used to price products and options. It can include base prices, component prices, calculated prices, customer-specific prices, channel discounts, minimum margins, validity dates, currencies, taxes, freight, installation and non-recurring engineering charges.

    A price book is not the product model itself. The product model defines products, features, options, dependencies and constraints. The price book references those product elements and supplies monetary values or pricing logic.

    Element Primary question Manufacturing example
    Product model What can be configured? Which pump sizes, materials and seal types are compatible?
    Configuration rules Which combinations are valid? A high-temperature seal is required for a specified fluid temperature.
    Price book What should the valid configuration cost or sell for? A stainless-steel casing adds a defined amount or uses a calculated rate.
    Cost model What does the manufacturer expect to spend? Material, labor, machining and purchased-component costs.
    Quote document How is the commercial offer presented? Line items, options, terms, delivery assumptions and totals.

    How product configuration and price books work together

    The normal sequence is configuration first, pricing second, although the user interface may show indicative prices while the product is being configured.

    1. Select a product family. A salesperson or dealer starts with a pump, conveyor, switchgear assembly, industrial vehicle or other configurable product.
    2. Capture requirements. Inputs may include flow, pressure, voltage, load, dimensions, temperature, material, environment and required delivery date.
    3. Apply configuration rules. The CPQ system filters invalid options, recommends compatible choices or blocks combinations that cannot be engineered or manufactured.
    4. Resolve the configuration. The system records selected options, calculated values, quantities and any unresolved engineering questions.
    5. Calculate costs and prices. Price rules read the configuration and retrieve or calculate the values required for the commercial offer.
    6. Generate downstream outputs. Depending on the platform, CPQ may create a configurable BOM, engineering request, CAD output, order payload or ERP quote.
    7. Route approvals. Discounts, low margins, unusual terms, non-standard options or engineering effort can trigger approval workflows.
    8. Generate the quote. The final document presents the configured product, included and excluded items, price, delivery assumptions and commercial terms.

    The configuration result should be the shared reference for pricing, BOM generation and quoting. Re-keying selected options into a separate spreadsheet or ERP screen creates opportunities for discrepancies between what was quoted and what is eventually manufactured.

    See the detailed guide to product configuration and configuration rules for a deeper explanation of product models, dependencies and constraints.

    Price book architecture for configurable products

    Base product prices

    A base price represents a standard product or starting configuration. For example, a centrifugal pump family may have base prices for each frame size. The base price should have a clear scope: it may include a standard motor and coupling, or it may represent only the bare pump.

    Option and component prices

    Options can be priced as fixed additions, replacements, quantities or formula-driven values. A stainless-steel wetted-part package may add a fixed amount. A longer conveyor frame may be priced per metre. A larger motor may replace the standard motor rather than add its full list price.

    Formula-based pricing

    Some products cannot be priced accurately with a simple option table. Formula-based pricing can use dimensions, capacity, surface area, weight, power, material grade or production time. An enclosure might be priced from width, height, depth and material. A heat exchanger may require a calculation based on area and selected metallurgy.

    Formula inputs must be governed carefully. A pricing formula should not be used to approve a technically invalid configuration. Engineering rules validate the product; pricing formulas value the valid result.

    Customer, channel and market price books

    Manufacturers may maintain different commercial views for direct sales, distributors, original equipment manufacturers (OEMs), service partners or export markets. A price book can be selected by customer account, sales channel, territory, currency, contract or business unit.

    These variations should not create hidden product rules. A distributor discount may change the selling price, while a voltage option or material restriction belongs in the product model. Separating commercial rules from engineering rules improves maintenance and auditability.

    Effective dates and version control

    Price books normally require effective-from and effective-to dates. A quote created before a raw-material price increase may need to retain the earlier price, while a new quote uses the current book. Version control is particularly important when open opportunities, blanket orders and engineering revisions overlap.

    Pricing, costing and margins

    Pricing and costing are related but not identical. Costing estimates what the manufacturer expects to spend. Pricing determines what the customer is charged. A CPQ system may support one, both or neither in depth, so buyers should verify the documented capability.

    Calculation Typical inputs Purpose
    Material cost Material type, quantity, weight, waste and current rates Estimate direct material expenditure
    Purchased-part cost Supplier item, quantity, currency and procurement price Value motors, valves, drives and other bought-in parts
    Labor or process cost Operations, work centres, setup and run time Estimate manufacturing effort
    Engineering charge Design hours, review effort and non-standard requirements Recover ETO or application-engineering effort
    Sell price Cost, margin, market, customer terms and discount Produce the commercial offer

    A manufacturer may use a cost-plus model, target margin, price matrix, market price, contract price or a combination. For example, the cost of a custom mounting frame may be calculated from steel weight and fabrication hours, while the sell price is controlled by a product-family margin policy.

    Discounting should be applied after the system has established the applicable list or calculated price, unless the commercial model explicitly requires another sequence. Approval thresholds may use gross margin, absolute discount, total order value, contribution margin or deviation from an approved price corridor.

    How configuration affects BOM generation and quoting

    A valid configuration can drive a configurable BOM. A BOM is a bill of materials: the list of components, quantities and relationships required for a product. In manufacturing, it is important to distinguish an engineering BOM (EBOM), which describes the product from an engineering perspective, from a manufacturing BOM (MBOM), which organizes items and operations for production.

    CPQ may generate a sales or configured BOM that is later transformed into an EBOM or MBOM by PLM, ERP or manufacturing engineering systems. Other implementations may generate a production-ready structure directly. This depends on the product model, integration architecture and platform capability.

    For a configurable electrical cabinet, the selected enclosure size, breaker ratings, busbar arrangement, cable-entry position and accessories can determine:

    • which components appear in the configured BOM;
    • the quantity of breakers, terminals and cable glands;
    • the estimated material cost;
    • the description shown on the quote;
    • the engineering or panel-layout work required;
    • the data sent to ERP or a manufacturing system.

    Pricing and BOM logic should be coordinated but not conflated. A line item may be commercially bundled while remaining several manufacturing components. Conversely, a component can appear in the BOM without being shown as a separate quoted line.

    Read more about BOM generation, costing, pricing and quote automation.

    Rules that connect configuration to price

    Manufacturing CPQ commonly uses several types of rules. They solve different problems.

    Rule type Function Example
    Compatibility rule Prevents invalid combinations A motor voltage must match the selected control panel.
    Selection rule Adds or removes dependent options Selecting outdoor installation adds a weatherproof enclosure requirement.
    Calculation rule Derives a technical or commercial value Frame length is calculated from conveyor travel distance.
    Pricing rule Assigns or modifies a price A hazardous-area certification adds a defined surcharge.
    Approval rule Routes an exception for review A discount below the approved margin requires management approval.

    Rules should have clear ownership. Product engineering may own compatibility and technical calculations. Product management may own standard option structures. Finance or commercial operations may own discount policies and price-book governance. IT or a CPQ administrator may implement and test the rules, but should not become the only person who understands the product model.

    Illustrative example: pricing a configurable industrial pump

    Consider a pump configured for a chemical-processing application. The user selects flow rate, discharge pressure, casing material, impeller material, seal type, motor power, hazardous-area certification and control method.

    The configuration model may enforce the following:

    • the selected impeller must meet the required operating point;
    • the motor must provide sufficient power with an engineering margin;
    • the seal material must be compatible with the fluid and temperature;
    • hazardous-area certification requires an approved motor and terminal arrangement;
    • the selected control method must be compatible with the motor and drive;
    • some casing materials may be unavailable for the selected pressure class.

    After validation, the pricing engine can calculate the base pump price, material upgrades, motor price, seal package, certification surcharge, control-panel price, engineering charge and freight assumption. The configured BOM can include the casing, impeller, shaft, seal, motor, coupling, baseplate, instrumentation and documentation package.

    If the customer requests a non-standard operating point, the system may create an engineer-to-order (ETO) task rather than silently pricing the configuration as standard. The quote can show a provisional price or an allowance, with final approval required after engineering review.

    Quote documents and commercial transparency

    A quote document should make the relationship between configuration and price understandable without exposing unnecessary internal logic. Depending on the sales process, it may include:

    • configured product name and description;
    • key technical parameters and selected options;
    • included accessories and exclusions;
    • quantity, unit price and extended price;
    • discounts, surcharges, taxes and freight assumptions;
    • estimated lead time or delivery conditions;
    • engineering, installation, commissioning or documentation charges;
    • validity period and applicable terms;
    • approval notes or conditions for non-standard requirements.

    A customer-facing document should not imply that an engineering drawing, delivery date or certification is final if those items still require review. Quote templates need status indicators and carefully defined language for provisional configurations.

    Integration with ERP, CRM, PLM, PDM and CAD

    Each enterprise system has a different responsibility. Customer relationship management (CRM) software manages accounts, opportunities and sales activities. Enterprise resource planning (ERP) manages commercial transactions, inventory, purchasing, production and financial processes. Product lifecycle management (PLM) manages product structures, revisions and engineering lifecycle information. Product data management (PDM) commonly manages CAD files and related design data. Computer-aided design (CAD) systems create engineering models and drawings.

    CPQ can sit between customer requirements and these systems, but the exact boundary must be designed rather than assumed.

    System Potential exchange with CPQ
    CRM Opportunity, account, salesperson, quote status and commercial activity
    ERP Items, prices, customers, inventory context, orders, costs and financial data
    PLM Product revisions, approved structures, lifecycle status and engineering definitions
    PDM CAD documents, files, metadata and revision references
    CAD Parameters, model selections, drawings, layouts and design outputs
    MES Manufacturing execution data, operations or production instructions in selected architectures
    PIM Product descriptions, attributes and commercial content for channels

    Integration can be real-time, scheduled, event-driven or file-based. A price book may be mastered in CPQ, ERP or a dedicated pricing system. Product attributes may be mastered in PLM or PIM. Duplicating the same price and product rule in multiple systems creates version conflicts, so every important data element should have an identified system of record.

    See the guide to CPQ integrations with ERP, CRM, PLM, PDM, CAD and other systems.

    Manufacturing workflows: CTO, ETO, MTO and ATO

    Price-book design depends partly on the manufacturing strategy.

    • Configure-to-order (CTO): the customer selects from a controlled product model and the resulting configuration can be produced using known structures and processes.
    • Engineer-to-order (ETO): the sale triggers new or modified engineering work. Pricing may need engineering estimates, assumptions and later revision.
    • Make-to-order (MTO): production starts in response to an order, often using a defined product or configuration.
    • Assemble-to-order (ATO): standard modules are stocked or prepared and assembled after the order.

    In CTO and ATO, price books can often be relatively deterministic. In ETO, the price model may need allowances, engineering hours, risk factors, review stages and change control. A CPQ implementation should show where automated pricing ends and engineering quotation begins.

    Learn more about configure-to-order, engineer-to-order and related manufacturing workflows.

    Benefits of integrating price books with configuration

    • Faster quoting: sales engineers do not need to rebuild option prices manually for every valid configuration.
    • Fewer commercial errors: incompatible options, omitted accessories and incorrect replacement pricing are easier to control.
    • More consistent margins: discounts and surcharges can be evaluated against cost and policy.
    • Better engineering handoff: the selected configuration and assumptions accompany the quote.
    • Traceable BOM and price relationships: commercial line items can be connected to the components that drive cost.
    • Controlled regional and channel pricing: different books can be governed without cloning the entire product model.
    • More reliable quote documents: the document can be generated from the validated configuration rather than manually re-entered data.

    Limitations and implementation risks

    Connecting price books to a product configurator does not automatically produce accurate manufacturing prices. Common risks include:

    • Incomplete product data: missing option relationships or obsolete items lead to invalid configurations and inaccurate prices.
    • Ambiguous ownership: no team knows who approves price changes, engineering rules or product revisions.
    • Overly complex formulas: pricing logic becomes difficult to test and explain.
    • Duplicated masters: CPQ, ERP and spreadsheets contain different versions of prices or components.
    • Bundling problems: a customer-facing bundle hides manufacturing components needed for costing or production.
    • Unmanaged exceptions: sales teams use manual overrides for non-standard products without recording the reason.
    • Weak effective dating: old opportunities are repriced unintentionally after a new price release.
    • Insufficient testing: a price change fixes one product family but breaks a related configuration or channel.

    A price book should not be treated as a spreadsheet import alone. It is part of a governed product and commercial data model.

    Implementation approach

    1. Define the commercial and engineering scope

    Start with a limited product family and document the quote-to-order process. Identify which options are standard, which require engineering review and which are not currently supported.

    2. Map product and price data

    Inventory product families, option codes, units of measure, revisions, costs, price lists, currencies, discount schedules, customer agreements and quote templates. Identify duplicates and obsolete records before migration.

    3. Separate rule categories

    Document compatibility, selection, calculation, pricing and approval rules separately. This makes testing and ownership clearer.

    4. Establish systems of record

    Decide whether CPQ, ERP, PLM, PDM or another system owns each product, price, cost, customer and revision attribute. Define synchronization frequency and conflict handling.

    5. Model the BOM and quote views

    Specify which components are shown to the customer, which remain internal, how configurable BOMs map to EBOM or MBOM structures and how replacements, quantities and phantom assemblies are handled.

    6. Test combinations and commercial scenarios

    Test valid and invalid configurations, boundary dimensions, price-book dates, currencies, customer discounts, low-margin cases, engineering exceptions and revisions. Recalculate the same quote after a price release to confirm intended behavior.

    7. Govern releases

    Use controlled changes, approvals, effective dates and audit history. A price release should identify affected product families, customers, quotes and integrations. Product and commercial teams should be able to review changes without relying on undocumented code.

    The wider CPQ implementation guide covers data migration, architecture, testing, governance, deployment and maintenance.

    How to evaluate a CPQ configurator for price-book use

    When evaluating a CPQ configurator, ask vendors and implementation partners to demonstrate a real manufacturing scenario rather than a simple catalogue discount. Useful tests include:

    • Can the system represent dependencies between dimensions, materials, motors and accessories?
    • Can a price be fixed, formula-based, quantity-based or derived from a replacement component?
    • Can different price books be selected by customer, channel, currency, region and effective date?
    • Can the system distinguish cost, list price, net price and margin?
    • Can a configuration generate a BOM or pass structured data to another system?
    • Can non-standard configurations be routed to engineering without being treated as standard?
    • Can users see why an option is unavailable or why approval is required?
    • Can rules and prices be tested independently and audited after release?
    • Can quote documents show technical selections and commercial conditions accurately?
    • What is documented for ERP, CRM, PLM, PDM, CAD and API integration?

    Do not assume that a platform offering price books also provides deep product configuration, CAD automation, BOM generation, engineering calculations or PLM integration. Verify each capability, its data requirements and the implementation responsibility.

    Semantic map

    Price books and product configuration form a connected manufacturing data chain: customer requirements lead to a validated product configuration; the configuration drives prices, costs and potentially BOM and CAD outputs; the resulting quote can move through approval into ERP, PLM, CRM or production workflows.

    • Product requirements connect to product configuration.
    • Product configuration connects to compatibility and calculation rules.
    • Validated options connect to price-book entries and pricing formulas.
    • Configured products connect to configurable BOMs.
    • Configurable BOMs connect to EBOM, MBOM or ERP structures.
    • Configuration parameters can connect to CAD automation and engineering calculations.
    • Price and cost results connect to margin and approval rules.
    • Approved configurations connect to quote documents and order processes.
    • CPQ connects commercial, engineering and manufacturing systems through integrations.

    Frequently asked questions

    What is the difference between a price book and a product configurator?

    A price book supplies prices and commercial rules. A product configurator determines which product options and combinations are valid. Manufacturing CPQ connects the two so that a valid engineered configuration receives an appropriate price.

    Can a price book contain configuration rules?

    It can contain price-dependent conditions, but technical compatibility rules should normally reside in the product model or rules engine. Keeping technical and commercial logic separate makes both easier to govern.

    Does every CPQ system generate a BOM?

    No. Some CPQ systems generate configurable BOMs, while others pass selections to ERP, PLM or an engineering application that creates the structure. This capability must be verified for the specific product and integration architecture.

    How does configuration affect product pricing?

    Configuration selects the components, dimensions, materials and services that drive the price. The pricing engine can then apply fixed option prices, replacement prices, formulas, customer terms and discounts.

    Can one product have multiple price books?

    Yes. Manufacturers commonly maintain books for regions, currencies, distributors, OEM contracts, customer accounts or sales channels. Effective dates and selection priorities should be explicitly governed.

    Should costs and prices be stored in the same price book?

    They may be managed in the same CPQ model, but cost and sell price should remain distinct data elements with separate visibility and governance. Costs support margin analysis; prices support the commercial offer.

    How are dimensions used in a manufacturing price book?

    Dimensions can select a price tier or feed a formula. For example, conveyor length may determine material quantity, fabrication effort, freight class and selling price.

    How are discounts applied to configured products?

    Discounts can be applied by product family, customer, channel, quantity, contract or total quote value. Approval rules should evaluate the resulting margin and any exceptions.

    What happens when a configuration requires engineering work?

    The CPQ process can create an ETO or engineering-review task, include an allowance or estimate, and prevent the quote from being treated as fully final until engineering confirms the design.

    Can CPQ price a configurable BOM?

    Yes, where the platform supports BOM-driven pricing. It can value components, quantities, replacements and assemblies, although the final production BOM may be created or transformed in ERP or PLM.

    How do EBOM and MBOM affect CPQ pricing?

    An EBOM describes the engineered product, while an MBOM organizes production requirements. CPQ may use a sales BOM or configured structure and pass it to systems that create or manage the EBOM and MBOM.

    Can price books include freight and installation?

    They can, if the CPQ design includes those commercial elements. Freight may depend on weight, dimensions, destination and shipping class, while installation may depend on scope, location and engineering assumptions.

    How should price-book revisions be controlled?

    Use version numbers, effective dates, approvals, audit history and regression testing. Define whether existing quotes retain their original price or are recalculated under a new release.

    What is a price override in manufacturing CPQ?

    A price override is a deliberate change to the calculated or approved price. It should record the user, reason, amount, margin impact and approval status rather than silently replacing the system result.

    Can a CRM own the manufacturing price book?

    A CRM may display or consume pricing, but it is not automatically the best system of record for complex product, cost and manufacturing logic. Ownership should be selected according to data complexity, governance and integration requirements.

    How does CAD automation relate to price books?

    CAD automation uses configuration parameters to create product-specific models or drawings. Its outputs may affect BOM content, engineering effort and price, but CAD generation and price-book management are separate capabilities.

    What should manufacturers test before launching a price book?

    Test valid and invalid configurations, formula boundaries, replacements, currencies, discounts, effective dates, customer contracts, margin approvals, BOM results, quote documents and integration payloads.

  • Cost Rollups for Configurable Products

    Cost rollups for configurable products calculate the estimated cost of producing a specific product configuration. In a manufacturing Configure, Price, Quote (CPQ) process, the rollup normally starts with a validated configuration, resolves the required components and operations, applies material, labor, subcontracting and overhead costs, and returns a cost basis for pricing, margin analysis and quote approval.

    This is different from simply adding a few option prices to a base product. A configured industrial pump, machine enclosure, conveyor or specialty vehicle may change its bill of materials (BOM), manufacturing route, engineering effort, purchased components, labor content and lead time. A reliable cost rollup must reflect those changes and preserve a traceable connection between the customer selections, the product model, the resulting BOM and the quoted price.

    Cost rollups are therefore one of the points where product configuration, engineering, costing, pricing and quoting meet. Some CPQ platforms calculate costs natively. Others obtain costs from an enterprise resource planning (ERP) system, product lifecycle management (PLM) system, costing service or custom integration. Buyers should verify the actual data flow rather than assume that every CPQ configurator provides manufacturing-grade costing.

    What is a cost rollup?

    A cost rollup is a calculation that aggregates the costs of all materials, components, labor activities, subcontracted operations and applicable overhead required to produce a product or configured assembly. The result may be called standard cost, estimated cost, rolled-up cost, manufacturing cost or configuration cost, depending on the organization.

    For a configurable product, the calculation is performed against the selected configuration rather than only against a generic product number. The rollup may include:

    • raw materials such as steel plate, aluminum, copper, plastics or rubber;
    • purchased components such as motors, pumps, valves, drives, sensors and fasteners;
    • subassemblies selected by configuration rules;
    • labor operations such as cutting, welding, machining, painting, assembly and testing;
    • machine time and work-center rates;
    • outside processing and subcontracting;
    • engineering or design effort for engineered-to-order work;
    • packaging, freight allowances or installation-related costs when included in the commercial model;
    • scrap, yield, waste and material utilization factors; and
    • manufacturing overhead or other cost allocations.

    A simple conceptual formula is:

    Total configured cost = material cost + purchased component cost + labor cost + machine cost + subcontracting cost + engineering cost + allocated overhead + other applicable costs

    The exact formula depends on the company’s costing policy. A quote may use a standard cost for financial consistency, a current purchase cost for procurement accuracy, an estimated job cost for engineer-to-order work, or several parallel cost views for different business purposes.

    Why configurable products require more than option pricing

    In generic sales CPQ, an option may add a fixed amount to a base price. Manufacturing CPQ often needs to determine what the option physically changes. Selecting a larger motor for a pump skid can change the motor cost, coupling, base frame, electrical protection, enclosure size, cable requirements and assembly time. Selecting a higher-pressure valve may change the valve body material, actuator, testing requirements and certification documentation.

    These effects can be represented through a configurable BOM, rule-driven component selection, formulas, engineering calculations or integrations with CAD and ERP systems. A cost rollup is reliable only when the product model captures the relevant dependencies.

    Commercial option Potential manufacturing effect Cost data required
    Higher pump flow rate Larger pump, motor, coupling, base and possibly piping Component costs, sizing rules, assembly labor and test cost
    Stainless steel wetted parts Different castings, seals, fasteners and fabrication processes Material-specific prices, supplier parts and routing changes
    Custom enclosure dimensions Changed sheet-metal blank, machining, coating and assembly effort Dimension formulas, material utilization and work-center rates
    Outdoor installation package Weather protection, heater, gland plates and additional testing Option components, labor standards and compliance costs

    How a manufacturing CPQ cost rollup works

    1. The customer or sales engineer creates a configuration

    The process begins with selections such as capacity, dimensions, material, voltage, motor type, operating environment, accessories and delivery requirements. A rules engine validates the selections. Depending on the product model, the system may use rules-based configuration, constraint-based configuration, guided selling or a combination of these methods.

    Rules-based configuration uses explicit conditions such as “if voltage is 480 V, select this starter family.” Constraint-based configuration evaluates relationships and limits, such as a maximum shaft load, pressure rating or dimensional envelope. Guided selling asks questions that lead a user toward suitable choices; it may simplify the experience but does not by itself guarantee engineering validity.

    The configuration must be valid before costs are rolled up. Otherwise the system may calculate a price for an impossible or incomplete product.

    2. The product model resolves components and operations

    The CPQ system translates the selected features into a product structure. This may be a configurable BOM, a modular BOM, a rules-based component list or a set of inputs for an external engineering system.

    A configurable BOM contains alternative or conditional components that become active when particular selections, dimensions or calculations apply. For example, a pump package may include:

    • one pump family selected by flow and pressure;
    • one motor selected by power, voltage and efficiency requirements;
    • a coupling selected by motor and shaft size;
    • a base frame selected by pump and motor dimensions;
    • different valves selected by material and pressure class;
    • instrumentation selected by the control package; and
    • installation hardware selected by mounting and environmental conditions.

    The product model may also resolve quantities. A cable tray quantity might depend on enclosure width, while the amount of sheet material may depend on surface area and an allowance for scrap.

    3. Engineering calculations determine variable values

    Some costs cannot be obtained from a static option table. They depend on calculations. Examples include sheet-metal weight, cable length, frame length, insulation area, structural steel mass, number of fasteners, paint quantity or the capacity of a selected heat exchanger.

    A CPQ platform may perform these calculations internally, call an engineering service or exchange parameters with computer-aided design (CAD) and product data systems. CAD automation may generate a product-specific model or drawing, while the cost model uses calculated dimensions and materials. More information about this relationship is available in the guide to CAD and engineering automation.

    4. Each item receives a cost

    The system then obtains or calculates a cost for each resolved BOM line and operation. Cost sources may include:

    • material master records;
    • supplier or purchase prices;
    • inventory or standard costs;
    • manufacturing work-center rates;
    • labor standards;
    • routing operations;
    • outside-processing rates;
    • engineering estimates; and
    • manually maintained cost assumptions.

    Costs may be held in the CPQ product model, retrieved from an ERP system, supplied by a costing database or calculated by a specialized service. Maintaining duplicate cost data in several systems creates a governance risk, particularly when supplier prices, currencies or manufacturing rates change.

    5. The system aggregates costs through the product structure

    Leaf-level component and operation costs are aggregated through subassemblies and parent assemblies. A subassembly may have its own material, labor and overhead cost before becoming a line in the finished product structure.

    For example, a conveyor may contain a drive package. The drive package cost includes the gearbox, motor, coupling, guard, mounting plate and assembly labor. The conveyor rollup then adds the drive package to the frame, belting, controls, guarding, supports and testing operations.

    The result should normally retain detail rather than return only one total. Cost detail supports margin analysis, approval decisions, variance investigation and later comparison with actual production results.

    6. Pricing and margins are applied separately

    Cost is not the same as price. Cost represents the organization’s estimated expenditure or resource consumption. Price is the amount offered to the customer after applying margin, markup, commercial adjustments, freight policy, discounts, currency rules, taxes and other pricing logic.

    A manufacturing CPQ system may calculate:

    • material and manufacturing cost;
    • engineering or non-recurring cost;
    • target margin;
    • list price and customer-specific price;
    • discount limits;
    • minimum margin thresholds; and
    • approval requirements.

    For example, an engineered enclosure may have a rolled-up manufacturing cost of 18,000 monetary units. The commercial price may be based on a target gross margin, a project discount and a separate engineering charge. Treating the entire amount as a simple percentage markup can hide important differences between recurring product cost and one-time engineering work.

    7. The quote and approval process use the result

    The cost rollup feeds the quote document, margin analysis and approval workflow. A quote may show only customer-facing prices, while internal users see detailed costs and margins. If a configured product falls below a margin threshold, the CPQ system may require sales management, finance or engineering approval.

    The approved configuration and commercial result can then be passed to order management and downstream systems. The exact handoff depends on whether the product is configure-to-order (CTO), make-to-order (MTO), assemble-to-order (ATO) or engineer-to-order (ETO).

    Cost rollups and BOM types

    BOM terminology matters because different BOM structures serve different purposes.

    BOM type Purpose Role in cost rollups
    Configurable BOM Represents alternatives, conditions and variable quantities before a specific configuration is finalized Provides the rules and structure from which the configured cost is resolved
    Engineering BOM (EBOM) Represents the product from an engineering and design perspective May provide design components, materials and engineering attributes
    Manufacturing BOM (MBOM) Represents how the product is assembled and produced Supports labor, routing, work-center and manufacturing-cost calculations
    Configured or order BOM Represents the specific product selected for an order or quote Provides the concrete component list for costing, production and fulfillment

    EBOM and MBOM are not interchangeable. An engineering structure may contain design groupings that do not correspond to shop-floor operations. Conversely, an MBOM may include consumables, fixtures, packaging or intermediate assemblies that are not represented in the EBOM. A CPQ implementation must define which structure is authoritative for each cost element and how structures are transformed or synchronized.

    The guide to BOM generation, pricing and quote automation provides broader context on these relationships.

    Data required for a reliable cost rollup

    A cost rollup depends on more than a price list. Typical data requirements include:

    Product and configuration data

    • features, options and allowed values;
    • compatibility rules and constraints;
    • component selection logic;
    • quantity formulas;
    • dimension and performance calculations;
    • revision and effectivity dates; and
    • configuration status and validation results.

    Cost and sourcing data

    • material grades, weights and units of measure;
    • supplier, purchase and subcontracting costs;
    • currency and conversion rules;
    • minimum order quantities and lot-size effects;
    • scrap, yield and waste factors;
    • labor rates and machine rates;
    • routing operations and setup times; and
    • overhead allocation policies.

    Commercial data

    • price lists and customer agreements;
    • discount and surcharge rules;
    • freight and installation policies;
    • target margins;
    • approval thresholds; and
    • tax and currency requirements.

    Data ownership should be explicit. ERP may own item, supplier and standard-cost records. PLM may own engineering revisions and product structures. A product data management (PDM) system may control CAD files and design metadata. A CPQ system may own the selling model and configuration rules. A product information management (PIM) system may manage descriptions and channel content. These systems should not be treated as interchangeable.

    Integration architecture

    There are several common architecture patterns for cost rollups.

    CPQ-owned costing

    The CPQ platform stores the relevant component costs, formulas and rates. This can provide fast response during configuration, but it requires disciplined synchronization and governance. It may be suitable for a focused product line or when the CPQ platform has sufficiently deep costing capabilities.

    ERP-sourced costing

    The CPQ system resolves the configuration and sends item identifiers, quantities, dimensions or a temporary structure to the ERP. The ERP returns standard, average, planned or estimated costs. This reduces duplicate cost ownership but may require real-time interfaces, temporary items or a method for representing configurable structures.

    External costing service

    A dedicated costing service calculates material utilization, process costs or engineered estimates. CPQ supplies configuration parameters and receives cost lines or totals. This approach can support complex formulas but adds another system, interface and testing responsibility.

    PLM, PDM and CAD participation

    PLM manages product lifecycle information and revisions. PDM manages design files and related product data. CAD creates or modifies geometry. These systems may contribute dimensions, materials, revisions or manufacturing attributes, but they do not automatically provide a complete commercial cost rollup. The integration must define which system owns each value and when the data becomes effective.

    Enterprise integration should also account for customer relationship management (CRM), manufacturing execution systems (MES) and ecommerce or dealer channels. CRM may provide the opportunity and customer context. MES may consume production instructions or report actuals. Ecommerce may expose a simplified configuration experience. Details on these connections are covered in CPQ integration architecture.

    Worked example: configurable industrial pump package

    Consider a centrifugal pump package configured with the following selections:

    • capacity and pressure duty;
    • carbon-steel base frame;
    • stainless-steel wetted components;
    • 75 kilowatt motor;
    • 460-volt electrical package;
    • variable-frequency drive;
    • outdoor enclosure;
    • pressure and temperature instrumentation; and
    • factory performance testing.

    The configuration rules first validate that the selected pump, motor, drive and base are compatible. Engineering calculations determine the required motor rating, coupling size, base dimensions and approximate cable length. The configured BOM then includes the selected pump, motor, drive, enclosure, valves, instruments, fasteners and fabricated frame.

    The cost rollup may contain:

    Cost group Example contents
    Purchased components Pump, motor, drive, valves, sensors and enclosure hardware
    Fabricated materials Steel plate, profiles, stainless fittings and cable supports
    Labor Fabrication, welding, painting, electrical assembly and mechanical assembly
    Testing Performance test, electrical checks and documentation
    Engineering Configuration review, drawing updates and application engineering
    Overhead Applicable work-center or factory overhead allocation

    If the customer changes the motor to a higher rating, the system should not merely add the motor price. It may need to select a larger coupling and base, update the drive, increase cable size, change the enclosure and add assembly labor. The quote should show the commercial impact of the change, while internal users should be able to trace it to the affected cost lines.

    Cost rollups across CTO, ETO, MTO and ATO

    Manufacturing strategy affects the appropriate cost model.

    • Configure-to-order (CTO): the product is selected from a controlled model, and standard components and routings can usually be rolled up automatically.
    • Assemble-to-order (ATO): standard modules are assembled after the order. The rollup must account for module costs and final assembly labor.
    • Make-to-order (MTO): production begins after the order, often using a standard product with order-specific planning. Material availability, batch size and production labor may affect the estimate.
    • Engineer-to-order (ETO): the configuration requires new engineering, custom geometry or project-specific validation. The rollup may need engineering hours, design risk allowances, prototype work and provisional costs.

    ETO costing is particularly difficult because the final design may not yet exist. A CPQ system can estimate based on parametric rules, historical templates or engineering estimates, but the result should be labeled as an estimate and governed through approval and revision processes.

    These distinctions are important in the broader configure-to-order and engineer-to-order workflow.

    Benefits of cost rollups in manufacturing CPQ

    • More accurate margin analysis: the commercial team can evaluate margin against the actual configured product rather than a generic base item.
    • Faster quote decisions: sales engineers can evaluate alternatives without requesting a manual costing exercise for every variation.
    • Better engineering handoff: the configuration, cost assumptions and selected components remain connected.
    • Improved approval control: exception workflows can identify low-margin configurations, unusual materials or excessive discounts.
    • More consistent pricing: repeatable formulas reduce spreadsheet variation between sales regions or estimators.
    • Better production planning: a resolved structure can support downstream ordering, planning and manufacturing preparation.
    • Traceability: users can identify which option, rule or cost source caused a change in the quote.

    Limitations and common failure modes

    Stale or duplicated cost data

    If CPQ stores copied supplier or ERP costs without effective dates and synchronization controls, the rollup may become inaccurate. A process is needed for updates, exceptions and failed integrations.

    Incomplete product rules

    A configuration can be syntactically valid but commercially or technically incomplete. For example, a selected motor may be compatible with the pump but require a different mounting kit that the model does not include.

    Confusing standard cost with actual cost

    Standard cost is a planning or accounting value. It may not reflect current supplier prices, expedited freight, project-specific labor or actual production variance. The quote should state which cost basis it uses.

    Uncontrolled manual overrides

    Manual cost overrides can be necessary for unusual projects, but unrestricted overrides undermine trust. The system should record who changed the value, why it changed, which approval was required and how long the override remains valid.

    Missing indirect costs

    Some rollups include only material and direct labor. Others include setup, testing, quality inspection, packaging, freight, engineering and overhead. A comparison is meaningful only when the cost definitions are consistent.

    False precision

    A cost displayed to the nearest currency unit may appear exact even when dimensions, labor content or supplier assumptions are provisional. Estimated values should include an appropriate confidence category or explanatory note.

    Weak revision control

    A quote created under one product revision should not silently recalculate under a later revision unless the business process explicitly allows it. Configuration rules, costs, CAD outputs and BOM revisions need effective-date and version controls.

    Implementation guidance

    Define the cost model before selecting technology

    Document what the organization means by material cost, conversion cost, standard cost, estimated cost, engineering cost, overhead and margin. Decide whether the quote needs one cost view or multiple views for sales, finance and manufacturing.

    Map the end-to-end data flow

    For each field, identify the source, owner, update frequency, unit, currency, revision and fallback behavior. A useful data map covers configuration inputs, resolved items, quantities, routings, rates, costs, prices, approvals and outputs.

    Start with a bounded product family

    Pilot the model on a product line with meaningful configuration complexity but manageable scope. Industrial pumps, modular electrical panels or standard machine enclosures can provide useful test cases if their rules and costing data are sufficiently understood.

    Test combinations, not just individual options

    Testing should cover valid and invalid combinations, boundary dimensions, unit conversions, currency changes, missing costs, expired prices, revision changes, alternative suppliers and manual overrides. Compare CPQ results with independently reviewed spreadsheets or ERP calculations.

    Govern rule and cost ownership

    Assign responsibility for product rules, engineering formulas, item data, rates, supplier costs, pricing policies and approval thresholds. A governance board or controlled release process may be needed when multiple departments maintain the model.

    Measure actual-versus-estimated performance

    After orders are produced, compare estimated costs with actual material usage, labor, subcontracting and other relevant costs. Variance analysis can reveal missing operations, outdated rates, incorrect quantities or overly optimistic engineering assumptions.

    Additional guidance on requirements, migration, testing, deployment and maintenance is available in the CPQ implementation guide.

    How to evaluate CPQ cost-rollup capabilities

    When comparing CPQ configurators, ask vendors to demonstrate a real manufacturing scenario rather than a simple product option list. The demonstration should show a configuration changing the BOM, a calculated dimension changing material quantity, a purchased component receiving a current cost, a routing or labor operation being added, and the resulting margin approval.

    Evaluation area Questions to ask
    Product model Can the model represent conditional components, variable quantities, revisions and effectivity dates?
    Rules and calculations Can the system express compatibility constraints, engineering formulas and dimensional limits?
    Cost sources Are costs maintained internally, retrieved from ERP or supplied by another service?
    BOM output Can the system generate a configured BOM, and can it distinguish EBOM and MBOM requirements?
    Labor and operations Can setup, run time, work-center rates, testing and subcontracting be included?
    Traceability Can users see which selection or rule produced each cost line?
    Overrides Are manual changes controlled, logged and included in approvals?
    Integration Can the platform exchange data with ERP, PLM, PDM, CAD, CRM and MES where required?
    Performance Can the system calculate complex configurations quickly enough for interactive quoting?
    Governance Are model changes tested, versioned and released without disrupting open quotes?

    Do not evaluate a platform solely by the presence of a “costing” feature. Verify whether the documented capability supports the required manufacturing data, costing method, integration pattern and level of engineering complexity. A useful starting point is the broader guide to manufacturing CPQ software.

    Semantic map

    The following relationships summarize how cost rollups connect product configuration with manufacturing and commercial processes:

    • Configuration rules resolve customer selections into valid product structures.
    • Valid product structures resolve conditional components and operations.
    • Configured BOMs provide the component and quantity basis for costing.
    • Engineering calculations provide dimensions, weights and quantities for variable-cost items.
    • ERP systems provide item, supplier, inventory or standard-cost data.
    • Manufacturing routings provide labor, machine and operation costs.
    • Cost rollups provide the cost basis for margin and pricing calculations.
    • Pricing rules convert cost and commercial policies into customer prices.
    • Approval rules govern discounts, margins and unusual cost assumptions.
    • Approved configurations support quote documents, orders and production handoffs.
    • CAD automation can generate product-specific geometry and drawings.
    • Actual production costs provide feedback for improving estimates and product models.

    Frequently asked questions

    What is a cost rollup in manufacturing CPQ?

    A cost rollup aggregates the material, component, labor, machine, subcontracting, engineering and overhead costs required to produce a specific configured product. It uses the resolved configuration and BOM rather than only a generic base-product price.

    Is a cost rollup the same as a selling price?

    No. The cost rollup estimates what the manufacturer expects to spend or consume. The selling price applies margin, markup, discounts, freight, taxes and other commercial rules.

    Can every CPQ configurator perform manufacturing cost rollups?

    No. Some CPQ systems focus on guided selling, pricing and quote generation. Others support BOMs, routings, engineering calculations and cost integrations. Capability must be verified for the specific product and data model.

    What is needed to calculate a configurable product cost?

    The main requirements are a validated product model, configuration rules, a configurable or resolved BOM, component costs, material and labor data, operation rates, formulas and defined costing policies.

    How does a configurable BOM affect cost?

    A configurable BOM contains conditional components, alternatives and variable quantities. When selections are made, the applicable lines are resolved and their costs are aggregated into the configured product cost.

    Should cost data come from CPQ or ERP?

    There is no universal answer. CPQ-owned costing can be fast and flexible, while ERP-sourced costing can reduce duplicate master data. The correct choice depends on cost ownership, response-time requirements, data complexity and integration maturity.

    Can cost rollups include labor?

    Yes, if the product model or integrated manufacturing data includes operations, labor standards, setup time, run time and work-center rates. Simple option-price tables often do not include these costs.

    How are engineering-to-order products costed?

    ETO products may use parametric estimates, historical templates, engineering-hour allowances, provisional BOMs or external costing services. Because the final design may not exist, the estimate should be identified, approved and revised as engineering progresses.

    What is the difference between EBOM and MBOM costing?

    An EBOM represents the design view of a product, while an MBOM represents how it is assembled and manufactured. MBOM costing may include routings, consumables, packaging and shop-floor operations that are absent from the EBOM.

    Can CAD automation improve cost rollup accuracy?

    It can improve accuracy when geometry, dimensions, materials or calculated quantities affect cost. However, CAD automation does not automatically provide supplier prices, labor rates or complete manufacturing costing.

    How should material waste be handled?

    Waste can be modeled through scrap rates, yield factors, nesting assumptions, cut-length rules or material-utilization formulas. The method should match the manufacturing process and be clearly distinguished from the nominal material quantity.

    How do cost rollups support quote approvals?

    The rolled-up cost provides the basis for margin and discount checks. If the configured price falls below a threshold or includes an unusual manual override, the CPQ workflow can require management, finance or engineering approval.

    What happens when a supplier price changes?

    The responsible system should update the relevant cost record according to its effective date and synchronization process. Open quotes may either retain the original snapshot or be recalculated under controlled rules.

    Should a quote store the cost used at the time of creation?

    Usually, yes. Storing a cost snapshot preserves the basis for the quoted margin and supports auditability. The system may also retain a link to the source record and revision used for the calculation.

    How can manufacturers test a cost-rollup model?

    Test valid and invalid configurations, boundary values, alternative components, missing costs, unit conversions, currency changes, revision changes, manual overrides and actual-versus-estimated outcomes.

    What is the difference between standard cost and actual cost?

    Standard cost is a planned or accounting value used consistently for analysis. Actual cost reflects what was really purchased, consumed or spent. A CPQ quote may use standard or estimated cost, but the basis should be stated.

    Can a cost rollup include freight and installation?

    It can if the commercial model requires them. Manufacturers should distinguish product manufacturing cost from logistics, installation and service charges so that margin analysis remains understandable.

    What should a vendor demonstration include?

    Ask the vendor to configure a product where selections change components, quantities, materials, labor or engineering effort. The demonstration should show the source of each cost, BOM output, margin calculation, approval workflow and integration behavior.

    How often should cost-rollup rules be reviewed?

    Review frequency depends on supplier volatility, product-change frequency and manufacturing practice. In addition to scheduled reviews, changes to items, rates, routings, revisions and pricing policies should trigger controlled updates.

  • Using Simulation and Engineering Calculations During Configuration

    In manufacturing, simulation and engineering calculations allow a CPQ configurator to evaluate whether a proposed product will work before the quote reaches engineering or production. Instead of only selecting options and calculating a price, the system can calculate capacity, dimensions, performance, operating limits, material requirements and other technical results from the customer’s inputs.

    For example, a pump configurator may use flow rate, head, fluid properties, temperature and motor requirements to recommend a suitable pump size. An industrial machinery configurator may calculate frame dimensions, drive power, lifting capacity or guarding requirements. The result can include a validated configuration, an engineering summary, a configurable bill of materials (BOM), product-specific CAD outputs and a quote based on technically feasible requirements.

    This is a major distinction between manufacturing CPQ and generic sales CPQ. A sales-oriented system may configure commercial options and calculate a price. A manufacturing CPQ system may also execute engineering formulas, call simulation services, generate CAD data and pass validated product information to enterprise systems.

    What are engineering calculations during configuration?

    Engineering calculations during configuration are formulas, algorithms or external engineering services that transform configuration inputs into technical results. The results may determine whether a product is feasible, which components are required, how the product should be dimensioned or what performance it can deliver.

    The calculation normally runs after, or during, a user’s configuration choices. It can use selected options, numeric dimensions, environmental conditions, material properties, product standards and data from a product model. The output may be a warning, a required option, a calculated value, a recommendation, a component selection, a CAD parameter or an approval requirement.

    Calculation type Typical inputs Possible outputs
    Capacity calculation Load, flow, speed, volume or duty cycle Required motor, frame size or rated capacity
    Dimensional calculation Length, width, height, clearance or installation space Product dimensions, shaft length or enclosure size
    Thermal calculation Temperature, heat load, ambient conditions and materials Cooling requirement, insulation class or derating
    Hydraulic calculation Flow, pressure, fluid density, viscosity and pipe geometry Pipe diameter, pump selection or pressure loss
    Electrical calculation Voltage, current, power, phase and protection requirements Cable size, breaker rating or control-panel components
    Structural calculation Loads, spans, materials, supports and safety factors Section size, reinforcement or engineering review

    These calculations do not always constitute a full physical simulation. A simple algebraic formula may be sufficient for product selection. More advanced cases may use finite element analysis, computational fluid dynamics, kinematic simulation or an external engineering application.

    Where calculation fits in a manufacturing CPQ architecture

    A calculation-driven configurator usually sits between product data, engineering logic and commercial processes. The CPQ system manages the customer-facing configuration and often coordinates the data exchange, while specialized systems may perform calculations or generate design outputs.

    1. User inputs: The salesperson, dealer, engineer or customer enters requirements such as capacity, dimensions, material, operating environment and delivery constraints.
    2. Configuration model: The CPQ product model applies options, dependencies, exclusions and constraints. It determines which selections are permitted.
    3. Calculation engine: Formulas or an external service calculates technical values and evaluates performance or compliance.
    4. Selection and validation: The system selects components, reports warnings and requests additional information where needed.
    5. Engineering output: Parametric CAD, drawings, specifications, calculations or simulation results are generated when supported.
    6. Commercial output: The calculated configuration drives costing, pricing, a quote and potentially approval workflows.
    7. Manufacturing handoff: The validated configuration creates or updates a BOM, order structure and data sent to enterprise systems.

    The surrounding systems have different responsibilities. CAD means computer-aided design and contains geometric or design information. A product lifecycle management system (PLM) manages product definitions, revisions and lifecycle processes. A product data management system (PDM) generally manages CAD files and related engineering data. An enterprise resource planning system (ERP) manages operational data such as items, inventory, purchasing, orders and production. A manufacturing execution system (MES) supports execution on the shop floor.

    These systems are related but are not interchangeable. A CPQ system may orchestrate data between them through APIs, files, middleware or integration platforms. The appropriate architecture depends on where the authoritative version of each product and engineering record is maintained.

    Rules, calculations and simulation are different capabilities

    Product configuration rules, engineering calculations and simulation often work together, but they solve different problems.

    Capability Main question Example
    Rules-based configuration Is this selection allowed? A stainless-steel option requires a compatible seal material.
    Constraint-based configuration Which combinations satisfy multiple technical constraints? The selected motor, voltage and enclosure must be compatible with available space and power requirements.
    Guided selling Which product or option should be recommended based on user needs? Recommend a valve family based on media, pressure and temperature.
    Engineering calculation What technical value or component follows from the requirements? Calculate required pump head or structural section size.
    Simulation How will the proposed design behave under modeled conditions? Evaluate stress, airflow, motion or thermal performance.

    A rule may prevent an invalid combination without calculating anything. A formula may calculate a result without modeling physical behavior in detail. A simulation usually represents more complex behavior and may require more inputs, longer processing time and specialist validation.

    Manufacturing examples

    Pump and fluid equipment configuration

    A pump configurator can collect flow rate, total dynamic head, fluid type, temperature, viscosity, installation arrangement and power supply. Rules may prevent incompatible materials or seal combinations. Engineering calculations may estimate system resistance, pump duty point and motor power. A selection algorithm can identify suitable pump sizes from a controlled product catalog.

    The result may include a pump assembly, motor, coupling, baseplate, seals, instrumentation and a configurable BOM. A CAD system may use the selected pump, nozzle orientation and base dimensions to produce a model or drawing. The price can incorporate the selected materials, motor size and engineering options.

    HVAC and air-handling equipment

    An air-handling unit configurator may calculate airflow, heating or cooling capacity, coil dimensions, fan selection and pressure drop. Inputs can include air volume, entering and leaving temperatures, humidity, altitude, filtration requirements and available installation space.

    The calculation may identify a standard configuration, a non-standard design requiring engineering review or an infeasible request. It can also influence enclosure dimensions, access-panel positions, motor selection and the BOM. A quotation should make clear which results are calculated automatically and which remain subject to final engineering approval.

    Industrial machinery

    For a conveyor, hoist or packaging machine, configuration inputs may include product weight, throughput, travel distance, duty cycle, line speed and layout dimensions. Calculations can determine drive torque, motor power, belt width, roller spacing or frame requirements.

    If the requested combination exceeds the standard design envelope, the CPQ system may route the opportunity into an engineer-to-order (ETO) process. ETO means that substantial engineering work is performed for a particular order. By contrast, configure-to-order (CTO) uses predefined choices and generally produces a standard or modular product.

    Electrical equipment and enclosures

    An electrical equipment configurator may calculate enclosure size, heat dissipation, cable-entry requirements, protective-device ratings and available panel space. Rules can enforce voltage, phase, short-circuit rating and component compatibility.

    Where the design involves safety, regulatory compliance or high fault energy, automated results should be treated as decision support unless the organization has formally validated the calculation method and approval process.

    Using simulation during configuration

    Simulation is useful when a simple rule or formula cannot adequately predict product behavior. It may represent structural stress, airflow, fluid movement, heat transfer, motion, acoustics or energy consumption. In a CPQ workflow, simulation can be synchronous, asynchronous or performed after the initial configuration.

    Synchronous simulation

    A synchronous simulation runs while the user is configuring the product and returns a result before the workflow continues. This can provide immediate technical feedback, but it requires fast execution, a controlled model and reliable error handling. It is more appropriate for simplified calculations or reduced-order models than for computationally intensive analyses.

    Asynchronous simulation

    An asynchronous simulation runs as a background job. The CPQ system submits inputs, receives a job identifier and later retrieves the result. This approach supports more demanding analysis but requires status management, timeouts, notifications, version tracking and a clear user experience.

    Simulation after configuration

    Some companies allow a preliminary configuration and price to be created first, then run a detailed analysis before order acceptance. This is common when the analysis needs specialist software, licensed engineering tools or a controlled approval process. The commercial workflow should identify the quote as conditional if technical validation is incomplete.

    CAD and 3D outputs from calculated configurations

    Engineering calculations become more valuable when their outputs drive computer-aided design (CAD). A parametric CAD template can use calculated dimensions and selected options to create a product-specific model, drawing or visualization.

    For example, a configured material-handling system may calculate conveyor length, support spacing and drive position. Those values can populate CAD parameters. The resulting model may show the selected arrangement, while a drawing generator adds dimensions, hole patterns, connection details and notes.

    Possible outputs include:

    • 3D product models for review or customer approval;
    • 2D drawings with calculated dimensions;
    • installation layouts and clearance envelopes;
    • rendered images for a proposal;
    • neutral CAD exchange files;
    • engineering calculation reports;
    • manufacturing or assembly documentation.

    Not every CPQ platform generates CAD. Some integrate with CAD automation software, while others only store a reference to an externally generated file. Buyers should verify which CAD systems are supported, how templates are governed, how revisions are controlled and whether generated files can be reproduced from the saved configuration.

    For more detail, see the guide to CAD automation and engineering automation in manufacturing CPQ.

    How calculations affect BOMs, costing and quotes

    A bill of materials (BOM) lists the components, quantities and relationships required for a product or assembly. A calculated configuration can determine not only which options appear on a quote, but also which components are required for manufacturing.

    A configurable BOM may contain rules such as:

    • selecting a motor based on calculated power;
    • adding reinforcement when a load exceeds a threshold;
    • changing material grades based on temperature or fluid compatibility;
    • adding sensors when a control option is selected;
    • changing fasteners, seals or coatings for an environmental condition;
    • selecting different subassemblies for a calculated size range.

    An engineering BOM (EBOM) describes the product from an engineering and design perspective. A manufacturing BOM (MBOM) describes how the product is assembled or manufactured, including production structure and sometimes manufacturing-specific items. A CPQ process may generate or influence an EBOM, an MBOM, a configurable BOM or an order-specific structure, but the exact responsibility depends on the system architecture.

    Calculated values can also affect costing and pricing. A larger motor, thicker material, additional reinforcement or custom machining may increase cost. However, technical calculation and commercial pricing should remain conceptually separate. The calculation determines what is technically required; the pricing engine determines how that requirement is valued commercially.

    See BOM generation, costing and quote automation for the relationship between configuration outputs and commercial documents.

    Managing the sales-to-engineering handoff

    A strong configuration workflow reduces the amount of information engineering must reconstruct from a sales conversation. The handoff should include the customer requirements, selected options, calculated values, assumptions, warnings, approvals, revision identifiers and generated outputs.

    For example, a sales engineer handing over a configured pressure system should not send only a product code and price. Engineering may also need fluid properties, design pressure, temperature, corrosion allowance, selected materials, calculated wall thickness, instrumentation requirements and the version of the calculation method used.

    The handoff can be automatic for CTO products. For ETO products, the CPQ system may create an engineering request containing the preliminary design and identify the unresolved decisions. This preserves the work already performed while allowing an engineer to review non-standard requirements.

    Manufacturing workflow concepts such as CTO, ETO, make-to-order (MTO) and assemble-to-order (ATO) are explained in the guide to manufacturing CPQ workflows.

    Data required for reliable calculations

    Calculation quality depends on the quality and governance of the underlying data. A calculation is not reliable merely because the formula is mathematically correct.

    • Input definitions: Units, permitted ranges, precision, default values and required fields must be explicit.
    • Engineering constants: Material properties, efficiency factors, safety factors and performance curves require controlled ownership.
    • Product data: Component ratings, dimensions, compatibility information and lifecycle status must be current.
    • Versioning: The system must identify which formula, product revision and engineering data produced a result.
    • Assumptions: Ambient conditions, duty cycles, installation factors and user-provided estimates should be visible.
    • Units and conversions: The system must prevent errors between metric and imperial units or between related engineering measures.
    • Validation ranges: Inputs should be checked for missing, implausible or contradictory values.

    Product data may be maintained in the CPQ system, PLM, PDM, ERP or a specialist engineering database. The implementation should define which system is authoritative for each data category and how updates are published.

    Benefits and limitations

    Benefits

    • Fewer technically invalid quotes reach customers.
    • Sales engineers can evaluate standard configurations without repeating manual calculations.
    • Quotes can include more accurate dimensions, performance values and scope.
    • Calculated selections can drive BOMs, drawings and downstream order data.
    • Engineering effort can shift from repetitive selection work to genuinely non-standard designs.
    • Customers and dealers can receive faster feedback on feasibility and trade-offs.

    Limitations and risks

    • A calculation model may be valid only within a defined operating envelope.
    • Automated results may be wrong when inputs are incomplete or product data is outdated.
    • Detailed simulation can introduce long processing times and specialist software dependencies.
    • CAD automation can fail when templates, geometry or naming conventions are not maintained.
    • Complex rules may become difficult to test and explain if ownership is unclear.
    • Safety-critical or regulated products may require formal engineering sign-off.
    • A CPQ result does not automatically replace design verification, certification or professional engineering judgment.

    The system should distinguish between an automatically validated configuration, a configuration requiring review and a configuration that is outside the supported product model. A warning should explain the reason and the next action rather than merely displaying a generic error.

    Implementation approach

    1. Define the decision to automate

    Start with a specific engineering decision, such as motor selection, nozzle sizing, enclosure dimensioning or load validation. Avoid attempting to automate an entire engineering process before the inputs, outputs and acceptance criteria are understood.

    2. Document the existing method

    Capture spreadsheets, selection charts, CAD templates, manual calculations and approval practices. Identify hidden assumptions and exceptions. A formula that exists only in an experienced engineer’s personal worksheet is not yet a governed product rule.

    3. Separate inputs, rules and outputs

    Define which values are customer requirements, which are derived values, which are constraints and which are commercial decisions. This separation makes testing and future maintenance easier.

    4. Choose the calculation location

    The calculation may run inside the CPQ rules engine, in a dedicated calculation service, in CAD automation software or in an external simulation platform. Selection should consider performance, licensing, security, maintainability, auditability and integration requirements.

    5. Build test cases

    Test normal configurations, boundary values, invalid combinations, missing data, unit conversions, changed product revisions and failure responses. Include known engineering examples and independently verified results.

    6. Establish review and release governance

    Assign ownership for formulas, material data, component ratings, CAD templates and product rules. Changes should be versioned, reviewed and tested before being released to sales or dealers.

    7. Pilot a bounded product family

    A pump family, standard enclosure range or modular conveyor is often easier to pilot than a complete product portfolio. Measure calculation accuracy, engineering review time, quote rework, failed configurations and maintenance effort.

    Implementation planning should also cover migration, integrations, deployment, user adoption and long-term governance. The manufacturing CPQ implementation guide provides a broader framework.

    Integration considerations

    Calculation-driven CPQ commonly exchanges data with several enterprise systems. A customer relationship management (CRM) system may provide the opportunity and account context. CPQ manages configuration and quote logic. PLM or PDM may provide controlled engineering definitions. CAD generates geometry. ERP receives order, item, pricing or BOM data. A product information management (PIM) system may provide descriptions and commercial content. MES may consume production data later in the process.

    Integration design should specify the direction, timing, ownership and format of each data exchange. It should also define what happens when a calculation service is unavailable, a CAD job fails or an ERP item does not yet exist. APIs, event messages, files and middleware can all be valid approaches depending on the environment.

    Read more about CPQ integration with ERP, PLM, PDM, CAD and other systems.

    How to evaluate a CPQ configurator for engineering calculations

    When evaluating software, ask vendors to demonstrate a realistic product scenario rather than a generic option-selection screen. The demonstration should include numeric inputs, dependencies, calculations, a boundary condition, a generated BOM and a handoff to an engineering or ERP system if those capabilities are required.

    • Can the platform model formulas, constraints and calculated attributes?
    • Can users see why a configuration is invalid or requires review?
    • Can calculations be versioned and tested independently?
    • Can the platform call external calculation or simulation services?
    • Can calculated values drive component selection and BOM logic?
    • Can CAD parameters, drawings or 3D outputs be generated or exchanged?
    • How are engineering approvals and exceptions represented?
    • Can the system preserve the exact inputs, rules and revisions used for a quote?
    • What happens when a calculation, integration or CAD generation job fails?
    • Which capabilities are native, and which require custom development or partner software?

    Do not assume that a platform described as a CPQ configurator includes engineering simulation, CAD automation or manufacturing BOM generation. Verify each capability against the required product family and operating process. The manufacturing CPQ comparison and selection guidance can help structure this evaluation.

    Semantic map

    The article connects the following entities and concepts:

    • Manufacturing CPQ connects customer requirements with product configuration, engineering validation and quoting.
    • Configuration rules prevent invalid option combinations.
    • Engineering calculations transform requirements into technical values and component selections.
    • Simulation evaluates modeled product behavior under defined conditions.
    • Calculated values can drive CAD parameters and product-specific drawings.
    • Configured products can generate configurable BOMs and order structures.
    • Engineering BOMs describe design structure, while manufacturing BOMs support production structure.
    • CPQ exchanges configuration and commercial data with ERP, CRM, PLM, PDM, CAD, PIM and MES systems.
    • CTO uses predefined product choices, while ETO includes order-specific engineering.
    • Engineering governance controls formulas, product data, revisions, testing and approvals.

    Frequently asked questions

    What is simulation in a manufacturing CPQ system?

    Simulation in manufacturing CPQ evaluates how a proposed configurable product may behave under modeled operating conditions. It can cover structural, thermal, fluid, motion or other engineering behavior and may use an external specialist application.

    Are engineering calculations the same as configuration rules?

    No. Rules determine whether selections are allowed, while engineering calculations derive technical values or selections from inputs. A calculation can support a rule, but the two capabilities should be modeled and tested separately.

    Can a CPQ system calculate motor size?

    It can when the product model contains suitable inputs, formulas, performance data and validation limits. For example, load, speed, torque, duty cycle and efficiency may be used to recommend a motor, subject to engineering review where necessary.

    Can calculations generate a BOM?

    Yes, in systems that support calculated product structures or BOM logic. A calculated result may select components, quantities or subassemblies, but the resulting BOM should be reconciled with the organization’s engineering and manufacturing systems.

    Does every manufacturing CPQ platform include simulation?

    No. Some platforms provide rules and formulas only. Others integrate with CAD automation, calculation services or simulation software. The required capability must be verified for the specific product and engineering use case.

    What is the difference between a formula and a simulation?

    A formula usually calculates a result directly from defined variables. A simulation models behavior over conditions or time and may involve more complex numerical methods, larger data sets and longer execution times.

    Can sales representatives use engineering calculations?

    Yes, if the user interface exposes only the necessary inputs and the product model controls technical boundaries. Complex or safety-sensitive results may still require a sales engineer or engineering approval.

    How does CAD automation use calculated values?

    CAD automation can map calculated dimensions, selected options and component choices into parametric templates. It may then generate a 3D model, 2D drawing, installation layout or other product-specific output.

    What happens when a configuration is outside the calculation model?

    The system should identify the condition clearly and route it to engineering review, reject it as unsupported or initiate an ETO workflow. It should not silently produce a standard quote for an unvalidated design.

    How do calculations affect pricing?

    Calculations can determine required materials, components, capacity or processing, which then influence cost and price. The calculation engine determines technical requirements; the pricing engine applies commercial rates, margins, discounts and approvals.

    Can an engineering calculation be stored with the quote?

    A well-designed system should preserve inputs, outputs, assumptions, rule or formula versions and review status with the configuration or quote. This supports auditability and later reproduction of the result.

    What data is needed for a reliable engineering calculation?

    Typical data includes requirements, units, material properties, component ratings, performance curves, environmental conditions, safety factors and defined operating limits. The data must also be versioned and maintained.

    When should a simulation run synchronously?

    Synchronous execution is suitable when the calculation is fast and stable enough to provide immediate feedback. More demanding analyses are usually better handled asynchronously or after an initial configuration.

    How does CPQ support engineer-to-order products?

    CPQ can capture requirements, perform preliminary calculations, generate a preliminary structure and create an engineering request. Engineering then resolves non-standard design work before final approval and production release.

    What is the role of PLM in calculation-driven CPQ?

    Product lifecycle management (PLM) may provide controlled product definitions, revisions, materials, approved components and engineering change information. CPQ can use that data while managing the customer-specific configuration and quote workflow.

    How should calculation rules be tested?

    Testing should include normal cases, boundary values, invalid inputs, missing data, unit conversions, product revisions, integration failures and independently verified engineering examples. Results should be reviewed by qualified subject-matter experts.

    Can a CPQ calculation replace engineering approval?

    Not automatically. It can reduce repetitive work and validate standard configurations, but regulated, safety-critical, novel or out-of-range designs may still require formal engineering verification and approval.

    What should buyers ask CPQ vendors about engineering calculations?

    Ask whether formulas, constraints, external services, simulation jobs, CAD parameters, BOM logic, versioning, audit trails and approvals are supported natively or through customization and integrations. Request a demonstration using representative manufacturing data.