A large enterprise company offers flexible options for customers to lease or buy products. Before implementing Revenue Cloud, the company had a large product catalog to ensure that each product could be associated with the correct price to support both lease and buy use cases.Which Revenue Cloud feature should help the company rationalize its product catalog?
Answer(s): A
Salesforce Revenue Cloud introduces the Product Selling Model and Product Selling Model Option framework to help companies offer multiple purchase or subscription options for the same base product, reducing catalog sprawl. This approach is ideal for businesses that previously created multiple product records (e.g., separate SKUs for lease vs. buy) just to accommodate different pricing or selling logic.With selling models, you define whether a product is sold as a one-time purchase, subscription (e.g., monthly, annual), lease, or usage-based. You can then attach multiple Selling Model Options to a single product, each reflecting a specific commercial approach (e.g., Lease Monthly, Term Annual, One-Time).This allows the business to maintain a streamlined catalog while supporting diverse sales motions.Option B refers to the decomposition process and is more relevant for fulfillment than pricing.Option C (Multiple Price Books) enables regional or segmented pricing but doesn't solve the core problem of catalog sprawl due to multiple sales models.Exact Extracts from Salesforce Revenue Cloud Documents:Subscription Management Implementation Guide "Product Selling Models":"Selling Models reduce catalog complexity by allowing a single product to support multiple commercial options such as one-time, lease, or subscription."CPQ Implementation Guide "Product Configuration Best Practices":"Use selling model options to attach different billing or pricing terms to a single product record rather than duplicating products."
Subscription Management Implementation GuideSalesforce CPQ Implementation GuideRevenue Cloud Product Catalog Strategy Notes
A telecommunications customer currently subscribes to the Standard Data Plan (US$50/month). On October 15, halfway through their monthly billing cycle, they decide to upgrade to the Unlimited Data Plan ($100/month). The company's policy is to immediately apply the new plan's benefits and proportionally adjust the current month's billing.An administrator needs to accurately calculate the credit for the unused portion of the Standard Data Plan and then charge for the used portion of the Unlimited Data Plan in October.Which pricing element should the administrator use?
Answer(s): C
The Provision element is used in Salesforce Billing and Subscription Management to support mid- cycle changes and proration logic, which is exactly what is required in this scenario. When a customer changes their subscription partway through a billing cycle, Salesforce can use Provision elements to:Prorate credits for the unused portion of the original serviceCalculate the partial charge for the new service based on the remaining billing periodAccurately reflect the change in the invoice and subscription recordThis functionality is part of Amendments and Mid-Term Changes in Subscription Management and supports use cases like upgrades, downgrades, and plan switches.Option A (Derived Price) calculates pricing based on formulas or derived fields but doesn't handle time-based adjustments.Option B (Aggregate Price) is used when rolling up prices from multiple child components or bundles, not for mid-cycle adjustments.Exact Extracts from Salesforce Revenue Cloud Documents:Subscription Management Implementation Guide "Prorated Billing and Provisioning":"Use Provision pricing elements to handle partial-period charges and credits during plan changes or mid-term amendments."Billing Implementation Guide "Handling Amendments with Pro-ration":"Provision elements automate adjustments to billing based on service activation or termination dates within the billing period."
Salesforce Subscription Management Implementation GuideSalesforce Billing Implementation GuideRevenue Cloud Amendments and Proration Handling Documentation
A sales rep notices that while creating a quote, the Browse Products button isn't visible on the Quote Page Layout.What is the cause of the problem?
The Browse Products functionality is part of the Product Discovery experience in Salesforce Revenue Cloud. For a user to access and utilize this interface during quote creation, they must be assigned the Product Discovery User permission set. This permission set includes the necessary access to Product Discovery components, UI elements, and underlying Apex classes that support the Browse Products button on the quote page.According to the Salesforce Revenue Cloud Product Discovery documentation, failure to assign this permission set will result in the Browse Products button being hidden or inaccessible, even if the rest of the CPQ package is functional.Option A refers to the Product Configurator, which enables configuration of bundles and rules, but doesn't control the Browse Products experience.Option B is related to users who design product configuration rules -- not end users like sales reps.Exact Extracts from Salesforce Revenue Cloud Documents:CPQ Implementation Guide "Enabling Product Discovery":"Users must be assigned the Product Discovery User permission set to access the Browse Products button and use the Product Discovery experience on the quote page."Admin Guide "Setting up Product Discovery for Sales Users":"Add the Product Discovery permission set to ensure visibility of Browse Products and category-based browsing."
Salesforce CPQ Implementation GuideRevenue Cloud Product Discovery Setup GuideSalesforce Revenue Cloud Admin Permissions Reference
A Revenue Cloud Consultant recently implemented Revenue Cloud for a customer and wants to ensure successful adoption and maintenance.Which steps should the consultant take with the customer after go-live?
Post-go-live success in Revenue Cloud implementations hinges on knowledge transfer, user enablement, and documentation. According to Salesforce's Implementation Best Practices, consultants should conduct structured knowledge transfer sessions to walk through configuration decisions, key processes, and any customizations. This should be complemented with help documentation, training materials, and recorded walkthroughs to enable self-sufficiency.The goal is to ensure the client's internal admins and users understand:Product catalog structurePricing logicRenewal and amendment flowsInvoice and billing configurationsOption A reflects this industry standard and aligns with Salesforce's prescribed approach for post-go- live readiness.Option B (Slack support) is informal and not scalable or secure for enterprise implementations.Option C is unrealistic as a short-term expectation and doesn't guarantee the user's understanding of the specific implementation.Exact Extracts from Salesforce Revenue Cloud Documents:Salesforce Implementation Guide "Post-Go-Live Support and Enablement":"Conduct knowledge transfer sessions with client stakeholders, and provide recorded demos, configuration documentation, and a runbook for maintenance."Revenue Cloud Delivery Framework "Transition to Support":"A successful go-live includes detailed documentation, admin training, and clear handoff materials to ensure smooth transition to client ownership."
Salesforce Revenue Cloud Implementation GuideRevenue Cloud Partner Delivery FrameworkSalesforce Success Guide: Post-Go-Live Strategy
A company is offering a subscription service with a standard monthly price of US$200. The proration settings are as follows:Proration Period: MonthlyPeriod Boundary: Align to CalendarPartial Periods Allowed: YesA customer begins their subscription on March 20, 2021, and ends it on December 31, 2021.For the initial partial period (March 2031), which formula should the consultant use to calculate the proration multiplier?
In Salesforce Billing and Subscription Management, proration is applied when a customer begins or ends service mid-period. With Monthly Proration and Calendar-Aligned Boundaries, the system determines the correct prorated charge by calculating the proportion of the month the service is active.For a start date of March 20, the service is active from March 20 to March 31. The correct proration multiplier formula is:Number of remaining days in March / Total number of days in MarchThis calculates the billable fraction of the month and applies it to the monthly price. In March, there are 31 days, so the proration multiplier is:(31 - 20 + 1) / 31 = 12 / 31 0.3871This aligns with Salesforce's proration logic when "Partial Periods Allowed = Yes" and "Align to Calendar" is selected.Option B incorrectly calculates used days, not remaining days.Option C applies to Annual Proration, not monthly, and is not relevant here.Exact Extracts from Salesforce Revenue Cloud Documents:Subscription Management Implementation Guide "Proration Settings":"For calendar-aligned billing periods, the proration multiplier is calculated as (remaining days in period / total days in period)."Billing Implementation Guide "Partial Period Calculation Examples":"When partial periods are enabled, proration applies from service start to end of period based on remaining days."
Salesforce Subscription Management Implementation GuideSalesforce Billing Implementation GuideProration and Billing Period Calculations Guide
Post your Comments and Discuss Salesforce Rev-Con-201 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Rev-Con-201 content, but please register or login to continue.