{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":37487,"path":"order-management/fallout-management-overview.md","title":"Managing order fallout","bundle":null,"doc_type":null,"release":"australia","body":"\n# Managing order fallout\n\nOrder fallout occurs when an order encounters an error in its normal fulfillment flow. Learn how Fallout Management enables you to identify, investigate, and resolve order issues so that orders can be processed to completion.\n\n## Overview of order fallout\n\nOrder fallout refers to the failures that occur due to errors and exceptions that may take place during order fulfillment. Fallout is a task-type object created to support scenarios where an order fails to proceed. These exceptions include the following:\n\n-   Incorrect data\n-   Connectivity problems\n-   Inadequate inventory supply\n-   Other unforeseen issues\n\nSome issues could originate in inbound and outbound external systems that integrate with Order Management. A single order task can have multiple types of fallout issues.\n\nThe following table provides examples of fallout errors and exceptions that can occur during order processing.\n\n<table id=\"table_hny_kmr_drb\"><thead><tr><th>\n\nType of failure\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nFailures in downstream fulfillment systems\n\n</td><td>\n\nFulfillment system can't process the request due to incorrect or missing data.\n\n</td></tr><tr><td>\n\nFailure to complete system interaction in a timely manner\n\n</td><td>\n\nTimeouts that occur during system interactions.\n\n</td></tr><tr><td>\n\nFailure in connection\n\n</td><td>\n\n-   Network connectivity issue.\n-   Unable to locate or route a request to a target system.\n\n</td></tr><tr><td>\n\nUnavailable inventory\n\n</td><td>\n\nInventory stock isn't available in the Enterprise Resource Planning \\(ERP system\\) to fulfill certain items on the order.\n\n</td></tr></tbody>\n</table>## Order fallout management flow\n\nWith Fallout Management, you can track each order fallout and automatically trigger the actions and interventions that can resolve your order fallout in a timely manner. The following diagram shows the order fallout management flow. Fallout Management processes order fallout through the following stages:\n\n1.  Identify and classify order fallout: Detect orders that have encountered errors or exceptions and classify the type of fallout.\n2.  Notify and assign order fallout: Route the fallout record to the appropriate team and notify them to begin investigation.\n3.  Resolve order fallouts: During runtime execution, fallout can be resolved through one of two paths:\n    -   Manual intervention: An agent investigates and resolves the fallout directly.\n    -   Automated process followed by manual intervention: An automated process attempts resolution first. If the automated process cannot resolve the fallout, it is escalated for manual intervention.\n4.  Verify and close order fallout: Confirm the issue is resolved and close the fallout record so the order can continue to fulfillment.\n\nFallout Management enables you to identify the orders in a failed state. Fallout tasks can be triggered and automatically routed to the appropriate team to investigate, diagnose, and resolve the underlying issue that is stopping order fulfillment.\n\n## Fallout Management tools\n\nThe Fallout Management function includes the following tools:\n\n-   **Order fallout tracking**\n\n    With this tool, you can assign a unique number to each order fallout to track the progress of the fallout, from inception through resolution. By using an Order Fallout dashboard, a designated order fallout manager can view the status of all open fallout records. To learn more, see [Review a fallout record](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/select-order-fallout-records-review.md).\n\n-   **Fallout resolution**\n\n    With this tool, you can use the ServiceNow AI Platform features such as routing, notifications, and Workflow Studio to process order fulfillment exceptions in an automated manner. To learn more, see [Creating automated fallout records](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/creating-automated-manual-fallout-records.md).\n\n\nFor example, your customer orders a router, but insufficient inventory quantities are available in your ERP system to reserve the item and fulfill the order.\n\n-   You create a fallout record for tracking and investigative purposes. This record places the customer order line item on hold.\n-   An order fulfillment agent can follow up to determine what is causing the shortage. It can be due to the unavailability of the host ERP system or because of an actual stock outage for the ordered item. If it's due to a stock outage, someone can take remedial action to contact the customer, reorder the item, or find a suitable replacement.\n\nAfter you resolve the issue, you can restore the customer order line item back to a normal state for completion of the order.\n\nWithout a fallout management process, your order fulfillment personnel would have to analyze and resolve these fallout issues manually. These additional tasks would result in a longer fulfillment process and could lead to poor customer and employee experiences.\n\n-   **[Creating automated fallout records](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/creating-automated-manual-fallout-records.md)**  \nWith Fallout Management, a provider can create automated fallout records for specific order tasks so that your orders can continue processing through to completion.\n-   **[Create a manual fallout record](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/create-manual-order-fallout-record.md)**  \nCreate a fallout record manually for an order task that has a condition or issue that prevents it from being completed.\n-   **[Review a fallout record](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/select-order-fallout-records-review.md)**  \nReview a fallout record to make sure that the detailed information is correct and complete.\n-   **[Update a fallout record](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/review-update-selected-order-fallout-records.md)**  \nReview the detailed information for a selected fallout record to verify that the information is correct and complete. You can change the fallout type, state, or priority. You can even assign it to a specific person to follow up on.\n-   **[Resolve order fallouts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/resolve-order-fallouts.md)**  \nLearn how to close the order fallout tasks in Order Management so that you can progress with order fulfillment.\n\n**Parent Topic:**[Using Order Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/using-order-management.md)\n\n**Related topics**  \n\n\n[Configuring Order Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/order-mgt-configuring.md)\n\n[Order management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/explore-order-management.md)\n\n"}}