--- schema_version: "1" id: f53f5c7f44cfd499a7f14eba64ae0ff12d21fa927220a4b075dfd18493dbcbb7 title: Dynamic Revenue Orchestration with Order Management collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/om_dro_order_management.md canonical_url: https://help.salesforce.com/s/articleView?id=commerce.om_dro_order_management.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: da9e934313d43f4d1a8aa945a5c8fd93023a9f07959622ba4d83295045033d95 description: Use the Dynamic Revenue Orchestrator (DRO) with Order Management to manage orders containing both physical products and digital services. With DRO and Order Management, customer service reps (CSRs) can see physical logistics and digital orchestration in one order summary, without switching between systems. products: - Commerce - Salesforce Order Management release: "264" --- # Dynamic Revenue Orchestration with Order Management Use the Dynamic Revenue Orchestrator (DRO) with Order Management to manage orders containing both physical products and digital services. With DRO and Order Management, customer service reps (CSRs) can see physical logistics and digital orchestration in one order summary, without switching between systems. ### Required Editions
View supported editions.
To use DRO with Order Management, you need: - Order Management Growth license - Revenue Cloud RevenueLifecycleManagementAddOn license - DROAddOn license DRO with Order Management doesn’t support bundles. DRO provides two services, decomposition, which is optional, and orchestration, which is necessary. Decomposition splits SKUs that contain both physical and digital purchases, such as a phone bundle that contains a phone, charger, anti-virus, and warranty. Orchestration handles the fulfillment of the components of the order, while Order Management handles the physical products. If you’ve set up a decomposition plan, use the isDecomposable flag to tell the system which items require orchestration. - **Items with isDecomposable = true**: If an item isn’t shipped, it requires orchestration, which DRO handles. - **Items with isDecomposable = false**: If an item is shipped, it’s fulfilled through Order Management’s standard fulfillment processing. A CSR can change in-progress, or in-flight, orders. The integration supports these in-flight modifications: - **Cancellations**: Freeze the DRO fulfillment plan, cancel unfulfilled digital line items, reconcile the plan, and unfreeze it to continue processing remaining items. - **Returns**: Process returns of physical items through Order Management while keeping the DRO fulfillment plan intact for digital services. - **Plan reconciliation**: After in-flight changes, automatically reconcile the fulfillment plan by removing previous fulfillment order line items and creating updated ones. The freeze and cancel steps are separate by design to avoid timeouts and give you flexibility in how to combine them into your business processes. DRO and Order Management use several mechanisms to keep both systems synchronized: - **DRO triggers Order Management routing**: DRO can initiate routing for physical items by creating an OrderSummaryRoutingSchedule record through an AutoTask step in the orchestration plan. - **Order Management signals fulfillment completion**: When a physical item is fulfilled, Order Management publishes a FulfillmentSourceChangeEvent that signals DRO. This event resumes any pause steps in the plan that need physical fulfillment before proceeding with digital provisioning. - **Fulfillment order status management**: For digital order item summaries, DRO manages fulfillment order status transitions. When an [expression set](https://help.salesforce.com/s/articleView?id=ind.dro_configure_es_mapping.htm&type=5&language=en_US) evaluates context data, it considers only the order item summaries that are directly related to the given step. The expression set establishes this relationship through the FulfillmentStepSource junction record rather than by scanning every order item summary on the order. The factors determine which order item summaries are linked to a step are: - The scope defined in the step definition - The product fulfillment scenario configuration Dynamic Revenue Orchestrator creates these FulfillmentStepSource associations during the plan composition stage, when you submit the order summary. If your context definition doesn't return the expected order item summary data, check these associations before you assume that there's a mapping issue. - **[DRO for Order Management Prerequisites](https://help.salesforce.com/s/articleView?id=commerce.om_dro_prereqs.htm&release=264.0.0&type=5)** Before you can use DRO with Order Management, enable the feature, clone the necessary flows, and set up Revenue Cloud DRO. - **[Configure Dynamic Revenue Orchestrator to Pause Status Changes](https://help.salesforce.com/s/articleView?id=commerce.om_configure_dro_pause_steps.htm&release=264.0.0&type=5)** Coordinate fulfillment between Dynamic Revenue Orchestrator (DRO) and Order Management by configuring pause steps that wait for specific Order Management milestones. For example, pause fulfillment until all ordered items are delivered. #### See Also - [DRO for Order Management Prerequisites](https://help.salesforce.com/s/articleView?id=commerce.om_dro_prereqs.htm&release=264.0.0&type=5 "Before you can use DRO with Order Management, enable the feature, clone the necessary flows, and set up Revenue Cloud DRO.")