Pricing
From a context to a net price
Pricing procedures, expression sets, decision tables, adjustments
Pricing in Revenue Cloud is a procedure — an ordered list of steps, expressed as an expression set — that reads a context definition and produces a net price. Decision tables and adjustment schedules are what it calls along the way.
The single decision that keeps a catalog maintainable is knowing when not to use a decision table. A table is for a condition or a tier. A flat price belongs on the price book entry. Tables added by reflex are what fill a procedure up to its ceiling.
The objects
Select any object to open its detail — purpose, the fields that matter, what it relates to, and what to watch for.
The architecture
Scroll the diagram sideways
The rule that keeps a catalog maintainable: a decision table only when there is a condition or a tier. A flat price belongs on the PricebookEntry. Decision tables added by reflex are what fills a procedure up to its element ceiling.
And the procedure that runs is the compiled _Auto version, not the source you edit.
Implementation guides
Solution patterns
Included allowances and overage
Express “the first N hours are included, beyond that you pay” natively — and find out why only one of your allowances applies.
PricingScaling past the procedure ceiling
What to do when one pricing procedure can no longer hold the logic of every offer.
Use cases
Tiered setup fees and per-seat adders
A setup fee that steps at a threshold, plus adders that scale with a count — without filling the pricing procedure.
MigrationMoving pricing configuration between orgs
Why a pricing procedure that works in one org returns nothing in the next, and what has to travel together.