A customer wants to change specific line items of the order after it has been submitted but before it has been fulfilled. The system administrator has granted permissions to allow the order management team to make this change, but they are unable to do so.What is the reason for this issue?
Answer(s): B
Salesforce Billing Implementation Guide "Order Activation" section:"Once an order is activated, it is considered finalized and cannot be modified directly. Activated orders are used to generate invoices, fulfillments, and billing schedules. Any required changes must be made through amendments or new orders."Salesforce CPQ Implementation Guide "Orders and Contracts" section:"After an order is activated, the order lines become read-only. Users can no longer edit the order or its line items. To change product quantities, pricing, or terms, use the amendment or change order process."Subscription Management Implementation Guide "Order Lifecycle Management" section:"Activation transitions an order from a draft or submitted state into a locked state for processing. No direct modifications to order lines are permitted once activated."Step-by-Step ReasoningUnderstand the scenario:The order has been submitted and permissions were granted, but the team still cannot edit line items.Key factor:If an order is activated, its records (header and line items) become locked for billing and fulfillment synchronization.Why option B is correct:Activation locks the order, preventing direct edits. The only way to make changes post-activation is via amendments or change orders, not direct editing.Why A and C are incorrect:A (Asseized): Not a Salesforce term related to order lifecycle.C (Decomposed): Decomposition refers to fulfillment item breakdown, not a locking mechanism preventing edits.ReferenceSalesforce Billing Implementation Guide -- Order Activation and Amendment ManagementSalesforce CPQ Implementation Guide -- Orders and ContractsSalesforce Subscription Management Implementation Guide -- Order Lifecycle and Change Management
A company sells a wide range of products across multiple business units. Each product must support different selling models, such as one-time, term-based, and evergreen. The company wants to bundle these products in configurable ways without duplicating product records. Additionally, product attributes should be reusable across offerings, and product teams need to maintain the catalog with minimal manual effort.Given these requirements, how should a consultant design the product catalog in Revenue Cloud?
"Product Classifications allow you to define and manage attributes that are reusable across multiple products, ensuring catalog consistency and reducing maintenance.""Selling Models define how a product is sold--one-time, term-based, or evergreen--and can be applied to a product without duplicating the record.""A flexible catalog design leverages reusable metadata like Product Classifications, Selling Models,and Attribute Sets rather than creating separate product records for each variation.""Dynamic or configurable bundles support product combinations across business units without static dependencies or hard-coded configurations."Step-by-Step Reasoning:Core Requirement: Minimize catalog duplication while supporting various selling models and reusable attributes.Key Design Factor: Use Product Classifications to standardize and reuse product attributes across offerings.Implementation Approach: Assign Selling Models at the product level (One-Time, Term, Evergreen) for flexible pricing and lifecycle management.Outcome: This setup enables consistent catalog governance, lower maintenance, and support for configurable bundles across multiple business units.Incorrect Options:A: Creates redundant records and increases maintenance.C: Static bundles eliminate flexibility and reusability, conflicting with requirements.
Salesforce Subscription Management Implementation Guide -- Product Catalog and ClassificationsSalesforce CPQ Implementation Guide -- Product Configuration and Selling ModelsSalesforce Billing Implementation Guide -- Catalog Setup and Product Lifecycle Management
A smartphone product is currently sold as a one-time upfront payment.In order for it to be sold with equal monthly installment payments for 12 months, what should the consultant set up?
Answer(s): A
"A Term Selling Model defines a fixed duration for a product or service, such as 12 months, and specifies how the customer is billed--monthly, quarterly, or annually.""Evergreen Selling Models are used for ongoing, indefinite subscriptions without a predefined end date.""To convert a one-time purchase into an installment plan over a fixed period, use a Term-based Selling Model with the appropriate billing frequency."Step-by-Step Reasoning:Current State: Product is a one-time purchase.Required Outcome: Convert to 12 equal monthly payments -- this is a fixed duration (12 months) with monthly billing frequency.Correct Setup: Assign Term Monthly selling model, defining the duration as 12 months with monthly charge intervals.Why Others Are Incorrect:B (Term Annual): Uses annual billing, not monthly.C (Evergreen Monthly): Represents an open-ended subscription, not a fixed 12-month term.
Salesforce Subscription Management Implementation Guide -- Selling Models and Billing FrequenciesSalesforce CPQ Implementation Guide -- Product Selling ModelsSalesforce Billing Implementation Guide -- Term and Evergreen Subscription Setup
An administrator is configuring a subscription product in Revenue Cloud for a customer whose order starts on January 1. The finance team wants to collect payment before the service begins so that each invoice is sent on the 15th of the prior month.Which Billing Type should the Billing Treatment Item have to meet this requirement?
Exact Extracts from Salesforce Billing Implementation Guide:"Billing Type determines when a customer is invoiced and charged for a subscription or service. You can set Billing Type to Advance or Arrear.""Advance billing collects payment before the service period begins. The invoice is generated prior to the start date of the service period.""Arrear billing collects payment after the service has been delivered."Step-by-Step Reasoning:Requirement: The finance team wants invoices to be sent before the service begins (on the 15th of the prior month).Advance Billing Type: Ensures that invoicing occurs prior to the service period start, aligning perfectly with the "collect before service" requirement.Arrear Billing Type: Would bill after the service delivery, which does not meet the requirement.None: Would result in no defined billing schedule, leaving the invoicing behavior undefined.Therefore, Advance Billing Type is correct.
A product designer is setting up a product bundle that consists of T-shirts and caps. They want to ensure customers can order a maximum of three T-shirts and three caps, but the total number of products should not exceed five.How should the product designer set this up?
Exact Extracts from Salesforce CPQ Implementation Guide:"Local Cardinality defines the minimum and maximum quantities allowed for an individual product option within a bundle.""Group Cardinality defines the quantity range allowed across all options within a product option group. It restricts the total number of items a user can select within that group.""Use both local and group cardinalities together to control both per-option limits and total group quantity constraints."Step-by-Step Reasoning:Requirement:Max 3 T-shirtsMax 3 capsTotal bundle limit = 5 items combined.Solution:Local Cardinality: For each item (T-shirts, caps) min 1, max 3 ensures flexibility.Group Cardinality: Across both min 1, max 5 ensures total combined limit of 5.Why B is Correct:It satisfies both individual and group quantity rules while maintaining configuration flexibility.Why Others Are Incorrect:A: Allows total of 6 (violates the total maximum requirement).C: Missing group cardinality -- does not control total combined quantity.
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.