Migrating Google Merchant Center from the Content API to the Merchant API on Shopify means moving your product sync from Google’s legacy Content API for Shopping, which was sunset on August 18, 2026, to the new Merchant API. Most Shopify stores migrate simply by using an up-to-date Google channel or feed app; brands running custom integrations must rebuild their sync against the new API.
Key takeaways
- The Content API for Shopping was sunset on August 18, 2026; the Merchant API is its replacement.
- Most Shopify stores migrate automatically by keeping their Google channel/feed app current.
- Custom integrations must be rebuilt against the Merchant API’s new, sub-API structure.
- From September 1, 2026, legacy Content API requests without an extension began failing with HTTP 410.
- Audit which sync method you use before assuming you are safe.
What is the Merchant API and why did Google replace the Content API?
The Merchant API is Google’s redesigned programmatic interface to Merchant Center. It replaces the older Content API for Shopping with a modular design, separate sub-APIs for products, data sources, accounts, and reporting, that is meant to be easier to extend over time. Google’s migration and compatibility guide is the authoritative reference for the move.
According to Google’s deprecation and sunset documentation, the Content API for Shopping was sunset on August 18, 2026, and from September 1, 2026 requests without an active extension began intermittently failing with HTTP 410 Gone, with full decommissioning planned for early 2027. In other words, this is not optional, and the window has effectively closed for legacy custom integrations.
Does this affect my Shopify store?
It depends entirely on how your products reach Merchant Center. Identify your path first.
| How you sync to Google | What the migration means |
|---|---|
| Google & YouTube channel app for Shopify | Handled by the app; keep it updated, no code work for you |
| Third-party feed app (e.g. feed management apps) | Handled by the vendor; confirm they have migrated |
| Scheduled fetch of a feed URL | Feed format largely unaffected; verify Merchant Center source still reads it |
| Custom in-house Content API integration | Must be rebuilt against the Merchant API |
The large majority of Shopify parts brands fall into the first two rows and simply need to confirm their app is current. If you built a bespoke pipeline, common for big catalogs that outgrew off-the-shelf apps, read on.
How do you migrate a custom integration?
- Audit the current integration. Find every Content API call your sync makes and the data each one moves.
- Map to the new sub-APIs. Products, data sources, and accounts are now separate services. See the accounts overview and the data sources overview.
- Rebuild the product sync. Use the Merchant API’s products service to insert and update listings.
- Re-create data sources. Primary and supplemental sources are modeled explicitly; rebuild them as data sources.
- Test in parallel. Validate the new sync writes correct data before cutting over.
- Monitor diagnostics. Watch Merchant Center for disapprovals and feed errors after cutover.
This is the plumbing underneath the feed strategy in our Shopify ecommerce pillar. If you want the data done right, it is part of our web and paid ads work.
What is actually different in the Merchant API?
The biggest conceptual change is modularity. Where the Content API bundled most operations under a single service, the Merchant API splits functionality into focused sub-APIs: products, inventories, data sources, accounts, promotions, and reporting, each versioned independently. That makes the surface cleaner but means a one-to-one port of old calls rarely exists; you map old behavior to the new service that owns it.
| What you did before | Where it lives now |
|---|---|
| Insert/update products | Products sub-API (product inputs & processed products) |
| Manage primary and supplemental feeds | Data sources sub-API |
| Account and sub-account settings | Accounts sub-API |
| Pull performance data | Reporting sub-API |
Feeds are now first-class “data sources.” A primary data source carries your full catalog; supplemental data sources patch or enrich specific fields, the same layered strategy large parts catalogs already rely on, just modeled explicitly. If you understood the old primary/supplemental feed split, the new model will feel familiar.
Who is most at risk from the sunset?
The brands most exposed are those that outgrew off-the-shelf apps and built bespoke pipelines, often exactly the large powersports parts catalogs this site is written for. A custom script that pushed thousands of SKUs via the Content API, a middleware layer syncing an ERP to Merchant Center, or an in-house feed generator hitting the old endpoints will all fail progressively now that the API is retired. If that describes you and you have not migrated, your listings are at risk of going stale or disappearing.
Stores on the standard Shopify Google channel or a maintained third-party feed app are largely insulated, because the vendor absorbed the migration. The danger zone is custom code, which is why the audit in the next section matters.
What should you check right now?
- Open Merchant Center and confirm products are still active and updating.
- Confirm your Shopify Google/feed app shows a current, supported version.
- If you run any custom code against Google, confirm it targets the Merchant API. The Content API is retired.
- Check for a spike in feed errors or disapprovals dated after the sunset.
How do you migrate without losing listings?
The cardinal rule is: never cut over blind. For a store with real revenue on the line, a parts catalog disappearing from Shopping for even a day is lost sales. Run the new Merchant API sync in parallel with whatever is still working, compare the product data it produces against your source of truth, and only switch once the new path writes correct, complete data. Then keep a close eye on diagnostics for the first few days. Supersessions, identifier handling, and category mapping are the usual places small differences surface.
A safe sequence for a custom migration looks like this:
- Stand up Merchant API access and authenticate the new integration.
- Re-create your data sources (primary + supplemental) in the new model.
- Write products through the new products service to a test or secondary feed.
- Diff the output against your live listings; resolve any gaps.
- Cut over, monitor diagnostics daily, and retire the old code path.
If this is beyond your team’s bandwidth, it’s exactly the kind of under-the-hood work we handle. See our web and paid ads services. The goal is continuity: the catalog keeps selling while the plumbing changes underneath it.
Related reading
- Pillar: Shopify & ecommerce for powersports parts brands
- How to get fitment data into Google Shopping
- Meta ads for motorcycle parts brands: account structure
Frequently asked questions
Do I need to do anything if I use the Shopify Google channel app?
In nearly all cases, no code work. The app handles the API relationship with Google. Keep the app updated and verify your products are still active in Merchant Center. Custom work is only required if you built your own sync.
Did the sunset already happen?
Yes. Google lists the Content API for Shopping sunset as August 18, 2026, with requests failing progressively from September 1, 2026 and full decommissioning planned for early 2027. If you still rely on it, migrate right away.
Will my supplemental feeds still work after migrating?
Yes. The concept carries over. In the Merchant API, feeds are modeled as data sources, with primary and supplemental roles. The strategy of patching fields in bulk via a supplemental source is unchanged; only the mechanism is renamed and restructured.
How long does a custom migration take?
It varies with how much custom logic sits in your sync. A straightforward product-update integration is a modest project; one that manages accounts, multiple data sources, and reporting takes longer. Plan for parallel testing so you never run blind in Merchant Center.
By Brooks Tomblin, Ormond Brand Consulting. Marketing & business consulting for motorsports and outdoors businesses.
Last updated: November 2026

