TL;DR
- Google's Merchant Center help page on automations now says products whose price or availability changes more than once per day may be disapproved instead of updated.
- Google may also stop automatic updates if the total number of detected mismatches becomes too large; the page gives no threshold or duration.
- PPC News Feed dated the help-page revision to 27 September 2026; Search Engine Roundtable reported it on 8 October 2026, and a 17 March 2026 archive copy has no such warning.
- For frequent repricing, the page now tells merchants to use the Merchant API, replacing its March 2026 suggestion of the Content API.
Google's Merchant Center help page on automatic item updates now warns that the feature "may not work for products with frequent price or availability value changes (for example more than once per day)", and that such a product "may be disapproved instead of updated" when Google detects a mismatch. The same paragraph adds that Google may stop updates altogether if the total number of detected mismatches becomes too large. The page also now points merchants with fast-moving prices to the Merchant API instead of the Content API. This was a documentation edit, not an announced product launch: PPC News Feed dated the revision to 27 September 2026, and Search Engine Roundtable reported it on 8 October 2026.
What changed on the automatic item updates help page
The page in question is titled "Allow Merchant Center to update product information automatically", published in the Google Merchant Center Help center. On the page, Google calls the feature "automations"; we refer to them below as Merchant Center automations. They let Google overwrite four attributes in your product data with what it finds on your own product pages: price, sale price, availability and condition.
The new warning sits in the "Notes" box under the benefits section. Read in full, it says three separate things:
- Automations may not work for products whose price or availability changes often, with "more than once per day" given as the example.
- If Google detects a mismatch on such a product, the product may be disapproved instead of updated.
- Google may stop updates if the total number of detected mismatches becomes too large.
The third point is the one to read twice. It is not limited to the fast-changing product. The help page does not define "too large", does not say whether the stop applies per product or per account, and does not say how long it lasts. Those details are simply absent from the page.
How the March 2026 version compared
Search Engine Roundtable noted that the document has many more edits than the warning and linked to an Internet Archive copy captured on 17 March 2026 for comparison. Reading that archived copy against today's page shows the frequent-change warning was not there in March. Several other sentences also changed between the two versions, which tells you how Google now wants merchants to think about the feature.
The table below lists the wording changes that can be checked directly in the two versions of the page.
| Topic | March 2026 archived version | Current live version |
|---|---|---|
| Fast-changing products | No warning about change frequency | May not work above about one change per day; product may be disapproved; updates may stop if mismatches become too many |
| Prices changing several times a day | Best practices said that if most products on your site update multiple times per day, automations "can help you avoid errors" | That best-practice line is gone; the Notes now warn automations "may not work" above about one change per day |
| Recommended tool for frequent updates | "Consider using the Content API to schedule product uploads" | "You should use the Merchant API to manage product updates" |
| What automations fix | "Temporary" accuracy problems; "avoid price, availability, and condition mismatches" | "Sporadic" accuracy problems; "avoid some price, availability, and condition mismatches" |
| Strikethrough prices | Price automations "will update" strikethrough prices | Price automations "may also update" strikethrough prices |
The pattern is consistent. In March the page promised to avoid mismatches. Now it promises to avoid "some" of them, and it describes automations as a patch for sporadic problems on a small share of products. Both versions already said automations "aren't a replacement for regular updates of your product data". The current version adds a stated consequence for leaning on them anyway, and drops the March best-practice line that pitched automations as a help for sites updating prices several times a day.
How automatic item updates work, as Google documents them
It helps to be precise about the mechanism, because the risk comes straight out of it. Pieced together from the help page, the process has three parts.
1. Your product pages carry the data
Google reads schema.org structured data on your landing pages. The mapping is fixed: the feed's price attribute maps to schema.org price and priceCurrency (either directly on the Offer or through priceSpecification), availability maps to availability, and condition maps to itemCondition. Prices must be plain numbers without currency symbols, thousands separators or spaces, such as "1498.99", and the currency must be a three-letter ISO 4217 code. For Thai merchants that means THB.
2. Extractors fill gaps when markup is missing
If a page has no structured data, or the markup is incomplete or wrong, Google says it relies on "advanced data extractors" that use statistical models and machine learning to read product data from the HTML. The page is candid about limits here: Google may not have extractor coverage for every domain, schema.org annotations may be disabled if they are not accurate, and if the extractors cannot determine price, availability or condition, the products are subject to product-level disapprovals.
3. Google compares and overwrites
Google finds products on the pages given in your link attribute and compares what it sees with your feed. The help page's own example: if your latest upload lists a product at $4 but the page shows $3, Google updates the product to $3 in your ads or free listings. Availability uses relaxed matching, so in_stock, preorder and backorder all count as compatible with in_stock.
Put those three parts together and the frequency warning makes sense. Automations are a correction layer that depends on Google seeing your page at a given moment. If the price on that page moves several times a day, the page Google saw and the page a shopper sees can differ again before the correction lands. Google's wording says that in this case it may stop treating the gap as something to fix and treat it as a reason to disapprove.
Where to find and change the setting
Automations are on by default. The help page gives this path in Merchant Center:
- Select Products.
- Select the Automations tab.
- Choose the automation you want to change (the page lists price, availability, condition and image improvements).
- Select View details and toggle updates on or off.
In a multi-client account, each sub-account has automations enabled, and sub-accounts can specify their own settings. Agencies and marketplace operators running many sub-accounts should check each one, not just the parent.
What a merchant should check now
None of the following requires guessing about Google's internals. Each item comes from the help page itself or follows directly from it.
How often your feed actually updates
Google's notes tell merchants to "continue to provide accurate product data frequently (for example, updating your product data source)". Look at how often your primary data source is fetched or uploaded compared with how often your store's prices change. If your store reprices hourly and your feed refreshes once a day, automations were carrying most of the weight, and that is the setup the new warning targets.
Whether you should be on the Merchant API
The current page says that if you expect pricing, availability and condition to update frequently, "you should use the Merchant API to manage product updates". The March version suggested the Content API. If your team or platform plugin still runs on the Content API, check with whoever maintains it what their plan is. The help page itself does not give a migration deadline, so do not read one into it.
Whether your price automation should be on at all
The page says that if product pages show multiple strikethrough prices, Google may not find the correct one, and "you shouldn't enable automatic updates for price in this case". Many sale templates show an original price, a member price and a sale price together. If yours does, the help page's own advice is to turn price automation off.
Sale price dates and time zones
The best-practices section asks merchants using sale_price to set sale_price_effective_date correctly, including the time zone, and to make sure any strikethrough value on the store matches the price attribute. A sale that starts at midnight Bangkok time but is dated in UTC opens a seven-hour window where the feed and the page disagree.
Diagnostics for disapprovals
The help page does not name a specific report, issue code or alert for the new disapproval behaviour. Watch your product-level issues in Merchant Center after price changes, and if disapprovals cluster on items you reprice often, the warning is the likely explanation.
What the source did not say
Reporting on a quiet help-page edit means being clear about the gaps. Google did not publish an announcement or blog post about this change that we could find; the evidence is the page itself and the dated revision noted by PPC News Feed's Hana Kobzová. The page does not say when enforcement started, whether it already applies to every market, what threshold counts as "too large", how long a stop on updates lasts, or how to get updates restarted. "More than once per day" is offered as an example, not a hard limit. Anyone telling you the exact number of changes that triggers a disapproval is going beyond the published text.
What this means for Thai marketers
The help page says nothing about Thailand. What follows is our reading of how the documented behaviour meets the way Thai online retail runs.
Thai e-commerce calendars are built around double-date mega-sale days such as 10.10, 11.11 and 12.12, plus payday sales. A store that runs flash deals changing price several times in a single day on those dates falls squarely within the "more than once per day" example in Google's note. A store that has relied on automations to catch the gap between a once-daily feed and an hourly-changing site now has a documented reason to expect disapprovals on the very products it is promoting hardest.
The practical response for 11.11 and 12.12 is to plan feed timing around the sale schedule. Push price changes into Merchant Center as they happen through the Merchant API or a more frequent data source refresh, set sale_price with correct Asia/Bangkok effective dates rather than editing the base price, and review whether price automation should stay on for SKUs with layered strikethrough prices. For Shopping and Performance Max campaigns, a disapproved hero product during a flash window is lost revenue that bidding cannot recover. Our e-commerce marketing and Google Ads management pages cover how feed health fits into campaign planning.
Frequently asked questions
Will Google disapprove my products if prices change more than once a day?
It may, if automations detect a mismatch on those products. The help page says automations "may not work" for products whose price or availability changes more than once per day and that such a product "may be disapproved instead of updated". It is a possibility described by Google, not a stated automatic rule.
When did Google make this change?
PPC News Feed dated the help-page revision to 27 September 2026, and Search Engine Roundtable reported it on 8 October 2026. An Internet Archive copy from 17 March 2026 does not contain the warning. Google did not announce it separately.
Should I turn automatic item updates off?
Not by default, because automations still correct sporadic mismatches and Google enables them by default. The help page does say to switch off price automation if your product pages show multiple strikethrough prices. For frequent repricing, Google's advice is to send updates through the Merchant API, not to rely on automations.
Does this apply to merchants in Thailand?
The help page does not limit the change to any country, but it also does not confirm rollout timing for any market. Treat the documented behaviour as applying to your account until Google says otherwise.
What does "updates may stop" mean?
Google says it may stop updates if the total number of detected mismatches becomes too large. The page does not define the threshold, the scope or the duration, so the only safe reading is to keep mismatches low through accurate, frequent feed updates.
Bottom line
Automatic item updates were always meant as a safety net, and Google's September edit now spells out what happens when merchants treat them as the main pipe: possible disapprovals on fast-moving products and a possible stop to updates. With 11.11 and 12.12 ahead, the time to check feed frequency, API setup and sale price dates is before the flash deals start. If you want a second pair of eyes on your Merchant Center setup before the next mega-sale, our team can help.
