Problem with Merchant Feed and Prestashop

[A.Acero]

Hello everybody,

Google merchant rejects my products becauses is taking the price without taxes in my product sheet on prestashop. I have loaded a data feed with VAT included on price but all time Google decline my products.

Example for this product https://grupolasmimosas.com/tienda/sillas-para-ducha/silla-con-respaldo-orthoprim:

 

Price on feed=31.45EUR

Price read on the web=28.59EUR (this is the price without taxes on my backoffice)

 

Anybody can help me? 

Thanks all and  good day!!

[tdsoft]

Where is your feed?

Are you using a external module or use function from Prestashop's Default?

[A.Acero]

I update my feed from a CSV file directly on Merchant but the [price] is correctly wrote with tax included. I dont know how Google reads my Presta URL but all time read the price without taxes.

[apvd]

On 11/15/2019 at 10:01 AM, A.Acero said:

I update my feed from a CSV file directly on Merchant but the [price] is correctly wrote with tax included. I dont know how Google reads my Presta URL but all time read the price without taxes.

have you been able to resolve this issue? this could be related to the enabled countries and where google is indexing the page from.

[A.Acero]

10 minutes ago, apvd said:

have you been able to resolve this issue? this could be related to the enabled countries and where google is indexing the page from.

Hello, first of all thanks for your answer!!

 No one has been able to help me. To this day everything remains rejected and I am deseperate with this problem. I have been told the same about the other countries but nobody tells me HOW I should solve it. Could you tell me what should I do? 

[apvd]

That was a guess, I'm fighting now with it, I'm testing with tor connecting from other countries and the price is always correct, now I will experiment with this meta added on the price specification, I'll let you know if this works:

priceSpecification
        
@type UnitPriceSpecification
valueAddedTaxIncluded http://schema.org/True
price $pricewithvat
priceCurrency EUR

 

also, do you have a solid way to test this issue, and see what google sees? also google webmaster tools see the price correctly with vat..

Edited February 13, 2020 by apvd (see edit history)

[apvd]

if you go under international > localization > Geolocation and disable geolocation by ip address, you can show the default tax rules to everyone if that's your case:

 

I tested with Tor browser from an USA exit node and with or without the rule the price changes, if you want specific rules then you have to set new tax rules but here I don't know how to tell google "show this price for this state"

 

[Ivan N.]

16 hours ago, apvd said:

if you go under international > localization > Geolocation and disable geolocation by ip address, you can show the default tax rules to everyone if that's your case:

 

I tested with Tor browser from an USA exit node and with or without the rule the price changes, if you want specific rules then you have to set new tax rules but here I don't know how to tell google "show this price for this state"

 

I have the same issue. My tax rule is 20% VAT for all European countries, NO TAX for outside EU countries. When geolocation is enabled, the front end is showing up correct prices. I ve tested it from Germany, UK...etc. prices are VAT included. I did the same with an US and Australian proxy, prices are VAT excluded, as they supposed to be. Everything correct, except, the price in microdata is always VAT excluded. It does not follow the tax rules.

If you switch Geo off, then all prices in the price microdata are TAX included...which is fine for EU countries, but bad for non-EU countries, where the price needs to be VAT excluded. So, it seems to me, that if geolocation enabled, the price in microdata doesnt follow the tax rules at all. When you switch it off, it just ads the VAT, but does not deduct it where needed.

I ve been consulting it with Google, because my UK merchant account has been suspended for VAT not included in price and they told me to fix mi price snippet. They saw that the landing page and feed prices are correct (tax incl), but, the price in microdata was price exlcluded. Until this is fixed, they will not lift the suspension.

Apparently, there is no solution for this...

[apvd]

Hello Ivan,

so they told you that the same page had the price correct for EU countries but the microdata not? did they told you or you verified what microdata was incorrect, if the meta property or the itemprop inside the body?

   
 

<meta property="product:pretax_price:amount" content="{$product.price_tax_exc}">

<meta property="product:price:amount" content="{$product.price_amount}">

 

<div itemprop="offers" price="{$product.price_amount}" itemscope itemtype="https://schema.org/Offer">

 

[Ivan N.]

1 minute ago, apvd said:

Hello Ivan,

so they told you that the same page had the price correct for EU countries but the microdata not? did they told you or you verified what microdata was incorrect, if the meta property or the itemprop inside the body?

   
 

<meta property="product:pretax_price:amount" content="{$product.price_tax_exc}">

<meta property="product:price:amount" content="{$product.price_amount}">

 

