---
schema_version: "1"
id: 05de96c031e30634402f864504fe26abb5a912b3f324d1321f2a4932393bb458
title: Submit Orders for Decomposition and Order Fulfillment
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_run_time_administration.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_run_time_administration.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2d273379fdbe0aba9721e8db6806088584b93da3c4f945ddedcf2c2e6cb7f6a7
description: Sales reps submit orders to Dynamic Revenue Orchestrator (DRO) for decomposition and fulfillment. During run time, fulfillment operators can track the decomposition and orchestration plans for submitted orders.
products:
  - Revenue Cloud
release: "264"
---
# Submit Orders for Decomposition and Order Fulfillment

Sales reps submit orders to Dynamic Revenue Orchestrator (DRO) for decomposition and fulfillment. During run time, fulfillment operators can track the decomposition and orchestration plans for submitted orders.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

- **[Create and Submit an Order](https://help.salesforce.com/s/articleView?id=ind.dro_create_and_submit_standard_orders.htm&release=264.0.0&type=5)**  
    Sales reps submit simple or bundled product orders in Dynamic Revenue Orchestrator (DRO) for decomposition and to instantiate the orchestration plan.
- **[Monitor Decomposition During Fulfillment](https://help.salesforce.com/s/articleView?id=ind.dro_monitor_decomposition_during_fulfillment.htm&release=264.0.0&type=5)**  
    After a user submits an order to Dynamic Revenue Orchestrator (DRO), you can see how products decompose and can spot issues right away.
- **[Order Fulfillment With Time-Awareness](https://help.salesforce.com/s/articleView?id=ind.dro_time_aware_fulfillment.htm&release=264.0.0&type=5)**  
    Manage complex, multi-year subscription lifecycles by using time-awareness in fulfillment assets. Instead of using a static snapshot of an asset, time-awareness aligns orchestration with the effective dates of each change, so that additions, cancellations, and renewals of backdated and future-dated orders update only the assets that change in that period.
- **[Monitor Fulfillment During Order Orchestration](https://help.salesforce.com/s/articleView?id=ind.dro_fulfillment_plan_actions_and_information.htm&release=264.0.0&type=5)**  
    Act on steps or learn more about how the fulfillment process is progressing directly from the orchestration plan.
- **[Fulfillment Step States](https://help.salesforce.com/s/articleView?id=ind.dro_fulfillment_step_states.htm&release=264.0.0&type=5)**  
    As steps progress through the fulfillment process, you can check the fulfillment plan to see the state that the steps are in.
- **[View Fulfillment Step History](https://help.salesforce.com/s/articleView?id=ind.dro_view_fulfillment_step_history.htm&release=264.0.0&type=5)**  
    Monitor the changes to a fulfillment step, such as status modifications, on its detail page by using the Fulfillment Step History related list.
- **[Retry or Complete Multiple Failed Fulfillment Steps](https://help.salesforce.com/s/articleView?id=ind.dro_retry_or_complete_multiple_failed_fulfillment_steps.htm&release=264.0.0&type=5)**  
    From a list view or queue, retry or complete multiple steps at once. If you complete a step in this way, the step ignores any errors that can otherwise stop the completion of the step.
- **[Retry Assetization for a Dynamic Revenue Orchestrator Order](https://help.salesforce.com/s/articleView?id=ind.dro_retry_assetization_for_an_order.htm&release=264.0.0&type=5)**  
    If assetization doesn't complete after fulfillment, fix the cause of the failure and invoke the Create or Update Asset from Order action. The action retries commercial assetization for the order and starts technical assetization to create or update its fulfillment assets.
- **[Handle Conflicts During Asset Date Amendments by Using Submit Order with Validation Flow](https://help.salesforce.com/s/articleView?id=ind.dro_submit_order_with_validation_flow.htm&release=264.0.0&type=5)**  
    It's common to request adjustments to license subscription start dates, either moving them earlier if your users are ready to use them or delaying them if they are not. However, if the order that created the asset has incomplete steps in its fulfillment plan, submitting an asset amendment can result in two orders updating the asset simultaneously. Identify and handle incomplete steps in the fulfillment plan by using the Submit Order with Validation flow.
- **[Configure Custom Logic between Decomposition and Orchestration](https://help.salesforce.com/s/articleView?id=ind.dro_hook_custom_logic_details.htm&release=264.0.0&type=5)**  
    To insert custom logic into the fulfillment process between the decomposition and orchestration steps, invoke the two processes separately. The standard Submit Sales Transaction invocable action runs decomposition and orchestration processes sequentially. To decouple the processes, use the individual Decompose Sales Transaction and Orchestrate Sales Transaction invocable actions. Add your custom logic and compose the fulfillment plan with the necessary, up-to-date information. Custom logic is critical if certain data needed for specific validations or data enrichment is only available after decomposition. After the custom logic executes, trigger the Orchestrate Sales Transaction invocable action through various methods, such as custom platform events, Apex triggers, or direct flow actions.