Tag: solution pricing

Product bundles and solution pricing in manufacturing CPQ allow a company to quote a complete engineered solution rather than pricing isolated parts. A bundle may combine a base machine, drive system, control panel, safety equipment, installation accessories and service coverage. The CPQ system validates whether the selected components work together, calculates costs and prices, produces the relevant bill of materials (BOM), routes exceptions for approval and generates a customer-ready quote.

In this context, CPQ means configure, price, quote. Manufacturing CPQ extends beyond generic sales quoting: it can connect product rules and engineering calculations to configurable BOMs, computer-aided design (CAD) outputs, enterprise resource planning (ERP), product lifecycle management (PLM) and production processes. Not every CPQ platform supports all of these capabilities, so manufacturers must verify the depth of product modeling, bundle logic, costing, downstream integration and engineering automation before selecting a system.

A useful starting point is the guide to CPQ software for manufacturing. For the specific product-modeling foundation, see product configuration, and for the downstream commercial and manufacturing data flow see BOM, pricing and quoting.

What are product bundles and solution pricing?

A product bundle is a commercially and technically related group of products, assemblies, options, services or consumables sold as one solution. A bundle can be fixed, configurable or partially configurable. A fixed bundle always contains the same items. A configurable bundle allows choices such as capacity, material, voltage, motor, enclosure, accessories or service level. A solution bundle can also include multiple related products that must be engineered or delivered together.

Solution pricing is the calculation of a price for the complete configured solution rather than simply adding unrelated item prices. It may include component prices, configuration-dependent costs, engineering effort, labor, freight, installation, warranty, risk margins, discounts and commercial adjustments.

For example, a pump manufacturer might sell a chemical-transfer package containing:

• a centrifugal pump selected by flow rate, head and fluid compatibility;
• a motor selected by power, voltage and hazardous-area requirements;
• a baseplate and coupling guard;
• valves, strainers and instrumentation;
• a control panel and variable-frequency drive;
• documentation, testing and commissioning services.

The bundle is not valid merely because every item exists in the catalog. The motor must match the pump duty, the materials must be compatible with the fluid, the control panel must support the selected voltage and the enclosure may need to meet a specified environmental or hazardous-location rating. The final price must reflect the resulting engineering and manufacturing requirements.

How bundles differ from simple product kits

Manufacturers should distinguish a commercial bundle from a manufacturing kit, sales package or configured solution. The terms are sometimes used interchangeably, but they can represent different data and operational behavior.

Concept	Meaning in manufacturing	Typical CPQ requirement
Fixed bundle	A predefined group of items sold together.	Bundle definition, price and component availability.
Configurable bundle	A package with selectable options and dependencies.	Rules, constraints, option pricing and validation.
Solution	A combination of products, assemblies, services and engineering work that addresses a customer requirement.	Cross-product compatibility, calculations, approvals and often project-level pricing.
Kit	A set of parts grouped for picking, assembly or delivery.	Kit structure, inventory behavior and possibly a configurable BOM.
Package or system	A technically integrated equipment group delivered as a functional unit.	System rules, interfaces, engineering outputs and production handoff.

A simple sales bundle may only add several stock items to a quote. A manufacturing solution model may need to create a new assembly structure, select engineered components, calculate dimensions and send data to ERP or PLM. The implementation should therefore define whether the bundle is only a commercial construct, a manufacturing structure, or both.

How manufacturing CPQ models a bundle

A bundle model normally contains a hierarchy of products and assemblies. At the top is the solution or package. Under it are mandatory components, optional modules, substitution groups, accessories, services and engineering outputs.

Bundle structure

A typical industrial equipment bundle might be modeled as follows:

• Solution: packaged water-treatment skid.
• Primary equipment: pump, tank, filter and heat exchanger.
• Drive and controls: motor, variable-frequency drive, panel and sensors.
• Mechanical integration: frame, piping, fittings, guards and supports.
• Commercial options: extended warranty, spare-parts kit, commissioning and training.
• Engineering outputs: configured BOM, specification sheet, layout drawing and installation requirements.

