When using the Products List (POST) API in Salesforce Revenue Cloud, developers can query and filter the list of available products using specific supported parameters. According to the Salesforce Product Catalog and Discovery API documentation, the valid and commonly used filters for the Products List API include:
Product2 IDs: to retrieve specific products directly by their ID
Catalog IDs: to filter products based on a specific product catalog
Category IDs: to filter products that belong to a particular category within a catalog This allows developers to fetch only relevant products for a specific UI component or experience, such as in a Product Discovery component or a custom Lightning Web Component (LWC).

Dynamic Revenue Orchestrator (DRO) is Revenue Cloud's orchestration engine for post-order processes. Documentation describes DRO capabilities such as:
Decomposing orders into multiple fulfillment tasks or sub-orders based on product configuration.
Applying different orchestration/fulfillment plans for hardware, software, and services.
Managing task dependencies, SLAs, and routing to the appropriate teams and systems.

Contracts AI in Salesforce Revenue Cloud leverages AI-based document parsing to extract key data elements (clauses, values, terms) from uploaded contract files, such as PDFs. To configure this, an administrator creates a Contract Extraction Template, which determines how AI-extracted data maps into Salesforce fields.
In order to associate the template with an existing context definition (so extracted data aligns with the correct objects and relationships), the consultant must define both:
Attribute Definitions -- specify the data elements to extract (e.g., Start Date, Term, Renewal Clause).
Context Mapping -- links the extracted attributes to the appropriate fields and nodes within the selected context definition.
Without Attribute and Context mapping, Contracts AI cannot correctly populate contextual Salesforce data structures.

When an in-term change is made to an Asset, Revenue Cloud generates an Asset Action of type Amend, and proration is calculated based on the remaining time within the current Asset State Period (comparing the change date to the term end date). This produces a prorated Order/Quote for just the incremental value, while preserving the historical Asset State Periods for accurate MRR tracking. The original Quote is not recalculated retroactively, since it represents a point-in- time transaction that has already closed.

In Salesforce Subscription Management and CPQ, Asset Actions and Asset State Periods track changes in asset quantity, pricing, and lifecycle states over time.
When the initial order for "Training" is activated, Salesforce creates:
One Asset Action for the creation (initial assetization).
One Asset State Period representing the active subscription for 50 seats.
When the same asset is amended later that day to add eight more seats (quantity change), Salesforce generates:
A second Asset Action to record the amendment event (quantity increased by 8).
A second Asset State Period to represent the new asset state (58 seats active).
Each amendment creates a new Asset Action and corresponding State Period because Salesforce tracks historical lifecycle events for traceability, revenue recognition, and audit integrity.
The original state remains closed as of the amendment date, and a new one begins immediately.