Integrations

Integrations

Open in ChatGPT
Ask ChatGPT about this page
Open in Claude
Ask Claude about this page

How to check the sync

Search for Ecommerce Integration Log in the Awesome Bar to view the status of any synchronization. The log displays details of each sync request, including its status, processing result, and any errors encountered, making it easier to monitor and troubleshoot integration issues.

The Ecommerce Integration Log - one entry per sync action.

Reading the log

Each synchronization action-such as creating a Sales Order, preparing a Delivery Note, or uploading an Item-creates its own Ecommerce Integration Log entry with one of the following statuses:

  • Queued - The webhook was received, and a background job was scheduled.
  • Success - The synchronization completed successfully, and the document was created or updated.
  • Error - The synchronization failed. The log contains the request data and the traceback to help diagnose the issue.
  • Invalid - The request was rejected because it failed validation or contained invalid or unsupported data. Review the log details to identify and correct the problem.

You can filter the logs by Method to view a specific type of synchronization (for example, sync_sales_order or prepare_delivery_note), or by Status to quickly locate queued, successful, invalid, or failed syncs.

When something didn't sync

An Error log entry is the starting point for diagnosing most synchronization issues.

Open the log to review:

  • Request Payload - The data received from Shopify.
  • Exception Details - The error or traceback raised by ERPNext during processing.

Use this information to identify the cause of the failure, then follow the steps in the Troubleshooting section to resolve the issue.

Troubleshooting

Still Stuck?

Troubleshooting

If the issue persists:

  1. Open Ecommerce Integration Log.
  2. Locate the failed synchronization entry.
  3. Review the Request Data, Status, and Error Traceback.
  4. Use the log details to determine whether the issue is related to authentication, configuration, data mapping, or invalid request data before retrying the synchronization.
Last updated 3 weeks ago
Was this helpful?
Thanks!