Each node can have attributes, valid values, quantities, dependencies, costs, prices and fulfillment behavior. A component may be included automatically when another option is selected. For example, selecting a high-temperature application may require a different seal material, insulation package and temperature-rated sensor.

Rules and constraints

Rules-based configuration uses explicit conditions such as “if voltage is 480 V, use a 480 V control package.” Constraint-based configuration evaluates permitted relationships and limits, such as motor power, shaft speed, flow, pressure and enclosure requirements. Guided selling asks questions in a sequence that helps a user reach a valid configuration, but it may not provide the same depth of technical constraint solving.

A bundle model may contain several types of rules:

• Inclusion rules: selecting a fire-rated enclosure adds a fire-rated door assembly and approved cable glands.
• Exclusion rules: two incompatible communication modules cannot be selected together.
• Dependency rules: a remote monitoring option requires a gateway and a suitable network connection.
• Quantity rules: a long conveyor requires additional supports at defined intervals.
• Calculation rules: pump size, motor rating, material thickness or cable size is calculated from technical inputs.
• Approval rules: a nonstandard material, discount or delivery commitment requires review.

Detailed guidance on product options, dependencies and validation is available in the product configuration guide.

Solution pricing architecture

Solution pricing should separate the different reasons why a price changes. This makes the model easier to test, explain and maintain.

Pricing layer	Examples	Manufacturing considerations
Component price	Pump, motor, valve or panel list price.	Item revisions, currencies, units and effective dates.
Option price	Stainless-steel construction, upgraded controls or additional sensors.	May replace a standard component rather than add to it.
Quantity price	Additional conveyors, filters or spare parts.	Quantity may be calculated from dimensions or capacity.
Configuration surcharge	Special coating, hazardous-area compliance or nonstandard testing.	Should be tied to a clear technical trigger.
Engineering price	Application engineering, design work or custom documentation.	Often depends on ETO complexity and approval.
Service price	Installation, commissioning, training or maintenance.	May depend on site, duration, travel and scope.
Commercial adjustment	Customer discount, dealer margin or project-level adjustment.	Requires authority limits, approval thresholds and auditability.

The price engine may calculate a list price, net price, cost, gross margin and price explanation. A manufacturer should preserve the distinction between cost and price. Cost may include purchased components, labor, overhead, freight and engineering effort. Price is the amount offered to the customer after margins, discounts and commercial policies are applied.

Bundle pricing strategies

Several pricing approaches can be combined:

• Component aggregation: add the prices of all selected items and services.
• Bundle price: assign a defined price to a valid combination.
• Replacement pricing: subtract the standard component and add the upgraded component.
• Tiered pricing: apply different prices based on quantity, capacity or order volume.
• Formula pricing: calculate price from dimensions, power, material weight or processing time.
• Cost-plus pricing: apply a margin or markup to calculated cost.
• Project pricing: combine equipment, services, risk allowances and commercial terms at solution level.

Pricing rules should also handle effective dates, currencies, units of measure, regional price lists, customer-specific agreements and channel margins. If the CPQ price differs from ERP or finance data, the integration must define which system is authoritative for each value.

From configured bundle to BOM

A configured solution can generate one or more BOM structures. A configurable BOM represents possible components and selection logic before a customer configuration is finalized. An engineering BOM (EBOM) represents the product from an engineering and design perspective. A manufacturing BOM (MBOM) represents how the product is assembled and produced. These structures may be related but are not interchangeable.

For a packaged machine, CPQ might generate:

• a quote-level commercial BOM showing customer-visible assemblies;
• an EBOM for engineering review and design release;
• an MBOM or ERP order structure for purchasing, routing and production;
• a spare-parts list and service BOM for after-sales use.

Whether CPQ directly creates an EBOM or MBOM depends on the platform architecture and integration design. Some systems produce a structured order configuration that ERP, PLM or a product data management (PDM) system transforms into the appropriate downstream structure. Others can generate production-relevant BOM lines directly. This capability must be verified rather than assumed.

For a deeper treatment of BOM structures and quote generation, see BOM, pricing and quoting in manufacturing CPQ.

Relationship with CAD and engineering automation

