Merchant Center Price-Change Disapprovals (October 2026): What Small Online Stores Should Diagnose Before Black Friday

Google revised its Merchant Center help page on automatic item updates to warn that products whose price or availability changes “more than once per day” may be disapproved instead of updated. Hana Kobzova of PPC News Feed dated the revision to September 27, 2026, and Barry Schwartz flagged it on Search Engine Roundtable on October 8, seven weeks before Black Friday.

The products most likely to be switched off are the ones you reprice most often, which are usually your best sellers. Below: the symptoms to look for, what each means, and a fix a two-person team can finish before Q4.

What did Google change in Merchant Center automatic item updates?

Google added language saying automations “may not work” for products with frequent price or availability changes, and that such products “may be disapproved instead of updated” when Google detects a mismatch. The page also says Google may stop updates altogether “if the total number of detected mismatches becomes too large.”

Automatic item updates are on by default. Google crawls your product page, reads the price, sale price, availability and condition (from schema.org markup, or by machine-learning extraction when the markup is missing), and quietly corrects your Shopping listing when it doesn’t match your feed. Schwartz linked a March 17, 2026 archived copy for comparison and noted the page carries other edits too.

Why does changing prices often cause a disapproval?

Each price change opens a gap between your feed and your page, and each gap is a chance for Google to catch a mismatch before it can correct it. If prices change often enough, the gaps overlap and the correction never catches up.

Your feed sends a price at fetch time. Your repricing app changes the page an hour later. Google’s crawler visits at some point after that, sees the new price, and overwrites the listing. Change it once a day and the overwrite holds and everything reconciles. If it changes three times a day, Google’s corrected value may already be stale by the time a shopper clicks. So Google stops correcting the item and disapproves it.

That model lets you predict cases the help page doesn’t spell out. A one-of-a-kind vintage listing that goes from in stock to sold once is fine, because that’s one change. A product at one or two units, where a stock app flips it between in_stock and out_of_stock as carts are held and released, is at risk even though the price never moves. Google treats preorder and backorder as compatible with in_stock, so those swaps don’t count as mismatches. Flips to out_of_stock do.

How do you know if your store is affected?

Look for three symptoms: disapprovals clustered on your most-repriced products, mismatch-related item issues that keep coming back after they clear, and Shopping clicks dropping on SKUs that still show as active in your store. Each one points to a different cause.

• Disapprovals concentrated on repriced SKUs. If the flagged items line up with what your repricing app touches, that’s the frequent-change rule. Fix the repricing cadence, not the feed.
• Mismatch issues that clear and then come back. This means the automation is correcting the item and then losing the race again. It’s an early warning before an outright disapproval.
• Mismatches on products you never reprice. This usually isn’t frequency at all. Check for a product page whose default variant shows a different price than the feed item, or structured data that marks up the wrong price.
• Many items losing updates at once. This fits Google’s “too large” clause, which applies at a scale above any single item. Google publishes no threshold, so treat any account-wide drop as urgent.

Is constant repricing actually helping a small store?

Usually not. Looked at through price anchoring, frequent repricing wears away the reference price that makes your discounts work, and Google’s rule now adds a distribution penalty on top. I chose this lens on purpose. Through a direct-response lens, the fix is technical: sync faster so Google keeps up. Through price anchoring, the fix is strategic: change prices less often.

Price anchoring says buyers judge a price against the reference they’ve already seen. A $38 bag of single-origin coffee reads as a deal only if shoppers have seen it at $44. A store whose repricing app nudges that bag between $39.20, $41.10 and $38.75 across a day never sets an anchor. It just teaches shoppers to wait. Small stores rarely win that race against marketplaces anyway, and now the habit carries a distribution cost.

I’d also push back on how Google describes this. The help page calls it an automation limitation. Read alongside the “too large” clause, it’s closer to a trust policy: Google is keeping the right to decide that a merchant’s prices are too unstable to show, without saying where the line is. Stores with stable prices lose nothing and keep the safety net. Stores that reprice dynamically lose it exactly when they need it most, during promotions. Accurate prices are a fair goal, but a rule with no published threshold can only be managed by staying well below it.

What does this cost a small store in Q4?

