G2

Travis W.

Digital Marketing Manager

Enterprise (> 1000 emp.)

10/17/2026

"I support it because pricing logic is now centralized, and offers no reliance on memory"

4.5/5

What do you like best about SAP CPQ?

Product catalog and pricing rules are in SAP CPQ and exposed through REST APIs by configuration engine, which are then called by our CRM when the Opportunity is in the proposal stage. The final quote is posted back in JSON along with a PDF. The authentication is based on OAuth 2.0 and a service key obtained from SAP BTP. Price lists are synced once a day from S/4HANA. No custom connector. The turnaround of quotes decreased from 3 days to less than 4 hours. The number of pricing mistakes in quotes fell from nine percent to less than one, and the time needed to get a proposal to closing was reduced by about a week in two quarters. Review collected by and hosted on G2.com.

What do you dislike about SAP CPQ?

I have a problem with variant rules. The first product model I created had some dependency issues and the configuration provided different options until I divided the rules per product family and verified each one by applying real quote scenarios generated by sales. Review collected by and hosted on G2.com.

What problems is SAP CPQ solving and how is that benefiting you?

By reducing the time required from creating a quote to sending it to us to hours and eliminating pricing errors from reaching our customer in the field, SAP CPQ saved us many days. I would have created campaign offers in slides, and then depend on sales ops to manually enter the pricing of the offer. 6 emails for each custom request. I got quotes from old price lists and I had no idea until a prospect sent me a quote that nobody on our side had ratified. Review collected by and hosted on G2.com.