---
schema_version: "1"
id: d9f6a207de94685f6113fa5c83b1b8162812d4be83864c4a6601e25530eb8aab
title: Define How a Product Decomposes
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_define_how_a_product_decomposes.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_define_how_a_product_decomposes.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d5efee6dc5a216f1f79ecfca98b6f45162c82c850fb506e943de4a61ab244799
description: Use the decomposition workspace to set up rules that control how a commercial product or product classification breaks down into technical products. Define conditions and priorities for the decomposition rules. By default, all products decompose into fulfillment line items unless you specify an execution rule and that rule evaluates to false for a given sales transaction item.
products:
  - Revenue Cloud
release: "264"
---
# Define How a Product Decomposes

Use the decomposition workspace to set up rules that control how a commercial product or product classification breaks down into technical products. Define conditions and priorities for the decomposition rules. By default, all products decompose into fulfillment line items unless you specify an execution rule and that rule evaluates to false for a given sales transaction item.

### 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: both Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><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>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d92219e69">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d92219e69 ">To define how a product decomposes:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d92219e69 ">
              <p>Fulfillment Designer</p>
              <p>OR</p>
              <p style="margin-bottom:0;">DRO Admin User</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d92219e69 ">To define decimal quantity at design time and run time:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d92219e69 ">
              <p>Decimal Quantity Design Time</p>
              <p>AND</p>
              <p style="margin-bottom:0;">Decimal Quantity Run Time</p>
            </td>

          </tr>
        </tbody>
      </table>

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

Note

Before you can define how products decompose, you must create your product catalog and understand the role of the Decomposition Scope. See [Build Your Technical Product Catalog for Dynamic Revenue Orchestrator](https://help.salesforce.com/s/articleView?id=ind.dro_technical_product_in_dro.htm&release=264.0.0&type=5 "A technical product represents the items, services, or processes that enable order fulfillment to deliver a complete commercial product to your customer. A technical product lets fulfillment designers decouple front-office entities from mid- and back-office entities. To use Dynamic Revenue Orchestrator, you must configure your technical products using Product Catalog Management.").

For information on the number of products and decomposition rules supported, see [Dynamic Revenue Orchestrator Limits](https://help.salesforce.com/s/articleView?id=ind.dro_dynamic_revenue_orchestrator_limits.htm&release=264.0.0&type=5 "Order fulfillment processes are governed by limits on order submission, order line items, fulfillment order line items, and workspace usage. These limits differ for asynchronous and synchronous intake, and Dynamic Revenue Orchestrator responds in specific ways when the limits are exceeded.").

1. From the App Launcher, find and select **Dynamic Revenue Orchestrator**.
2. From the app navigation menu, select **Products**.
3. Click a product.
4. Go to the Decomposition tab.
    
    The Decomposition tab is available out-of-the-box when accessing the product page within the DRO app. For other applications, manually add and configure the Product Decomposition Workspace Lightning Web Component to the record page using Lightning App Builder.
    
    The workspace shows product class-based decomposition rules that the product inherited alongside the product’s decomposition rules. If the destination is a technical bundle, the workspace shows the complete hierarchy starting from the decomposed product as the root. By default, the canvas shows the full structure, including parent products. Switch the action bar toggle to only see the decomposed technical products. In the workspace side panel, rules are grouped and sorted to list the product class-based decomposition rules first, followed by product-based rules. Within these groups, rules are sorted by priority and then by modification date.
    
    For details on how technical bundles affect grouping, see. [Technical Bundles](https://help.salesforce.com/s/articleView?id=ind.dro_technical_bundles.htm&release=264.0.0&type=5 "Technical bundles organize related fulfillment line items into a hierarchy under a single root. This grouping keeps related products together so they follow consistent fulfillment actions throughout their lifecycle.")
    
    ![Decomposition tab on the product record page showing the decomposition workspace with the side panel.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_decomp_workspace.png)
5. Click **Add Decomposition Rule** and enter a unique name.
6. Enter a unique name for the decomposition rule.
    
    Don't include special characters like the greater-than symbol (>) in decomposition rule names. This character can cause plan execution failures during fulfillment.
7. Enter the priority. The lower the number, the higher the priority.
    
    When you configure two decomposition rules that map to the same target, Dynamic Revenue Orchestrator writes data from the rule with the lowest number to the destination product. If two decomposition rules have the same priority, then the most recently modified rule takes precedence.
8. Enter a destination product.
    
    The source product or product classification decomposes to the destination product.
9. Save your work:
    - To save and view the details page for the rule, click **Save**.
    - To save and then define conditions for when the rule runs during fulfillment, click **Save & Add Execution Rules**. See [Define Execution Rules for a Decomposition Rule](https://help.salesforce.com/s/articleView?id=ind.dro_define_conditions_for_a_decomposition_rule.htm&release=264.0.0&type=5 "To apply logic that determines when a specific decomposition rule runs, define execution rules that specify the conditions for the rule. By default, products decompose into fulfillment line items independent of execution rules.").

You can map fields and attributes between the commercial and technical products of your decomposition rules, so that the fulfillment line items inherit data from the source products. See [Define Field and Attribute Mapping](https://help.salesforce.com/s/articleView?id=ind.dro_define_field_and_attribute_mapping.htm&release=264.0.0&type=5 "Define how Dynamic Revenue Orchestrator (DRO) maps fields and attribute data between products. DRO uses this mapping to copy or transform commercial order data to the data that fulfillment systems or processes require.").

#### See Also

- [Decomposition Relationship Types](https://help.salesforce.com/s/articleView?id=ind.dro_decomposition_relationship_types.htm&release=264.0.0&type=5 "Dynamic Revenue Orchestrator (DRO) supports one-to-one, one-to-many, many-to-one, and many-to-many decomposition relationships.")