For a store that reprices its best sellers, it can cost the majority of its Shopping revenue for as long as the disapproval lasts. Here is an illustrative example.

A two-person supplement store carries 120 SKUs. A competitive repricing app adjusts 25 of them up to three times a day, and those 25 drive roughly 60% of Shopping revenue. The store spends $90 a day on Shopping at a 4x return, so about $360 a day in sales. Disapprove those 25 items in the week of November 23 and it loses about $215 a day in its busiest week. Nobody checks Merchant Center daily, so the store finds out when Black Friday comes in low.

How should a small team fix this before Black Friday?

Change prices at most once a day, schedule promotions in the feed instead of overwriting prices, and check weekly through Cyber Monday.

1. Check your automations. In Merchant Center, go to Products, open the Automations tab, and confirm which of price, availability and condition are on. They’re on by default, and each sub-account in a multi-client setup has its own settings.
2. List your fast movers. Export 14 days of price history from your repricer and mark every SKU that changed more than once in a day.
3. Set a daily limit. Configure the repricer to make at most one change per day, at a fixed time ahead of your feed sync. If it can’t, exclude your top 20 revenue SKUs.
4. Move promotions to scheduled sale prices. Instead of overwriting price, submit sale_price with sale_price_effective_date in ISO 8601 format with a timezone, for example 2026-11-27T00:00-0500/2026-11-30T23:59-0500. Google knows the change is coming, and your regular price stays visible as the anchor.
5. Fix variant pages. Make sure the price in each product page’s structured data matches the feed item it belongs to, especially when the default variant differs from the one you advertise.
6. Turn off price automation if your pages show several strikethrough prices. Google’s documentation says to, because the automation can rewrite strikethrough values.
7. Calm down low-stock flips. If your inventory app marks items out of stock at a threshold of one or two units, raise the threshold or switch to backorder where you can actually fulfil it.
8. Book a weekly check. Review item issues for 15 minutes every Monday until December 1.

If you’re also planning Q4 bid strategy, set the pricing cadence first. The decisions in our breakdown of Google Ads Promotion Mode before Black Friday assume your products are eligible to serve in the first place.

Which dates matter between now and Cyber Monday?

Finish your pricing rules by mid-November, so any disapprovals show up and clear before Black Friday week.

• September 27, 2026: help page revised, per PPC News Feed.
• October 8, 2026: change reported on Search Engine Roundtable.
• October 31: Halloween, a low-stakes test of scheduled sale prices.
• November 13: a suggested internal deadline (not a Google date) to lock repricer limits and load Black Friday sale dates into the feed.
• November 27 to 30: Black Friday through Cyber Monday, when competitor repricing is heaviest and disapprovals cost the most.

If margin matters as much as volume this season, pair this with our Product Value Optimization margin playbook, since stable prices also make margin-based bidding easier to trust. If you plan Q4 campaigns in CampaignPress.ai, add these dates to that plan, but the fix itself takes a repricer setting and a feed column.

FAQ

Does Google define “frequent” price changes?

Only loosely. The help page gives “more than once per day” as an example and doesn’t set a hard count. It also doesn’t say how many mismatches make the total “too large” before Google stops updates. Keep each product to one change per day at most, and schedule known promotions with sale price dates rather than editing the live price.

Should I just turn automatic item updates off?

Not as a first move. The automation still fixes the occasional mismatch for stores with stable prices, which is most small stores. Turning it off doesn’t make a mismatch acceptable. It only removes the correction. The exception is pages showing several strikethrough prices, where Google recommends turning price automation off.

Do availability changes count, or only price?

Both are named. The wording covers frequent “price or availability” changes. Google treats in stock, preorder and backorder as compatible, so swapping between those isn’t a mismatch. Flipping between in stock and out of stock several times a day is the pattern to watch, and it’s common on low-inventory products managed by stock-threshold apps.

Will scheduled sale prices still show a discount to shoppers?

Using sale_price with sale_price_effective_date is Google’s supported way to run a time-limited discount. Your regular price stays in the feed as the reference, and the sale value applies only within the dates you set. Whether a sale annotation appears is Google’s call, but it’s the method least likely to trigger a mismatch.