Google Shopping Feed API Deadline: Sept 17

What Happened

On August 18, 2026, Google switched off the Content API for Shopping, the legacy interface that thousands of ecommerce integrations have used for years to push product feeds, prices, and inventory into Google Merchant Center. The replacement is the Merchant API v1, generally available since August 2025, which Google has positioned as the long-term foundation for shopping data. It is a modular redesign, splitting the old monolithic API into separate products, inventory, accounts, data-sources, and reporting sub-APIs with better performance and richer reporting than the legacy interface ever offered.

The cutoff is hard rather than gradual: nightly feed pushes, inventory syncs, price updaters, and custom connectors still calling the old endpoints now fail. And because Google keeps Merchant Center listings alive for only 30 days after their last successful refresh, products that were last pushed via the Content API on shutdown day are set to expire around September 17, 2026, a cliff edge that lands squarely in Q4 preparation season.

Key Facts

• The Content API for Shopping was fully shut down on August 18, 2026, with no gradual sunset period.
• The replacement, Merchant API v1, has been generally available since August 2025 and uses the same OAuth scope, so existing tokens keep working without re-consent.
• Merchant Center listings persist for only 30 days after their last successful refresh, so items last pushed via the old API expire around September 17, 2026.
• Only API-based integrations are affected: manual uploads, scheduled fetches of hosted feed files, Google Sheets feeds, and apps that already migrated are not.
• Key data-shape changes in Merchant API v1: prices become integer micros (49.99 USD = 49990000), enums switch to underscore format such as in_stock, and targetCountry becomes feedLabel.
• Some Shopify Google & YouTube app migrations have reportedly changed product ID formats, for example Shopify_US_12345 to shopify_ZZ_12345, which can silently break campaign filters, custom labels, and conversion tags keyed to the old IDs.

Why This Matters for Shopify Merchants

For Shopify merchants, Google Shopping is one of the few acquisition channels that compounds with AI search: Shopping listings feed Google's AI Overviews and Gemini shopping experiences, so a dead feed increasingly means invisibility across Google's entire shopping surface, not just the Shopping tab. Merchants using the official Google & YouTube channel app are largely insulated because Shopify manages that integration, but a large share of serious Shopify operators run third-party feed apps such as Simprosys, Feedonomics, or GoDataFeed, supplemental feeds for enriched attributes, or custom private apps for headless builds. Every one of those paths is exactly the kind of API-based integration the shutdown hits.

The failure modes are quiet, which is what makes this dangerous. A migrated integration can return empty results with no error if the Cloud project is not registered against the merchant account. A feed-label mismatch stops Shopping ads from serving without a single disapproval email. And an unexpected product-ID change resets review status and severs reporting history. With the September 17 expiry falling weeks before Black Friday planning ramps up, a store that discovers the problem in mid-September has already lost its 30-day buffer.

Platform deadline pressure is stacking up across the stack this month: Shopify's Stocky inventory app also reaches its final shutdown on August 31, 2026, with 90 days of read-only data exports before merchant history is gone for good.

What Merchants Should Do Now

1. Open Google Merchant Center and go to the Data sources page. For every primary and supplemental feed, record the name, owner, type, and last update time. Anything still labeled Content API is your exposure list.
2. If you use the official Shopify Google & YouTube channel app, confirm the data source now shows Merchant API or the Shopify app and that your product IDs are stable. Do not reinstall the app just to test the migration.
3. If you use a third-party feed app, ERP connector, or custom integration, get written confirmation from the vendor that it has moved to Merchant API. Ask specifically about product ID changes, feed label mapping, and how supplemental feeds join on ID.
4. Export your current product data now: IDs, item_group_id, custom labels, feed labels, review status, and the item_id values in your conversion tags and GA4 events. Map old IDs to new IDs before changing anything, because a changed ID is treated as a brand-new product and breaks history, filters, and reporting.
5. Watch Merchant Center daily through mid-September for products entering unexpected re-review, expiring statuses, or ads that stop serving without disapprovals. If listings start disappearing, re-push via the Merchant API or a migrated app immediately, since every day dark restarts the 30-day clock.

Original Source

Original source: EcomWatch
Original publication: 2026-08-19
Coverage updated: 2026-08-24