--- schema_version: "1" id: 5d9396deedf3d828beafc3094827c2948a8aff38ccf83b6ad9ad49e983154811 title: Design Your Order Orchestration collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_design_time_orchestration.md canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_design_time_orchestration.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: e8f702cb5b464c697d8102cc1fc7dfbaf15074b0d2ed643b218a3b973fec9c29 description: Build strategic, efficient, and adaptable order orchestration in Dynamic Revenue Orchestrator (DRO). Create order fulfillment steps, fulfillment step groups, dependencies, and rules for how DRO fulfills orders. Fulfillment steps can be automated, manual, or dependent on other steps. products: - Revenue Cloud release: "264" --- # Design Your Order Orchestration Build strategic, efficient, and adaptable order orchestration in Dynamic Revenue Orchestrator (DRO). Create order fulfillment steps, fulfillment step groups, dependencies, and rules for how DRO fulfills orders. Fulfillment steps can be automated, manual, or dependent on other steps. ### Required Editions
Available in: Enterprise, Unlimited, and Developer Editions
Order Orchestration runs after decomposition completes. If you haven't designed your decomposition rules yet, see [Design Your Order Decomposition](https://help.salesforce.com/s/articleView?id=ind.dro_design_time_decomposition.htm&release=264.0.0&type=5 "Define how your commercial products decompose into technical products that your order fulfillment team can deliver to your customers. Products decompose based on rules you define, and the technical products can inherit field and attribute data from related commerical products."). You can decide the depth at which to implement orchestration in DRO. Orchestration can a simple fulfillment tracker, with most of the fulfillment details handled by your ERP, or use DRO to more deeply model your orchestration. To get started designing your order orchestration solution, follow these instructions: - **[Define Orchestration Plan Components](https://help.salesforce.com/s/articleView?id=ind.dro_define_orchestration_components.htm&release=264.0.0&type=5)** Create and organize fulfillment steps, their dependencies, and fulfillment processes in fulfillment workspaces. - **[Fulfillment Step Types](https://help.salesforce.com/s/articleView?id=ind.fulfillment_step_types.htm&release=264.0.0&type=5)** When you plan your orchestration, keep in mind the different types of fulfillment steps, and how they work. Fulfillment step types can be used to define manual tasks, automated tasks, milestones, callouts, and other actions. - **[Design Orchestration with the High Tech Order Orchestration Template](https://help.salesforce.com/s/articleView?id=ind.dro_hi_tech_order_orchestration_template.htm&release=264.0.0&type=5)** Use the High Tech Order Orchestration Template as a starting point for orders that combine project work, hardware assembly, software provisioning, billing, and revenue scheduling. - **[In-Flight Order Changes](https://help.salesforce.com/s/articleView?id=ind.dro_in_flight_order_changes.htm&release=264.0.0&type=5)** Sometimes customers request modifications to their orders after the order is submitted for fulfillment by the sales rep. Modifications can include changing the entire order, specific line items, or even canceling part or all of the order. Changes that happen during fulfillment are called in-flight order changes. - **[Import a Fulfillment Step Definition Group](https://help.salesforce.com/s/articleView?id=ind.dro_import_a_fulfillment_step_definition_group.htm&release=264.0.0&type=5)** To help scale your fulfillment plans, and ensure consistency across plans, you can import your existing fulfillment step definition groups directly from a fulfillment workspace. - **[Set Dependencies Between Fulfillment Steps](https://help.salesforce.com/s/articleView?id=ind.dro_set_dependencies_between_fulfillment_steps.htm&release=264.0.0&type=5)** Connect fulfillment step definitions to create a dependency between them. When an order is submitted, the steps run in the order that you define. - **[Create a Fulfillment Task Assignment Rule](https://help.salesforce.com/s/articleView?id=ind.dro_create_a_fulfillment_task_assignment_rule.htm&release=264.0.0&type=5)** Create reusable rules to automatically assign manual tasks to users based on the criteria and conditions defined in the rule. - **[Configure a Fulfillment Scenario](https://help.salesforce.com/s/articleView?id=ind.dro_configure_scenarios_for_a_fulfillment_step_definition_group.htm&release=264.0.0&type=5)** Use a fulfillment scenario to define when Dynamic Revenue Orchestrator (DRO) adds a fulfillment step definition group to a fulfillment plan after an order is submitted. Fulfillment scenarios help you add common fulfillment steps automatically instead of creating the steps for each order. - **[Define Conditions for a Fulfillment Step to Run](https://help.salesforce.com/s/articleView?id=ind.dro_define_conditions_for_a_fulfillment_step_to_run.htm&release=264.0.0&type=5)** You can prevent a fulfillment step from running until certain conditions are met. - **[Configure Steps for Future Execution](https://help.salesforce.com/s/articleView?id=ind.dro_configure_steps_for_future_execution.htm&release=264.0.0&type=5)** Fulfillment designers can configure the steps to be executed at a future date and time. They can set a delay for the execution of steps based on the start date of the source line item, the execution time of the previous steps, or a custom date based on a context definition field. - **[Apply Custom Scopes to Fulfillment Steps and Dependencies](https://help.salesforce.com/s/articleView?id=ind.dro_custom_scope_step_dependencies.htm&release=264.0.0&type=5)** Use custom scopes to group fulfillment steps and resolve step dependencies based on a business value that you define, such as a tenant group, ramp segment, service location, or sales transaction item group. Standard scopes use a fixed level, such as Plan, Bundle, or Line Item.