Order decomposition

  • Release version: Australia
  • Updated March 12, 2026
  • 5 minutes to read
    • Summarize
    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

    Order decomposition in ServiceNow breaks down approved customer or service orders into smaller, manageable domain orders—product, service, and resource orders—for fulfillment. This process uses product catalog definitions, including specifications, specification relationships, and decomposition rules, to ensure accurate provisioning of all order components. The decomposition creates hierarchical domain orders with work orders for tasks like installation, which must be completed to proceed with fulfillment.

    Show full answer Show less

    Hierarchy of Domain Orders

    • Product order (Parent): Defines commercial intent, including brand, pricing, and terms; initiates fulfillment by triggering service and resource orders.
    • Service order (Child of product order): Manages technical fulfillment of services and may involve multiple service and resource orders.
    • Resource order (Child of service order): Handles provisioning of physical or logical resources needed to deliver the service.

    Each product order can have multiple service orders, and each service order can include multiple resource orders, reflecting the product specification relationships.

    The Role of Specification Relationships and Decomposition Rules

    Decomposition relies on:

    • Specifications: Define product, service, and resource attributes.
    • Specification relationships: Define how specifications relate (e.g., Bundles, Realized as, Requires).
    • Decomposition rules: Conditional logic that acts as exclusion rules to prevent domain order creation when certain characteristics are absent.

    Based on relationship types, decomposition generates customer-facing service orders (CFS), resource-facing service orders (RFS), and resource orders. If a characteristic is not present, associated domain orders are excluded. Adjusting attribute values can increase or decrease the number of generated orders.

    Customer Order vs. Service Order Decomposition

    While both use similar principles, key differences include:

    • Customer order decomposition triggers on customer order approval, generates product, service, and resource orders, supports staggered and quantity-based decomposition, and manages changes during fulfillment.
    • Service order decomposition triggers on service order approval, generates only service and resource orders, and focuses on logical service breakdown without staggered or quantity-based decomposition.

    Examples:

    • SD-WAN Service Package: Decomposes into parent product and multiple child product and service orders with rules based on characteristics like Tenancy or WAN Optimization.
    • Managed firewall service: Decomposes into customer-facing service orders, resource-facing service orders, and resource orders based on order characteristics.

    Additional Features in Customer Order Decomposition

    • Staggered decomposition: Creates domain orders at later stages based on updated information such as service availability or customer needs.
    • Quantity-based decomposition: Supports splitting orders by quantity and managing revisions or cancellations during fulfillment.
    • Support for change orders: Allows updates to quantity characteristics enabling upgrades, downgrades, and inventory management.

    Order decomposition is the process of breaking down an approved customer or service order into a set of smaller, manageable domain orders for fulfillment. This process is driven by definitions in the product catalog to ensure that all necessary components are provisioned correctly. Learn about the decomposition process for customer and service order and their differences.

    Overview of order decomposition

    When an order is approved, the system breaks down the commercial elements of an approved order into its smaller, actionable technical components called domain orders (product, service, and resource orders) for fulfillment. Decomposition defines the Bill of Material for an ordered component. The decomposition is guided by specifications, specification relationships, and decomposition rules defined in the product catalog. Decomposition rules (often exclusion rules) determine when domain orders should or should not be created, based on characteristics or options present in the order line item. Decomposition establishes hierarchical relationships between source and target specifications, generating the necessary product, service, and resource orders.

    For example, consider the SD-WAN Service Package from the demo data. For this product, specification relationships and decomposition rules determine which product, service, and resource orders are generated based on the order's characteristics.

    During order decomposition, work orders are created for product or service orders that need further action. For example, installation of a device at the customer site. You must close the order tasks and work order tasks associated with the domain orders to proceed with order fulfillment. Fallout records are created if you manually close the domain orders.

    Hierarchy of domain orders

    The domain order hierarchy is structured as follows:
    Product order (Parent)
    Defines the commercial intent of what is being sold. It is based on a product specification that includes brand, pricing, terms, and other product-related materials. The product order initiates the fulfillment process by triggering associated service and resource orders.
    Service order (Child of product order)
    Manages the fulfillment of a specific service specification. It outlines the technical realization and delivery of the service, often involving multiple service and resource orders.
    Resource order (Child of service order)
    Handles the provisioning of physical or logical resources required to deliver the service. It is based on a resource specification and may include multiple resource orders depending on the complexity of the service.

    Each product order can have multiple service orders, and each service order can have multiple resource orders, depending on the relationships defined in the product specification.

    The role of specification relationships and decomposition rules

    The following core components drive the decomposition process:
    • Specifications: Define the attributes of products, services, and resources.
    • Specification relationships: Define how different specifications are related to each other.
    • Decomposition rules: Provide conditional logic for the decomposition process.
    Decomposition runs on the specification associated with the order line item and its hierarchy. The type of relationship between specifications determines the outcome.
    • If the relationship is of type Bundles, Realized as, or Requires, decomposition process creates the following types of orders for the target specification:
      • A corresponding customer-facing service order (CFS), which is a service order that is generated for performance of customer-faced services.
      • A resource-facing service order (RFS), which is a service order that is generated for internal use of resources required to perform the actual services for the customer.
      • Resource order.
    • If the relationship is of type Composed of, decomposition does not occur for that relationship.

    Decomposition rules function as exclusion rules. They are used to prevent the creation of certain domain orders if the incoming order does not contain a specific characteristic or characteristic option. This allows for optional components within a product or service offering. For example, a rule can be set to only generate a service order for a specific feature if the customer explicitly selected that feature during the ordering process.

    Specification relationships and decomposition rules can be defined to exclude domain orders when certain characteristics are not present. For example, if a customer or service order does not include a required characteristic such as Tenancy or WAN Optimization, the related domain order is not generated.

    The decomposition process uses the source specification (defining the relationship) and the target specification (being defined to), with rules mapped to specific characteristics and values.

    When the attribute value is increased, more number of CFS/RFS is created.

    When the attribute value is decreased, it decreases the number of CFS/RFS.

    Customer order vs. Service order decomposition

    While the fundamental principles of decomposition remain the same, there are key differences when decomposing a service order compared to a customer order. The most significant difference is that service order decomposition does not generate product orders. The process is focused exclusively on the fulfillment of services and their underlying resources. The decomposition of a service order generates a specific set of service and resource orders:
    • Customer-Facing Service (CFS) Order: A service order for the performance of a customer-facing service.
    • Resource-Facing Service (RFS) Order: A service order for the internal use of resources required to perform the actual service for the customer.
    The scope of service order decomposition is focused on the logical breakdown of services. It does not typically involve concepts like staggered or quantity-based decomposition, which are more common in customer orders that may include physical products with variable quantities and complex, multi-stage fulfillment cycles. The key differences are listed in the following table.
    Table 1. Comparing decomposition of customer and service orders
    Aspect Description Customer order Service order
    Trigger Action that triggers order decomposition Approval of a customer order by fulfillment manager Approval of a service order by service order manager
    Basis for decomposition Basis on which the domain orders are generated Based on specifications, specification relationships, and the decomposition rules that are defined in the product catalog between the product, service, and resource specifications. Based on specifications, specification relationships, and the decomposition rules that are defined in the product catalog between the service, and resource specifications.
    Domain order generated Type of domain orders Product, service, resource orders Service and resource orders only
    Staggered decomposition The process that allows domain orders to be created at a later stage, based on updated information such as customer needs, service availability Yes No
    Quantity-based decomposition The process that supports splitting orders based on quantity, handling changes in order quantity, and managing inventory updates or cancellations for in-flight orders Yes No
    Example -

    SD-WAN Service Package

    • Bundles multiple product specifications.
    • Decomposition creates a parent product order and multiple child product and service orders, with rules to include or exclude based on characteristics like Tenancy or WAN Optimization.

    Managed firewall service

    Decomposition creates a customer-facing service order (CFS), multiple resource-facing service orders (RFS), and resource orders, based on relationships and characteristics present in the order.

    Additional features in customer order decomposition

    Customer order decomposition supports the following additional features:
    • Staggered decomposition: Customer orders may use staggered decomposition, creating domain orders at later stages based on updated information such as service availability or customer needs.
    • Quantity-based decomposition: Customer orders can be decomposed into multiple domain orders based on order quantity, supporting revisions, and fulfillment of multiple instances.
    • Support for change orders: Customer order decomposition supports updates to quantity characteristics, enabling upgrades, downgrades, and inventory management during fulfillment.

    Fore more information, see Customer order decomposition.