The Discount Distribution Service (DDS) element is the correct pricing element for spreading calculated discounts evenly across quote or order line items. According to Revenue Cloud Pricing documentation, the Discount Distribution Service element allows administrators to apply discounts at the quote header level and automatically distribute those discounts across eligible line items.
The Discount Distribution Service supports multiple distribution methods: equal distribution (where the discount is divided equally across all lines) and proportional distribution (where the discount is allocated based on line item values). It accepts various discount types including dollar amounts, percentages, and target overrides. The element also supports enforcement of minimum unit prices and tracks remaining discount amounts that couldn't be applied due to price floor constraints.
Critically, the DDS element must be positioned as the LAST element in the pricing procedure.
This placement ensures that all other pricing calculations are completed before discount distribution occurs. The element configuration requires mapping input variables (header and line item fields including discount type, discount value, distribution logic, and line item pricing) and output variables (resulting discount values, net unit prices, and remainder amounts).

When a user removes (unselects) a bundle component during an amendment, Salesforce displays the removed item in the quote as a cancellation action.
From the RLM / CPQ Configurator documentation:
"When a component is removed during an amendment, the TLE displays a red cancellation indicator."
"The system shows the cancellation as a negative quantity (-1 or reduction of original quantity)."

The Place Sales Transaction API is the modern, high-performance API for order creation in Salesforce Revenue Cloud. It is specifically designed for transactional use cases--such as ecommerce order placement--where multiple products (up to thousands) need to be processed efficiently in a single transaction.
This API accepts comprehensive input data, including customer, pricing, and contextual attributes, and supports multi-line item transactions with automatic validation, pricing, and order creation. It ensures the correct generation of order records, order products, billing schedules, and related context without requiring separate API calls for each record.
The Create Order and Place Order APIs are legacy or limited-scope endpoints that do not handle large volumes or contextual pricing with the same efficiency.

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.

Salesforce's recommended implementation methodology for Revenue Cloud emphasizes:
A cross-functional team with expertise in Quote-to-Cash, order management, billing, and finance.
A phased implementation plan (discover -> design -> build -> test -> deploy).
Early analysis of data migration, integrations, and configuration before customization.
From the Revenue Cloud Implementation Guide:
"Successful implementations begin with assembling a cross-functional team familiar with Quote- to-Cash processes."
"Plan the implementation in phases and scope foundational setup such as data modeling, catalog design, and integrations."
"Avoid enabling all settings at once or jumping directly into custom development."