If you push product data to Google Shopping through a custom integration — a feed builder, a PIM sync job, an internal Node/Python service that calls shoppingcontent.googleapis.com — you are on a clock. On August 18, 2026, Google permanently shuts down the Content API for Shopping. Every products.insert, every products.list, every inventory and price update against the v2.1 endpoints stops returning data and starts returning errors. There is no soft cutoff and no grace period after that date.
That part is loud. You'll know within minutes because the calls 404, the feed job alerts, and the catalog stops updating.
The part that bites quietly is the migration itself. The Merchant API is not a renamed Content API — it's an architectural rebuild with new resource shapes, a new identifier scheme, and a new money type. A migration done as a search-and-replace of the base URL will compile, authenticate, return 200, and silently write wrong data to your live catalog. Here are the three surfaces where that happens.
What actually changes
Surface
