No sync from Zettle to WooCommerce

Hello,

Thank you for reaching out to us.

The stock sync issue is an issue we are seeing every now and then and can have 2 different causes:

1. plugin conflict
2. Security measures block the stock sync communication.

The first thing I would do is to make sure you can reproduce the issue by manually adjusting the stock in the Zettle web interface and checking that it gets updated on WooCommerce. This is in order to verify is any of the next activities fix the issue.

The 2 possible activities to fix the sync issue are:

1. Deactivate all other plugins (except WooCommerce and Zettle) and see if you can make a stock sync from Zettle –> WooCommerce.

2. Any installed security plugin would already be excluded by the previous test, so the only security/firewall that needs to be investigated is the one managed by your hosting partner. For this, you need to reach out to them and ask them if they are possibly blocking the JSON webhooks that are required for the stock updates. We are hearing that the hosting partner firewalls are sometimes blocking these requests since they are interpreted as DDOS attacks and block the phpflood that is being seen.

We have an bug open to work on limiting the phpflood ourselves, but we don’t know when this will be developed/resolved, so taking action on #2 is definitely advised. This phpflood is being caused by the requests that are being done for the Zettle status bar in the product overview. If this is what is causing the issue, you could avoid it by deactivating this column in the “Screen Options”. However, you would also need to get your hosting party to lift the restrictions before it would actually fix the issue.

Please let me know what your findings are.

Kind regards,
Joost

I am facing the same issue. I will try following the first suggestion.

Hello @desisvaad and @tudrich

I have not heard back from you for over a month, so I am going to mark this thread as resolved.
However, I want to add one additional option to the causes of this problem:
Website URL change.
Some merchants first test our plugin on a staging site and change the URL afterwards when it needs to become live. In this way, the Zettle API Key, stored on the Zettle server, will most likely contain the URL of the old URL and will not be able to find the WooCommerce site for updating the stock.
It should be possible to resolve this issue by deactivating/activating the plugin so that the URL gets refreshed in the API key stored on the Zettle server.

I hope you both already got the issue resolved. If you still don’t have it resolved, you can open a new thread or contact us via our service desk (following these instructions) and we can take a closer look.

Kind regards,
Joost

Hi Joost, I’ve now tried all of your suggestion but I cannot get the Zettle to sync back to WooCommerce. When a product changes in WooCommerce the Zettle updates it’s self but if I make a sale on the Zettle or change any product details like price of quantity, the changes don’t appear in WooCommerce. I’ve tried turning off all plugins apart from Woo and Zettle and also a different theme. I’ve also check with our hosting partners and they have confirmed they do not block any requests toward the xmlrpc.php file. The server’s firewall and security mechanisms are not blocking any type of requests or hooks. There are no Mod_Security rules being triggered.

Thanks

Hello @tudrich,

have you tried turning off all other plugins (except WooCommerce & Zettle) and replacing the theme with Storefront? This would exclude all plugins and themes from the equation.

If that was done or you will do it now and it does not help, we can take a look at your system report, logs and possibly staging site to see if we can find the cause for this to happen.
If you don’t feel comfortable sharing those details on a public forum, please open a ticket with our service desk. You can find the instruction for this here: https://zettle.inpsyde.com/docs/request-support/

Kind regards,
Joost

Hi Joost

I’ve just opened a ticket on your service desk.

Hello,

since we continued our investigation via our service desk, I will mark this thread as resolved. If you still need our support on this or any other issue, please open a new thread or engage us via the service desk.

Kind regards,
Joost