Pricing·Reference·6 min·Updated 2026-10-05
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.
Business requirement
A setup fee at one price below a headcount threshold and another above it, plus per-unit adders, driven by a quantity that is not the seat count.
Why it is not trivial
Two different quantities drive the price and they are easy to conflate. And every threshold expressed as a decision table consumes procedure capacity that is finite.
Recommended architecture
A decision table for the threshold — it is a genuine condition — and the flat adders on the price book entry. Drive the scaling element from the field that actually carries the count, not from the one whose name sounds right.
Salesforce components
Select one to open its detail.
Flow
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
Name the driving quantity explicitly on the product and write down which one drives which element. This is the detail that is re-derived painfully a year later.
Watch out
- A decision table for a price with no condition is pure waste against the element ceiling. Flat prices belong on the price book entry.
- Editing the procedure deactivates it.
Alternatives
Expressing thresholds as separate products removes the decision table and multiplies the catalog. Reasonable for two tiers, unmanageable at five.