MACD decomposition is driven by three information sets: the new commercial request in the Order and Order Items, the current customer state represented by Assets and technical Inventory Items, and the commercial/technical catalog configuration that defines decomposition and fulfillment behavior. Order Management compares the requested state with the installed state through the configured technical model to determine the required actions. The recommended configuration follows the native Communications Cloud responsibility boundary: catalog and CPQ determine the commercial request, while Order Management, OmniStudio, or the relevant platform service performs the downstream processing required by the use case. Fulfillment Requests and FRLs are generated outputs of that decomposition, not the primary starting inputs. Quotes are upstream selling artifacts; the submitted Order is the operational request processed by Order Management. Avoiding duplicate logic is important because repeated rules across catalog, integration, and orchestration layers quickly become inconsistent as products evolve. The selected approach keeps the authoritative data in the correct object model, supports later lifecycle operations, and minimizes additional processing or manual intervention. It should be implemented declaratively wherever the platform feature can express the requirement, with customization reserved only for behavior that genuinely falls outside the supported framework.

Study Guide Reference:MACD decomposition; Orders and Order Items; Assets; Technical Inventory; EPC configuration.