SAP's configure-price-quote engine for complex enterprise product and pricing rules.
SAP CPQ is the configure-price-quote layer of SAP's sales portfolio, built to let reps assemble valid configurations of complex products, price them against governed rules, and generate quotes without engineering help. It handles deep product option logic, discounting guardrails, and approval routing, and connects to SAP's own CRM and ERP as well as Salesforce. Enterprises with intricate catalogs — industrial products, multi-line solution bundles, channel pricing — use it to keep quoting fast while pricing stays controlled.
Which of the capability map's modules SAP CPQ covers — each links to the module's own page, with every tool that supports it.
| Module | Phase | Depth | Note |
|---|---|---|---|
| Win the Deal | |||
| Product Configurator | Configure & Quote | Core | Rules-based configuration for large option matrices and dependent product logic |
| Pricing Calculation Engine | Configure & Quote | Core | Governed pricing with condition-based logic that can align with ERP pricing procedures |
| Advanced Approvals | Negotiate & Close | Supported | Discount thresholds and multi-step approval workflows on quotes |
Its pull is ecosystem gravity: for companies whose master data, pricing conditions, and order fulfillment already live in SAP ERP, quoting in SAP CPQ keeps the quote-to-order chain in one vendor's data model. Against Salesforce-native CPQs it competes on configuration depth and ERP continuity rather than on seller experience polish.
Mainly when your order management, pricing conditions, and product master already live in SAP ERP. Reusing that data avoids maintaining two pricing engines. If your GTM stack is Salesforce-first and your ERP integration is thin, a Salesforce-native or independent CPQ usually fits better.
It can model recurring charges and works alongside SAP Subscription Billing and BRIM for the downstream billing of consumption. The quote-time story for pure usage commits is weaker than in usage-native CPQs, so map your specific pricing mechanics before assuming coverage.
By overlap on the capability map — computed, not curated.