The Google Merchant API migration is mandatory for every ecommerce brand that uses programmatic product feed management, and the deadline is August 18, 2026. On that date, Google permanently shuts down the Content API for Shopping. Any system still running on the old API stops syncing product data, which means listings disappear from Google Shopping and Performance Max campaigns stop serving. This post explains exactly who is affected, what the migration requires, and what to do before the deadline.
Is your Google Shopping feed built to survive the migration?
We manage Google Shopping and Performance Max for ecommerce brands, including feed architecture, migration readiness, and ongoing optimization.
The Quick Take
| Content API for Shopping (Old) | Google Merchant API (New) |
|---|---|
| Shuts down August 18, 2026 | Generally available since summer 2025, now primary API |
| Legacy architecture | Rebuilt on Google’s API Improvement Principles (AIP) |
| Feed labels require manual reconnection after migration | Feed labels must be verified and reconnected to campaigns |
| File uploads and Google Sheets not affected | Only programmatic API integrations require migration |
| No AI-powered optimization features | Supports AI product optimization and batch processing |
The Takeaway: The Google Merchant API migration is not optional, and brands that delay past August 18, 2026 risk losing every product listing from Google Shopping overnight.
💡 Pro Tip: Complex migrations with custom scripts and third-party reporting dashboards require 16 to 20 weeks of planning and testing. If your setup is anything beyond a basic Shopify feed, start now. Brands that wait until July are running straight into their peak summer selling window with an untested system.
Table of Contents
→ Who Does the Google Merchant API Migration Actually Affect?
→ The Two Deadlines You Need to Know
→ How to Check Whether You Need to Migrate
→ What Actually Changes in the New Merchant API
→ What Shopify and Platform Users Need to Do
→ Migration Steps for Ecommerce Brands
→ The Bottom Line on the Google Merchant API Migration
→ FAQ: Common Questions About the Google Merchant API Migration
Who Does the Google Merchant API Migration Actually Affect?
The migration affects every ecommerce brand that uploads product data to Google Merchant Center programmatically through an API integration. This includes custom-built feed scripts, third-party feed management platforms, and any reporting dashboards that pull data directly from the Content API.
Brands that upload products through manual file uploads (CSV or XML), scheduled fetch, or Google Sheets are not affected by this deadline. The migration applies only to programmatic API connections. If you rely on a platform like Shopify, WooCommerce, or a feed tool like DataFeedWatch or Feedonomics, the migration status depends on whether that platform has already updated its integration.
The brands most at risk are those running custom scripts, proprietary data pipelines, or older third-party integrations that have not yet confirmed their migration plans. If you have not received a migration confirmation from your feed platform or developer, assume the work is still pending.
The Two Deadlines You Need to Know
Google set two separate deadlines for this migration, and one has already passed. Understanding both clarifies the urgency for anyone still on the old system.
| Deadline | Who It Affects |
|---|---|
| February 28, 2026 (passed) | Beta users of the Merchant API v1beta who had not yet moved to v1. This version shut down on February 28, 2026. |
| August 18, 2026 (active) | All remaining Content API for Shopping users. This is the full shutdown date. Any system still on the old API stops working entirely after this date. |
💡 Pro Tip: Google began sending warning notices to affected Merchant Center accounts in January 2026. If you received one of those emails and have not acted on it, your account is on the clock. Log into Merchant Center and check your Data Sources now.
How to Check Whether You Need to Migrate
Google built a straightforward way to check your API status directly inside Merchant Center Next. Navigate to Settings, then Data Sources, and look at the Source column for each data source. If any source shows “Content API” in that column, you need to migrate before August 18.
If your data sources show a feed file, Google Sheets, or a platform name like Shopify, you are likely not affected by this specific deadline. The key word is “likely” because some platform integrations still route data through the Content API on the backend, even when the interface looks like a standard feed.
The safest move is to contact your platform or feed management vendor directly and ask for written confirmation that their integration uses the Merchant API v1. Do not assume an automatic update happened without verification. According to Google’s official Merchant Center announcement, the shutdown is firm and non-negotiable.
What Actually Changes in the New Merchant API
The Google Merchant API is not a renamed version of the Content API. Google rebuilt it from the ground up using its API Improvement Principles, which means the structure of requests, resource identifiers, and data formatting all changed.
For ecommerce brands managing their own integrations, the most important operational change involves feed labels. Feed labels do not automatically transfer during migration. If your Shopping campaigns or Performance Max campaigns use feed labels for campaign targeting, those labels need manual reconnection after migration. Skipping this step causes campaigns to stop serving, even if the feed itself migrates successfully.
The new API also removes the channel field that the Content API used to distinguish online versus local inventory. The Merchant API replaces it with a legacyLocal boolean for physical store products. Online-only products do not need this field at all, but any custom integration that currently passes a channel value needs to update that logic.
The practical upside of the new architecture is real. The Merchant API processes inventory and pricing updates faster, supports AI-powered product optimization, and enables more granular control over product attributes. These improvements matter for ecommerce brands that connect their feed to Google’s AI product recommendations, an area we cover in detail in our guide to Google Shopping strategy for ecommerce brands.
What Shopify and Platform Users Need to Do
Most major ecommerce platforms are rolling out Merchant API updates, but automatic does not mean guaranteed. Shopify, WooCommerce, Shopware, and similar platforms have stated they plan to provide updated integrations. The critical question is whether the update applies to your specific version, app, or plugin configuration.
For Shopify merchants using the native Google channel app, Shopify controls the API integration and should update it automatically. The risk comes from merchants using third-party Google Shopping apps from the Shopify App Store. Those apps update on their own schedules, and some smaller developers may not hit the deadline.
The action item for platform users is straightforward: check with your app or plugin vendor now, confirm their migration timeline, and test your feed functionality after any update deploys. Do not wait for August to verify the integration is working. Run a feed test in a sandbox environment at least 60 days before the deadline to leave time for troubleshooting.
💡 Pro Tip: Feed quality directly determines impression share and AI product recommendation eligibility. The migration is the right moment to audit your full attribute set, not just swap APIs. Brands that use this transition to clean up titles, GTINs, and missing attributes come out of migration with better-performing feeds than they started with. Our Google Shopping strategy guide covers the full feed optimization framework.
Migration Steps for Ecommerce Brands
A structured migration plan is the only way to avoid disruption during a transition this complex. The steps below apply to brands managing their own API integrations or working with an agency on custom feed infrastructure.
- Audit your current setup. Identify every system that touches your product feed: custom scripts, reporting dashboards (Looker Studio, Google Sheets, Tableau), third-party tools, and agency integrations. Log each one and confirm whether it uses the Content API.
- Contact every vendor. Request written confirmation of migration status and expected completion date from every third-party platform or tool in your stack.
- Assign a technical lead. Someone needs to own the migration timeline. Agencies managing your feed should designate a point of contact for this work specifically.
- Test in a sandbox first. Google provides a sandbox environment for the Merchant API. Validate all scripts and data pipelines there before touching your live account.
- Reconnect feed labels. After migration, manually verify every feed label used in Shopping and Performance Max campaign targeting. Confirm campaigns continue serving before closing out the migration.
- Set a completion target of June 2026. This gives brands with Q4 focus adequate buffer to find and fix issues before the September-December peak window opens.
High-complexity setups with multiple custom integrations should plan for 16 to 20 weeks of total migration time. Per migration planning guidance from ALMcorp, brands that start in May 2026 are cutting it dangerously close. The August 18 deadline is not a suggested target. It is a hard shutdown.
The Bottom Line on the Google Merchant API Migration
The Content API for Shopping shuts down permanently on August 18, 2026, and any ecommerce brand still running on it loses their product listings that day. This is not a soft deprecation with a grace period. Google set a firm date and has been sending account-level warnings since January 2026.
The brands that treat this migration as a routine deadline will move fast, test thoroughly, and reconnect their campaign feed labels before summer. The brands that treat it as someone else’s problem will discover the problem on a Monday morning when their Shopping campaigns stop serving and their products disappear from Google’s results.
Use this migration as the forcing function it is. Audit your feed attributes, clean up your titles and GTINs, and come out of August with a Merchant API integration that positions your product data for both paid Shopping performance and organic AI product recommendations. The brands that optimize their feeds during this transition will have a structural advantage in Google’s AI-powered commerce layer going into Q4.
🎯 Not Sure If Your Feed Is Migration-Ready?
We audit Google Shopping feeds and campaign structures for ecommerce brands before any money changes hands. Book a free 30-minute strategy call and we will tell you exactly where you stand.
→ Book Your Free Feed Audit Call
The August 18 deadline does not move. Your migration plan should.
Frequently Asked Questions About the Google Merchant API Migration
What is the Google Merchant API migration deadline?
The Google Merchant API migration deadline is August 18, 2026. On that date, Google permanently shuts down the Content API for Shopping. Any system still using the old API stops syncing product data after this date.
Does the Merchant API migration affect my Shopify store?
It depends on how your Shopify store connects to Google. If you use the native Google channel app, Shopify controls the API integration and should update it automatically. If you use a third-party Google Shopping app, contact that vendor to confirm their migration timeline.
What happens if I miss the August 18, 2026 deadline?
Your product feeds stop syncing and your listings disappear from Google Shopping. Shopping campaigns and Performance Max campaigns that rely on those feeds stop serving, which means zero impressions and zero sales from Google’s paid channels.
How do I check if my Merchant Center uses the Content API?
In Merchant Center Next, go to Settings, then Data Sources, and check the Source column. If any data source shows Content API in that column, you need to migrate before August 18, 2026.
Do I need a developer to complete the Google Merchant API migration?
Not always. If you use a major ecommerce platform like Shopify or WooCommerce, your platform or plugin vendor may handle the migration automatically. If you use custom scripts or proprietary data pipelines, developer involvement is almost certainly required.
What is the difference between the Content API and the Merchant API?
The Google Merchant API is a complete architectural rebuild of the Content API for Shopping, not a simple rename. It uses new resource structures, request formats, and data formatting standards. It also adds AI-powered product optimization features and faster inventory sync that the Content API never supported.
Will my feed labels transfer automatically during migration?
No. Feed labels do not transfer automatically during the Google Merchant API migration. You need to manually reconnect feed labels after migration and verify that any Shopping or Performance Max campaigns using those labels continue serving.
I only use file uploads to Merchant Center. Do I need to migrate?
No. The migration deadline applies only to programmatic API integrations. Brands that upload product data exclusively through manual file uploads, scheduled fetch, or Google Sheets do not need to take any action.
How long does the Google Merchant API migration take?
Simple integrations can complete migration in a few weeks. Complex setups with custom scripts, multiple data pipelines, and third-party reporting tools should plan for 16 to 20 weeks of total migration time, including testing and validation.
Can I run the Content API and Merchant API at the same time during migration?
Yes. Until August 18, 2026, both APIs run in parallel. Google recommends running them simultaneously during the testing phase to verify data integrity before fully cutting over to the Merchant API.