--- 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 --- # Product inventory and closed loop # Product inventory and closed-loop order fulfillment {#ariaid-title1} Release version: Australia Updated July 14, 2025 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Product inventory and closed-loop order fulfillment Sales CRM for Telecommunications integrates product inventory directly with the PSR catalog used for quote configuration, eliminating the need for separate sales and fulfillment systems synchronization. Product inventory records are created upon order approval and managed throughout the service lifecycle, from installation pending through active, suspended, and inactive states. Closed-loop order fulfillment ensures automatic updates of inventory and order status based on activation feedback from downstream provisioning systems, streamlining operations and reducing manual interventions. Show full answer Show less ## Key Features * **Catalog-driven inventory instantiation:** Product inventory records are generated from the same PSR catalog definitions used for quoting, ensuring consistency between sales and provisioning. * **Automatic inventory state management:** Inventory records automatically transition through lifecycle states such as Installation Pending, Active, Change Pending, Suspended, and Inactive as orders progress. * **MACD order support:** Modify, add, change, and disconnect orders can be performed directly on product inventory records without requiring new catalog entries. * **Closed-loop activation feedback:** Activation confirmations from provisioning systems automatically update order and inventory states, reducing manual follow-up. * **TMF637 alignment:** Product inventory management complies with TM Forum TMF637 standards, supporting integration with third-party provisioning and inventory systems. * **Unified inventory and order visibility:** Sales and operations teams access a single platform view of product inventory states alongside order and fulfillment status. ## Product Inventory Lifecycle and Order Types Product inventory records progress through defined lifecycle states: * **Installation Pending:** Created at order approval with placeholders for specifications; service not yet active. * **Active:** All domain orders fulfilled; inventory reflects live service. * **Change Pending:** Change orders in progress; specifications update accordingly. * **Suspended:** Service temporarily deactivated. * **Inactive:** Service permanently disconnected. Supported order types acting on inventory records include Change, Suspend, Resume, and Disconnect, enabling full lifecycle management without new catalog entries or manual order creation. ## Closed-loop Order Fulfillment Process Closed-loop fulfillment connects order submission to confirmed service activation by: * Decomposing customer orders into domain orders routed to fulfillment systems. * Receiving activation confirmation responses from provisioning systems. * Automatically closing domain orders and updating product inventory states to Active. * Closing the customer order once all domain orders complete, reflecting accurate service status. This process aligns with TM Forum Open API standards (TMF637 and TMF641), ensuring standardized integration and operational efficiency. ## Benefits for ServiceNow Customers * Eliminates data synchronization overhead between sales and fulfillment by sourcing inventory directly from quotes. * Provides consistent, real-time visibility into service lifecycle status for sales and operations teams. * Reduces manual effort and errors with automated inventory state transitions and closed-loop activation updates. * Supports flexible service modifications through MACD orders without requiring catalog changes. * Ensures standards-based integration capabilities for extending inventory and fulfillment processes with third-party systems. Sales CRM for Telecommunications instantiates product inventory from the PSR catalog definition used to configure the quote. It manages the product lifecycle through the order, closing the loop between order submission and service activation. In Sales CRM for Telecommunications, product inventory is not a separate system. When a customer order is approved, the platform creates product inventory records directly from the PSR catalog definition used to configure and price the quote. This means what was sold and what is provisioned always derive from the same source, removing the need to synchronize data between sales and fulfillment systems. The order manages the inventory record throughout its lifecycle. As domain orders close during fulfillment, inventory states update automatically. When activation feedback returns from downstream provisioning systems, the platform updates the inventory record to reflect the confirmed service state. This closes the loop between order submission and service delivery. ## Benefits {#product-inventory-closed-loop-somt__pi-benefits} * Product inventory is instantiated from the same PSR catalog definition used to configure the quote, removing the need to synchronize data between separate sales and fulfillment systems. * Inventory state updates automatically as domain orders close during fulfillment, removing the need for manual inventory updates after service activation. * A single inventory record tracks the full service lifecycle from Installation Pending through Active, Suspended, and Inactive giving operations teams a consistent view of what is provisioned. * Change, suspend, resume, and disconnect orders act directly on product inventory records, so service modifications don't require new catalog entries or manual order construction. * Closed-loop activation feedback from downstream provisioning systems updates order and inventory state automatically, reducing manual follow-up between fulfillment and operations teams. * TMF637 alignment supports standards-based product inventory management with third-party provisioning systems extends this to the resource order layer. ## Features {#product-inventory-closed-loop-somt__pi-features} {#product-inventory-closed-loop-somt__table-pi-features__entry__2} | Feature | Description | |-|-| | Catalog-driven inventory instantiation | Creates product inventory records from the same PSR catalog definition used to configure and price the quote. Inventory is created at order approval with placeholders for all specifications, and activates as domain orders close during fulfillment. | | Automatic inventory state management | Transitions inventory records through Installation Pending, Active, Change Pending, Suspended, and Inactive states automatically as the order progresses. No manual inventory updates are required after order approval. | | MACD order support | Supports modify, add, change, and disconnect (MACD) order types directly against product inventory records. Change, suspend, resume, and disconnect orders act on Active or Suspended inventory records without requiring new catalog entries. | | Closed-loop activation feedback | Receives activation confirmation responses from downstream provisioning systems and uses them to close domain orders, update inventory states, and close the customer order automatically. Reduces manual follow-up between fulfillment and operations teams. | | TMF637 product inventory alignment | Manages product inventory instantiation and lifecycle in alignment with the TM Forum TMF637 Product Inventory Management API standard. Supports standards-based integration with third-party provisioning and inventory systems. | | Unified inventory and order visibility | Tracks product inventory state alongside order status, domain order progress, and fulfillment tasks on one platform. Sales and operations teams share a single view of what is sold, what is provisioned, and what is active. | [Table 1. Product inventory and closed-loop fulfillment features] {#product-inventory-closed-loop-somt__table-pi-features} ## Product inventory instantiation {#product-inventory-closed-loop-somt__pi-instantiation} Product inventory records are created and added to the Product Inventory \[sn_prd_invt_product_inventory\] table after an order is decomposed, completed, and fulfilled. The Product Inventory table extends the Sold Product \[sn_install_base_sold_product\] table. Product inventory records are created for products with specifications. The instantiation sequence is as follows: 1. After the fulfillment manager approves the order, the platform creates a product inventory record with placeholders for all specifications generated after decomposition. The associated models are in an Installation Pending state. 2. During fulfillment, as product, service, and resource orders close, the state of each associated specification updates to Active in the product inventory record. 3. When the customer order closes, all characteristics associated with the specifications on the customer order update the inventory record. Note: Depending on how the sn_ind_tmt_orm.enable_prod_invt_for_order_management system property is configured, the platform creates either sold product records or product inventory records. Only product inventory records support change, disconnect, suspend, and resume order types. ## Inventory lifecycle states {#product-inventory-closed-loop-somt__pi-lifecycle-states} The product inventory record transitions through the following states as the order progresses: {#product-inventory-closed-loop-somt__table-inventory-states__entry__2} | State | Description | |-|-| | Installation Pending | Record created at order approval. Placeholders exist for all specifications. The inventory record does not affect service availability at this stage. | | Active | All associated domain orders are closed and fulfillment is confirmed. Specifications update to Active and the inventory record reflects the live service state. | | Change Pending | A change order is approved. Changed or removed specifications update to Change Pending until the change order fulfillment completes. | | Suspended | A suspend order is fulfilled. The inventory record transitions from Active to Suspended after all associated tasks and jobs complete. | | Inactive | A disconnect order is fulfilled. The inventory record moves to Inactive after the order completes. Disconnect orders can be created for records in Active or Suspended states. | [Table 2. Product inventory lifecycle states] {#product-inventory-closed-loop-somt__table-inventory-states} ## Order types that act on product inventory {#product-inventory-closed-loop-somt__pi-order-types} Product inventory records support the following order types for managing the customer service lifecycle after initial activation: {#product-inventory-closed-loop-somt__table-order-types__entry__2} | Order type | Description | |-|-| | Change | Modifies an existing product or service. Changed specifications transition to Change Pending during fulfillment and return to Active on completion. | | Suspend | Temporarily deactivates a product or service. The inventory record transitions from Active to Suspended after all tasks and jobs complete. | | Resume | Reactivates a suspended product or service. The inventory record transitions from Suspended back to Active after all tasks and jobs complete. | | Disconnect | Permanently deactivates a product or service. The inventory record moves to Inactive after the order completes. Available for records in Active or Suspended states. | [Table 3. Order types for product inventory] {#product-inventory-closed-loop-somt__table-order-types} ## Closed-loop order fulfillment {#product-inventory-closed-loop-somt__pi-closed-loop} Closed-loop fulfillment connects order submission to service activation confirmation. When downstream provisioning systems complete activation, they return a response to Sales CRM for Telecommunications. The platform uses this response to update domain order states, close the associated order tasks, and transition the product inventory record to Active without manual intervention. This closed loop covers the following stages: * Order decomposition generates domain orders and routes them to fulfillment systems. * Fulfillment systems activate the service and return a confirmation response. * The platform closes the domain order and updates the associated product inventory specification to Active. * When all domain orders close, the customer order closes and the inventory record reflects the fully activated service. Sales CRM for Telecommunications aligns closed-loop fulfillment to TM Forum Open API standards. TMF637 manages product inventory instantiation and lifecycle. TMF641 manages service order routing and activation responses.