Unit is deleted

Hello @johnjohnsen

when you initiate the initial synchronization from WooCommerce and link it to your Zettle account, you will get the option to choose out of the following 2 options:
1) Add WooCommerce products –> Synced WooCommerce products and stock quantities will be added to the existing Zettle library.
2) Replace Zettle library –> Replace your existing Zettle library with synced products and stock quantities from WooCommerce.

In your case, it seems you choose option nr 2 and you replaced the Zettle library. In my experience using this plugin, it is the best situation to have your complete library set up in WooCommerce (correctly), so if any issue occurs, you can overwrite the entire library to Zettle.
For me, this is probably also the situation because we only support the plugin and do not use an actual physical store or the Zettle devices (so this situation might not apply to you).

Reading your comment one more time, what do you mean by “the field unit set”? Are you talking about the stock of the products? In that case: if any stock change occurs on either side (WC or Z) it should sync to the other product library as well (instantly). You cannot exclude the stock sync, since that is the main functionality of this plugin. Maybe you need to tell me a bit more details on what is happening and what you want from the plugin for me to be able to help you properly.

Kind regards,
Joost

You se the field called “Enhet”
There is no problem with stock sync or price sync:)

But when products sync from woo -> izetelle on price or stock change the field “enhet” is blanked out. m2 will disapear and i will have to go and manualy update the products in izetlle with m2 again.

https://www.dropbox.com/s/ctboha83cywkivq/Screenshot%202021-09-23%20at%2011.53.49.png?dl=0

Hello @johnjohnsen

Ok, so the “Unit” field in Zettle is being overwritten when you update the product’s price or stock on WooCommerce. When I test with the unit field, it gets reverted to not being used when I update WooCommerce.

It is strange that this field gets affected by WooCommerce since this field is not part of the synchronization in the plugin. Also, it is weird that for me it gets deactivated, while for you it gets forced to m2 instead.

Can you tell me what the original value is before it gets changed after the WooCommerce sync?

I will open a developers ticket for this and have my team investigate this issue.
Thank you for informing us about this situation; this should not happen.

Kind regards,
Joost

Hello Joost

The orginal value of the field is “m2” I set this manual in the backend on products in izettle.

As you say the field is deactivated when syncing products.

Before update of product in woocommerce
https://www.dropbox.com/s/igh70z0q9rrz6nu/Screenshot%202021-09-30%20at%2009.50.01.png?dl=0

After update of product
https://www.dropbox.com/s/hx8b9qzfmar2wjx/Screenshot%202021-09-30%20at%2009.50.22.png?dl=0

Hello @johnjohnsen

the bug has been raised with the team, I am still waiting for their initial response in order to get this fixed. Once I have any details I will let you know.

Kind regards,
Joost

Hi Joost,

We experience a similar problem.

We sync WooCommerce products with Zettle, that works fine. When in Zettle the product value of ‘Eenheid’ is set to a certain value (in our case ‘bottle’ because we sell whisky), and WooCommerce syncs data back to Zettle, this value is set to ‘default’.

We use Zettle to sell product in the store and in the webshop.

Is there a way to exclude this command from the API, or can I add an extra field to WooCommerce to sync back the value ‘bottle’ to the correct field in Zettle so it is not deleted every time a product syncs from the websdhop.

Thanks,

Ger.

Hello @gerdenhaan

sorry for the long wait. I have just reviewed the bug we have open for this issue (IZET-414) and see that this issue should be resolved in our next release, however, no date has been set for this yet.

Possibly I can provide you with a beta version that should fix this issue. I am waiting for the package to be provided. I will let you know when I have it for you.

Kind regards,
Joost

Hi Joost,

That would be nice!

Thanks for the support.

Ger

Hello @gerdenhaan and @johnjohnsen

The fix for this issue has been created and a beta version of our next release is available for you to download here: https://drive.google.com/file/d/1s20kzJJ-Zp4g8zHGwqz3GENZ86urN2ht/view?usp=sharing

If you choose to test this beta version, please let us know if you run into any issues with it, so we can adjust it if needed.

Kind regards,
Joost

Hi Joost,

Thanks!

I will start testing.

Ger.

Hello @gerdenhaan

Hope your testing went as successful as it did with me. This fix should be included in the release of version 1.5.3 that should become available today. I will mark this thread as resolved as our beta release already showed the fix was working as intended.

If you are still experiencing this issue we can reopen this or another thread. For now, I am marking it as resolved.

Kind regards,
Joost