Merchant Center price mismatch: Google's page says automatic updates may fail when a price changes more than once a day

Google’s Merchant Center help page on automatic updates says the feature “may not work” for products whose price or availability changes often, and it gives “more than once per day” as its example.¹ Automatic updates are Google’s safety net for a product feed, the file of product data a merchant sends to Google, when the feed lags behind the product page.

My reading, not either company’s, is that the crossed-out price now has two machine readers. Google’s system reads it off the product page and warns it may pick the wrong one when a page shows several, while Shopify sends it from the catalog to AI shopping agents.

This is a desk piece. I read the pages quoted here on October 12, 2026 and ran no test of my own, so every claim below is what a page says. The remedy the page gives is a faster feed, and nothing on it asks merchants to change prices less often.

Google’s page names one example of frequent change, more than once per day, and says the product may be disapproved if a mismatch is detected.

What does Google’s page say about prices that change more than once a day?

Google’s Merchant Center help page on automatic updates says automations “may not work for products with frequent price or availability value changes (for example more than once per day).”¹ Merchant Center is the Google tool where merchants send product data to the places product listings appear on Google. The page does not say a changing price breaks anything by itself. It says one Google feature, automatic updates, becomes unreliable for those products.

The same page describes what the feature is for. “Automations aren’t a replacement for regular updates of your product data,” it says, and they are “designed to fix sporadic problems with your price, availability, and condition accuracy for a small percentage of your products.”¹ To find those problems, Google “finds products on the product pages provided in the link attribute.”¹ The link attribute is the link field in your feed, which holds each product’s page address.

Whether the more-than-once-per-day sentence is recent is not something I could check. The page shows no last-updated date, and I read no archived copy, so I say only that the page says it. The Deal Ends badge article on this site cites the same page for a different claim.

Does Google disapprove a product for changing its price more than once a day?

Google’s page does not say a product is disapproved for changing price more than once a day. It says “the product may be disapproved instead of updated if we detect a mismatch,” where a mismatch means the price on the product page differs from the price in the feed.¹ The disapproval follows the detected mismatch. The number of price changes is only the page’s example of when automatic updates may fail to catch one.

The page adds a second limit. “We may also stop updates if the total number of detected mismatches becomes too large.”¹ It gives no figure for “too large”, and I searched the page text for a threshold and found none. A separate sentence warns that if Google’s page readers cannot determine price, availability or condition, “your products will be subject to product-level disapprovals.”¹

What does Google tell merchants with fast-changing prices to do?

Google tells them to send the changes themselves. The page says “If you expect the pricing, availability, and condition of your products to update frequently, you should use the Merchant API to manage product updates.”¹ The Merchant API is Google’s programming interface for pushing product data straight into Merchant Center. So the answer to faster price changes on this page is a faster feed, not slower prices.

My read, which is not Google’s wording, is that the safety net and the feed do different jobs. Automatic updates repair sporadic errors by reading the page after the fact. A feed that arrives as fast as the price changes keeps the two copies from drifting apart in the first place. A different problem, products that are approved but get no traffic, is covered in the eligible-not-distributed gap article.

Who else reads a price, and from where?

At least four systems read a product’s price, and each reads a different copy of it. Google’s automatic updates read the product page. A feed or Merchant API push carries the merchant’s own data. AI Mode, Google’s conversational search mode, can monitor changing information on request. Shopify Catalog sends a store’s prices to AI shopping agents. That list is my synthesis from four sources, not a list any one of them gives.

The table lists each reader, where it gets the price, and what its own source says happens when its copy disagrees with the page.

Reader of the price	Where it reads the price	What the source says about a disagreement
Google’s automatic updates	The product page, at the address in the link attribute	The product “may be disapproved instead of updated,” and updates may stop if detected mismatches become too large
A feed or Merchant API push	The merchant’s own product data, as sent	Not stated on the automatic updates page, which names this as the route for frequent changes
AI Mode monitoring	Sites, forums, social posts, real-time data sources and the Shopping Graph	Not stated in the post
Shopify Catalog sending prices to AI agents	The store’s compare-at price, sent only if higher than the current price	Not stated on Shopify’s help page

Three of the four sources say nothing about a disagreement, so the cost in those cases is unknown and not zero.

On AI Mode, Robby Stein posted on September 28, 2026 that Google is rolling out info monitoring to everyone globally. In his words, Search “will continuously check across changing info on the web like sites, forums and social posts, our real-time data sources, and Shopping Graph”.² The post lists “Back in stock & price drop updates” among the topics it suits.²

I read the post’s full text and did not watch its attached video. It says nothing about what happens when a monitored price differs from a merchant’s feed.

Why might Google’s warning and Shopify’s change be about the same field?

Google’s page and Shopify’s changelog both concern the crossed-out price, also called the strikethrough, compare-at or “was” price, though the link between them is my reading and not either company’s. Google’s page warns that “If product pages show multiple strikethrough prices, our system may not be able to accurately find the correct strikethrough price,” and adds “You shouldn’t enable automatic updates for price in this case.”¹ Shopify sends a crossed-out price to a second set of readers.

Shopify’s changelog, dated October 9, 2026, says “Shopify now shares your compare-at price with AI shopping agents through Shopify Catalog, so AI agents can see when a product is marked down.”³ It adds that “Previously, AI agents reading Catalog only saw the current price and markdown prices displayed in storefront were not shown.”³

Shopify’s help page says Catalog sends a compare-at price “only if it’s higher than the product’s current price,” and that AI agents “might use it to advertise strikethrough pricing.”⁴

So one field, the “was” price, is read by two systems from two places. Google reads it off the page, and Shopify’s agents get it from the store’s catalog. Neither source says the two copies are ever compared, and I have not tested whether they disagree.

Merchants can turn the sharing off. The changelog says to find the toggle “in the ‘Compare-at’ section” of admin.³ The help page says a store “starts with a default selection” and does not say which way it points, so the answer is not stated.⁴ The argument about defaults is in the catalog sharing article.

What should a merchant check after reading these pages?

Three checks follow from Google’s automatic updates page and Shopify’s changelog and help page, and none needs a special tool. First, count how many products in your feed change price more than once a day, since those are the ones the page says automatic updates may not catch. Second, open a sale product page and count the crossed-out prices on it. Third, look at the Compare-at toggle in Shopify admin and read which way it is set.

If the first count is above zero, the page’s own advice applies. Send those price changes through the Merchant API so the feed does not rely on Google reading the page.¹ If a page shows several crossed-out prices, the page says not to enable automatic updates for price on those products.¹

What would change the read of Google’s automatic updates page?

Two things would sharpen the read of Google’s automatic updates page. Google naming how many detected mismatches count as “too large” would let a merchant plan around the limit, because the page gives no figure. An earlier copy of the page would show whether the more-than-once-per-day sentence is old or recent, and I make no claim either way.

A third gap sits outside Google. Neither the AI Mode post nor Shopify’s pages say what an AI surface does when its copy of a price disagrees with the product page. Until one of them does, the safest reading is the plain one, which is only what each page says.