Googe Shopping Content API

[Jean1202]

Hi,

In GMC I have an alert for Automatic item updates active [price]. The samples seem to indicate that the Shopify content API feed shows prices without VAT while the VAT is included on the landing page, hence the warning. 

I have 386 products approved and the warning includes 116 of those (so far)...

It is odd that the content API would pick up the prices without VAT, am I right here?

If not, how can I correct this situation and make sure the API feed select the price including VAT?

I'm using the Google Shopping App. 

Thanks 

Jean

[JonWright]

Hi - pretty sure it's nothing to do with VAT. I use the Google Shopping App & am in the UK (so have VAT in my prices). I've just checked GMC and I have 15 products with the 'Automatic item updates active' warning (out of a few thousand). In my case the price sent in the API is higher than the price on my website and is out by various % (not 20%, the VAT rate in UK).

Also if if was to do with ex VAT then all my products would have that warning, not just a small %.

So not sure why it is happening but not VAT related. My guess is that we have changed the prices on those products recently and the API feed is simply out of date.

[Jean1202]

Thank you Jon,

In my case, all items concerned by this price warning are off by exactly 20%, I'm in the UK as well. 

And your right, if that was VAT related, all my products should be in warning, but only a 1/3 are in this situation. 

[JonWright]

Think I've worked out what is going on, at least in my case anyway. For all the products that I have that error on they have variants and Google appears to be picking up the price of the cheapest variant, rather than the actual variant in the feed.

For example, if I have a jacket in medium & large, at £70 & £75 respectively, Google is saying that it is been told by the feed that the large is £75 (which is correct) but it is £70 when they scan the website (and google is then showing that incorrect price in the shopping results).

Does that make sense? and is that the same for you?

[Jean1202]

I don't have that issue with my content api feed yet. I had it with my other feed via datafeedwatch, but a quick fix solved the issue (instructed the feed to replace the url by variant-url).