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
  Decomposition handles supplemental orders in the ways outlined in this topic.
• Decomposition use cases
  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
  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.