You are here:
Order Orchestration in Revenue Management
Dynamic Revenue Orchestrator (DRO) breaks down a single commercial order into multiple, manageable fulfillment steps. You can execute a tailored fulfillment plan for each product or service.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
Dynamic Revenue Orchestrator (DRO) breaks down a single commercial order into multiple, manageable fulfillment steps. You can execute a tailored fulfillment plan for each product or service.
| Available in: Enterprise, Unlimited, and Developer Editions |
Dynamic Revenue Orchestrator breaks down a customer's commercial order into the individual technical products, services, and tasks that are needed to fulfill it. The decomposition process bridges the gap between how a product is sold by sales reps and how it is actually delivered and managed by your order fulfillment team.
After order items are decomposed into fulfillment line items, an orchestration fulfillment plan tracks the stages and tasks required to fulfill the order to completion. A fulfillment plan can contain prioritization rules, SLAs, external callouts, automated tasks, manual tasks, and order fallout contingencies.
You can use DRO to orchestrate Industries Configure, Price, Quote (CPQ) orders. Because DRO is preintegrated with Industries CPQ, you can use DRO without migrating commercial product data out of Enterprise Price Catalog (EPC). See Salesforce Release Note: Integrate DRO with Industries CPQ.
Here's a high-level summary of the steps required to build your DRO solution.
To migrate product fulfillment decomposition rules, fulfillment scenarios, fulfillment step definitions, and fulfillment task assignment rules between Salesforce orgs, use Data API. For high-volume data transfers, use Bulk API to move these records and their associated condition data.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.