<div itemprop="offers" price="{$product.price_amount}" itemscope itemtype="https://schema.org/Offer">

 

Hello apvd,

they only addressed the wrong price in microdata while they checked my website, so i assume the issue is "itemprop price" which is not following the tax rules.

This is what Google support said:

"Please check with the Structured Data testing tool item like https://www.watchexclusive.eu/en/lunokhod-2/482-vostok-europe-6s30-6204212-lunokhod-2-grand-chrono-watch-4260157443501.html?SubmitCurrency=1&id_currency=3&utm_campaign=Gshopping&utm_source=SRCshopping&utm_medium=MEDgshopping.
In the feed we see price is 614.12 GBP and sale price is 601.83 GBP. The same thing we can see on the website; however, when we check with Structured Data testing tool the price is shown 501.53 GBP. 

Regarding the automatic updates I am talking about this About automatic item updates to be turned off. Only the feed updates should be left on for automatic update. As right now I cannot submit the account and products for review as the issue of price mismatch still is in the website and feed."

Regards

[Martin C.]

On 2/14/2020 at 10:34 AM, Ivan N. said:

Hello apvd,

they only addressed the wrong price in microdata while they checked my website, so i assume the issue is "itemprop price" which is not following the tax rules.

This is what Google support said:

"Please check with the Structured Data testing tool item like https://www.watchexclusive.eu/en/lunokhod-2/482-vostok-europe-6s30-6204212-lunokhod-2-grand-chrono-watch-4260157443501.html?SubmitCurrency=1&id_currency=3&utm_campaign=Gshopping&utm_source=SRCshopping&utm_medium=MEDgshopping.
In the feed we see price is 614.12 GBP and sale price is 601.83 GBP. The same thing we can see on the website; however, when we check with Structured Data testing tool the price is shown 501.53 GBP. 

Regarding the automatic updates I am talking about this About automatic item updates to be turned off. Only the feed updates should be left on for automatic update. As right now I cannot submit the account and products for review as the issue of price mismatch still is in the website and feed."

Regards

Hi Ivan,

Did you manage to solve this problem?

I have the same problem and am not sure what to do. I've been struggling to solve it in many ways, but it still doesn't work. I'm also using the GeoIP module, but there is an option to ignore bots, so I don't think this is the problem. 

Thanks 

[José M.]

I've contacted to Merchant Center Support regarding this topic, as it's reading prices without tax from my website. I'll keep you informed.

[Nickz]

On 7/9/2021 at 5:52 AM, Martin C. said:

I have the same problem and am not sure what to do.

Did you manage to solve it?

[José M.]

11 hours ago, Nickz said:

Did you manage to solve it?

 

On 11/8/2021 at 5:43 PM, José M. said:

I've contacted to Merchant Center Support regarding this topic, as it's reading prices without tax from my website. I'll keep you informed.

 

After speaking at the phone with a representative at Google Ads, they told me this can happen due to daily updates with the feed. "When it updates everyday, it may not catch the data value on the web right." He recommended me setting it weekly. I set it weekly with the next update in 3 days from that moment, and it worked.

[apollux]

Either disable price pre tax or disable automatic updates in Merchant Center on Google. Once the auto updates have started, it will mismatch your file and reject your products. I personally disable pretax for my clients because, either way, it is mandatory in the EU to show the price VAT inclusive (if available). Google should also abide by that.

[jetx]

Indeed it's a pain. I have been dealing with this annoyance for years. What I did was to set all countries to the same Value Added Tax tax rate (Taxes/ Tax Rules/ edit, select all and apply same rate). Generate the feed (I usually manually update the file) and reset the tax rates (if you sell in other countries). 

 

 

[Quentin Fahrner]

I encountered this issue also. It seems that Google Merchant Center is extracting the price data from the tax excluded price metadata.
I'll try to remove it and see if it fixes the issue.

[apollux]

On 3/15/2022 at 3:50 PM, Quentin Fahrner said:

I encountered this issue also. It seems that Google Merchant Center is extracting the price data from the tax excluded price metadata.
I'll try to remove it and see if it fixes the issue.

It doesn't if it already started to automatically update prices. It will deactivate all your products. The best way to tackle this is the update stocks automatically on Merchant Center, not prices. The price should be handled by your feed file.

[Quentin Fahrner]

In my situation the problem was caused by https://addons.prestashop.com/fr/analyses-statistiques/23806-google-tag-manager-enhanced-ecommerce-ua-pro.html
Removing the mentions to "price_tax_exc" in the module exposed data fixed the problem in Google Merchant Center.