How to review the Sales Orders Log [Step-by-Step Guide]

Modified on Wed, 30 Oct at 5:31 PM

When you manage Sales Orders you might need to check the Logs to find a specific issues or systems actions and messages.


NOTE: Make sure that you are operating at the right Vendor/Warehouse beforehand.


There are two ways to review the Sales Orders' logs:

  • At the specific Sales Order level
  • At the Sales Order Logs module level


This article details both procedures:


WITHIN THE SPECIFIC SALES ORDER


To review the log within the Sales Order itself you will have to:


1. Click Sales Orders under Sales


2. Click the Sales Order number to access it



3. Open the Processing Logs tab



4. Click the message text on the list


NOTE: You may use the Search bar if you have an extensive log to review to find an entry quickly.


The details of the message will be detailed in a scrollable pop-up message:




SALES ORDER LOGS 


To review the Log you will have to:


1. Click Logs under Sales


2. Filter information by any of the possible ways

  • Quick Search: Enter the value you are searching for in the search bar, which will look up for all the orders that match it; as you enter the value, it will gradually narrow down the results to a unique order if you specify a full sale order number
  • Advanced Search: Click in the Filter icon by the Search Bar to deploy the advanced fields and complete them accordingly




Select and/or combine the filters according to your needs and Apply.


3) Click in the log entry Message Text field to review the details


4) Look for keywords that might be related to the case you're trying to check, for example reference names (e.g. Sales Order), data or actions (e.g. Ship, Address), etc.

Each log entry will include the reference, date, type, start, end and duration.





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