Your sales reps spend two hours building a quote for a configurable product. They manually transcribe options from the ERP catalogue, recalculate discounts by hand, and send a PDF with no margin validation. Three days later, the customer still hasn’t received a response.
That is the clearest signal that a CPQ (Configure, Price, Quote) is justified.
Your ERP’s native quoting module handles straightforward cases. As soon as your offerings involve conditional configuration rules, matrix pricing, or differentiated discounts by customer segment, it reaches its limits. A CPQ fills exactly that gap — provided it is properly integrated with your ERP and CRM.
This guide explains what CPQ is, why it is not included by default in ERP systems, how to design the key data flows, what ROI to expect, and provides an overview of the leading solutions in 2026.
What Is CPQ and How Does It Differ from an ERP Quoting Module?
Definition: Configure, Price, Quote
CPQ is software that guides sales teams through three steps:
- Configure: select compatible options for a product or service, applying business rules that prevent impossible or unprofitable configurations.
- Price: automatically apply the appropriate pricing grid based on customer segment, volume, region, currency, or validity date, with margin control.
- Quote: generate a structured commercial document with professional presentation, branding, a configuration summary, and increasingly, integrated e-signature.
The goal is to reduce the quoting cycle from several days to a few hours, while eliminating configuration errors and margin overruns.
What an ERP’s Native Quoting Module Cannot Do Alone
The quoting module built into an ERP (Dynamics 365, SAP SD, Sage, Odoo) is designed for standard product sales. It handles item lists, quantities, simple discounts, and accounting validation.
It shows its limits as soon as:
- Products are configurable (mutually exclusive options, dependencies between components).
- Discount rules are complex (cross-conditional discounts, contract pricing by customer, volume-tiered pricing).
- Sales teams work in the CRM, not the ERP.
- Quotes need a professional presentation with a guided configurator or branded PDF.
- E-signature and open-tracking are needed to accelerate closing.
Use Cases That Justify CPQ
CPQ is relevant in at least one of these contexts:
- Industrial manufacturers with complex product ranges (machinery, custom equipment, configurable parts).
- Software vendors with variable subscription packaging (licences, tiers, add-ons, durations).
- Services companies with modular offerings (time-and-material, retainers, packages with options).
- B2B distributors with thousands of SKUs, contract discounts, and segmented promotions.
The simple rule: if your sales reps regularly spend more than two hours on a quote, or if the configuration error rate exceeds 5%, the ROI of a CPQ is probable.
CPQ, ERP, CRM: Who Does What in the Order-to-Cash Cycle?
| O2C Stage | Primary Tool |
|---|---|
| Opportunity management | CRM |
| Configuration and quoting | CPQ |
| Order and inventory | ERP |
| Production / delivery | ERP |
| Invoicing and accounting | ERP |
| Post-sale customer service | CRM / ERP |
CPQ sits between the CRM (which manages the opportunity) and the ERP (which manages the order). It is not designed to replace either. It orchestrates the handoff from quote to order, with all the business controls that neither CRM nor ERP can enforce on their own.
The Measurable Benefits of CPQ for Sales Teams
Reduction in Quote Generation Time
This is the most direct and fastest-to-measure benefit. According to Aberdeen Group research on commercial organisations using CPQ, the average sales cycle is 3.42 months compared to 4.68 months for organisations without CPQ (Aberdeen Group, Simplifying Complex Sales Processes with CPQ) — a reduction of approximately 27%.
This gain comes from two mechanisms: less preparation time per quote (the configurator guides the rep), and fewer back-and-forth corrections for configuration errors detected during negotiation.
Elimination of Configuration and Pricing Errors
In an industrial manufacturing project, an incorrect quote translates to an order that cannot be fulfilled, pushed-out lead times, and correction costs that erode margin. CPQ applies compatibility rules in real time, making it structurally impossible to order invalid configurations.
On the pricing side, CPQ controls margins before a quote is sent: if the granted discount pushes margin below a defined threshold, the quote is automatically submitted for management approval. This “pricing guardrails” mechanism is often cited as the most significant margin lever of any CPQ project.
Proposal Volume and Sales Cycle
Aberdeen Group also reports that teams using CPQ generate an average of 20.9 proposals per sales rep per month versus 14 for teams without CPQ — a 49% increase in proposal volume. This productivity gain enables teams to handle more opportunities without increasing headcount.
Improved Conversion via Guided Selling
Modern CPQ platforms include recommendation engines (cross-sell, up-sell) that automatically suggest complementary options based on customer profile and chosen configurations. These recommendations are based on order history and compatibility rules, not on individual rep memory.
Customer Experience: Professional Quotes and Integrated Signing
A quote generated by CPQ presents the full configuration, pricing detail, commercial terms, and delivery timelines in a structured, branded PDF. Most CPQ platforms integrate natively with e-signature solutions (DocuSign, Adobe Sign, PandaDoc), reducing the time between quote delivery and signed order.
CPQ and ERP Integration Architecture: Key Data Flows
CPQ-ERP integration is often more complex than CPQ-CRM integration. It involves critical transactional data: product catalogue, pricing rules, stock levels, orders.
Flow 1: Product Catalogue and Configuration Rules (ERP to CPQ)
The ERP is the master repository for items: bills of materials, components, substitution rules. CPQ must receive this data in real time or via scheduled synchronisations to display a configurator consistent with the actual catalogue state.
The classic pitfall: launching CPQ before cleaning up the product catalogue in the ERP. If item data is inconsistent in the ERP, the CPQ configurator reflects those inconsistencies, and generated quotes are wrong from the start.
Flow 2: Pricing and Discounts (ERP to CPQ, with Margin Logic)
Pricing grids often live in the ERP (price lists, commercial conditions by customer, contract discounts). CPQ must leverage them while applying its own margin rules. Governance of the “source of truth” on pricing is the trickiest question to resolve during a CPQ project: who can modify a price, in which system, with what approval?
Flow 3: Quote-to-Order Conversion (CPQ to ERP)
When a CPQ quote is accepted and signed, it must become an order in the ERP, with all configuration details, quantities, validated prices, and delivery terms. This flow is the most critical and most frequently underestimated. You need to define precisely which CPQ quote fields map to which ERP order fields, and how edge cases are handled (partially accepted quote, post-signature amendments).
Flow 4: Stock Availability and Lead Times (ERP to CPQ, Real-Time or Deferred)
For manufacturing or distribution companies, sales reps need to know whether the components of a configuration are available and what the delivery lead time is before sending a quote. This flow requires a real-time or near-real-time connection between ERP and CPQ, imposing significant architectural constraints.
Flow 5: Customer Data and Order History (CRM/ERP to CPQ)
CPQ needs the customer profile (segment, contract terms, discount history) to apply the right prices and configuration rules. This data comes from both the CRM (commercial information) and the ERP (transactional history). In practice, the CRM typically acts as proxy: ERP customer data is replicated into the CRM, and CPQ only queries the CRM.
Architecture Recommendations
Three approaches are available for connecting CPQ and ERP:
- Native connectors: available when both systems come from the same vendor (SAP CPQ with S/4HANA, Salesforce Revenue Cloud with Salesforce CRM). Simplified maintenance, but limited flexibility.
- iPaaS middleware: platforms like MuleSoft, Boomi, Make, or Zapier Enterprise connect CPQ and ERP without heavy custom development. Intermediate cost, high flexibility. This is the most common approach for best-of-breed configurations.
- Custom REST API development: relevant when flows are highly specific and technical teams master both systems’ APIs. Higher initial cost, but total autonomy.
CPQ Solution Comparison 2026
| Solution | Target Size | Native ERP | Compatible CRM | Strengths | Weaknesses |
|---|---|---|---|---|---|
| Salesforce Revenue Cloud | Mid-market, Enterprise | Salesforce ERP / external ERP | Salesforce CRM | Leader for subscriptions/SaaS, Revenue Operations | High price, implementation complexity |
| SAP CPQ (ex-Callidus) | Enterprise, industry | SAP S/4HANA native | SAP Sales Cloud, Salesforce | Native S/4HANA integration, robustness | Ageing UI, licence costs |
| Oracle CPQ | Enterprise, manufacturing | Oracle Fusion native | Oracle CX, Salesforce | Strong in manufacturing, 3D configurator | Complexity, Oracle ecosystem dependency |
| Conga CPQ | Mid-market | Agnostic | Salesforce, Dynamics | Large install base, advanced business rules | Weaker outside Salesforce |
| DealHub | SMB, Mid-market | Agnostic | Salesforce, HubSpot, Dynamics | Modern UX, fast implementation, transparent pricing | Less mature for highly complex configurations |
| Odoo (Sales + configurator) | SMB | Odoo native | Odoo CRM native | Integrated, low TCO, easy to start | Limited for advanced configuration rules |
Salesforce Revenue Cloud
Formerly Salesforce CPQ, Revenue Cloud is the reference solution for companies selling subscription-based, licence, or SaaS service offerings. Its native integration with Salesforce CRM is its primary asset. Connection with third-party ERPs (SAP, Oracle, NetSuite) requires middleware.
SAP CPQ
The natural choice for customers already running SAP S/4HANA. Integration is native via SAP Integration Suite, reducing architecture costs. Particularly well-suited to industrial companies with complex configurable product ranges and strict margin approval processes.
Oracle Configure, Price, Quote
Integrated into Oracle Fusion Cloud, strong in manufacturing with its 3D visual configurator inherited from the Configurator suite. Well-suited to large enterprises with custom manufacturing processes. Connection with non-Oracle CRMs is possible but requires significant integration effort.
Conga CPQ
An ERP-agnostic best-of-breed solution with a large install base across Salesforce ecosystems. Its business rules engines are among the most flexible in the market. Particularly suited to companies with highly granular pricing conditions (discounts by account, segment, region, and period).
DealHub
A modern challenger positioned for the mid-market. Its user interface is recognised for rapid adoption by sales teams, reducing training costs and resistance. Compatible with the main CRMs (Salesforce, HubSpot, Dynamics 365). Less suited to very complex product configurations with hundreds of compatibility rules.
Odoo (Sales Module and Configurator)
For SMBs already on Odoo, the integrated sales module with the product configurator extension is a coherent option. The configurator remains limited to simpler cases, but TCO is significantly lower than a dedicated CPQ. This is a good starting point, with a possible migration to a best-of-breed CPQ as needs evolve.
Choosing Between Native ERP CPQ and Best-of-Breed CPQ
The Case for Native CPQ
- Simplified integration: data flows with the ERP are pre-configured, no middleware to maintain.
- Reduced TCO: a single vendor licence, fewer technical layers.
- Progressive ramp-up: activate features incrementally without changing systems.
- Simpler governance: a single catalogue and pricing data repository.
This is the right option when products are relatively standard, quote volume is moderate, and the ERP in place is SAP, Oracle, or Odoo.
The Case for Best-of-Breed CPQ
- Advanced functionality: more powerful rules engines, visual configurators, algorithmic guided selling.
- Superior UX: interface designed for sales reps, not accountants.
- Business rule flexibility: best-of-breed CPQ can model discount and configuration rules that native modules cannot express.
- CRM compatibility: if the CRM is not from the ERP vendor, a best-of-breed CPQ integrates in both directions.
Decision Criteria
Ask yourself these four questions:
- Quote volume: fewer than 50 complex quotes per month → native module sufficient. Beyond that → dedicated CPQ.
- Configuration complexity: products with more than 10 interdependent options → best-of-breed CPQ.
- Existing CRM stack: if the CRM is Salesforce, HubSpot, or Dynamics 365, a best-of-breed CPQ integrates better than a native ERP module.
- Budget: SMB CPQ (DealHub, Odoo): £25,000 to £65,000. Mid-market/Enterprise CPQ (Salesforce Revenue Cloud, SAP CPQ, Oracle): £125,000 to £400,000 and above.
5 Mistakes to Avoid in a CPQ Project
1. Failing to involve sales reps in configuration rule design. CPQ is a sales tool. If rules are defined solely by IT or operations, the configurator will not reflect the reality of sales cycles. Sales reps need to be able to express exceptions, understand the logic, and validate edge cases.
2. Launching CPQ before cleaning up the product catalogue in the ERP. This is the most common and most costly mistake. If the ERP catalogue contains duplicates, obsolete references, or inconsistent prices, CPQ will import them and reproduce them in every quote. Product data governance is an absolute prerequisite.
3. Underestimating the complexity of discount and margin rules. Pricing rules in B2B companies are often the result of years of commercial negotiations. Documenting them, modelling them in CPQ, and validating them with sales and finance teams takes far longer than anticipated.
4. Trying to automate everything at once. The winning approach: start with the 20% of configurations that represent 80% of quote volume. Put CPQ into production on that limited scope, measure results, then expand progressively.
5. Neglecting order management team training. The quote-to-order conversion involves order management teams who enter orders in the ERP. If they do not understand how CPQ structures quotes and which fields map to which ERP fields, data entry errors multiply at the junction of the two systems.
CPQ Project ROI: How to Calculate It
The CPQ business case rests on four measurable levers.
Lever 1: Commercial Time Savings on Quoting
Formula: (Average time before CPQ − Average time after CPQ) × Number of quotes per year × Hourly cost of a sales rep
Example: 20 sales reps, 5 quotes per week, 4 hours per quote before CPQ, 1 hour after CPQ. Loaded hourly cost: £65.
Annual gain: 20 × 5 × 52 × 3 × 65 = £1,014,000 in liberated time, which sales reps can reinvest in working more opportunities.
Lever 2: Reduction in Configuration Errors
Formula: Current error rate × Quote volume × Average cost of an error (correction, delay, commercial gesture)
In manufacturing, a configuration error detected in the production phase can cost £5,000 to £50,000 depending on product complexity. Reducing this rate by half represents a significant and directly measurable gain on margin.
Lever 3: Additional Margin via Cross-Sell and Discount Control
Guided selling generates recommendations for complementary products. Discount control prevents margin overruns. These two effects are harder to isolate statistically, but they are real and measurable on a before/after CPQ quote cohort.
Lever 4: Closing Acceleration
A quote sent faster, with integrated e-signature, reduces the time between proposal and signed order. On an average three-month sales cycle, cutting this delay by two weeks frees up commercial capacity for subsequent quarters.
Simplified Business Case Example
| Parameter | Value |
|---|---|
| Number of sales reps | 20 |
| Complex quotes per week per rep | 5 |
| Average time per quote (before) | 4 hours |
| Average time per quote (after CPQ) | 1 hour |
| Loaded hourly cost | £65 |
| Annual gain on quoting time | £1,014,000 |
| CPQ project budget (mid-market, mid-range solution) | £125,000 |
| Return on investment | Under 2 months |
This calculation does not yet value error reduction, closing acceleration, or additional margin from guided selling. In practice, full ROI is typically achieved within 6 to 12 months.
Before launching a CPQ RFP, two complementary reads will help you structure your requirements:
- Our guide on CRM-ERP integration: the data flow architectures between these systems directly condition the feasibility of a CPQ integration.
- Our comparison of iPaaS platforms for connecting ERP applications: MuleSoft, Boomi, Make and alternatives, with selection criteria tailored to your context.