Bundles become more valuable when technical selections drive engineering outputs. A CPQ platform may pass configuration parameters to CAD automation, a rules-based design service or a separate engineering application. Possible outputs include a parametric 3D model, 2D drawing, dimensional specification, load calculation or equipment layout.

For example, a conveyor solution may use belt width, length, incline angle, product weight and throughput to determine frame sections, drive power, support spacing and guarding. The resulting dimensions can affect both the BOM and the price. If the system only changes the quote description without updating engineering data, the bundle is commercially configured but not fully engineered.

CAD automation is not a universal CPQ feature. Manufacturers should verify whether a prospective system can:

• store or calculate the parameters required by the CAD model;
• call an external CAD or engineering service;
• generate drawings or neutral files;
• maintain revision and approval status;
• return calculated dimensions and components to the CPQ model;
• handle failures, incomplete inputs and manual engineering review.

The CAD and engineering automation guide explains how these capabilities fit beside configuration and quoting.

Approvals and commercial governance

Solution pricing often creates approval requirements that do not exist for standard products. Approval triggers may include a margin below threshold, an unusual payment term, a nonstandard material, a custom delivery date, a safety-critical application or a large engineering commitment.

A practical approval workflow should show:

1. which rule or threshold triggered the approval;
2. what cost, price, margin or technical value is affected;
3. which person or role must review the exception;
4. whether the approval changes the configuration, price or terms;
5. which version of the configuration and pricing model was approved.

Approvals should not be used to compensate for missing product rules. If sales repeatedly requests approval for a combination that is always valid, the product model may need a new rule or standard option. Conversely, an approval should not override a genuine safety or technical constraint without a controlled engineering process.

Quote documents for bundled solutions

The quote should communicate enough detail for the customer to understand the proposed solution without exposing internal manufacturing structures unnecessarily. A bundle quote may contain:

• solution summary and application assumptions;
• selected equipment and major options;
• technical specifications and exclusions;
• commercial price by system, assembly or service category;
• delivery, installation and commissioning scope;
• warranty, payment and validity terms;
• drawings, rendered views or preliminary layouts where available;
• approval notes and revision information.

Customer-facing descriptions and internal BOM descriptions should be governed separately. A sales quote might describe “stainless-steel product-contact construction,” while the internal structure contains specific grades, fasteners and purchased parts. Both representations must remain linked to the same approved configuration.

Enterprise-system relationships

Bundle pricing normally involves several systems with different responsibilities.

System	Typical responsibility	Example exchange with CPQ
CRM, or customer relationship management	Accounts, opportunities, contacts and sales activity.	Opportunity context, customer and quote status.
ERP, or enterprise resource planning	Items, inventory, purchasing, orders, finance and production transactions.	Item masters, costs, orders, availability and order structures.
PLM, or product lifecycle management	Product revisions, engineering releases, change control and lifecycle data.	Released options, revisions, EBOMs and engineering status.
PDM, or product data management	CAD files, drawings and design metadata.	CAD references, revisions and generated design files.
CAD	Geometry, drawings and design calculations.	Parameters, models, layouts and drawings.
PIM, or product information management	Descriptions, attributes, media and channel content.	Customer-facing product information and option content.
MES, or manufacturing execution system	Shop-floor execution, work instructions and production status.	Released orders, routings or configuration-specific instructions.

These systems are not interchangeable. A CPQ platform may own the selling configuration and calculated quote, while ERP owns the order and financial transaction. PLM may own engineering revisions, and CAD or PDM may own design files. The integration architecture should document ownership, synchronization frequency, identifiers, revision behavior and error handling. More guidance is available in CPQ integrations for manufacturing.

Bundle workflows by manufacturing strategy

Bundles can support several operating models, but the required depth differs.

• Assemble-to-order (ATO): standard modules are assembled after the order. CPQ must select compatible modules and produce an order structure.
• Make-to-order (MTO): the product is made after the order using a relatively standard design. Pricing, availability and production data are central.
• Configure-to-order (CTO): customers select from predefined options and constraints. A valid configuration can usually map to known BOM and routing patterns.
• Engineer-to-order (ETO): the order requires new or materially changed engineering. CPQ must capture requirements, estimate engineering work and hand off controlled inputs for design.

