---
schema_version: "1"
id: a51cc56947215adb5130ad438bd2ecf2f2c3b9c1a46a5a25eb60999f8fd4e0d5
title: Overview of Supplemental Order Decomposition
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_t_overview_of_supplemental_order_decomposition_233970.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_t_overview_of_supplemental_order_decomposition_233970.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5c5fb894c4a37c2b89ac3c99a6a18fe5a9aa3d72f05a3c377ff5aae5c9aa7aba
description: When a fulfillment operator amends an order while the order is "in-flight" (that is, it hasn't completed yet), then Vlocity creates a new supplemental order.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Overview of Supplemental Order Decomposition

When a fulfillment operator amends an order while the order is "in-flight" (that is, it hasn't completed yet), then Vlocity creates a new supplemental order.

OM creates a decomposition plan based on the supplemental order, and then compares the new decomposition plan to that of the original order. When there are changes, OM creates a supplemental action to supersede the original one.

For example, let's say that a customer orders a phone. The order is decomposed and is partially finished with orchestration. Then the customer cancels the order. OM maintains the original "Add" action, but adds a supplemental "Cancel" action to supersede the original action.

- **[Decomposition flow supplemental orders](https://help.salesforce.com/s/articleView?id=ind.comms_t_decomposition_flow_supplemental_orders_233977.htm&release=264.0.0&type=5)**  
    Decomposition handles supplemental orders in the ways outlined in this topic.
- **[Decomposition use cases](https://help.salesforce.com/s/articleView?id=ind.comms_t_decomposition_use_cases_233996.htm&release=264.0.0&type=5)**  
    These use cases highlight how decomposition operates in different situations. For these use cases, let's assume that the orders are in progress, with the downstream order item having the scope of **Account**.
- **[Conflict of attributes](https://help.salesforce.com/s/articleView?id=ind.comms_t_conflict_of_attributes_234154.htm&release=264.0.0&type=5)**  
    If an attribute value was updated in fulfillment (for example, by an external integrator), and then the relevant order is superseded by a supplemental order, there might be a conflict between the updated value and the one in the supplemental order.