---
schema_version: "1"
id: 4f5a2b5b6f93aefcd2f485023e295b2046f9fdd1dfb97ef1881eaf882a06e6a5
title: Understand Execution Conditions for Order Fulfillment
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_conditions_in_dynamic_revenue_orchestrator.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_conditions_in_dynamic_revenue_orchestrator.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bde9ff3d555d2208201518bf4ddf5b3fba39aac3b8dbe42385011c21b7cae829
description: Create conditions to control when a fulfillment step, step group, scenario, or a task assignment rule applies.
products:
  - Revenue Cloud
release: "264"
---
# Understand Execution Conditions for Order Fulfillment

Create conditions to control when a fulfillment step, step group, scenario, or a task assignment rule applies.

### 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>

For example, set a condition so that a representative follows up by phone only if the customer lives in the same country. Or a condition that says that after a pause, fulfillment doesn’t continue until a credit check comes through.

When an entity in DRO requires, or allows, conditions to be set, it launches the Condition Builder pane.

![The Condition Builder pane](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_conditions_pane.png)

To configure logic for your fulfillment processes, use the Condition Builder. To set up conditions for a decomposition rule, see [Define Execution Rules for a Decomposition Rule](https://www.google.com/search?q=link-to-your-topic)

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_example.png)

Example This image shows three conditions.

- Condition #1: There's a fulfillment order line item tag called FulfillmentItemAction that equals Add.
- Condition #2: There's a tag called OriginalQuantity that's greater than 100.
- Condition #3: There's a tag called FulfillmentOrderID that doesn't equal 1221.

The Custom Condition Logic says (1 OR 2) AND 3. That means that condition #3 must be met, and that either condition #1 or #2, or both, must be met.

![The Conditions pane with conditions filled in as described in the text](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_conditions_pane_ex.png)

Let's look at some possible examples after an order is submitted.

Order #1:

- FulfillmentItemAction equals Add. Condition one is met.
- OriginalQuantity equals 150. Condition two is met.
- FulfillmentOrderID is 1221. Condition three isn't met. The condition requires that FulfillmentOrderID type is something other than 1221.

Because condition #3 isn't met, the set of conditions isn't met, and the entity associated with this rule doesn't run.

Order #2:

- FulfillmentItemAction tag equals Add. Condition one is met.
- OriginalQuantity equals 90. Condition two isn't met. The condition requires the value to be greater than 100.
- FulfillmentOrderID is 1000. Condition three is met. The condition requires the value type to be anything except 1221, and it is.

This set of conditions is met according to the custom logic and the entity associated with this rule runs.