Pricing is where many sales teams quietly bleed money. Not through one big mistake, but through dozens of small ones — a missing adjustment here, a forgotten tier there, a special rate someone applied by hand and someone else forgot. Salesforce CPQ has a tool built precisely to stop that slow leak: the price rule.
Let me walk you through it the way I’d want a beginner to learn it — calmly, and without the jargon doing the heavy lifting.
What a price rule does
A price rule automatically adjusts pricing on a quote based on conditions you define. When a certain product is present, or a quantity crosses a threshold, or a particular combination appears, the price rule steps in and sets or changes a value — and it does it consistently, every single time, without anyone remembering to.
Think of common situations: “If the customer buys the platform and the analytics add-on, give the add-on a special rate.” Or “If total quantity exceeds 100, apply a different unit price.” Or “Populate this field so a discount schedule kicks in.” A price rule encodes that logic once so it never depends on a rep’s memory.
The result is pricing that responds to the shape of the deal — dynamic, but controlled.
The anatomy: conditions and actions
Like product rules, price rules are built from two core ideas, and understanding this pair is most of the battle.
A price condition is the “when.” It examines the quote or a quote line and decides whether the rule should fire. “When the quote contains Product X.” “When quantity is greater than 50.” If the condition is true, the rule proceeds.
A price action is the “then.” It changes a value — setting a price, writing to a field, applying an adjustment. The action is what actually moves the number.
There’s also the matter of when in the calculation the rule runs. CPQ calculates prices in phases (often described as evaluation events like On Initialization, Before Calculate, On Calculate, After Calculate). Choosing the right phase is how you make sure your rule fires at the right moment — before or after other pricing has been applied. As a beginner, you don’t need to memorize every event; just know that timing is a setting, and getting it right is part of building a clean rule.
A price rule turns a pricing policy that used to live in someone’s head into logic the system applies automatically — the same way, on every quote, forever.
How price rules differ from product rules
This is the distinction that trips up almost every newcomer, so let me make it sharp.
Product rules govern configuration — what can be on the quote. Can these options coexist? Is a required component present? Is this combination valid? They never touch the price.
Price rules govern pricing — what it costs. Given what’s on the quote, what should the numbers be? They never decide whether a configuration is valid.
A simple way to hold it in mind: product rules answer “Is this allowed?” Price rules answer “What’s the price?” They share a similar structure — conditions and actions — which is exactly why they look alike. But they work on different parts of the deal. If you’d like to revisit the configuration side, it’s covered in CPQ Product Rules.
Price rules and the bigger pricing picture
Price rules are powerful, but they’re not the only way prices get set in CPQ. List prices come from price book entries. Quantity-based pricing often comes from discount schedules. Customer-specific rates can come from contracted prices carried over from past deals. Price rules sit on top of all of this, handling the dynamic, conditional adjustments the other mechanisms can’t express on their own.
So before you reach for a price rule, it’s worth asking: is there a simpler, built-in mechanism that already does this? Sometimes a discount schedule or a list price change is the cleaner answer, and the price rule should be reserved for genuinely conditional logic. For the wider view of how pricing fits together on the platform, Pricing in Revenue Cloud is a helpful companion.
A beginner’s path to building one
Start with a single, clear policy you can describe in one sentence: “When the analytics add-on is on the quote with the platform, its unit price should be 200.” Then build it in three small moves.
First, write the condition that detects the situation. Second, write the action that sets the price. Third, pick the evaluation event so it fires at the right time, and test it in the Quote Line Editor — adding the products and watching the price land correctly.
One working rule, tested with your own eyes, teaches more than any diagram. Then you build the next one. This is craft learned by repetition, and small details — the right condition, the right timing — are what separate pricing that works from pricing that almost works.
Where this leaves you
With product rules keeping configurations valid and price rules keeping numbers correct, the Quote Line Editor becomes genuinely trustworthy. The rep configures, the system prices, and the totals are right by design. The last layer is putting deliberate, controlled discounts on top of all of it.
Your next step
Round out your pricing knowledge:
Or return to the full CPQ series.