Skip to content
All posts
Platform UpdatesRevenue Protection

Google Merchant Center's September 2026 overhaul: Three changes that could silently break your shopping campaigns

Dan Garner··Updated 28 July 2026
Google Merchant Center's September 2026 overhaul: Three changes that could silently break your shopping campaigns

Google Merchant Center is about to get significantly busier for eCommerce teams. Between now and the end of September 2026, three separate changes will take effect, and the overlap between them creates a compliance challenge that most merchants aren't prepared for.

Taken individually, each update looks manageable. Taken together, they represent a compounding risk to your Shopping campaign performance that, without proactive monitoring, could quietly drain your paid-media budget before you notice something's wrong.

What's changing, and why it matters

1. Policy consolidation: One rulebook, new scrutiny

On July 15, Google announced that in September 2026 it will consolidate its Shopping ads and free listings policies into a single set of Shopping policies. Google has stated this is an organisational change, not a substantive tightening. No new restrictions are being added.

But here's the catch: consolidation often surfaces enforcement gaps that previously slipped through because different policy sets were evaluated independently. When Google's compliance systems begin evaluating products against a unified rulebook, products that were technically compliant under one set but borderline under the other may trigger fresh disapprovals.

For merchants operating across both Shopping ads and free listings, the transition window is the highest-risk period, the weeks where enforcement calibration is still settling.

2. New required attribute: Minimum order value

Starting September 30, 2026, Google Merchant Center will require merchants selling in the EU, UK, and Switzerland to include the new minimum_order_value attribute in their product feed requirements. This attribute specifies the minimum spend required for a customer to purchase and ship an order.

This isn't optional. If your store enforces a minimum order value and you sell into these markets, omitting this attribute from your feed after the deadline will result in product disapprovals. And here's the subtle problem: many merchants enforce minimum order values through their storefront logic (cart rules, checkout validation) but have never needed to declare it in their feed data. The disconnect between what your store does and what your feed says is exactly the kind of gap that triggers disapprovals.

3. Stricter out-of-stock landing page requirements

Google has also tightened the rules around out-of-stock product pages. Previously, merchants could hide the buy button entirely on out-of-stock items. Now, Google requires that the buy button remains visible but is clearly disabled, greyed out, not hidden or removed.

This is a landing page compliance issue that directly intersects with your product feed. If your feed says a product is available but the landing page shows it as out-of-stock with a hidden buy button, you face a double penalty: an availability mismatch and a landing page policy violation. Google explicitly notes that price and availability mismatches between feed and landing page remain the top cause of preemptive item disapprovals.

The compounding risk

Each of these changes introduces its own failure mode. But the real danger is how they compound:

  • A product goes out of stock. Your inventory system updates, but your storefront theme hides the buy button instead of greying it out. Your feed still shows the product as in stock because the sync lags behind.
  • You sell into Germany and enforce a €25 minimum order, but your feed doesn't include the new minimum_order_value attribute.
  • Policy consolidation means both of these issues are now evaluated under a unified compliance framework, and Google's crawlers catch them simultaneously.

The result? Multiple disapprovals across your catalogue, reduced impression share, and wasted budget on campaigns promoting products that Google has quietly pulled from auction. You won't get an error in your checkout flow. You won't see a broken page. You'll just see your Shopping performance slowly deteriorate, and by the time you investigate, you may have lost weeks of visibility.

What eCommerce teams should do now

With two months before the September 30 enforcement deadline, there’s still time to get ahead of this. Here’s where to focus:

1. Audit your out-of-stock page behaviour. Load a product page for an out-of-stock item. Is the buy button greyed out, or is it hidden? If hidden, your theme or platform needs updating before September.

2. Check your feed for the minimum_order_value attribute. If you sell into the EU, UK, or Switzerland and enforce any minimum order threshold, this attribute must be present in your feed by September 30.

3. Review your inventory sync frequency. How quickly does your feed reflect stock changes? If the lag is more than a few hours, you're exposed to availability mismatch disapprovals.

4. Set up continuous monitoring. Don't rely on periodic manual checks. The intersection of feed data, landing page behaviour, and Google's policy enforcement is too dynamic for spot audits.

Why this requires continuous monitoring

That last action item deserves elaboration, because the nature of this compliance risk is what makes it so difficult to manage manually.

The challenge with Merchant Center compliance is that it’s a moving target. Your feed data, your landing pages, your inventory status, and your storefront behaviour all need to stay in sync, not just at the moment you submit your feed, but continuously, because Google’s crawlers check your landing pages independently and on their own schedule.

Manual feed audits catch problems after they’ve already caused disapprovals. What merchants need is real-time awareness of the gaps between what their feed promises and what their storefront delivers.

AuditIQ eCommerce monitoring tool continuously tracks your storefront, not just your feed data, but the actual pages your customers and Google’s crawlers see. It detects mismatches between declared availability and on-page behaviour, identifies landing page compliance issues like hidden or missing buy buttons, and alerts you to feed-to-storefront discrepancies before they escalate into disapprovals.

The September 2026 Merchant Center changes aren't dramatic individually. But their overlap creates a compliance surface area that most eCommerce teams aren't watching closely enough. The merchants who avoid disruption will be the ones who catch the mismatches early.

Book a free AuditIQ demo to see how continuous storefront monitoring catches the feed-to-landing-page gaps that silently waste your paid-media budget.

About the author

Dan Garner writes from AuditIQ's experience monitoring eCommerce performance, SEO, security, and reliability issues across Magento, Shopify, WooCommerce, and Adobe Commerce stores.

Google Merchant Center's September 2026 overhaul: T...