How to Handle Orders Exceptions [Step-by-Step guide]

Modified on Tue, 4 Feb at 4:38 PM

The Statistics & Exceptions Dashboard helps you quickly identify and resolve exceptions (errors), ensuring smooth operations.


WARNING: This feature is in beta and supports only beta Sales Channels. All data displayed and processed here is exclusively derived from beta Sales Channels. For a complete list of supported Sales Channels, refer to techOMS Sales Channels - Master List [Guides List].


To handle exceptions:


1. Filter the desired order data in the dashboard.


For detailed filtering instructions, refer to the "Filtering data" section in the Getting Started With the techOMS Statistics & Exceptions Dashboard [Information].


2. In the Exceptions table, locate the exception you want to work with.


This table is dynamic; as soon as exceptions are solved, they will disappear. It displays:

  • Warning Processing: Exception description.
  • Entity Type: Type of order.
  • Source: Source of the exception.
  • Level: Exception level. For a complete reference of exception levels, refer to techOMS Event and Message Types [Information].
  • Count: Number of orders affected by this exception.
  • Actions: Actions you can take to troubleshoot this exception.



3. Press View Orders for the desired exception. This opens a new tab displaying the affected orders.



If the Warning Processing message is "Missing product variant", clicking the message will open a pop-up showing the missing SKUs table. From this table, you can press View Orders to open a new tab displaying the affected orders for that specific SKU.



After identifying the affected orders, take the necessary actions to resolve the exception, such as updating product details.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article