--- sourceDocument: Brazil Sales Customer Relationship Management sourceDocumentLink: https://www.servicenow.com/docs/r/order-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Sales Customer Relationship Management ft:clusterId : - omgmt bundleId : - omgmt workflow : - Customer and Industry --- # Order decomposition examples # Order decomposition examples {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Order decomposition examples This content explains how ServiceNow's order decomposition process works using demo data examples, illustrating how customer and service orders are broken down under various conditions. The decomposition supports complex order management and fulfillment workflows by handling optional characteristics, quantity-based decomposition, staggered fulfillment, and exclusion rules. It clarifies how specification relationships and decomposition rules influence the creation of product, service, and resource orders from a customer order. Show full answer Show less ## Specification Relationships and Decomposition Rules Specification relationships define how products, services, and resources relate hierarchically. Decomposition rules act as exclusion criteria that prevent the creation of domain orders if specific characteristics or options are missing from a customer order line item. For example, a "Requires" relationship ensures related service orders are created only if corresponding characteristics are present in the order. Conversely, "Bundles" relationships create child product orders for bundled items, while "Composed of" relationships do not trigger decomposition. ## Examples of Order Decomposition * **Managed Firewall Service:** A customer order for the Managed Firewall triggers decomposition to create corresponding resource-facing service (RFS) orders and resource orders, which then initiate fulfillment workflows based on order attributes. * **SD-WAN Service Package:** Bundles three product specifications (Controller, Edge Device, Security). When ordered, decomposition creates product orders for each component. Decomposition rules may exclude service orders if optional characteristics (e.g., Tenancy) are not selected. * **Characteristic-Referenced Decomposition:** Decomposition rules can reference specific characteristics and options, triggering order creation only when these are included in the customer order, ensuring precise fulfillment aligned with customer selections. * **Quantity-Based Decomposition:** When multiple instances of a product are ordered (e.g., three SD-WAN Service Packages), the process creates matching multiple product orders and corresponding child orders for fulfillment, enabling individual tracking and inventory management. * **Staggered Decomposition:** For offerings like the SD-WAN Bronze Plan, decomposition initially creates domain orders based on available characteristics. Missing characteristic values required for services (e.g., Routing, WAN Optimization) delay service order creation until fulfillment agents provide the necessary information, ensuring accurate and complete order processing. ## Practical Impact for ServiceNow Customers Understanding and configuring specification relationships and decomposition rules enables customers to automate complex order fulfillment processes accurately. This ensures that only relevant domain orders are created based on customer selections and characteristics, reducing errors and improving fulfillment efficiency. Customers can expect the decomposition process to generate appropriate product, service, and resource orders, trigger fulfillment workflows, and handle multi-quantity and staggered fulfillment scenarios effectively. Examples using demo data illustrating how customer and service orders can be decomposed under diverse conditions help you to understand the decomposition process. The conditions include optional characteristics, quantity-based decomposition, staggered fulfillment, and exclusion rules that support complex order management and fulfillment workflows. ## Specification relationship and decomposition rule example {#order-decomposition-examples__section_fvs_221_dqb} The Managed Firewall service demo data is an example of a customer facing service specification that has a Requires relationship with the following three resource-facing service specifications: * Firewall administrator * Firewall and DMZ * Threat and Intrusion Prevention service {#order-decomposition-examples__ul_gvs_221_dqb} The decomposition process creates an RFS service order only when the corresponding characteristic is available in the order line item for the Managed Firewall service specification. After receiving a service order for adding a Managed Firewall service, a service manager reviews and approves it. This process triggers decomposition, which creates the RFS service orders and resource orders. The service order has one order line item for the Managed Firewall service, which includes all of its characteristics. The service order decomposition process creates the following: * A CFS service order for Managed Firewall service. * Three RFS service orders for all three RFS specifications. * Three resource orders for resource specifications. {#order-decomposition-examples__ul_xsn_ck1_dqb} Next, the ServiceNow AI Platform triggers a fulfillment workflow for the decomposed service and resource orders. This workflow generates the required order tasks for fulfilling the domain orders and uses decision tables to identify the workflow for a decomposed order. The selected workflow is based on various attributes in the original service order. These attributes include the specification category, and an order line item action (Add, Change, or Delete), among others. To learn more about decision tables, see [Decision tables](https://www.servicenow.com/docs/access?context=decision-table&version=brazil&pubname=brazil-application-development&ft:locale=en-US): ## Example of an order decomposition that is based on specification relationships {#order-decomposition-examples__section_gxy_1xf_v4b} Specification relationships define the relationships between a product, service, and resource. When you define specification relationships, you can optionally create decomposition rules to specify how a customer order is decomposed, fulfilled, and delivered to your customer. The best way to view a decomposition rule is as an exclusion rule. You use decomposition rules to specify to exclude domain orders from being created when you receive a customer order that doesn't contain a characteristic or characteristic option. For example, in the SD-WAN Service Package demo data, the following occurs: * A specification relationship is defined between the SD-WAN Controller product specification and its service specifications.{#order-decomposition-examples___Tocd18e9050} * The service specification details the services that are required for the product. When an order is received for the SD-WAN Controller product, a product order and a service order are generated for the SD-WAN Controller Service. {#order-decomposition-examples__ul_ym5_syf_v4b} Decomposition runs on the specification that is associated with the customer order line item and its hierarchy of specifications. It works as follows: * If the relationships between the source and target specifications are Bundles, Realized as, or Requires types, a product, service, or resource order is created for the target specification when the customer order is decomposed. * Decomposition establishes the hierarchical relationship between the source and targets while generating the product, service, and resource orders. * If the specification relationship is of a Composed of type, decomposition doesn't happen. {#order-decomposition-examples__ul_utt_zj5_v4b} The SD-WAN Service Package demo data is an example of a composite product specification that bundles three other product specifications within it: * SD-WAN Controller * SD-WAN Edge Device * SD-WAN Security {#order-decomposition-examples__ul_gj2_vvn_4pb}The SD-WAN Service Package defines the following relationships: * SD-WAN Service Package has a Bundles relationship with an SD-WAN Controller * SD-WAN Service Package has a Bundles relationship with an SD-WAN Edge Device * SD-WAN Service Package has a Bundles relationship with SD-WAN Security {#order-decomposition-examples__ul_fgv_nl5_v4b} When a customer order is received for the SD-WAN Service Package, and that order is approved, decomposition is triggered. The customer order line item for the SD-WAN Service Package has a single product order for the SD-WAN Service Package. That SD-WAN Service Package Product order has three child product orders: * SD-WAN Controller * SD-WAN Edge Device * SD-WAN Security (if the option security product was ordered) {#order-decomposition-examples__ul_rjb_yst_hpb} ## Example of order decomposition that is based on defined decomposition rules {#order-decomposition-examples__section_gsq_bm5_v4b} When you define specification relationships, you can optionally create decomposition rules. With a decomposition rule, you can specify to exclude domain orders from being created when you receive a customer order that doesn't contain a specific characteristic or characteristic option. The following example shows that the SD-WAN Controller Tenancy product characteristic was designated as optional.Figure 1. SD-WAN Controller Tenancy product characteristic In the example, you see that a decomposition rule was defined for the SD-WAN Controller product specification relationship to the SD-WAN Controller Service. This rule excludes the specification when a customer does not select the Tenancy option.Figure 2. SD-WAN Controller Service decomposition rule When a customer places an order and doesn't select the Tenancy option, the related service order doesn't generate for it. ## Example of order decomposition that include references to characteristics and options {#order-decomposition-examples__section_whg_p4h_ppb} You can define the decomposition rules for a specification relationship and include references to a characteristic and characteristic option. The following elements comprise the specification relationship: * The source specification is the specification that defines the specification relationship. * The target specification is the specification that the relationship is being defined to. * Both values are automatically defined when you create the decomposition rule from the specification relationship. {#order-decomposition-examples__ul_jth_h13_ppb} If the characteristic and value are present on the order line, the ServiceNow AI Platform applies the decomposition rules to Add and Change type orders. They are not applied to customer order line items with a Disconnect (Delete) order action. In this example, the SD-WAN Edge Device is a product specification and SD-WAN Security is a service specification. * The SD-WAN Edge Device has a characteristic called WAN Optimization and has a Realized as relationship with SD-WAN Security. * There is a decomposition rule for this relationship with WAN Optimization as the characteristic. {#order-decomposition-examples__ul_y3w_zn5_v4b} If you receive an order for the SD-WAN Service Package that doesn't include the WAN Optimization characteristic, the decomposition rule prevents the generation of an SD-WAN Controller Service service order. The rule designates that the decomposition of that service order only happens if that characteristic is ordered. ## Order decomposition for order line-item quantity and order quantity characteristics changes {#order-decomposition-examples__section_knf_rwv_hsb} When order decomposition process uses the order quantity information from the order capture process to create multiple product orders that match the line item quantity for a customer order. An agent then fulfills each instance of the product separately, which create the inventory records for each of the fulfillment instances. When a customer submits an order for three instances of the SD-WAN Service Package product and you approve the order, the decomposition process creates three product orders for the SD-WAN Service Package including one product order for each order line item. Each product order in the SD-WAN Service Package creates three child orders for the products and services for the order fulfillment process. ## Example of staggered decomposition {#order-decomposition-examples__section_a1y_bzf_yrb} The following example describes the staggered decomposition process for a product offering called SD-WAN Bronze Plan. Figure 3. SD-WAN Bronze Plan product offering The SD-WAN Bronze Plan product offering uses a product specification, called an SD-WAN Service Package (as shown in the following example), that has three target specifications: * SD-WAN Edge Device * SD-WAN Security * SD-WAN Controller {#order-decomposition-examples__ul_g3f_c5h_yrb} Figure 4. SD-WAN Service Package product specifications The SD-WAN Edge Device product specification has specification relationships with SD WAN Optimization Service and SD-WAN Routing, and the underlying decomposition rules don't have any values for WAN Optimization and Routing characteristics. Figure 5. SD-WAN Bronze Plan specification relationships The following example shows the decomposition rules for the product offering for the SD-WAN Bronze Plan. Figure 6. SD-WAN Bronze Plan decomposition rules When your customer places an order for the SD-WAN Bronze Plan product offering and you approve this customer order, decomposition begins with the creation of the domain orders as per the defined specification relationships and decomposition rules. Because this customer order doesn't have the values for these characteristics for Routing and WAN Optimization, the decomposition rule doesn't create the service orders. However, as a part of the order fulfillment process, the information for Routing and WAN Optimization must be available. When your fulfillment agent provides the values for these characteristics, the decomposition rule creates the necessary service orders and the order decomposition completes. **Related concepts** * [Configuring Order Management](https://www.servicenow.com/docs/plvzJpZ6DQe34i32M_1_mQ "Learn how to configure the features and components that you need for customer and service order processing, depending on whether you are a provider or an enterprise customer.") * [Order management](https://www.servicenow.com/docs/syJuj4_5c95HS9h75RAYnQ "The Order Management application streamlines the order life cycle from capture to fulfillment. It automates decomposition, enrichment, and orchestration workflows, empowering users to accelerate delivery, reduce fallouts, and manage complex orders efficiently through a unified workspace and customer portal.")