Should you really enable automatic updates for prices and stock in Merchant Center?

Why is Google offering this option now?

Merchant Center and your website operate on two different rhythms. Your catalog may change every hour—flash sales, out-of-stock items, price adjustments. Meanwhile, Merchant Center retrieves your data via a feed that you upload once or twice a day, sometimes less.

The problem? Between two feed updates, Google detects discrepancies: the price displayed on the site differs from the feed, a product marked in stock when it is no longer available. The result: warnings, item suspensions, loss of Shopping visibility. Google thus proposes to reverse the logic: instead of penalizing you for desynchronization, it will crawl your site in real-time and automatically update pricing and availability in Merchant Center.

How do automatic updates work in practice?

Google crawls your product pages and extracts structured data (schema.org Product, price, availability). If this data differs from the Merchant Center feed, Google updates it automatically in your account rather than reporting a discrepancy.

This is a major shift: you delegate to Google the synchronization of critical data for your Shopping campaigns. The advantage? Zero manual intervention, zero risk of suspension for desynchronized prices. The downside? You lose total control over what is displayed in Merchant Center—and the quality of Google's crawl becomes your single point of failure.

Which e-commerce merchants are really affected?

This feature mainly targets hyper-dynamic catalogs: marketplaces, fast-fashion sites, retailers with daily promotions, sellers of perishable or seasonal products. If your stock changes multiple times a day and you cannot sync a feed in real-time, you are in the target.

On the other hand, if your catalog evolves slowly (furniture, industrial equipment, services) and you already upload a daily feed without issues, this option provides no tangible benefit. You just add a layer of complexity and dependency on Google's crawl.

• Optional Activation: this feature is not mandatory, you retain the choice to manage your feeds manually.
• Google Crawl Drives the Update: if a product page is not crawled, the data will not be refreshed in Merchant Center.
• Essential Structured Data: without proper schema.org Product markup, Google cannot extract prices and availability correctly.
• Risk of Reverse Desynchronization: if your markup is misconfigured, Google might propagate errors in Merchant Center instead of correcting discrepancies.
• Impact on Shopping Campaigns: data freshness potentially improves click-through rates and reduces cart abandonment due to incorrect pricing.

Is this feature truly a solution or just a band-aid?

Let’s be honest: this option addresses a symptom, not the root cause. The real issue is that many e-commerce merchants have never set up real-time synchronization between their ERP and Merchant Center. They still upload CSVs manually or via nightly cron jobs. Google offers them a crutch to avoid suspensions, but this does not replace a modern feed architecture.

Second point: you are handing over the responsibility of data freshness to Google. And Google crawls according to its own schedule, not yours. If a product page is crawled once a day, your price may remain outdated in Merchant Center for 24 hours. You gain automation, but you lose predictability. [To be verified] Google does not document anywhere the guaranteed crawl frequency for this feature.

What concrete risks should you anticipate?

The first risk: conflict between feed and crawl. If you upload a daily feed AND enable auto-updates, which takes precedence? Google states that the crawl overrides the feed for pricing and availability, but what about other attributes (GTIN, description, category)? No clear documentation.

The second risk: markup errors propagated at scale. Imagine a bug on the site that shows all prices as €0 for an hour. If Google crawls at that moment, it could update thousands of products in Merchant Center with price = €0. You end up with Shopping campaigns displaying absurd prices, without having touched the feed. This is a scenario I have seen occur in production—and it’s not theoretical.

In which cases is it better to disable this option?

If you already have a Content API feed synchronized in real-time with your ERP, this function is redundant and risky. You introduce a second update channel that could create conflicts. Maintain full control via API.

Similarly, if your catalog contains sensitive or regulated data (pharmacy, finance, embargoed products), allowing Google to automatically update your prices and stock without human validation is a legal liability you transfer to a third party. Not recommended.

What should you do before enabling this function?

First step: audit your structured data. All your product pages must expose valid schema.org Product data, including price, priceCurrency, availability, and ideally GTIN. Test with Google’s rich results test tool—not just on one page, but on a representative sample of your catalog.

Second step: check the current crawl frequency. Go to Search Console, crawling statistics section, filter by product page type. If Google only crawls your product sheets once every 3 days, this functionality won’t provide you with real-time freshness. You will first need to improve crawlability (sitemap, internal linking, crawl budget).

What mistakes should you absolutely avoid?

Mistake #1: enabling the function and completely disabling the manual feed. Keep a backup feed uploaded daily via Content API or SFTP. If the crawl fails or slows down, you have a safety net.

Mistake #2: not monitoring discrepancies after activation. Google may crawl and extract incorrect data due to a markup bug, a poorly configured A/B test, or poorly indexed dynamic JavaScript content. Monitor Merchant Center reports and compare them with your source of truth (product database).

How can you check if this automatic update works correctly?

Set up a differential monitoring: export Merchant Center data (pricing, availability) daily via API and compare it with your product database. Any discrepancy exceeding a defined threshold (for example, 5% of desynchronized products) should trigger an alert.

Also, test the propagation delay: manually change the price of a product on your site, measure how long it takes Google to crawl the page and update Merchant Center. If the delay exceeds 24 hours, this function is not suited to your synchronization needs.

• Audit structured data schema.org Product on 100+ representative product pages
• Check the current crawl frequency in Search Console (crawling statistics)
• Maintain a parallel daily feed via Content API or SFTP as a safety net
• Set up differential monitoring between Merchant Center and product database (alerts > 5% discrepancy)
• Test the propagation delay from crawl to Merchant Center update on a sample
• Document the priority between uploaded feed and automatic crawl (test in case of conflict)