Which integration guide are you following? The native VTEX connector or XML?
If you’re using the native connector and the Google Shopping configuration is enabled, the incorrect price being sent may be related to the Google Merchant configuration itself.
According to the documentation, to complete the integration, there are no mandatory settings that need to be configured in your Google Merchant Center account. However, to minimize errors, it is recommended that automatic item updates be disabled.
Disabling automatic updates prevents Google from changing your product prices, and this becomes handled exclusively by the VTEX Platform. So, after logging into Google Merchant Center, check that your account preferences are in line with this recommendation.
It’s also worth making sure there is only one active integration — if the native VTEX connector is active, the XML feed should be removed, and vice versa. The native app integration is the recommended approach.
If you’ve already set up Google Shopping on your VTEX account, just mark the cash price sending as YES, see here in this screenshot Screenshot by Lightshot — in this case it will pick up the lowest value shown on your site considering active promotions and the prices displayed on the product page.
Hi @Leidiane, thank you for your response.
I checked and the option is already marked as yes, but even so, the promotional price specified in the layout and configured on the platform doesn’t appear in Shopping.
Hello, @andremiani I’m doing it via API and via XML, and in both cases the promotional discounted price for cash payment via PIX did not reflect in Google Merchant.
Here’s a screenshot of the new XML I created, inserting price and sale_price.
It only brings one of the prices, even though in the layout I have both:
According to the VTEX track for setting up the Google Shopping integration.
It is inadvisable to configure both the XML and the native connector simultaneously, as this causes conflicts and inconsistencies in the information.
There might be something wrong with the price you’re setting as the sale price, and you may need to review your structured data markup, since Google reads that information — you can validate it here: https://validator.schema.org/
Either way, I would recommend using only one of the two integration methods to check whether you’re still experiencing this issue.
Hey @Renan8
On your product page, the schema markup is only reading the price, probably because you’ve done some customization and it can’t identify that field as the sale price. In the case of the PIX payment discount, the sale_price only actually changes when the customer reaches checkout and selects PIX as the payment method. There is a way to configure the store so that the default price is the PIX price — meaning the sale_price or price that Google reads will be the PIX value. Here’s the doc: Set a discount using the Checkout API
Just so we don’t leave the topic without a follow-up, we managed to find a solution and the price now correctly reflects the promotion on Google Merchant, along with the installment price. However, to our disappointment, it didn’t show up on Google Shopping with any kind of promotion highlight or anything like that, which was our goal — and when we spoke with Merchant support, they put up a lot of barriers.
We achieved a good part of our objective but ran into the Google giant.
Besides the API approach that Leidiane suggested, another way to do this would be by creating a new trade policy (usually a paid feature) and using that trade policy to pull the PIX prices as default prices, as well as using the same policy in the XML.