---
schema_version: "1"
id: f7acc1b3e59335d26cffae0cb914a40174d0fafae5e4648e8043f720872c26dd
title: How Skipping a Fulfillment Branch Works
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_how_skipping_a_fulfillment_branch_works.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_how_skipping_a_fulfillment_branch_works.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c4c7cd37fd9805cc2ff393c852d47bc2af374e89e5217a94079cab965e6f9465
description: A fulfillment branch contains an initial step and a series of dependent steps that follow it. When you turn on Skip Branch for a step and that step is skipped, the branch that depends on the step is also skipped because the remaining steps no longer apply. For example, if the Get Shipping Address step is skipped, the subsequent steps related to shipping are also skipped.
products:
  - Revenue Cloud
release: "264"
---
# How Skipping a Fulfillment Branch Works

A fulfillment branch contains an initial step and a series of dependent steps that follow it. When you turn on Skip Branch for a step and that step is skipped, the branch that depends on the step is also skipped because the remaining steps no longer apply. For example, if the Get Shipping Address step is skipped, the subsequent steps related to shipping are also skipped.

During fulfillment, an operator can click a step in the fulfillment plan to see whether the step is marked to skip the branch.

## Determine Which Steps Are Skipped

When a step is skipped and Skip Branch is turned on, DRO skips every step that depends solely on the original skipped step. Then it skips every step that depends solely on the steps that were just skipped.

In this example, the step Priority Onboarding is skipped, and Skip Branch is turned on. An unrelated step Ship Product isn't skipped:

![A chart highlighting what the text says about which items are skipped when Skip Branch is turned on.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/revenue_skip_branchoriginal.png)

The Send Welcome Kit step depends solely on Priority Onboarding, so it's skipped. The Schedule Call step depends solely on the Send Welcome Kit step, so it's also skipped.

But the Customer Onboarded step, though it depends on Schedule Call, also depends on Ship Product, which isn't skipped. So the Customer Onboarded step isn't skipped.

This example shows how DRO decides how far a skipped branch reaches when the warehouse fulfills a HiTech ServerDrive order. The Reserve Server Units step has Skip Branch turned on, and it doesn't meet its execution rule.

DRO skips Reserve Server Units and every step that depends solely on it. Pick from Warehouse depends solely on Reserve Server Units, so DRO skips it too. The branch then splits: both Pack Standard Order and Pack Express Order depend solely on Pick from Warehouse, so DRO skips both parallel chains.

![A chart highlighting an example of skipped branches](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/revenue_skipbranch_flowchart.png)

The branch ends when the next step, Finalize Shipment, depends on multiple steps. It depends on both Pack Standard Order and Print Shipping Label, and DRO doesn't skip Print Shipping Label. Because Finalize Shipment doesn't depend solely on the skipped branch, DRO runs it when its remaining dependencies are met.

DRO skips the branch only when the step's conditions aren't met. If the conditions are met, the step and the steps that depend on it run normally. To configure Skip Branch, 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.")