Subscription, Usage and Hybrid Pricing in Revenue Cloud
How pricing procedures, decision tables and billing schedules fit together.
Pricing is the design decision
How you charge decides how you build everything else in Revenue Cloud. The catalog, quote, order, asset and invoice all carry the pricing model you choose.
Most companies no longer sell one way. A single deal might mix a platform subscription, usage overage, a one-time setup fee and a price that steps up each year. Revenue Cloud is built for that kind of hybrid deal, but only if the pricing model is designed on purpose rather than added one exception at a time.
The building blocks
Pricing in Revenue Cloud is declarative. Instead of CPQ price rules and custom scripts, you combine a few standard pieces.
- Price books: Hold list prices, as in core Salesforce
- Price adjustments: Apply discounts, tiers and other changes to list price
- Context definitions: Tell the engine which quote, order or account data it can read
- Pricing procedures: Run the pricing steps in order, from list price to net price
- Decision tables: Look up values, such as a discount by region or segment, without code
On the back end, Usage Management and Rate Management handle consumption, and Revenue Cloud Billing turns all of it into billing schedules and invoices.
Source: Trailhead, Configure pricing for products
Five patterns and how to model them
- One-time. Typical example: Setup fee, hardware, training day. What to get right: Keep it off the subscription so renewals don't repeat it.
- Subscription. Typical example: Annual platform license. What to get right: Term length, billing frequency, and whether it renews automatically.
- Usage. Typical example: API calls, transactions, seats used. What to get right: Where usage data comes from, how it's rated, billed in arrears.
- Ramp. Typical example: Price or quantity steps up each year. What to get right: One deal with segments, so renewals and amendments see the whole ramp.
- Hybrid. Typical example: Subscription with included usage and overage. What to get right: Which piece carries the commitment, and which piece bills on actuals.
Revenue Cloud Billing can bill monthly, quarterly or annually, in advance or in arrears, on milestones, or on usage. It also adjusts billing schedules for ramp deals and creates new schedules automatically when an order is amended or cancelled.
Sources: Trailhead, Get started with Billing; Trailhead, Navigate the full billing lifecycle
Design tips before you build
- Start from the invoice. Ask Finance what the customer's invoice must show, then design backward to the quote.
- Name the commitment. For every hybrid offer, decide whether the customer commits to a subscription, a minimum spend, or nothing at all.
- Keep pricing data in decision tables. Regional prices and discount bands change often. Tables let your team update them without a release.
- Test the day-two cases. Price a mid-term upgrade, a ramp renewal and a cancellation before go-live, not just the first quote.
Need help modeling a complex pricing structure? Book a free consultation with Amwintech.
Salesforce, Revenue Cloud, Agentforce and Trailhead are trademarks of Salesforce, Inc.
Amwintech's Blog