A bundle can begin as CTO and become ETO when a customer requests a nonstandard capacity, interface or material. The system should make that transition explicit rather than pretending every solution is a standard configuration. See manufacturing CPQ workflows for related order-to-production patterns.

Benefits and limitations

Potential benefits

• Fewer incompatible combinations reach the customer or engineering team.
• Prices reflect selected options, calculated quantities and engineering scope.
• Sales engineers can quote complete solutions with less manual spreadsheet work.
• Configured BOM data can reduce re-entry between sales, engineering and ERP.
• Approval decisions become traceable and tied to configuration and margin data.
• Quote documents can present consistent technical and commercial information.

Important limitations

• A CPQ model is only as accurate as its product, cost and rule data.
• Complex engineering calculations may require specialist applications or manual review.
• Dynamic pricing can become difficult to maintain if formulas are undocumented.
• Different BOM structures may require transformation between CPQ, PLM and ERP.
• Frequent product changes create governance and regression-testing demands.
• Large bundles can produce performance, usability and version-control challenges.
• Commercial bundling does not automatically solve inventory, capacity or scheduling constraints.

Implementation approach

A successful implementation starts with a defined scope rather than attempting to model every product and exception at once.

1. Select a representative bundle: choose a product family with meaningful configuration, pricing and downstream impact.
2. Map the current workflow: document how requirements, options, costs, approvals, BOMs, drawings and orders move between teams.
3. Define system ownership: identify where items, costs, prices, rules, revisions, CAD files and customer data are maintained.
4. Separate standard and engineered content: mark which choices are CTO-valid and which trigger ETO review.
5. Build the product model: create attributes, options, dependencies, constraints, calculations and bundle structures.
6. Design the price model: define cost sources, price lists, formulas, discounts, margins, currencies and approval thresholds.
7. Define output structures: specify quote lines, configurable BOMs, EBOM or MBOM mappings, drawings and ERP order data.
8. Test realistic scenarios: include valid, invalid, boundary, obsolete, partially specified and exception configurations.
9. Establish governance: assign rule ownership, release procedures, version control, audit records and change-impact testing.
10. Measure operational results: track quote cycle time, configuration corrections, approval delays, engineering rework and order-data errors.

Implementation planning should include data migration, integration testing, user adoption and ongoing maintenance. The manufacturing CPQ implementation guide covers these concerns in more detail.

Evaluation checklist for manufacturing buyers

When evaluating CPQ software for bundled industrial solutions, ask vendors to demonstrate a complete scenario rather than isolated features:

• Can the system model nested bundles, substitutions and cross-product dependencies?
• Can technical constraints prevent invalid combinations before quote submission?
• Can calculated dimensions, capacities or quantities affect both BOM and price?
• Can the system distinguish customer-visible bundle lines from internal component structures?
• Can it calculate cost, margin, price and discount independently?
• Can approval rules identify technical, commercial and engineering exceptions?
• Can it produce the required quote, specification, BOM or order outputs?
• Which capabilities are native, and which require custom development or external services?
• How are product revisions, effective dates and obsolete options governed?
• How are ERP, CRM, PLM, PDM, CAD, PIM and MES integrations implemented and monitored?
• Can the model support dealer, distributor, internal sales engineering and customer self-service channels?
• How are failed calculations, integration errors and incomplete ETO requirements handled?

Vendor profiles and comparisons can help structure research, but manufacturers should validate documented capabilities through a scenario-based demonstration and technical proof of concept. See manufacturing CPQ software profiles and CPQ comparison and selection guidance.

Semantic map

The following relationships summarize how product bundles connect configuration, pricing, engineering and manufacturing execution:

• CPQ configures configurable products.
• Configuration rules prevent invalid combinations.
• Product bundles combine products, assemblies and services.
• Solution pricing calculates a commercial price for a configured solution.
• Configured products generate configurable BOMs.
• Engineering rules determine component compatibility.
• Cost calculations inform solution pricing.
• Approval rules govern commercial and technical exceptions.
• CAD automation generates product-specific drawings.
• EBOMs represent engineering product structures.
• MBOMs represent manufacturing assembly structures.
• CPQ exchanges item and order data with ERP.
• CPQ exchanges revisions and released structures with PLM.
• CRM provides opportunity and customer context to CPQ.
• ETO requirements trigger engineering review.
• Quote documents communicate approved solution scope.

