Google Is Sunsetting the Content API for Shopping and Rolling Out the Merchant API — What It Means and How to Prepare

Google has announced the general availability of the Merchant API and, at the same time, begun the deprecation of the Content API for Shopping. In practice, the legacy interface will remain active until August 18, 2026, after which it will be turned off. This is a systemic change: the Merchant API becomes the default programmatic way to manage data in Merchant Center, covering products, inventory, prices, account configuration, and diagnostics. For retailers, integrators, and agencies, it’s a clear signal to plan migration well in advance and treat it as an opportunity to audit data quality and streamline catalog publication and synchronization processes.

What’s Changing — and Why Is Google Doing It?

The Merchant API is designed to simplify integration architecture and accelerate the rollout of new features. A single, unified API means fewer edge cases, more predictable versioning, clearer error diagnostics, and a shorter path from catalog change to its reflection across Google services. Compared to the Content API for Shopping, the emphasis is on standardized operations, readable non-compliance messages, and improved tooling for oversight and reporting.

For day-to-day marketing and engineering workflows, this translates into fewer hard-to-trace failures, faster reactions to policy-driven disapprovals, and a better environment for experimenting with publication automation.

Who Is Affected?

Anyone who programmatically feeds Merchant Center with data:

• Large retailers with their own PIM or ERP,
• Smaller e-commerce stores using platform plugins and connectors,
• Integrators orchestrating multiple data sources,
• Performance agencies running product campaigns across markets.

If your codebase, CRON jobs, SaaS integrations, or helper scripts call the Content API for Shopping, you need to schedule a transition to the Merchant API. Be sure to include external partners—feed providers, marketplace aggregators, and software houses—to coordinate timelines and avoid downtime.

Timeline and Operational Impact

While the horizon may look comfortable, large projects rarely go perfectly. The closer you get to the shutdown date, the higher the risk that subtle differences and incompatibilities will surface only under production load. A sensible strategy is to prepare a Merchant API pilot as soon as possible, run parallel tests of critical flows, and progressively switch segments of the catalog.

This approach buys time to catch defects, fine-tune attribute mapping, verify permissions, and update operational documentation, schedules, and SLAs for price, inventory, and creative updates.

A Step-by-Step Migration Plan

1. Inventory your touchpoints with product data: creates and updates, variants, availability, promotional pricing, logistics attributes, bundles/sets, and images.

2. Map authentication and key management: OAuth, service accounts, scopes/permissions, and the client libraries your apps rely on.

3. Prepare a function-by-function mapping between the old and new APIs, alongside a list of business-critical operations that must be flawless on cutover day.

4. Build a Merchant API prototype covering read/write for core resources.

5. Run parallel tests: send identical changes through both channels and compare propagation times, statuses, and diagnostic messages.

Data Quality and Product Information Management

Migration is a great moment to improve data quality—no API can compensate for gaps in key attributes. In practice, that means standardizing product and variant IDs, verifying GTINs, enriching descriptions and specs, refining images, and defining clear logic for availability and pricing, especially during promotions.

Implement lightweight validations in your PIM/ERP, prepare test scenarios for new categories, and ensure fast publication paths for fixes during sales peaks. Better data quality reduces disapprovals, shortens diagnostics, and stabilizes product visibility.

Security, Permissions, and Compliance

Changes to auth flows and access scopes are a perfect chance to enforce least-privilege access, tighten key rotation, and review which systems are allowed to modify assortment data. In larger organizations, a two-step approval process for configuration changes and a clear separation of duties between technical and marketing teams work well.

Plan for abuse monitoring, secrets storage policy (e.g., password/secret managers), and access audits to prevent accidental or unauthorized modifications to product data.

The Risks of Delaying Migration

Pushing the decision to the last minute raises the risk of downtime and data drift in prices and inventory—hurting visibility, campaign quality, and revenue. Even a few hours’ delay in hot periods can burn media budgets and overload customer support. From a risk-management perspective, it’s better to complete the switch with a buffer and have a rapid rollback path in case an unforeseen incompatibility appears in production.

Benefits of a Well-Executed Migration

Beyond meeting Google’s requirements, moving to the Merchant API helps simplify your integration ecosystem, reduce technical debt, improve observability, and accelerate automation experiments. Combined with regular Merchant Center diagnostics reviews and a clear division of responsibilities between tech and marketing, this delivers more stable product visibility, better resilience to seasonal swings, and more predictable sales outcomes.

Bottom Line

Migration from the Content API for Shopping to the Merchant API is mandatory within the defined horizon, and it’s not worth postponing. The best results come from a phased approach: thorough discovery, a prototype on the new API, parallel tests on realistic data, hard metrics for product-information quality, a controlled cutover, and readiness to ship quick fixes in response to incidents. Treated as a modernization catalyst, this change can elevate data quality, simplify integrations, and give you greater control over how your offer is published across Google services.

Bibliography

SERoundtable, “Google Merchant API Replaces Content API for Shopping.” Accessed: 22.08.2025.
https://www.seroundtable.com/google-merchant-api-content-api-for-shopping-39958.html