---
sourceDocument: Australia Telecommunications, Media, and Technology
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/telecom-media-technology

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Telecommunications, Media, and Technology

ft:clusterId :

    - telmt

bundleId :

    - telmt

workflow :

    - Customer and Industry


---

# Intent-based fulfillment

# Intent-based order fulfillment {#ariaid-title1}

Release version: Australia  
Updated July 14, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Intent-based order fulfillment

Sales CRM for Telecommunications introduces intent-based order fulfillment, enabling the translation of customer configuration inputs into executable order tasks without requiring explicit catalog entries for every product variant.
This approach extends traditional catalog-driven fulfillment by separating the commercial catalog (what is sold) from the fulfillment view (what is activated), allowing sales and network operations teams to collaborate using a shared, structured order representation.
Show full answer Show less  

## How Intent-based Fulfillment Works

When a customer order is placed, the system decomposes it into actionable order tasks using three key catalog mechanisms:

* **Spec relationships:** Define how product specifications relate to service and resource specifications, determining the generation of service and resource orders for each product offering line item.
* **Decomposition rules:** Control the breakdown of customer orders into product, service, and resource orders, supporting staggered decomposition and dependency sequencing across order line items.
* **Attribute mapping:** Transfers quote and order attributes to order tasks, ensuring accurate data is available to southbound APIs during service order orchestration and eliminating manual data entry.

The order decomposition hierarchy aligns with TM Forum standards and consists of:

* Customer order containing one or more product offering bundle order line items (OLIs)
* OLIs decomposed into product orders aligned to product specifications
* Product orders decomposed into service orders via customer-facing service specifications
* Service orders decomposed into resource orders via resource-facing service specifications

## Key Features

* **Non-catalog order support:** Automatically translates non-catalog configuration inputs into structured order tasks without needing new catalog entries for every variant.
* **Catalog-based decomposition:** Uses spec relationships and decomposition rules from the PSR catalog to break down customer orders into product, service, and resource orders.
* **Attribute mapping:** Ensures seamless transfer of attributes from quotes to order tasks, facilitating data accuracy during order orchestration.
* **Dependency sequencing:** Supports staggered activation of dependent order line items based on catalog characteristics, avoiding manual coordination.
* **Closed-loop extension:** Enables automatic updates of order status through activation feedback from downstream systems, supporting closed-loop orchestration.
* **TMF standards alignment:** Conforms to TM Forum Open APIs (TMF633, TMF620, TMF641) for standardized integration with third-party systems.

## Benefits for ServiceNow Customers

* Streamlines order fulfillment by eliminating the need to create catalog entries for every product variant or non-catalog item.
* Reduces configuration complexity by using decomposition rules and spec relationships instead of custom workflow logic.
* Improves data accuracy and efficiency by automating attribute transfer from sales quotes to fulfillment tasks.
* Facilitates better collaboration and visibility between sales and network operations through a shared order structure.
* Supports automated, closed-loop order lifecycle management with real-time feedback from activation systems.  
Sales CRM for Telecommunications supports intent-based order fulfillment, translating non-catalog configuration inputs into order tasks without requiring explicit catalog entries for every product variant.
Sales CRM for Telecommunications extends catalog-driven order fulfillment with intent-based orchestration. Rather than requiring a catalog entry for every product variant, the platform translates configuration inputs into structured order tasks. This includes non-catalog items using spec relationships, decomposition rules, and attribute mapping.

This approach separates the commercial catalog (what is sold) from the fulfillment view (what is activated). Sales and network operations teams can work from a shared order structure without manual translation between domains.

## How intent-based fulfillment works {#intent-based-order-fulfillment-somt__intent-based-how-it-works}

When a customer order is submitted, Sales CRM for Telecommunications applies three catalog mechanisms to decompose it into executable order tasks:

Spec relationships
:   Define how product specifications relate to service and resource specifications in the PSR catalog hierarchy. These relationships determine which service orders and resource orders are generated for each product offering line
    item (OLI).

Decomposition rules
:   Control how a customer order is broken down into domain orders product orders (PO), service orders (SO), and resource orders (RO). Rules support staggered decomposition and dependency sequencing across order line items.

Attribute mapping
:   Carry quote and order attributes through to order tasks, making the correct data available to southbound APIs during service order orchestration. This eliminates manual data entry between sales and fulfillment systems.

## Order decomposition structure {#intent-based-order-fulfillment-somt__intent-based-order-structure}

A customer order decomposes into the following hierarchy:

* Customer order contains one or more product offering bundle order line items (OLI)
* Each OLI decomposes into product orders (PO) aligned to product specifications
* Product orders decompose into service orders (SO) via customer-facing service specifications (CFSS)
* Service orders decompose into resource orders (RO) via resource-facing service specifications (RFSS)

This structure maps directly to TM Forum standards: Service Catalog Management (TMF633), Product Order (TMF620), and Service Order (TMF641).

## Benefits {#intent-based-order-fulfillment-somt__intent-based-benefits}

* Non-catalog and variant products decompose automatically without new catalog entries.
* Decomposition rules and spec relationships replace complex workflow logic, reducing configuration overhead.
* Attribute mapping eliminates manual data transfer between sales and fulfillment systems.
* The platform supports closed-loop extension, enabling automated feedback from activation systems back into the order lifecycle.
* A shared order structure gives sales and network operations teams consistent visibility across decomposition, assignment, and execution stages.

## Features {#intent-based-order-fulfillment-somt__intent-based-features}

{#intent-based-order-fulfillment-somt__table-intent-features__entry__2}

| Feature | Description |
|-|-|
| Non-catalog order support | Translates configuration inputs that fall outside the PSR catalog into structured order tasks using intent-based orchestration, without requiring explicit catalog entries for every variant. |
| Catalog-based decomposition | Decomposes customer orders into product orders, service orders, and resource orders based on spec relationships and decomposition rules defined in the PSR catalog. |
| Attribute mapping | Maps attributes from the quote through to order tasks, making the correct data available to southbound APIs during service order orchestration. |
| Dependency sequencing | Supports staggered decomposition based on catalog characteristic values, so dependent order line items activate in the correct sequence without manual coordination. |
| Closed-loop extension | Supports extension for closed-loop orchestration, enabling activation feedback from downstream systems to update order status automatically. |
| TMF standards alignment | Aligns to TM Forum Open APIs TMF633 (Service Catalog Management), TMF620 (Product Order), and TMF641 (Service Order) for standards-based integration with third-party systems. |
[Table 1. Intent-based order fulfillment features]

{#intent-based-order-fulfillment-somt__table-intent-features}