What Is CPQ: Configuration, Pricing, Quoting, and How to Choose a System
What is CPQ: configuration, pricing and quoting as three separate problems, the rule mechanisms that set CPQ systems apart, and how to choose one.
Paul Maxwell, PhD
AUTHOR
GET WEEKLY REVOPS INSIGHTS
No spam. Unsubscribe anytime.
A quote goes out for a machine the plant cannot build, and the error surfaces only when the order reaches production. Two sellers price the same scope for the same account at figures $240 a month apart, each following a documented price list. A quote accepted seven months after issue binds the business to prices that no longer cover cost. Three different mechanisms have failed, and all three are offered as the reason to buy one category of software. The usual answer to what is CPQ is a feature list, and a feature list does not say which of the three problems a given business has.
This article defines CPQ and separates the three problems the acronym joins. It starts with the letters and the four questions the term runs together, then counts the valid combinations of a sample catalogue, which leads to the central finding: CPQ systems differ in kind at the configuration step, in when a rule acts and in whether one rule holds in both directions. Pricing, the quote document, the process, implementation variants, costs, a selection procedure, symptoms and boundaries follow.
A configuration rule is a stated relation between options: one requires another, excludes another, or limits its quantity. The nominal set is every combination a catalogue could list if no rule existed, and the valid set is the subset that satisfies every rule. Precedence is the order that decides which of two applicable price sources wins.
CPQ Meaning: What the Letters Stand For
CPQ stands for configure, price, quote, and each letter names a separate decision with its own owner. Configure decides which combinations may be sold together, under rules set by operations or engineering. Price decides what a valid combination costs, under rules set by finance: tiers, price books, discounts and the approvals a discount triggers. Quote produces the document a customer signs, with terms, an expiry and an approval record, under controls set by legal and the deal desk.
Four questions travel under the one acronym, and each has a different kind of answer. What CPQ means is a matter of definition, and what CPQ software does is a matter of documentation, checkable on each vendor's pages. Whether a business needs a dedicated system is a matter of its own quote history, which no vendor can supply, and the choice of product follows from that answer rather than from a feature list.
Two neighbouring terms are confused with CPQ. Quote-to-cash starts at the accepted quote and runs through order, invoice, recognition and collection, as set out in quote to cash; CPQ ends where that chain begins. Quoting software is the wider category of tools that produce a priced document, compared by sector in quoting software. A quoting tool without configuration rules is not CPQ in the sense used here.
Configuration Rules and the Valid Set
Configuration is the one stage whose difficulty can be computed before any software is examined, from the sizes of the nominal set and the valid set.
The catalogue below is sample data, invented for illustration, and describes no client. A packaged air-compressor line is sold in five option groups: frame (S, M or L), motor (5 kW, 11 kW or 18 kW), controller (basic or networked), dryer (none or integrated) and service plan (none, one year or three years). The nominal set is 3 × 3 × 2 × 2 × 3, which is 108 combinations. Four rules apply: frame S cannot take the 18 kW motor, frame L cannot take the 5 kW motor, and both the integrated dryer and the three-year plan require the networked controller. Applied in that order, the rules remove 12, 12, 21 and 7 combinations, leaving 56.
The count can be checked a second way. Seven frame and motor pairs survive the two exclusions; the basic controller then allows 2 dryer and plan combinations and the networked controller allows 6, so the valid set is 7 × (2 + 6), or 56.
If each option were picked without reference to the others, 52 of 108 machines, or 48 percent, could not be built. The nominal set also grows by multiplication: twelve option groups of four settings give 4^12, or 16,777,216 combinations, a space no seller can search, so at that scale the valid set has to be generated by rules rather than remembered by people. Length alone creates no such problem, since four hundred products each sold alone need no configuration rule at all.
Configuration Mechanisms in CPQ Software
The finding of this article is that CPQ systems differ in kind at the configure step. They differ in two linked respects: when a rule acts, and whether one rule holds in both directions. Vendor documentation read in September 2026 describes three mechanisms. One sample relation, written in each, turns the difference into a count of rules.
Validation after the pick. HubSpot's quote rules, a Revenue Hub Enterprise feature, can require or prevent products being sold together, cap quantities and set discount limits. A rule's outcome is either Show warning or Block publish. In the rule syntax reference each rule expression describes a violation condition. The rule inspects what is already on the quote: the seller adds products, the rule objects, the seller corrects. Neither outcome adds or removes a product.
Selection at the pick. Salesforce CPQ has four types of product rule, per Salesforce's training material: alert, validation, selection and filter. An alert shows a message the seller may ignore. A validation message must be fixed before the configuration or quote can be saved. Together they parallel HubSpot's Show warning and Block publish. The selection rule has no HubSpot counterpart: it adds, removes or hides products during bundle configuration. In the selection rules module, it fires when the configuration page loads and on every edit. The module also records that it does not undo its action once its condition stops holding. A rule that disables an option therefore needs a second rule to enable it again. Each rule also acts only in the direction it was written for.
Constraint before the choice. Salesforce's end-of-sale page describes the Salesforce CPQ configurator as rules-based over SKU bundles and options. It describes the successor, Revenue Cloud Advanced, as constraint-based over an attribute-based catalogue. In the general sense of the term, a constraint is a relation stated once and enforced whichever option is chosen first. Once either side is picked, the incompatible values on the other side are not offered. This article claims no more about Revenue Cloud Advanced than that page states.
One sample relation shows what the difference costs: the integrated dryer requires the networked controller. Under validation it is one rule, and a seller who picks the basic controller and then the dryer has already built an invalid combination when the rule objects. Under selection, one way to write it takes three rules: add the networked controller when the dryer is chosen, disable the dryer when the basic controller is chosen, and enable the dryer again when the basic controller is not. The third rule exists because the disabling rule does not undo itself. Under constraint it is one relation: whichever option the seller picks first, the incompatible value of the other is not offered.
Pricing and quoting show no comparable split in the documentation reviewed: HubSpot documents tier models, price books, approvals and expiry, Salesforce's end-of-sale comparison lists price rules and custom scripts for Salesforce CPQ and declarative pricing procedures for Revenue Cloud Advanced, and Oracle describes Oracle CPQ as covering product selection, configuration, pricing, quoting, ordering and approval workflows. The products differ there in reach and precedence handling, not in when the mechanism acts. Where few rules share a product, validation suffices because a warning names the broken rule; where correcting one violation produces another, the mechanism has to act during or before the choice.
Price Models, Price Books and Precedence
Pricing fails differently from configuration: two correct rules both apply, and nothing states which one wins. HubSpot's product library documents three tier models, each requiring a Revenue Hub subscription. Volume-based pricing applies one unit price, set by total quantity, to every unit; graduated pricing applies each tier's price only to the units inside that tier; stair-step pricing charges one flat fee for the highest tier reached.
The deal below is sample data: 120 seats of a subscription licence, priced at $40 per seat per month for seats 1 to 50, $35 for seats 51 to 100, and $30 from seat 101. Under the volume model, 120 × $30 gives $3,600 a month, and under the graduated model, 50 × $40 + 50 × $35 + 20 × $30 gives $4,350: the same table, quantity and customer, and totals $750 a month apart.
HubSpot's price books, a Revenue Hub Enterprise feature, hold alternative prices for partner, referral or regional selling. A book is assigned automatically only when a deal matches exactly one assignment rule, and only when the deal is created. Where several books match, the deal owner chooses between them. Suppose the sample deal matches a regional book at $34 per seat and a partner book at $32. One owner picks the regional book and quotes $4,080 a month. The owner of a second deal for the same account picks the partner book and quotes $3,840. The $240 difference breaks no rule, because no rule ranks the two books.
| Source of the price | Arithmetic | Monthly price |
|---|---|---|
| Source of the priceVolume-based tiers | Arithmetic120 × $30 | Monthly price$3,600 |
| Source of the pricePartner price book | Arithmetic120 × $32 | Monthly price$3,840 |
| Source of the priceRegional price book | Arithmetic120 × $34 | Monthly price$4,080 |
| Source of the priceGraduated tiers | Arithmetic50 × $40 + 50 × $35 + 20 × $30 | Monthly price$4,350 |
The highest figure is 20.8 percent above the lowest ($4,350 ÷ $3,600 = 1.208), and every row follows a documented model or a legitimate book. A pricing engine earns its place by deciding between rows, since each row alone is simple arithmetic.
Quote Documents, Expiry and Approval Records
The quote is the artefact that leaves the business, and three of its controls are documented precisely enough to configure. HubSpot allows a default expiration period of 1 to 365 days, set under Settings > Data Management > Objects > Quotes. A quote accepted in time does not expire, even if it is not yet countersigned or paid.
HubSpot's quote approvals come in two types that cannot run together. Standard approvals route quotes matching property filters to up to ten approvers, one or all of whom must approve. Advanced approvals, on Revenue Hub Enterprise, trigger on properties such as discount, amount, SKU and net terms, and run up to five sequences of up to ten approvers each.
Revision lineage is the third control: three revisions for one request are three documents and one opportunity, and an illustrative case study of a job shop's quoting implementation shows a single flag marking the revision that counts in the pipeline.
Packaging bears on all three. HubSpot's CPQ overview places quotes, approvals and tiered pricing under Revenue Hub Professional and Enterprise, and requires a Revenue Hub seat to create or edit a quote. Its legacy quotes documentation states that accounts created after 3 September 2025 have no legacy quotes, so for a new HubSpot account quoting is sold as CPQ.
The CPQ Process From Requirement to Accepted Quote
The CPQ process runs in six steps: requirement, configuration, pricing, approval where a threshold is crossed, document generation with terms and expiry, and acceptance, after which the quote passes to order entry. Line items carrying identifiers the billing system recognises pass intact; line items carrying typed descriptions are rekeyed by a person, at joins covered in quote-to-cash antipatterns.
CPQ Implementation Variants
A CPQ implementation takes one of four shapes, distinguished by configuration mechanism and by which system owns the product master. The firm is a HubSpot Solutions Partner and has an interest in the second row.
| Variant | Mechanism and product master | Fits when |
|---|---|---|
| VariantSpreadsheet and document template | Mechanism and product masterNone: rules live in people | Fits whenFew independent items, low volume |
| VariantCRM-native CPQ, such as HubSpot CPQ | Mechanism and product masterValidation rules that warn or block; price books in the CRM | Fits whenA valid set small enough to reach by correcting warnings |
| VariantCPQ on the CRM platform: Salesforce CPQ, Revenue Cloud Advanced | Mechanism and product masterSelection rules over bundles, or constraints over attributes | Fits whenInteracting rules, nested bundles |
| VariantStandalone CPQ, such as SAP CPQ or Oracle CPQ | Mechanism and product masterA separate engine connected to CRM and ERP | Fits whenA product master held in the ERP |
The alternatives to CRM-native CPQ win on two specific axes. On configuration, a selection or constraint mechanism acts during or before the choice, while HubSpot's quote rules act on the assembled quote. On precedence, a deal matching two HubSpot price book rules is assigned neither automatically and its owner chooses, while Salesforce's price rules, scripts and pricing procedures are places where precedence can be written down. SAP's training material describes SAP CPQ as integrating with CRM and ERP systems to apply customer and product data, which suits a catalogue mastered in the ERP. Salesforce no longer sells Salesforce CPQ to new customers, so for a business not already on it the Salesforce row means Revenue Cloud Advanced.
Costs and Returns of a CPQ System
At configuration a CPQ system buys the removal of unbuildable orders, and the return scales with the invalid share of the nominal set: 48 percent in the sample catalogue, zero where items are sold independently. At pricing it buys one answer where there were several, which on the sample deal was a $750 monthly spread. At quoting it buys an enforced expiry and an approval record an auditor can follow.
It costs licences, rule authoring and rule ownership. In HubSpot, quote rules, price books and advanced approvals need Revenue Hub Enterprise, and every quote author needs a Revenue Hub seat. Rule authoring appears on no price list: the rules are commercial and engineering knowledge held in people, and no licence writes them down. Ownership never ends: a rule set not updated with the catalogue keeps enforcing the old one.
The case is strongest where a combinatorial catalogue, discounting delegated to many sellers and quote volume beyond manual review occur together. It is weakest for a services business whose scope is written rather than assembled, where the quote tool already owned supplies expiry and approvals. It is also weak over an unrationalised catalogue, because rules over discontinued products cost as much to write as rules over live ones.
Selection Procedure and Its Verification
The procedure establishes which stage binds and which mechanism a catalogue needs, using exported quote history as evidence.
- Export the last two hundred quotes with line items, discounts, approval records, and issue, expiry and acceptance dates. Where quotes exist only as emailed documents, reconstructing this export is the first piece of work.
- Count the distinct combinations quoted, and compute the nominal set by multiplying the settings in each option group.
- Write every rule between products as a requires, excludes or quantity relation, and mark each pair of rules that share a product.
- For each configuration quoted more than once, name the model or book behind each price; a spread with no broken rule is a precedence gap.
- Count quotes with no expiry, quotes accepted after expiry, and discounted quotes lacking an authorised approval.
- Choose the mechanism: validation where few rules share a product, selection or constraint where rules interact or the nominal set cannot be searched, and no dedicated system where step 3 found no rules.
- Verify by rebuilding twenty historical quotes in the candidate system from the original requirement alone, then comparing configuration and price with what was sent. Each difference is a rule the system lacks or an error the business made, and both lists must be explained before a contract is signed.
Symptoms by Stage and Their Mechanisms
Orders reach production for configurations the plant cannot build. The rules are missing, or set to Show warning, which displays a message but does not stop publication; a HubSpot rule meant to bind belongs on Block publish.
The same scope carries different prices on different quotes. Either a deal matched two price book assignment rules and its owner chose, or a book assigned at deal creation outlived a change to company properties. HubSpot does not rerun price book assignment. The remedy is an assignment rule set in which every deal matches exactly one rule, plus a Super Admin override when a deal's circumstances change. Changing a deal's book removes the line items associated with the previous book, so the override belongs before the quote is built.
Line items added by automation ignore the negotiated price. The Add line item to deal workflow action does not apply pricing from the deal's price book, which applies only to lines added in the line items editor.
Quotes are accepted at prices that have since changed. The default expiration period is unset or outlasts the pricing it protects, and a quote accepted before its date stays live without countersignature or payment.
Configuration rules multiply faster than products. Each selection rule needs a counterpart, or each correction under validation reintroduces a violation: the mechanism is too weak for the catalogue, and the remedies are a stronger mechanism or fewer interacting options.
Boundaries of This Article
This article defines CPQ and the mechanisms that separate CPQ systems, without ranking products; HubSpot's tools are treated in HubSpot CPQ. Contract management, billing and revenue recognition sit downstream of the accepted quote and outside its scope.
Product facts are as documented in September 2026. HubSpot's CPQ overview, quote rule, price book and product library pages were updated between 21 and 24 September 2026, and its approval and quote setup pages earlier that month. The linked pages are authoritative over this text. Salesforce CPQ's rule types come from Salesforce's training material, because its help articles could not be retrieved for checking. SAP CPQ is described from SAP's training material, because its product page refused automated retrieval. SAP CPQ and Oracle CPQ are described only as far as those pages state.
The finding rests on documentation, not on testing each product against one catalogue, and the sample catalogue and deal exist only to make the arithmetic checkable. Which mechanism suffices for which kinds of catalogue, across real businesses, is a question this article has no data to answer.
Frequently Asked Questions
What is CPQ? Configure, price, quote: the three steps between a customer's requirement and a signed quote, which are configuring a valid combination of products, pricing it, and producing the quote document.
What is CPQ software? Software that holds the rules for those three steps: configuration rules that decide which combinations may be sold, price logic that decides what they cost, and quote templates carrying terms, expiry and approvals.
What is a CPQ? Shorthand for a CPQ system, one product holding configuration rules, price logic and quote templates; HubSpot, Salesforce, SAP and Oracle each document one.
What does CPQ stand for? Configure, price, quote, in order of dependency: a price is computed only for a valid configuration, and a quote issued only for an approved price.
What is Salesforce CPQ? A managed package on Salesforce with a rules-based configurator over SKU bundles and options. Salesforce no longer sells it to new customers and names Revenue Cloud Advanced as its successor.
What is SAP CPQ? SAP's cloud CPQ product, which SAP's training material describes as serving complex products and services, automating pricing, generating quotes and proposals, and integrating with CRM and ERP systems.
What is the best CPQ for custom products? No single product. Where options interact or the nominal set is too large to search, selection or constraint-based configuration fits; where a warning on the assembled quote suffices, a CRM-native tool does.
What is the best CPQ for enterprise sales? None for the category as a whole. The deciding questions are which system owns the product master, when configuration must act, and how many sequential approval levels a deal passes.
In Summary
CPQ stands for configure, price, quote: three problems with three owners, joined by dependency. Configuration can be measured before any software is seen, and four rules cut the sample catalogue from 108 combinations to 56. Pricing fails when two correct rules apply without stated precedence, as in the sample deal priced four defensible ways between $3,600 and $4,350 a month. Quoting controls expiry, approval and revision lineage.
CPQ systems differ in kind at the first letter, in when a rule acts and whether one rule holds in both directions. HubSpot's quote rules, like Salesforce CPQ's validation rules, warn or block once an invalid pair is on the quote. Salesforce CPQ's selection rules change the configuration at the pick, one direction per rule, with no undo. Written that way, the sample relation between dryer and controller takes three rules. Salesforce describes Revenue Cloud Advanced as constraint-based, and a constraint states that relation once. The question to settle before any demonstration is when a configuration rule has to act for this catalogue, and two hundred exported quotes, counted for invalid combinations and unranked prices, answer it.