UNDERSTANDING EBAY ERRORS – DEBUG MODE
IMPORTANT: Starting from version 6.5.4 of the module, the “Debug” section is available inside its dedicated tab named “Debug”.
The synchronization of your catalog may generate errors returned by eBay, which can prevent product listings from being published.
Fastbay provides several tools to help you understand and analyze eBay error messages in detail.
In the documentation, within the FAQ section, you’ll find a list of the most common eBay errors, along with explanations and instructions for resolving them quickly.
Among the different ways to identify errors, debug mode is certainly the most complete, as it allows you to view the full XML response returned by eBay after a request made by the module.
As of version 6.7.0, a historical call log table has been introduced, available under the Debug tab, showing the following information for each request:
- The date and time of execution
- The type of call made (e.g.
GetCategories,ReviseInventoryStatus, …) - The response status (Success, Warning, Failure)
- The content of the XML request
- The response received from eBay (Success and Warning indicate a successful request; Failure indicates it failed)
All these details are available directly from the table using inline preview buttons, without needing to download files, making the analysis process faster and more efficient.
To detect an error, simply:
- Enable debug mode from the Debug tab.
- Open the product page of an item you want to synchronize and save it to trigger synchronization to eBay.
- Return to the Debug tab and review the latest entry to inspect the request and response XML.
An example of an eBay response visible in the table is shown below:
If there is an error, the message will be visible in the body of the XML response.
If the message is unclear, you can consult the documentation and module FAQs by searching the eBay error message to understand how to resolve the issue.