# Exception Order Processing ### Overview Exception Order Processing ensures inventory accuracy when orders are cancelled, deleted, or fail — whether by the shopper or internally. Instead of losing track of stock tied to invalid orders, the WMS automatically recovers it and guides operators through a simple workflow to return items back into inventory. This prevents revenue loss, reduces manual work, and protects fulfillment from errors caused by “ghost orders.” ### How It Works The process begins when the operator enters the **order ID**. If the order was cancelled, deleted, or failed before fulfillment began, the WMS instantly returns the products to available inventory with no manual input required. If the order had already been picked, the system guides the operator through a structured put-back process. All items from the order appear in a dropdown, and the operator selects each product, assigns it to the correct storage location, and scans it back into stock. This is repeated until all items are reconciled. In both scenarios, Exception Order Processing ensures that stock tied to invalid orders is properly tracked, accounted for, and returned to inventory — preventing discrepancies and keeping records accurate. ### Why It Matters * Protect revenue by making sure products from cancelled, failed, or deleted orders are never lost or left unaccounted for. * Keep inventory accurate by instantly returning stock from unfulfilled orders back into available inventory. * Reduce wasted labor with automation that handles simple cases, while guiding operators step by step when manual put-backs are required. * Prevent “ghost stock” from tying up products that should be available for new orders. ### Best Practice Process exception orders as soon as they occur to prevent stock from being tied up unnecessarily. When restocking picked items, always confirm locations with a scan to avoid misplacements. Create a dedicated section for exception stock so operators can quickly identify and move cancelled, failed, or deleted orders flagged during picking and packing. Finally, review exception order patterns regularly to uncover upstream issues — such as repeated shopper cancellations or failed payments — and address them before they affect fulfillment at scale. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.getlogentic.com/workflows/orders-management/exception-order-processing.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.