You can troubleshoot any issues that arise in the WooCommerce - Megaventory connection in the WooCommerce interface
To do that you need to enter the Megaventory administrator panel in WooCommerce by clicking a link on the sidebar.
On the top of the admin panel, you can see two sections: status and setup.
The Status section indicates the status of the plugin:
Connection indicates whether a connection with Megaventory servers could be established. If this item indicates an issue, make sure your servers are online. If so, then the problem probably lies on the Megaventory side and you should contact our support.
Key indicates whether the API key is correct.
Currency indicates whether the Megaventory and WooCommerce main currencies match.
If any of those items does not indicate success, the plugin is completely halted until the issues are resolved. Problems should be taken care of starting from the top of the list – e.g. Problems with connection will also cause other statuses to indicate failure (with no connection, there is no way to check if API key is correct, or if the currencies match). Taking care of the uppermost problem will often solve the problems below.
The following sections can help identify the cause of any issues that come up and how to address them.
Interface – Error Log
Beneath the top of the interface you can find the error log. It shows all the information about when and where the plugin encountered problems. The list is sorted with the most recent issues on top.
The table consists of the following columns:
ID – the id of the error message
Megaventory ID – The Megaventory ID of the entity the error refers to. 0 or negative values mean that this ID is not relevant (e.g. The entity does not exist in Megaventory yet, or the plugin failed to find ID).
WooCommerce ID – The WooCommerce ID of the entity the error refers to. 0 or negative values mean that the ID is irrelevant in this case.
Created at – Indicates when the error was logged.
Error type – the type of the error. There are three error types:
Warning – This explicitly notifies about some actions that happen behind the scenes but do not necessarily mean that something went wrong.
Error – This indicates that something went wrong, most usually an entity (Client, Product, etc.) failed to be saved for some reason.
Fatal – This causes the whole plugin to halt, instead of affecting just certain processes only. In most cases, such an error means additional notices in the status section of the interface.
Entity name – the name of the entity the error refers to. This may sometimes be empty, when the name of the entity doesn’t exist, etc.
Problem – the description of what the problem is; this description is supposed to quickly and comprehensively describe what happened.
Full Message – the full description of the problem.
Error code – The code of the error. This is aimed to be a reference for programmers or Megaventory team.
Most often errors appear because an entity (Product, Client, Order, etc.) was not correctly synchronized due to incorrect details (name too long, SKU missing, product already exists, etc.). In most cases these issues require a quick manual intervention.
Interface – Taxes Table
The following table is available below the error log:
Use this table to make sure that taxes are correctly synchronized:
Every tax should be represented with a separate row in the table
Every tax must have an Megaventory id. If the Megaventory id column is empty, zero, or has a negative value, this tax is not correctly synchronized and will cause problems. Refer to the error log for more information.