A high-tech company offers cloud storage services and wants to define different rates for API calls based on customers' usage patterns.
How should a consultant set up this requirement?
Use base card entries
Use attribute rate entries
Use tier rate entries
Comprehensive and Detailed Explanation From Exact Extract:
Salesforce Billing and Subscription Management support multiple usage-based pricing (UBP) models.
From the Subscription Management and Billing Implementation Guides:
“Attribute rate entries enable pricing based on characteristics of usage events, including call type, region, or customer usage behavior.”
“Use attribute rate entries when pricing varies based on usage attributes and patterns, not volume alone.”
This fits the requirement of applying different rates to API calls depending on how customers use the service.
Why other options are incorrect:
Base card entries: Apply a flat rate.
Tier rate entries: Apply rates based on volume tiers, not usage attributes.
Submit