csv update doesnt sync changes to zettle

Hello @nickstulane

I am sorry you are running into this issue, but this is the expected behavior of the plugin. The sync listens to triggers that occur in WooCommerce product pages (in order to minimize traffic) and does not start the sync when activities are performed outside of the standard workflow.

I reviewed our backlog and it seems we did not have a feature request open for this, so I added it to our backlog. I will link this thread to the feature request so you will be updated via this thread when/if it becomes available.

Let me know if you have any more details you want to share on this request or if I can mark this as resolved.

Kind regards,
Joost

is there any way to perform a re-sync to copy all existing barcodes over?

i did try and disconnect and then reconnect with a new API key but it didn’t sync the barcodes

Hello @nickstulane

When you press the update button in the individual product, it does not update the barcode?

if your products in Zettle are identical to the WooCommerce library, you can try removing your Zettle library, disconnecting the account from the plugin and connecting it again.
I believe that if you still have the products in the Zettle library, the plugin believes that it is the same product and does not attempt to check the details.

I do advise you to test this first and not do this straight away in your live environment. It is best to create some test product(s) and see if it works first. Also, be sure to make backups before you do any tests.

Let me know if any of this helps you get further on this matter.

Kind regards,
Joost

Yea manually changing the status of the post in bulk edit works but it only handled 50 at a time.

does that mean that if the product name is changed it won’t be updated in Zettle?

I assume it is only the price that is synced once the initial product sync is completed?

if so it would be good to have a force full sync button somewhere in your plugin so that names, barcodes, etc can be refreshed.

• This reply was modified 2 years, 4 months ago by nickstulane.

Hello @nickstulane

the standard process that this plugin was developed for was that any adjustment to the product would be made on the product page of WooCommerce. When the “update” or “publish” button is pressed on this page, all the attributes that are synced to Zettle will be pushed and corrected if they have been changed.

However, I believe that you have been importing products in Bulk and this can mess a little bit with the synchronization. This is why we would need to know exactly what occurred in order for us to give you a better response.

If you want, you can also open a private support request with us via these instructions.

Let me know if you have more questions.

Kind regards,
Joost

there wasn’t really an error it was just the fact we imported via CSV but then had to manually edit each product and update to get the values across. Felt like the CSV upload was a bit pointless as we had to manually edit anyway.

imagine if a client wanted to change all the product names across the site perhaps by adding the manufacturer before the product name, this could be done with a CSV upload using SKU Name but this wouldn’t be sent to Zettle unless each product was then manually edited 1 by 1 or a few bulk at a time. still a long-winded process.

if there was a way to bulk send the data/refresh in the Zettle settings area perhaps it would solve the issue and importing data via CSV could be done and then 1 button click to send any changes to settle.

just a suggestion/idea…..

Hello @nickstulane

yes, I understand the issue and I agree that some support functionality from our plugin in these bulk updates is needed for it to become useful (that is also why I often suggest manual changes in the current situation).

I think a bulk export/import from our plugin page would be a great function and will add it to our backlog. But as informed before: we are pending approval to add any new features to the plugin and can’t do much until we get this. I have created the feature request and linked it to this thread; we will update the thread when/if it gets picked up and developed.

The input you gave us is appreciated in any case.
I will mark this thread as resolved.

Kind regards,
Joost