Frequently asked questions

1. What is a product bundle in manufacturing CPQ?

A product bundle is a group of related equipment, components, options and services sold as one configurable solution. It may also produce a structured BOM for engineering or production.

2. How is solution pricing different from adding item prices?

Solution pricing can include compatibility-driven substitutions, calculated quantities, engineering effort, services, risk allowances, discounts and project-level approvals in addition to component prices.

3. Can a bundle contain products from different product families?

Yes. A pump package, for example, may contain a pump, motor, valves, controls, piping and services. Cross-family rules must validate interfaces, capacities, materials and electrical requirements.

4. Does every CPQ system generate a BOM?

No. Some CPQ platforms generate quote lines or order configurations only. Others generate configurable BOMs or integrate with ERP and PLM to create downstream structures. This must be verified for each product.

5. What is a configurable BOM?

A configurable BOM describes possible components and selection logic before a specific customer configuration is finalized. It differs from an EBOM or MBOM, which represent engineering or manufacturing structures.

6. Can CPQ generate an EBOM?

Some systems can generate or export engineering-oriented structures, while others pass configuration data to PLM or engineering tools. The supported revision, release and transformation process should be documented.

7. Can CPQ generate an MBOM?

Some platforms or integrations can create manufacturing-relevant structures, but this is not universal. ERP or manufacturing systems may own the MBOM and transform data received from CPQ or PLM.

8. How do bundle rules prevent configuration errors?

Rules enforce inclusions, exclusions, dependencies, quantities, technical limits and required approvals. They can prevent incompatible motors, materials, controls or accessories from reaching the quote.

9. What happens when a bundle requires custom engineering?

The configuration can be routed to an ETO workflow. CPQ may capture requirements, estimate engineering effort, flag assumptions and hold the quote for engineering review.

10. Can solution pricing include installation and commissioning?

Yes. Services can be modeled as bundle components or calculated charges. The model may use site conditions, duration, travel, labor rates and scope assumptions.

11. How should costs and prices be separated?

Costs represent internal or supply-side economic inputs such as materials, labor and engineering. Prices are customer charges after margins, discounts, terms and commercial policies are applied.

12. Can bundle pricing vary by customer or region?

It can, provided the pricing model supports customer agreements, regions, currencies, channels, effective dates and approval controls. The authoritative source for each price should be defined.

13. Is CAD automation required for manufacturing bundles?

No. Many bundles can be quoted without automated CAD. CAD automation becomes important when selections change geometry, dimensions, drawings, layouts or engineering calculations.

14. How does CPQ connect bundles to ERP?

Depending on the architecture, CPQ may exchange item identifiers, prices, configuration data, BOM lines, customer information and order details with ERP. Ownership and error handling must be designed explicitly.

15. How does PLM differ from ERP in a bundle workflow?

PLM generally manages product revisions, engineering releases and lifecycle data. ERP manages transactions such as purchasing, inventory, costing, orders and production. Both may receive different outputs from CPQ.

16. Can distributors use manufacturing CPQ bundles?

Yes. A dealer or distributor channel can use a controlled bundle model with permitted options, channel pricing, customer-specific discounts and quote outputs while protecting technical rules.

17. What approval triggers are common for solution pricing?

Common triggers include low margin, unusual discounts, nonstandard materials, safety-sensitive applications, custom delivery commitments, large engineering effort and exceptional commercial terms.

18. How should bundle models be tested?

Test valid and invalid combinations, boundary values, substitutions, obsolete options, price changes, revision changes, incomplete requirements, integration failures and ETO escalation paths.

19. What is the main limitation of a bundle model?

It can become difficult to maintain when rules, prices, BOM mappings and engineering exceptions are undocumented or owned by different teams without coordinated governance.

20. What should manufacturers ask during a CPQ demonstration?

Ask the vendor to configure a realistic multi-product solution, apply technical rules, calculate cost and price, trigger an approval, generate the required BOM and quote, and show the ERP, PLM or CAD handoff.