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