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, @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

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.

Thanks Moshtafizur,

I look forward to your response ??

Regards,
Andy

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!

Thanks @xootix

Your help is much appreciated!

Many thanks @xootix

I’m sure there was an element of WF being somewhat over zealous regards this alert, but I’m sure I speak for everyone when I say I would rather the risk not be there at all.

Thanks again for your swift action ??

I concur, would be good to know when a ‘fix’ might be forthcoming for this?

Hi Matt,

Many thanks for the swift reply!

And apologies for wasting your time, I should’ve realised that!

Andy

• This reply was modified 3 years ago by Fortem Digital.

Thanks Tijmen,

Brilliant, that worked a treat!

Much appreciate your help.

Kind regards,
Andy

Hi,

I’ve found out the issue. Even though I was inputting the prices ‘correctly’, they needed to be input with 3 decimal places. ie a role based price of ￡1.43 (inc 20% tax), should actually be input as ￡1.428 NOT ￡1.43. This allows for WooCommerce rounding the tax up and ‘distorting’ the sub total on multiple quantities of the same product.

Many thanks,
Andy

Hi Phil,

Apologies for the delay in replying. Happy new year btw!

OK, I’ve been through all of your recommendations above to no avail unfortunately. The only thing left to try, is looking at the PHP logs to see if it’s a possible memory error which seems the likely culprit.

I will let you know once the hosting company have forwarded them on to me.

Kind regards,
Andy

• This reply was modified 6 years, 2 months ago by Fortem Digital.

Cart tab hidden, yup, sensible ??

Shame about no pro version on the roadmap as it would be good to have a few more styling options. ‘Is a really useful plugin.

Many thanks again for your time,
Have a good one!

Hi James,

Ah, got them thanks! Am I right in thinking there’s a few less customisable features than the previous version? Are you planning on developing a pro version with more functionality/styling options?

Andy

Yup, worked for me!

Many thanks Art Project Group ??