---
schema_version: "1"
id: a4869db55992355e2c91b704a79b0a40309734a68e68bc675f9b08dbd6babfca
title: Define a Fulfillment Step
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_define_a_fulfillment_step.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_define_a_fulfillment_step.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: df93048b81bbf7b22eabffead311551af053189db5adf3e5add51667bcd856e0
description: After you create a fulfillment step definition group in the workspace, add a fulfillment step definition to it. When an order is submitted, Dynamic Revenue Orchestrator (DRO) creates a fulfillment step in the Orchestration Plan for the order based on this definition.
products:
  - Revenue Cloud
release: "264"
---
# Define a Fulfillment Step

After you create a fulfillment step definition group in the workspace, add a fulfillment step definition to it. When an order is submitted, Dynamic Revenue Orchestrator (DRO) creates a fulfillment step in the Orchestration Plan for the order based on this definition.

Here's how to create a fulfillment step definition:

1. From the App Launcher, find and select **Fulfillment Workspaces**.
2. Choose a fulfillment step definition group and click **Add Step**.
3. Enter a Fulfillment Step Definition Name.
4. Select a **Step Type**.
    
    Some step types require additional information. For details on how to configure each step type, see [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.").
5. Select a **Scope**.
    
    The scope determines how many instances of the fulfillment step is created once the orchestration plan is underway. The scope options are:
    
    - Plan: One instance of the step appears in the entire orchestration plan.
    - Bundle: One instance of the step appears per bundle in the order.
    - Line Item: One instance of the step appears per line item.
    - Custom: One instance of the step appears per scope identifier. To create a custom fulfillment scope, see [Create Custom Fulfillment Scope Configuration](https://help.salesforce.com/s/articleView?id=ind.dro_create_custom_scope_config.htm&release=264.0.0&type=5 "Custom scopes use a configurable field in the line item or product object as the scope identifier. This identifier defines how fulfillment line items and steps are instantiated. During decomposition and orchestration, custom scopes group fulfillment order line items and steps according to the scope identifier.").
6. Optional: Enter a **Custom Config Parameter**.
    
    A Custom Config Parameter is a step-specific configuration value passed from an autotask step to a Salesforce Flow. Use it to drive custom logic in the flow based on the parameter's value.
7. Optional: Select a **Run As User**.
    
    When DRO executes this step, it uses the selected user's permissions. If you don't select a Run As User, then the step is executed as the Fulfillment User as defined in the DRO settings.
8. Optional: Select an Execution Schedule. For more information, see [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.").
9. Optional: If you have In-flight amendment enabled in DRO settings, configure [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.").
10. Optional: To configure the conditions for running the step, see [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.").