Asynchronous order processing for large customer and consumer orders

  • Release version: Australia
  • Updated March 23, 2026
  • 3 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 Asynchronous order processing for large customer and consumer orders

    Asynchronous order processing in ServiceNow’s Order Management application is designed to efficiently handle high-volume enterprise and consumer orders without requiring immediate processing. This improves system performance for communications service providers (CSPs) managing large multi-site or bulk orders. Unlike synchronous processing, which immediately creates orders and returns a 201 Created status, asynchronous processing returns a 202 Accepted status and an order ID, indicating the order is received but not yet created.

    Show full answer Show less

    How Asynchronous Order Processing Works

    • Orders are received via the Product Order Open API in asynchronous mode and validated first.
    • Validated orders are inserted into the Inbound Queue [sntmtcoreinboundqueue] table rather than being created immediately.
    • A scheduled job later processes these queued orders, creating customer order records in bulk or delayed batches, improving efficiency.
    • If validation errors occur, error messages are returned without adding the order to the queue.
    • Administrators control validation behavior using system properties createproductordervalidationasync and createserviceordervalidationasync, both enabled by default.
    • Orders can also be manually processed from the Inbound Queue module by selecting the Create Order button, bypassing the scheduled job.

    How Synchronous Order Processing Differs

    Synchronous processing validates and creates order records immediately upon receipt through the API, returning a 201 Created status. It can be slower for large volumes because all records are processed simultaneously. Validation can be toggled with system properties createproductordervalidationsync and createserviceordervalidationsync.

    Key Actions for ServiceNow Customers

    • Activate the Product Order Open API and utilize the mode parameter to specify synchronous or asynchronous processing.
    • Use asynchronous processing to improve performance when handling large or bulk orders.
    • Monitor and manage the Inbound Queue for order entries awaiting creation.
    • Configure and schedule order creation jobs or manually trigger order creation as needed.
    • Validate orders during asynchronous processing to ensure correct product offerings, order lines, specifications, and characteristics before creation.

    Benefits

    Implementing asynchronous order processing helps CSPs efficiently manage large volumes of orders, reduces processing time delays, and improves overall system scalability and performance in ServiceNow Order Management.

    Asynchronous order processing handles high-volume enterprise and consumer orders without waiting for immediate processing, improving system performance for communications service providers (CSP) using Order Management.

    Overview of asynchronous order processing

    CSPs support both enterprise customers and consumers. Enterprise customers typically place large multi-site orders, while consumers place high-volume orders. Asynchronous order processing enables you to create bulk or high-volume orders without waiting for each order to be processed immediately, improving efficiency and system performance.

    When you submit an asynchronous order request, the system responds with a 202 Accepted status and an order ID. This indicates the order is received for processing but not yet created. This differs from synchronous processing, which returns 201 Created when the order is immediately created.

    If you have a Telecommunications Service Management subscription, you can use the Product Order Open API to receive an order in the Order Management application. Order processing goes through three stages:
    • Order validation
    • Order ingestion
    • Order creation

    How synchronous order processing works

    With synchronous order processing, an order is received in the Order Management application through the API. Then, the order records are simultaneously created in a customer order table after the order validation.

    As an administrator, you can activate or deactivate the order validation for synchronous order processing by setting the create_product_order_validation_sync and create_service_order_validation_sync system properties to True (Default) or False in the ServiceNow AI Platform. Synchronous order processing takes longer than asynchronous order processing when it comes to creating a large number of customer order records.

    How asynchronous order processing works

    In asynchronous order processing, high-volume orders or large numbers of order payloads are received through the Product Order Open API in the Order Management application from external Configure, Price, and Quote (CPQ) systems.

    The order details are first validated and then inserted into the Inbound Queue [sn_tmt_core_inbound_queue] table. If validation errors occur, an error message is returned in the response. The actual order creation happens later when a scheduled job processes entries from this queue, allowing for bulk or delayed processing.

    This validation is managed by the create_product_order_validation_async system property for product orders and the create_service_order_validation_async system property for service orders. These properties control the validation in the asynchronous processing of orders before the orders are inserted into the Inbound Queue [sn_tmt_core_inbound_queue] table. The default value is set to True.

    When the order details are successfully validated, a scheduled job runs to pick up the records from the Inbound Queue [sn_tmt_core_inbound_queue] table and then creates entries in the customer order table as shown in the following diagram.

    Figure 1. Asynchronous order processing workflow
    Workflow showing how an asynchronous order is created. For text description, refer to the steps that follow.
    The asynchronous order processing follows these steps:
    1. You must activate the Product Order Open API. The new parameter mode enables the API to process orders synchronously or asynchronously. For more information about the API, see Product Order Open API.
    2. After you receive high-volume orders or large numbers of order payloads through the Product Order Open API in asynchronous mode, the system responds with a 202 Accepted status and an order ID. The order details are validated first and include the product offering, order line items, order specifications, order line item characteristics, and the specification relationship of order line items. For more information on how the validation works, see Validating your orders through asynchronous order processing.
    3. After the validation of the order details is complete, an entry for each order with a unique record ID is created in the Inbound Queue [sn_tmt_core_inbound_queue] table. To learn more about how the order entries are created, see Create order entries manually during the asynchronous order processing.
    4. When all the orders are captured in the Inbound Queue [sn_tmt_core_inbound_queue] table, a scheduled job runs to create the customer orders for the records in the New state. You can also manually trigger order creation from the Inbound Queue module by selecting the Create Order button, bypassing the wait for the automated job. After processing, you can verify the created orders in the customer orders section. To learn how a scheduled job creates orders, see Configure a scheduled job for asynchronous order creation.