SAP CPQ

What is SAP CPQ?

SAP CPQ is SAP’s configure, price, quote platform for complex B2B products: sales reps configure valid product combinations step by step, pricing rules and discount approvals fire automatically, and branded quotes generate in minutes instead of hours. The official product page and the SAP CPQ documentation cover the full capability set; the platform connects natively to SAP Sales Cloud V2 and SAP ERP.

Spadoom implements SAP CPQ as an SAP Gold Partner for manufacturers and technology companies across Switzerland, Germany, Austria and Italy. The rest of this page covers what we deliver, what a CPQ project changed for one of our customers, and how we model product rules before the first quote goes out.

What Spadoom delivers

We implement SAP CPQ for manufacturers and technology companies across DACH and Southern Europe. Our clients sell complex products: industrial equipment, medical devices, configurable machinery, multi-component systems. Their product catalogues have hundreds or thousands of valid combinations. Pricing depends on volume, customer tier, region and contract terms.

As an SAP Gold Partner, we bring certified consultants who have configured CPQ for real product lines, not demo environments. Every project follows SAP Activate methodology: five phases from discovery through hyper-care. We adapt the framework for CPQ-specific challenges like rule modelling, pricing migration and quote template design.

The starting point is usually the same. Reps pull data from several systems, check configurations by memory or by asking a colleague, and chase approvals by email. CPQ moves those checks into the system, so the quote is correct when it is created rather than after someone reviews it.

The ERP seam: where CPQ projects break

A quote is only as good as the price and material data behind it. Pricing conditions, material masters, variant configuration and the creation of the sales order all live in the ERP. Most CPQ projects that disappoint do not fail inside CPQ. They fail at the handover: the accepted quote that will not post as an order, the price CPQ cannot resolve, the configuration the plant cannot build.

Spadoom delivers SAP S/4HANA Public Cloud and the CX side (Sales Cloud V2, CPQ, Commerce) with one team. The quote-to-order handover therefore has one owner, and it is tested with real orders before go-live. If the ERP side is still ahead of you, the ERP and CX transformation guide shows how we sequence both, and SAP BTP covers the extensions that neither standard product handles.

A result from one of our CPQ projects

BDTronic builds dispensing, plasma treatment and heating systems. Every order is a custom configuration from a catalogue of more than 1,400 components, and the compatibility rules filled a 60-page internal document. Before CPQ, reps built quotes in spreadsheets.

After the SAP CPQ implementation, BDTronic reports:

• 70% shorter quote turnaround.
• Zero configuration errors in quotes, because invalid combinations can no longer be built.
• Three times as many quotes per rep.

Your numbers depend on your catalogue, your pricing logic and how clean your ERP data is. Want to model a scenario for your team? Run it in our ROI calculator.

The product configuration challenge

Getting product rules right is the hardest part of any CPQ implementation. Rules that are too rigid frustrate sales reps. Rules that are too loose create orders for impossible configurations. Both cost money.

We run structured workshops before a single rule is coded. Our process:

1. Catalogue mapping. We document every product family, option set and dependency. We identify which combinations are valid, which require engineering review and which are impossible.

2. Rule modelling. We translate business logic into CPQ configuration rules. This includes constraint rules (what can combine with what), recommendation rules (what should combine) and exclusion rules (what must never combine).

3. Edge case testing. We pull 50–100 historical quotes, including the messy ones, and run them through the new configuration engine. If the system produces a different result than what was sold, we investigate. Sometimes the old quote was wrong. Sometimes our rules need adjustment.

4. Sales team validation. Reps test the configuration flow before go-live. They try to break it. They flag scenarios we missed. This front-loaded investment pays back immediately, because you do not spend the first months of production fixing rules.

Multi-level BOMs get special attention. A parent product with three levels of dependent sub-assemblies requires careful dependency mapping. We model these as hierarchical configuration trees where each level inherits constraints from the level above. The result: a rep selects a base unit, and the system narrows available options at every subsequent level automatically.

Dynamic pricing and discount management

Pricing in CPQ goes far beyond a price list. Most B2B companies we work with have at least four pricing dimensions running simultaneously.

Volume tiers. For example: buy 10, pay list price. Buy 100, get 12% off. Buy 1,000, trigger a custom pricing request. CPQ applies the right tier automatically based on line quantities and total order value.

Customer-specific pricing. Key accounts have negotiated rates. Distributor tiers carry different margins. Regional pricing reflects local market conditions. CPQ pulls customer-specific price books and applies them without the rep needing to look anything up.

Approval workflows with teeth. For example, discounts above 15% go to the regional sales director, above 25% to the VP of Sales, above 35% to the CFO. These thresholds are configurable per product line, per region and per customer segment. The system enforces them, with no exceptions and no workarounds.

