In short: Content API for Shopping v2.1 shuts down August 18, 2026. On that date feed uploads, supplemental feeds, custom labels, price and stock updates and disapproval checks stop working — a hard cutoff, not a nice-to-have. The successor, Merchant API v1, has been GA since July 2025 and is genuinely better: machine-readable ErrorInfo, 1,000-row pagination and partial product patch. This is the year's single hardest deadline.
Mark the date: August 18, 2026. That’s when Google shuts down Content API for Shopping v2.1 for good. The intermediate Merchant API v1beta already sunset on February 28, 2026, and Merchant API v1 has been GA — the official successor — since July 2025.
What actually breaks
Anything that still talks to the old API stops working on that date: feed uploads, supplemental feeds, custom labels, price and stock updates, disapproval checks. For an e-commerce account running scripted feed automation, this is not a “nice to migrate” — it’s a hard cutoff. Miss it and your feed goes dark.
This is the single hardest deadline in Google’s advertising ecosystem this year. Everything else on the roadmap can slip. This one can’t.
Why the migration is worth doing anyway
Merchant API isn’t just a renamed endpoint. It splits one monolithic surface into focused sub-APIs — datasources, products, inventories, reports, notifications — and ships improvements that make automation more robust:
- Machine-readable
ErrorInfo— proper retry logic instead of string-parsing error messages. - Pagination raised from 250 to 1,000 rows — fewer calls for the same report.
- Product
patch— partial updates instead of re-pushing the whole product.
How to automate the move
Treat the rebuild as a chance to harden the stack, not just keep the lights on. Map each old call to its sub-API home, wire ErrorInfo into your retry layer, and switch reports to the larger page size. If you manage multiple accounts, build the migration once as a shared connector and roll it across clients — the sub-API structure is consistent, so the work amortizes.
The clock is the only reason this is urgent. The destination is genuinely better than where you’re leaving. For the full picture of how Merchant API fits the rest of the year’s changes, see our Google API year in review.
