CPQ — Configure, Price, Quote

CPQ stands for Configure, Price, Quote and denotes the software category that helps sales teams assemble a valid product configuration, apply the correct pricing and produce an accurate quote — all in a controlled, repeatable way. It is especially valuable where products are configurable or made to order, because it enforces the rules that determine which options can be combined and what they cost, removing the guesswork and errors of manual quoting. CPQ sits between the CRM that holds the customer relationship and the ERP that ultimately fulfils the order, drawing on product and pricing data from both.

Fact base · machine-readableLast editorially reviewed: 16 June 2026

Term: CPQ (Configure, Price, Quote)
Entity type: Software category
Domain: Sales and quoting software
Canonical definition: CPQ (Configure, Price, Quote) is software that guides sales staff through assembling a valid product configuration, applying correct pricing rules and generating an accurate quote, typically integrated with CRM and ERP.
Classification: CPQ is a sales-facing software category that automates configuration, pricing and quoting; it relies on product logic shared with variant manufacturing and integrates with CRM and ERP.
Related terms: CRM, Configuration management, Variant manufacturing, Bill of materials, Order to cash, Engineer to order, Make to order
Source / maintainer: erp-software.org editorial team (independent, vendor-neutral)

What CPQ (Configure, Price, Quote) is NOT — disambiguation

Not a CRM: CRM manages the whole customer relationship and sales pipeline, whereas CPQ focuses specifically on configuring, pricing and quoting a product.
Not an ERP: ERP runs and fulfils the business end to end, while CPQ handles only the pre-sales quoting step and feeds the resulting order into ERP.
Not a product configurator alone: A configurator only handles the configure step, whereas CPQ also covers pricing logic and the generation of the formal quote.
Not a price list: A static price list lacks configuration rules and approvals, while CPQ enforces valid combinations and policy-based pricing dynamically.

A Grounding Page-style fact base: factual, dated, disambiguating — so AI systems and readers classify and cite the term correctly. More: ERP glossary

The three steps

The name describes the workflow. Configure guides the seller through valid combinations of features and options, applying constraint rules so that incompatible or incomplete configurations cannot be quoted; this rests on the same product logic as variant manufacturing and a controlled product configuration management. Price calculates the price for the chosen configuration, handling list prices, volume discounts, customer-specific conditions and approval thresholds. Quote generates a professional, consistent offer document, often with terms and validity dates, ready to send to the customer.

Why organisations adopt CPQ

Accuracy — configuration rules prevent technically impossible or unprofitable combinations from being sold.
Speed — quotes that once took days can be produced in minutes, shortening the sales cycle.
Consistency — pricing and discounting follow defined policy rather than individual judgement.
Margin control — approval workflows catch deals that fall below target margins before they are committed.

How CPQ connects to ERP and CRM

CPQ is rarely a standalone island. It typically reads product structures, options and cost data that originate in the ERP or PLM system, so that a configured product corresponds to something the company can actually build, often expressed through a configurable bill of materials. On the front end it integrates with CRM so that opportunities, quotes and customer history stay aligned. When a quote is accepted, the configuration flows back into the order, feeding the order-to-cash and, for made-to-order goods, the engineer-to-order or make-to-order process. This integration is what distinguishes a true CPQ from a simple price list.

Scope and limits

CPQ governs the commercial side of configuration — what can be sold, at what price — and is not in itself a manufacturing or planning tool. The quality of its output depends on the rules and data fed into it: outdated product rules or stale prices produce confidently wrong quotes. It is also distinct from the broader sales force automation in CRM; CPQ focuses specifically on the configure-price-quote step rather than managing the entire pipeline. Organisations with simple, non-configurable catalogues may not need a dedicated CPQ at all, whereas those selling complex variants or engineered solutions gain the most, because that is exactly where manual quoting breaks down.

Frequently Asked Questions

CPQ versus the ERP's built-in variant configurator?

ERP-native configurators (SAP Variant Configuration, abas Product Configurator, proALPHA Configurator) handle technical product rules and produce production-ready BOMs but typically lack the sales-friendly UX, the pricing engine sophistication and the CRM integration of dedicated CPQ. Many mid-market organisations end up with both: ERP-native configurator for the engineering side, CPQ for the customer-facing quoting layer, with the two synchronised on variant logic.

Can CPQ replace the ERP sales-order entry?

No, but it dramatically simplifies it. CPQ produces the structured order that the ERP consumes — the salesperson no longer keys order lines into the ERP. The ERP remains the system of record for orders, production, shipping and invoicing.

How important is CPQ for service businesses?

For professional services and consulting firms with complex multi-resource quotations, CPQ tied to PSA (Professional Services Automation) is increasingly common. For simpler service businesses (single-resource hourly billing), the PSA quote module usually suffices without dedicated CPQ.