Margin protection. CPQ calculates margin as the rep builds the quote. Floor prices prevent reps from going below cost. Warning thresholds flag deals that are technically valid but commercially questionable. Finance sees the margin impact before the quote leaves the building.

Currency conversion, tax calculation and Incoterms handling run automatically based on the ship-to location. For companies selling across Switzerland, the EU and beyond, this removes an entire category of quoting errors.

Quote-to-order automation

The quote itself is the output that customers see. It needs to look right and contain the right information.

Branded PDF generation. CPQ produces professional quote documents from templates. Product images, line item details, terms and conditions and pricing breakdowns are assembled automatically. No more copying data into Word or PowerPoint. Templates are configurable per product line, per region and per language.

E-signature integration. DocuSign, Adobe Sign and other providers connect directly to the CPQ workflow. The customer receives the quote, reviews it, signs digitally, and the acceptance flows back into the system. No printed paper. No scanned PDFs. No “I’ll send it Monday.”

ERP order creation. This is where CPQ pays for itself. When a quote is accepted, CPQ creates the sales order in SAP ERP or S/4HANA automatically. Bill of materials, pricing, delivery dates and payment terms are transferred without manual re-entry. The order is correct because it was correct in CPQ. No one types it again.

For companies running SAP Commerce alongside CPQ, the same configuration engine can power self-service quoting on the B2B storefront. Customers configure products, see pricing and request quotes through the same rules engine that sales reps use internally.

Integration with SAP Sales Cloud V2

CPQ works best when it is embedded in the sales workflow, not bolted on as a separate tool. In SAP Sales Cloud V2, the integration is native.

Embedded launch. Reps open CPQ directly from the opportunity in Sales Cloud V2. No separate login. No context switching. The customer data, opportunity details and account pricing carry over automatically.

Bidirectional sync. Quotes created in CPQ appear as quote records in Sales Cloud V2. Status changes flow both ways. When a quote is approved, accepted or rejected, the opportunity reflects it immediately. Activity history stays unified.

Pipeline accuracy. Because quotes carry real configuration and pricing data, pipeline values become trustworthy. Forecast calls stop being guessing games. Managers see what was actually quoted, not what a rep estimated.

Single source of truth. No more version conflicts between the CRM and the quoting tool. The quote in CPQ is the quote in Sales Cloud V2 is the order in ERP. One data lineage from opportunity to invoice.

We configure this end-to-end integration as standard on every project. The quote-to-order flow should require zero manual steps from the rep.

Industry use cases

SAP CPQ serves any business that sells configurable products. These are the industries where the need shows up most often.

Manufacturing. Industrial equipment with modular assemblies, optional accessories and region-specific compliance requirements. Configuration rules prevent invalid combinations. Pricing reflects volume commitments and framework agreements. Quote-to-order automation closes the gap between “deal won” and “order in ERP.”

High-tech. Software and hardware bundles with subscription pricing, perpetual licences, maintenance add-ons and upgrade paths. CPQ handles mixed billing models (one-time and recurring) in a single quote. Renewal quoting pulls current contract terms automatically.

Medical devices. Regulated products with strict configuration constraints. Certain components require specific certifications in certain markets. CPQ enforces regulatory rules alongside commercial rules. Audit trails document every configuration decision for compliance reviews.

Automotive (aftermarket and fleet). Vehicle configuration, parts kitting and fleet pricing with dealer-tier discounts. Multi-currency, multi-country pricing for European distribution networks. CPQ replaces the 47-tab Excel file that no one trusts but everyone uses.

Pricing and licensing

SAP CPQ is licensed as a subscription per user. The exact price depends on volume, contract length and bundling with other SAP CX products, and SAP sets it in the licence negotiation. We do not publish list prices that would be out of date by the time you read them.

The larger cost question is usually integration. SAP CPQ connects to SAP Sales Cloud V2 and S/4HANA through supported APIs and preconfigured SAP Integration Suite content. That removes a lot of custom work, but SAP-to-SAP integration still needs mapping, error handling and monitoring. We scope it before anyone compares licence prices, and we include it in the estimate.

Spadoom provides a detailed cost estimate after the discovery phase. No surprises. No scope creep.

What good looks like

A successful CPQ deployment produces outcomes you can point to in a board meeting.

• More quotes per rep. The same team produces more quotes because configuration and pricing checks no longer need a second person.
• Fewer order corrections. Configuration rules and automated pricing prevent the manual mistakes that end up as rework and credit notes.
• Less dead time in the sales cycle. Faster quotes, parallel approvals and automatic ERP order creation remove waiting from the process.
• Reps sell instead of administering spreadsheets. Time spent on quote assembly goes back to customers.
• Finance gets visibility. Margin data, discount tracking and approval audit trails replace the quarterly “what happened?” analysis.

We agree the measures and the baseline with you before go-live and track them at 30, 90 and 180 days. If they are not moving in the right direction, we adjust. That is what the hyper-care phase in our methodology is for.