---
schema_version: "1"
id: 3dc8b6a3a0c4bf7f2a228337ba5a66bb0df642533b253d3c41bba78b8f2716a6
title: Decomposition Scope
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_decomposition_scope.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_decomposition_scope.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1e3d2a546a6a0f51318e9227b4c97e29862a7ae99c8299475eda780719d4abdc
description: Set the decomposition scope to limit how many instances of a fulfillment order line item appear in fulfillment.
products:
  - Revenue Cloud
release: "264"
---
# Decomposition Scope

Set the decomposition scope to limit how many instances of a fulfillment order line item appear in fulfillment.

When you create a product, choose from one of these decomposition scopes in the Decomposition Scope field.

Order Line Item

For every order line item that decomposes to the fulfillment order line item, one instance of the fulfillment order line item is created. This scope is the default if you don't select a scope.

Order

A single instance of the fulfillment order line item is created per order. When the scope is set to Order, the fulfillment order line item cannot be assetized.

Bundle

A single instance of the fulfillment order line item is created per bundle within an order.

Account

A single instance of the fulfillment order line item is created across orders from the same account.

Custom

A single instance of the fulfillment order line item is created per scope identifier. 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.").

Here's an example of Decomposition Scope in action:

Let's say that there's a technical product called Shipping Service. There are lots of commercial products that decompose to Shipping Service, because lots of products require shipping. However, you don't want to fulfill each of those Shipping Service products individually for the same order.

To handle this situation, set the scope of the Shipping Service product to Order. That way, only one instance of the Shipping Service product is created for every order, no matter how many products in the order call for shipping.

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

Warning

When you create a bundle, don't make the child product's scope broader than the parent's scope. For example, if the parent's scope is Order Line Item, then don't set the child's scope to Account. From broad to narrow, the scope is Account, Order, Bundle, Order Line Item.