EAN number changing to 1111

To add to this, it seems to happen when an order is placed on a product. Once the order is placed, it changes the EAN code to 1111 for that particular variable.

Very odd indeed!

Hi there,

I am really sorry to know you are experiencing problems.

I have escalated this with our development team. They will get back to you as soon as they can.

Kind regards,
Moshtafizur

Thanks Moshtafizur,

I look forward to your response ??

Regards,
Andy

Hi, @twostrong,

That’s really odd, I agree. The first thing that comes to mind is that this is done by some other plugin or custom code. Could you please try temporarily setting a different value (e.g., my_ean) for the “Meta key” option in “WooCommerce > Settings > EAN > Advanced”? Then, set a new EAN for one of your products, place an order, and check if the EAN was changed. By the way, did you modify the “Meta key” option previously, or is it set to the default _alg_ean?

Hi, @algoritmika

Many thanks for coming back to me regards this.

I have checked, and the Meta key is currently set to to the default _alg_ean , but I can try changing to something else to see if it still suffers the same issue once an order is placed for that particular product/product variable.

You can see the current settings here – https://capture.dropbox.com/hKmSqKlTcwHM2BLR

I will come back to you once this has been tested.

Hi, @twostrong,

Sounds good. Will be waiting for the test results.

Hi, @algoritmika,

Apologies for the radio silence, but I thought I would give you where we’re at with this issue.

After much testing, we’ve nailed down the culprit! The client uses Veeqo Inventory Management Software https://www.veeqo.com/gb which pulls and pushes product data to and from the website.

BTW, This only seems to affect variable products – When a sale is made, Veeqo pulls the amended stock level, then pushes data back to the site, and this is when it overwrites the EAN code for that particular product variable.

Veeqo (of course) state it’s not their issue etc etc but I have yet to try your possible solution of changing the meta key to a different value from default.

I will let you know the results…

• This reply was modified 1 year, 3 months ago by Fortem Digital.

Hi @algoritmika,

So changing the meta key did the trick! Although why Veeqo were overwriting it in the first place I guess we’ll never get to the bottom of!

The main takeaway here is this issue seems to have been fixed ??

Many thanks again for your help, it was much appreciated!

Have a great weekend,

Andy

Hi, @twostrong,

Happy to hear it’s solved ??