Hello Peter,
The thing you are trying to achieve is to show the products with taxes in Zettle and to show them in the WooCommerce store without. I am not sure that is possible, since the tool is set to create the same prices for both sides. If the tax settings of both sides are not the same, the product prices will not sync.
Maybe that is what you want to do: not sync the price (option in the onboarding and plugin settings) and then add the prices manually on Zettle. There is no other option I can think of to get the result you are looking for.
Let me know what you think.
Kind regards,
Joost
Thread Starter
codeid
(@codeid)
Hi Joost,
Thanks for the quick reply!
It’s a bit confusing. 🙂
For example:
I have a product in WC backend that is 1 euro (excl. VAT). It sells in the shop frontend for 1,21 (incl. 21% VAT)
In Zettle the product shows up as 1 euro, including 0,17 VAT. While ideally, the price in Zettle should also be 1,21.
Is there a workaround to correct this?
I would prefer to sync the prices. Since our shop has over 700 products.
Thanks in advance!
Regards,
Peter
Hello @codeid
as I said before: you cannot sync prices when the tax settings (or currency) are not the same. Because of this, your requirement will not be met; there is nothing I can do. Possibly a developer can insert a solution, but using our plugin in the default setup, this is not possible.
I am checking with my team if there is any code available for achieving this, but I am not sure we will have anything. I am pending their response, will update this thread if I get anything from them.
Kind regards,
Joost
Thread Starter
codeid
(@codeid)
Ok, thanks the effort Joost! 👍
Kind regards,
Peter
Hello @codeid
I checked with the developers’ team, but there is no solution for this request from our end, so you will need to create or get a developer to look into this.
I will mark this thread as resolved, as there is not much more we can do for this custom request. If there is anything else we could help with, don’t hesitate to open a new thread.
Kind regards,
Joost
Thread Starter
codeid
(@codeid)
No problem.
Thanks for checking with the developers team Joost!
Kind regards,
Peter