A CPQ pricing waterfall is the ordered sequence of adjustments between list price and the number the customer sees. If you cannot draw it, the engine will invent one for you.
A CPQ pricing waterfall is the ordered path from list or cost to net price: contracted prices, discounts, promotions, partner adjustments, and approvals. Salesforce CPQ, Oracle CPQ, and SAP CPQ all implement a waterfall. The consulting job is to make that order explicit so sales, finance, and audit see the same math.
Names change by vendor. The order should not be a surprise.
Salesforce CPQ encodes the waterfall with price books, price rules, discount schedules, contracted prices, and additional discount fields. Teams get into trouble when a QCP script inserts an invisible step. If a seller cannot explain a line’s net price from the Quote Line Editor, the waterfall is lying.
Finance reports a margin the quote UI cannot reproduce. Two sellers get different nets for the same SKU. A promotion stacks on a partner discount that was already supposed to be exclusive. Those are design bugs, not user-training problems.
We write the waterfall on one page with finance before configuration starts. Then we map each step to a native rule. Custom code is a last resort and must print its adjustment on the line so audit can see it.
It is the ordered set of price adjustments from a starting price to the net price on the quote. Order matters. Two engines with the same discounts will produce different nets if the sequence differs.
Yes. Price books, contracted prices, price rules, discount schedules, and additional discounts form the waterfall. Custom QCP can add steps. Those extra steps should be visible on the quote line.
Finance owns the policy. Sales owns the exception path. CPQ configuration encodes both. If only IT owns it, the next promotion will be hardcoded.
