A manufacturing CPQ process flow takes a customer need and turns it into a technically valid, manufacturable and commercially accurate quote. CPQ means configure, price, quote. In manufacturing, the process can include product configuration rules, engineering calculations, CAD automation, bill of materials generation, costing, pricing, approvals and integration with enterprise systems.
The flow is usually: capture requirements, select or build a product configuration, validate technical constraints, perform engineering calculations, generate product and manufacturing data, calculate cost and price, prepare the quote, obtain approvals and hand the approved configuration into order execution. The exact sequence varies by product and business model. A standard configure-to-order product may follow an automated path, while an engineer-to-order product may require engineering review before a quote is released.
This is different from generic sales CPQ, which may focus mainly on selecting commercial options, applying discounts and producing a proposal. Manufacturing CPQ must also answer whether the product can be built, which components are required, how it should be engineered and what data production needs. The manufacturing CPQ guide provides broader context on this category.
What is the manufacturing CPQ process flow?
The manufacturing CPQ process flow is the controlled sequence used to convert customer requirements into a validated product definition and quote. It connects commercial activity with product engineering and operations.
| Stage | Primary question | Typical output |
|---|---|---|
| 1. Customer need | What must the product do? | Requirements, application data and target specifications |
| 2. Product configuration | Which valid product choices meet the need? | Configured product and selected options |
| 3. Technical validation | Can the selected combination work safely and correctly? | Validated configuration, warnings or engineering tasks |
| 4. Engineering definition | What product-specific design is required? | Calculations, dimensions, CAD data, drawings or engineering instructions |
| 5. BOM and manufacturing data | Which parts and assemblies are needed? | Configurable BOM, EBOM, MBOM or manufacturing package |
| 6. Cost and price | What will the product cost and what should the customer pay? | Cost breakdown, price, discounts and margins |
| 7. Quote and approval | How should the offer be presented and controlled? | Customer quote, assumptions, lead time and approvals |
| 8. Handoff | How does the approved result enter execution? | Order, ERP transaction, engineering job or production release |
Stage 1: Capture the customer need
The process begins before a product option is selected. A salesperson, dealer, application engineer or customer may describe the required duty, environment and operating conditions rather than naming a specific model.
For a pump manufacturer, the requirements might include flow rate, pressure, fluid type, temperature, material compatibility, motor voltage, installation arrangement and regulatory requirements. For industrial machinery, they may include throughput, workpiece dimensions, available floor space, cycle time, safety requirements and automation interfaces.
A manufacturing CPQ application can capture these requirements through guided questions, technical input fields, imported data or a dealer portal. Guided selling presents questions in an order that helps the user reach an appropriate product family. It is not the same as a rules engine: guided selling helps select a suitable solution, while configuration rules determine whether selected features are technically compatible.
Requirements should be represented as structured data wherever possible. Free-text notes can preserve context, but they are difficult to validate and cannot reliably drive calculations, BOM selection or CAD automation.
Important requirement data
- Application and operating conditions
- Required capacity, performance or duty point
- Dimensions, weights and connection standards
- Materials, coatings and environmental conditions
- Power, voltage, controls and communication requirements
- Compliance, certification and documentation needs
- Delivery location, quantity and requested date
- Customer-specific standards or approved components
Stage 2: Select the product family and configure the product
Once the need is structured, the user selects a product family and configures its features. A product model defines available options, attributes, components, rules and relationships. The model may represent a pump, valve assembly, air-handling unit, conveyor, electrical cabinet, trailer or complete production machine.
Configuration can use several approaches:
- Rules-based configuration: explicit rules allow, require or prohibit options. For example, a high-temperature seal may require a specific material and exclude a standard elastomer.
- Constraint-based configuration: the system evaluates relationships and limits across many variables. For example, motor power, impeller diameter, frame size and flow may need to remain within engineering limits.
- Guided selling: questions narrow the product choice based on customer requirements. The result may then be checked by configuration rules.
A configuration model should distinguish commercial options from technical attributes. A customer may choose a stainless-steel housing as an option, while the resulting wall thickness, fastener material and manufacturing operation are derived values that the customer never selects directly.
The product configuration guide explains product models, dependencies, constraints and configuration validation in more detail.
Stage 3: Validate technical constraints
Validation prevents a quote from being created for a product that cannot be built, will not perform as required or violates a company policy. Validation may happen continuously as the user configures the product or as a formal review before quoting.
Typical rules include:
- an option requires another option;
- two materials or components are incompatible;
- a dimension must remain within a defined range;
- a motor must match the voltage and load;
- a pressure rating must exceed the application requirement;
- a selected component is unavailable for a particular product family;
- a certification requires specific construction or documentation;
- a customer-specific standard limits approved suppliers or parts.
Validation can produce errors, warnings or review tasks. An error blocks the configuration. A warning may allow the user to proceed while recording an assumption. A review task routes the case to engineering, compliance, purchasing or another specialist.
Rules should be tested against valid and invalid combinations. A large rule set can become difficult to maintain if rules are duplicated, embedded in code without documentation or owned by no clear business team. Product configuration governance is therefore as important as the rule technology.
Stage 4: Perform engineering calculations and design automation
Some products can be selected from a fixed catalog. Others require calculations that determine product dimensions or components. Manufacturing CPQ may perform these calculations directly, call an engineering service or create a task for an engineer.
For a pump, calculations may determine required head, power, impeller selection and operating range. For a heat exchanger, they may calculate surface area and connection sizes. For a conveyor, they may determine frame length, belt width, drive requirements and support spacing. For a vehicle body, they may calculate clearances, payload effects and mounting requirements.
Design automation can use these results to create a product-specific design. Parametric computer-aided design, or CAD, systems can update dimensions and component selections. The output may include a three-dimensional model, a two-dimensional drawing, a specification sheet or manufacturing instructions. Not every CPQ platform includes CAD automation, so this capability must be verified separately.
Engineering automation is particularly valuable when the same design logic is repeated across many orders. However, it requires governed engineering formulas, compatible CAD templates, reliable input data and a process for handling cases outside the automation envelope. The CAD and engineering automation guide covers these relationships.
Stage 5: Generate the bill of materials and manufacturing data
A validated configuration can drive a bill of materials, or BOM. A BOM is a structured list of the components, materials and quantities required for a product or assembly. In a manufacturing CPQ process, BOM generation may be immediate, conditional or delegated to an ERP, product lifecycle management system or engineering system.
Several BOM concepts should be distinguished:
- Configurable BOM: a product structure containing optional, conditional or variable components that are resolved for a particular configuration.
- EBOM: an engineering bill of materials, organized around the designed product and engineering relationships.
- MBOM: a manufacturing bill of materials, organized around how the product is assembled or produced.
An industrial machine might have one configured product definition, an EBOM describing the designed assembly and an MBOM that adds work instructions, packaging, consumables or production-specific grouping. These structures may be related but are not interchangeable.
CPQ may also derive routings, labor assumptions, purchased components, alternates, tooling requirements and documentation. In other implementations, CPQ creates a configuration identifier and passes the commercial result to an enterprise resource planning system, or ERP, which owns the official item and BOM transaction.
The BOM, pricing and quoting guide explains how configurable BOMs connect to costing and quote generation.
Stage 6: Calculate cost, price and lead time
Costing and pricing are related but different activities. Costing estimates the internal resources required to produce the configured product. Pricing determines what the customer is charged.
Cost inputs may include materials, purchased parts, labor, machine time, subcontracting, freight, tooling, engineering effort, warranty exposure and overhead allocations. Pricing may apply list prices, customer agreements, regional adjustments, quantity breaks, project discounts, channel margins, surcharges and target margin rules.
A manufacturing CPQ process should make clear which values are calculated, which are retrieved from a source system and which can be overridden. For example, material cost may come from ERP, a standard component price may come from a product information management system, and a project discount may require sales management approval.
Lead time can also be configuration-dependent. A standard motor may be available from stock, while a custom coating, nonstandard material or engineered frame may add procurement and production time. A quote that shows price without realistic delivery assumptions is incomplete for many industrial buyers.
Stage 7: Generate the quote and manage approvals
The quoting stage turns the validated commercial result into a customer-facing document. A manufacturing quote commonly contains:
- configured product description and option summary;
- technical specifications and performance data;
- quantities, unit prices and total price;
- discounts, surcharges, taxes or freight assumptions;
- estimated lead time and delivery terms;
- scope boundaries, exclusions and customer responsibilities;
- warranty, validity period and payment terms;
- drawings, images, datasheets or compliance documents when appropriate.
Approval workflows should be based on business risk, not only price. A quote may need engineering approval for a nonstandard operating point, finance approval for a low margin, legal approval for unusual terms or operations approval for a capacity constraint.
Document generation should use the same configuration and pricing data used to create the quote. Re-keying selected options into a word processor or spreadsheet creates a risk that the document will not match the product being offered.
Stage 8: Handoff from quote to order and production
When the customer accepts the quote, the approved configuration becomes an order candidate or an engineering release. The handoff depends on the manufacturing workflow.
| Workflow | Typical CPQ handoff | Example |
|---|---|---|
| Configure-to-order (CTO) | Validated configuration, item identifiers and resolved BOM enter order processing | Standard pump package with selectable materials and motor sizes |
| Engineer-to-order (ETO) | Requirements, calculations and engineering tasks create a project-specific design | Large custom material-handling machine |
| Make-to-order (MTO) | Demand triggers procurement or production after order acceptance | Configured electrical enclosure built after approval |
| Assemble-to-order (ATO) | Standard modules are combined after order receipt | Modular conveyor assembled from stocked sections |
The handoff may involve customer relationship management, or CRM, for the opportunity and account; ERP for order, inventory, purchasing and financial transactions; product lifecycle management, or PLM, for product definitions and revisions; product data management, or PDM, for CAD files and documents; manufacturing execution systems, or MES, for production execution; and CAD for design outputs. These systems have different responsibilities and should not be treated as interchangeable.
The manufacturing workflow guide explains CTO, ETO, MTO and ATO processes, while the CPQ integration guide covers system boundaries and data exchange.
How the process differs by manufacturing environment
Configure-to-order
CTO works best when the product architecture, options and manufacturing structures are known in advance. Automation can validate selections, resolve a BOM, calculate price and create an order with limited manual engineering.
Engineer-to-order
ETO begins with a customer need but requires project-specific design. CPQ can capture requirements, identify a product platform, calculate preliminary dimensions, estimate engineering effort and create a controlled handoff. It should not be presented as fully automated if engineers must still design and approve the product.
Dealer and distributor sales
Dealer users may need a simplified interface, controlled access to prices and product guidance without seeing internal costs or engineering rules. The manufacturer must still ensure that the resulting configuration can be produced and supported.
Self-service and ecommerce
Self-service configuration can work for bounded products with clear rules, stable pricing and predictable fulfillment. Products requiring application engineering, site surveys or safety review may need a hybrid workflow that routes complex cases to specialists.
Systems and data architecture
A manufacturing CPQ solution commonly sits between customer-facing channels and engineering or enterprise systems. The CPQ application may own the configuration session and quote, while other systems remain authoritative for specific data.
| System | Typical responsibility |
|---|---|
| CRM | Accounts, contacts, opportunities and sales activity |
| CPQ | Configuration session, rules, calculations, pricing logic and quote |
| ERP | Items, inventory, purchasing, orders, finance and operational costing |
| PLM | Product structures, revisions, change processes and lifecycle governance |
| PDM | CAD files, engineering documents and controlled design data |
| CAD | Parametric models, drawings and design outputs |
| PIM | Product attributes, descriptions, media and channel content |
| MES | Production dispatch, execution, quality and shop-floor records |
In practice, ownership must be agreed for each data object. For example, CPQ may calculate a configuration-specific option set, PLM may own released engineering structures, ERP may own sellable item numbers and costs, and CAD may generate the geometric model. Integration should transfer identifiers, revisions, quantities, units and status as well as descriptive text.
Benefits of a controlled manufacturing CPQ flow
- Fewer configuration errors: rules prevent incompatible options from reaching the quote.
- Faster response: repeatable calculations and document generation reduce manual work.
- More consistent pricing: cost and price logic is applied systematically.
- Better engineering leverage: engineers spend less time answering repetitive selection questions.
- Improved production handoff: approved configurations can carry structured BOM and specification data.
- Traceability: the company can record who configured, reviewed and approved the quote.
- Improved channel control: dealers can sell complex products within defined technical and commercial boundaries.
Limitations and common failure points
CPQ does not eliminate product complexity. It exposes and formalizes it. Implementation can be difficult when product options are poorly defined, engineering knowledge exists only in documents, prices are maintained in disconnected spreadsheets or BOM ownership is unclear.
Common failure points include:
- trying to automate products whose engineering rules have not been documented;
- treating every custom request as a simple option;
- using one product structure for sales, engineering and manufacturing without mapping their differences;
- allowing uncontrolled manual overrides;
- ignoring units, revisions, effective dates and regional variations;
- building integrations before agreeing on data ownership;
- failing to test negative cases and unusual but valid applications;
- assuming that a vendor’s generic CPQ capability includes CAD, BOM, ETO or PLM functions.
Some configurations should remain subject to engineering review. A good process makes the boundary visible and routes exceptions deliberately rather than hiding them in manual workarounds.
Implementation considerations
Manufacturers should begin with a defined product family and a measurable workflow problem. Map the current process from customer inquiry through quote and order release. Identify where users re-enter data, where errors occur, which decisions require engineering and which systems own the relevant information.
Before building the model, document:
- features, options, attributes and valid ranges;
- dependencies, exclusions and required combinations;
- engineering formulas and their owners;
- component selection and BOM logic;
- cost sources, price rules and approval thresholds;
- quote templates, assumptions and revision controls;
- interfaces to CRM, ERP, PLM, PDM, CAD, PIM and MES;
- exception paths for ETO and nonstandard requests.
Use representative examples for testing: a normal configuration, an invalid combination, a boundary value, a discontinued component, a revision change, a low-margin quote and an ETO case. Test not only the user interface but also the outputs: configuration identifier, BOM, CAD file, price, lead time, quote document and downstream transaction.
Ownership should continue after deployment. Product management may own commercial options, engineering may own technical rules, manufacturing may own assembly logic, finance may own pricing policy and IT may own integrations. A release and change-control process is necessary when products, components, suppliers or regulations change.
The CPQ implementation guide covers requirements, migration, testing, governance, adoption and maintenance. Buyers evaluating platforms can also use the manufacturing-focused CPQ comparison and selection resources.
How to measure the process
Useful measures should cover speed, quality and downstream usefulness rather than quote volume alone. Possible measures include quote cycle time, percentage of quotes requiring engineering intervention, configuration error rate, quote-to-order conversion, margin variance, time from order to engineering release, percentage of orders requiring rework and the proportion of BOM data accepted without manual correction.
Metrics need clear definitions. For example, quote cycle time may begin when all required technical inputs are available rather than when an incomplete inquiry first arrives. Otherwise, the measure may encourage premature quotes instead of accurate ones.
Conclusion
A manufacturing CPQ process flow connects customer requirements to a valid product, an engineering definition, manufacturing data, cost, price and a controlled quote. The strongest implementations do not treat CPQ as a document generator. They establish a reliable product model, make configuration rules explicit, separate EBOM and MBOM responsibilities, automate appropriate engineering work and exchange governed data with CRM, ERP, PLM, PDM, CAD and MES systems.
The right level of automation depends on the product. Standard CTO products may support near-real-time configuration and order handoff. ETO products may use CPQ to structure requirements and accelerate preliminary engineering while retaining expert review. In both cases, the objective is the same: provide a commercially accurate offer that the manufacturer can build, deliver and support.
Semantic map
The following relationships summarize the entities and data flows described in this guide:
- Customer requirements lead to product configuration.
- Product configuration is evaluated by configuration rules.
- Configuration rules prevent invalid combinations.
- Engineering calculations determine product-specific parameters.
- Validated configurations generate configurable BOMs.
- EBOMs describe engineered product structures.
- MBOMs describe manufacturing assembly structures.
- CAD automation generates product-specific design outputs.
- Costing estimates resources required to build the product.
- Pricing converts cost and commercial policy into a customer price.
- CPQ generates quotes from configuration and pricing data.
- CRM stores opportunity and customer context.
- ERP manages orders, inventory, purchasing and financial transactions.
- PLM governs product definitions, revisions and lifecycle changes.
- MES supports production execution after order release.
- ETO requires engineering review for project-specific designs.
Frequently asked questions
1. What is a CPQ process flow in manufacturing?
It is the sequence that converts customer requirements into a validated configuration, engineering and manufacturing data, cost, price and a formal quote.
2. What does CPQ stand for?
CPQ stands for configure, price, quote. In manufacturing, configure may include technical validation and engineering outputs in addition to selecting commercial options.
3. How does manufacturing CPQ differ from sales CPQ?
Sales CPQ often concentrates on product selection, discounts and proposals. Manufacturing CPQ may also manage constraints, calculations, BOMs, CAD outputs, costing and production handoff.
4. What happens first in the CPQ process?
The process starts by capturing structured customer requirements such as duty, dimensions, materials, environment, performance and compliance needs.
5. What is the role of configuration rules?
Configuration rules define valid and invalid combinations, required options, exclusions, ranges and technical dependencies.
6. Is guided selling the same as product configuration?
No. Guided selling asks questions to recommend a product or configuration path. Product configuration validates the selected features and their technical relationships.
7. Can CPQ generate a bill of materials?
Some manufacturing CPQ systems generate or resolve BOMs, while others pass configuration data to ERP, PLM or another system that owns the BOM. This capability must be verified for each platform.
8. What is the difference between an EBOM and an MBOM?
An EBOM represents the engineered product structure. An MBOM represents how the product is assembled or produced. They may contain different groupings, parts and manufacturing information.
9. Does every CPQ system include CAD automation?
No. CAD automation may be a native capability, an integration or an external engineering service. Buyers should verify supported CAD systems, templates, outputs and revision handling.
10. How does CPQ support engineer-to-order products?
CPQ can capture requirements, select a product platform, perform preliminary calculations, estimate engineering effort and create a controlled engineering handoff. It does not necessarily replace project engineering.
11. How does CPQ calculate manufacturing prices?
It can combine material, labor, purchased-component, freight, engineering and overhead inputs with price lists, margins, discounts, surcharges and approval rules.
12. Which systems commonly integrate with manufacturing CPQ?
Common integrations include CRM, ERP, PLM, PDM, CAD, PIM and MES. The exact scope depends on the product model and the responsibilities assigned to each system.
13. What information should appear in a manufacturing quote?
A quote should normally include the configured product, technical specifications, quantities, price, lead time, assumptions, exclusions, terms and relevant drawings or documentation.
14. Why are manufacturing CPQ implementations difficult?
They require product rules, engineering knowledge, pricing data, BOM logic, system ownership and exception handling to be made explicit and maintained over time.
15. Should every configuration be fully automated?
No. Standard, repeatable configurations are good automation candidates. Novel, safety-critical or highly customized designs may require engineering review.
16. What is the difference between CTO and ETO?
Configure-to-order uses predefined product structures and options. Engineer-to-order requires project-specific engineering before or during order fulfillment.
17. How does CPQ support configure-to-order production?
It validates options, resolves the configuration, calculates price and can pass item, BOM and specification data into order and production systems.
18. What should be tested before launching a CPQ process?
Test valid, invalid, boundary, discontinued, revised, low-margin and ETO scenarios, including the resulting configuration, BOM, price, quote, CAD output and downstream transactions.
19. Who should own manufacturing CPQ rules?
Ownership is usually shared: product management for commercial options, engineering for technical rules, manufacturing for assembly logic, finance for pricing and IT for integrations.
20. What is the main objective of manufacturing CPQ?
The objective is to create an accurate, technically valid and commercially acceptable offer that the manufacturer can reliably build, deliver and support.