The correct approach to refresh prices for existing assets without service disruption is to amend the original asset, leave the original quantity unchanged, and use the reprice functionality. This method ensures continuity while updating pricing terms.
When amending an asset in Revenue Cloud, the amendment flow allows sales reps to create an amendment quote reflecting the desired changes. The amendment quote inherits the asset's current configuration while allowing price adjustments. By leaving the quantity unchanged but rephricing the quote, the system applies the new pricing without requiring the customer to purchase additional units or experience a service gap.
After repricing the amendment quote with the updated prices, the sales rep creates and activates an order from the quote. Upon order activation, the system processes the amendment by creating new Asset Actions that update the asset's financial terms while maintaining the customer's existing subscription. This approach preserves service continuity because the asset never goes inactive; it simply gets updated with the new pricing terms effective from the amendment start date.
Option A (negate quantity and re-add) would create unnecessary complexity and could cause momentary service gaps as the original quantity goes to zero before re-adding. This approach is inefficient for simple price updates. Option C (changing end date and re-adding) similarly creates duplication and potential service disruption. The reprice amendment approach, per the Amendment Creation process documented in Revenue Cloud, is the streamlined method that updates pricing while maintaining uninterrupted customer service.
References: Revenue Cloud Help - Asset Lifecycle Management, Amend, Renew, and Cancel Assets in Revenue Cloud, Asset Creation and Amendment Tutorial

In Salesforce Revenue Cloud's Subscription Management and Order Fulfillment framework, Decomposition Scope determines how fulfillment requests are grouped during the decomposition process. If the goal is to group multiple commercial products (and their technical/fulfillment counterparts) from different bundles within the same order into a single shipment, the appropriate scope is "Order".
Using Order-level Decomposition Scope ensures that all applicable products within the same order are processed as a single unit for fulfillment, which is ideal when shipping coordination is needed across bundles or product lines. This avoids generating multiple shipments for each product or bundle, thereby streamlining logistics and enhancing customer experience.
Option C (Bundle) would result in decomposition happening separately per bundle, leading to multiple fulfillment requests - contrary to the requirement.
Option A (Account) is too broad and may introduce unrelated products into the same fulfillment group, which is not desirable.
Exact Extracts from Salesforce Revenue Cloud Documents:
* Subscription Management Implementation Guide - "Decomposition Scope Settings":"The decomposition scope determines the grouping of products for fulfillment. Setting the scope to 'Order' allows all decomposable products in an order to be grouped into a single fulfillment request."
* Order Management Configuration Guide - "Controlling Decomposition and Fulfillment":"Use 'Order' as the decomposition scope to consolidate fulfillment for all products in the same order, even if they are from different bundles." References:
Subscription Management Implementation Guide
Salesforce Order Management Configuration Guide
Revenue Cloud Fulfillment Architecture Notes

Comprehensive and Detailed Explanation From Exact Extract:
Calculation sequence:
* Original List Price = $15,000
* Attribute-based price override # Price becomes $12,000
* Bundle-based adjustment discount: $12,000 # $1,000 = $11,000
* 10% manual discount on $11,000:
* 10% of 11,000 = 1,100
* 11,000 # 1,100 = $9,900
Therefore, the Net Price = $9,900.
References:
Revenue Lifecycle Management / Salesforce Pricing Guide - Pricing Element Order and Net Price Calculation

Explanation (150-250 words)
In Salesforce Subscription Management, flows that handle asset lifecycle actions-such as Amend, Renew, and Cancel-are centrally managed through the Revenue Settings configuration. When a custom version of these flows is created, administrators must update the Managing Assets flow references in Revenue Settings to point to the new flow definitions.
Even if a new flow is activated, the system continues to use the one defined in Revenue Settings until that reference is explicitly updated. This is why users still experience the default behavior.
The Manage Asset Viewer component (option A) calls the configured flow indirectly; it doesn't hold flow references itself. Product Discovery Settings (option C) relate to catalog exploration and are unrelated to asset lifecycle operations.
Exact Extract from Salesforce Subscription Management Implementation Guide:
"When customizing standard manage asset flows, update the flow references under Revenue Settings to ensure the system invokes the new version for amend, renew, or cancel actions." References:
Salesforce Subscription Management Implementation Guide - Customizing Manage Asset Flows Salesforce Revenue Cloud Setup Guide - Revenue Settings Configuration Salesforce Solution Architect Handbook - Asset Lifecycle Flow Governance

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.
References:Salesforce Billing Implementation Guide - Usage-Based Pricing Models; Attribute Rate Pricing.