Usage-based Product Pricing Guidelines

Hello Champs!

Let me brief on Usage-based Product!

Quote and price your products based on predefined rates for future consumption of the product or service you’re selling.

The price scales alongside usage, reducing initial purchase barriers and driving higher revenue. You can configure your units of usage and setup different pricing rates based on usage volume.

Salesforce CPQ and Salesforce Billing let you manage usage-based products with either consumption schedules or price schedules.

PRICING GUIDELINES

• Products with consumption schedules can’t have price dimensions.
• Clicking Clone with Related on a product with consumption schedules won’t clone the consumption schedules on the cloned product.
• To use products with consumption schedules in Salesforce CPQ and Salesforce Billing, make sure both packages are on the same major release version, such as Summer ‘19.
• Quote lines with consumption schedules can have a quantity of only one. When amending or renewing, you can change the quantity from one to only zero.
• Products with consumption schedules don’t support renewal pricing.
• You can use the product consumption schedule object to associate multiple consumption schedules to the same product. However, each of these consumption schedules must have unique units of measure and matching attributes.
• Consumption rate billing terms must be greater than or equal to one month.
• Consumption rate billing terms must be less than or equal five years or 60 months.
• Usage processing orders can be negative.
• All of a schedule’s consumption rates must have unique usage processing orders.
• Consumption rate upper bounds aren’t inclusive. If you want your rate to evaluate up to 10 units of usage, set its upper bound to 11. The next consumption rate’s lower bound must equal the previous consumption rate’s upper bound.

• As of Salesforce CPQ Spring ‘20, if your org is set to allow inline edits, the upper bound, lower bound, and price fields can be edited in the quote line editor.