Google is shutting down the Content API for Shopping on August 18, 2026, and if you sync your Shopify catalog to Merchant Center through the official Google & YouTube app, that shutdown may rewrite every single product ID in your feed.
Not change the price. Not change the title. Change the identifier that Google uses to remember which of your products actually sell. Merchants are reporting that migrating the app rewrites IDs from the old Shopify_US_12345_67890 format to a new Shopify_ZZ_12345_67890 format. To Google, a product with a new ID is a product it has never seen before. Your item-level conversion history, your Smart Bidding learning, your historical CPA and ROAS per SKU: gone, replaced by a blank slate on every item in the catalog.
I have been running Google Shopping as the primary revenue channel on high-ticket stores for over a decade, and at Ecommerce Paradise I manage Shopping accounts for clients selling $2,000 to $15,000 products. Item-level history is the single most valuable asset in those accounts. It is what lets the algorithm know that the $6,400 sauna converts at a 6x return and the $2,100 one does not. Reset it across 300 SKUs and you are back to day one on a channel that pays your rent.
Google Ads Liaison Ginny Marvin has acknowledged the reports. Google has not confirmed a fix. August 18 is five weeks out.
When a vendor migration can silently erase five years of data, you learn to care which vendors have been around long enough to not do that to you. Northwest Registered Agent has run the same service for 25 years without churning through owners, rebrands, or platform rewrites that break your filings. See why I use Northwest as my registered agent →
Google Content API Sunsets August 18, Breaking Shopify Product IDs
The Content API for Shopping is the pipe that has carried product data from ecommerce platforms into Google Merchant Center for years. Google is retiring it entirely on August 18, 2026 and replacing it with the Merchant API, which is a ground-up redesign rather than a version bump. Per Google’s own Content API release notes, the v1beta stage of the Merchant API already sunset back on February 28, 2026. August 18 is the hard stop for everything else.
The redesign matters because of how the new API identifies things. Under the Merchant API, products, inventories, and accounts are referenced by resource-name strings that look like accounts/123/products/en~US~SKU42 rather than the numeric IDs the old system used. Any integration still pushing product data through Content API endpoints after August 18 stops working.
For most merchants that is a developer problem. For Shopify merchants it became an operator problem, because the official Google & YouTube app is the default way Shopify stores get products into Merchant Center, and the app’s migration path appears to reissue every product ID.
The clearest reporting on this came from Barry Schwartz at Search Engine Roundtable on July 6, who documented the exact ID transformation merchants are seeing. Old format: Shopify_US_12345_67890, with the country code varying by market (AU, GB, and so on). New format: Shopify_ZZ_12345_67890. The ZZ is a generic placeholder replacing the country segment, and that one substring change is enough to make every item read as new.
Emmanuel Flossie, who runs FeedArmy and has spent years inside Merchant Center feeds, has been the loudest voice on this. His guidance is blunt: if you are planning to migrate the Google & YouTube app by uninstalling and reinstalling it, do not do it. He raised the issue publicly in January and escalated it again in July after concluding it had not been fixed.
Ginny Marvin, Google’s Ads Product Liaison, finally responded on LinkedIn in early July: “Hi all, I’ve been tagged in this post a couple of times and just want to let you know that we’re looking into this.” That is an acknowledgment, not a resolution. Google’s own Merchant Center documentation on onboarding to the Google & YouTube app does not currently spell out an ID-preserving migration path.
Matinique Roelse offered the workaround that most feed specialists have converged on: stop using the Shopify app as your feed source before the deadline and move to a feed management tool where you control the product IDs yourself. If the IDs are yours, a reinstall does not touch them.
How the Merchant API Migration Turned Shopify_US Into Shopify_ZZ
This did not appear out of nowhere. Google announced the Merchant API as the Content API’s successor well over a year ago and has been walking the ecosystem toward it in stages. February 28, 2026 killed v1beta. August 18, 2026 kills the Content API. Every app, agency tool, and custom integration that touches Merchant Center has been on notice.
The ID collision is a side effect of how Shopify’s app constructs identifiers. The old scheme baked the target country into the ID string, which made sense under a Content API model where each country market was effectively its own feed. The Merchant API restructures how accounts and feed labels relate to products, and the app’s new scheme appears to drop the country segment in favor of a placeholder. That is a reasonable engineering decision in isolation. It is a catastrophic one if nobody builds an ID-mapping bridge, because Google Ads keys performance history off the item ID.
What makes this ugly is the timeline. Flossie flagged it in January. Google said nothing publicly for roughly five months. The acknowledgment came in July, about six weeks before the deadline, with no confirmed fix and no official migration guidance that addresses ID continuity. Feed specialists have been telling merchants to bail out of the app for months while Google’s own channel was silent.
Migration complexity is not trivial either. Estimates circulating among developers put a full Content API to Merchant API migration at 16 to 20 weeks for high-complexity merchants. A store running the plug-and-play Shopify app was supposed to be insulated from all of that. Instead the app is the exact place the breakage lands.
What a Product ID Reset Costs a High-Ticket Shopping Campaign
Low-ticket sellers can absorb a feed reset. They have volume. A store doing 400 orders a month at $40 rebuilds Smart Bidding learning in two or three weeks because the algorithm gets hundreds of conversion signals to chew on.
High-ticket stores do not have that luxury. Take a typical client account of mine: 280 SKUs, $3,400 average order value, roughly 22 conversions a month across the whole catalog. That is the reality of selling saunas, generators, or commercial-grade equipment. Twenty-two data points a month is barely enough to keep Smart Bidding calibrated when it already knows your catalog. Strip the history and the algorithm is guessing on every product for months, not weeks.
Here is the rough math. If Shopping drives 70% of a $180,000-a-month store, that is $126,000 in monthly revenue running through the channel. A learning-period efficiency drop of 25% to 40% is normal after a major feed disruption. Carry that for two months while the algorithm relearns and you are looking at $60,000 to $100,000 in revenue that does not show up, on a channel that was working fine on August 17.
August 17 is not an accidental date to pick. Google is changing how Smart Bidding treats budget-limited campaigns on August 17, forcing campaigns that have been outperforming their Target CPA or Target ROAS to deliver closer to the stated target. So on August 17 your bidding targets get enforced, and on August 18 the item history those targets were calibrated against can vanish. Two structural changes to the same channel, 24 hours apart, both landing in the back half of August.
Item-level history is also what feeds the newer reporting Google has been rolling out. The PMax channel diagnostics that finally let you see where your spend is going are only useful when the items being reported on have a track record. Same with the AI-driven scoring Merchant Center now applies to your products. Reset the IDs and those systems are scoring strangers.
There is a real counterpoint worth holding. Google says it is looking into this, and Google has quietly fixed migration bugs before. If you rip your feed out of the Shopify app and Google ships an ID-preserving migration next week, you did work you did not strictly need to do. That is the downside case, and it costs you a weekend and a tool subscription. The other downside case costs you your catalog’s entire performance history in your highest-revenue channel. I know which asymmetry I am playing.
If reading that math made you want to hand the whole thing to someone else, that is a rational reaction. Feed architecture, Merchant Center account structure, Shopping campaign builds, and supplier catalog management are four separate disciplines, and most store owners are trying to do all four alone. My team builds and runs the entire stack for clients through the turnkey done-for-you service, and migrations exactly like this one are why that service exists.
If feed migrations and Merchant Center structure still feel like a black box, start with the fundamentals before August 18 turns them into an emergency. Get my free high-ticket dropshipping mini course →
How to Protect Your Google Shopping Feed Before August 18
Five weeks is enough time to do this calmly. It is not enough time to do it in the last 48 hours.
- Confirm how your products actually reach Merchant Center. Open Merchant Center, go to your data sources, and check whether the feed is coming from the Google & YouTube Shopify app or from a third-party feed tool. If it is the app, you are in the blast radius. If you already run a dedicated feed tool, confirm with that vendor in writing that their Merchant API migration preserves your existing offer IDs.
- Export your current product IDs today. Pull a full export from Merchant Center with the item ID, title, and 12 months of item-level clicks, conversions, and conversion value. Store it somewhere outside Google. If the IDs do get rewritten, this export is the only bridge between your old performance data and your new catalog, and you cannot generate it after the fact.
- Move feed control to a system you own. The consensus fix is to stop letting the Shopify app mint your IDs. A feed management tool like Channable lets you define the product ID yourself, so a reinstall on Google’s side changes nothing. For catalog and inventory syncing across suppliers, I have used Stock Sync for years to keep SKU data consistent before it ever reaches the feed.
- Do not uninstall and reinstall the app to “get ahead of it.” That is the specific action that triggers the rewrite. Flossie’s warning is aimed exactly at merchants who think proactively reinstalling is the safe move. It is the opposite.
- Baseline everything else while you are in there. Export your search term data, your SEMrush ranking snapshot, and your top-selling SKU list, and get your email flows exported from Omnisend. When a channel goes sideways you want a clean before-picture, and a VA from OnlineJobs.ph can pull all of this in an afternoon for under $50.
- Get a second set of eyes on your specific account. Feed architecture decisions are hard to reverse and every catalog is different. If you want me to look at your Merchant Center setup before the deadline, book a discovery call. I am also posting weekly breakdowns of how this migration is actually playing out across client accounts inside my Patreon.
If you want to move fast on the export and audit work, I have been using Claude to parse Merchant Center exports and flag which SKUs carry the most conversion history, which tells you exactly which items you cannot afford to lose.
Frequently Asked Questions
Is the product ID rewrite confirmed by Google?
No. Merchants and feed specialists have documented it, and Ginny Marvin has said Google is looking into it, but Google has not confirmed either the problem or a fix.
What happens if I do nothing before August 18?
If Google ships a fix, possibly nothing. If it does not, your product IDs get rewritten on migration and your item-level Google Ads performance history resets across the catalog.
Does this affect stores on platforms other than Shopify?
The Content API sunset affects everyone. The specific ID rewrite issue is tied to how the Google & YouTube Shopify app constructs IDs, so it is a Shopify-specific symptom of a platform-wide deadline.
Will switching to a feed tool cost me my history too?
Not if you configure the new feed to use your existing offer IDs. That is the entire point of moving off the app. Match the old IDs exactly and Google sees continuity.
How long does Smart Bidding take to relearn after a feed reset?
On a high-volume store, two to three weeks. On a high-ticket store doing 20 to 30 conversions a month, expect two to three months of degraded efficiency.
I am just getting started and do not have a feed yet. Does this matter to me?
You have the easiest path of anyone: set up your feed through a tool you control from day one and skip this entire problem. Start with the step-by-step guide to starting a high-ticket store, then pick your vertical from the 1,000 high-ticket niches list.
Should I just hire an agency for this?
If Shopping is more than half your revenue and you cannot confidently answer where your product IDs come from, yes. Compare options in my breakdown of the best Google Shopping ad agencies.
Want my full step-by-step masterclass on building and scaling a high-ticket store, feed architecture included? Get the masterclass →
I will keep tracking this one. If Google ships an ID-preserving migration before August 18, I will say so. Until they do, assume your history is at risk and act accordingly. Subscribe to the YouTube channel for daily breakdowns. More breaking news later today.
Related Articles
If this was useful, these go deeper:
- Google Resets Your Shopping ROAS Aug 17. Act Now
- Google’s 2026 Feed Spec Comes for Your Images
- Google Just Cracked Open the PMax Black Box
- Google Now Scores Your Store Inside AI Shopping
- How to Find Suppliers for High-Ticket Dropshipping
Trevor Fenner is an ecommerce entrepreneur and the founder of Ecommerce Paradise, a platform focused on helping entrepreneurs build and scale profitable high-ticket ecommerce and dropshipping businesses. With over a decade of hands-on experience, Trevor specializes in high-ticket dropshipping strategy, niche and product selection, supplier recruiting and onboarding, Google & Bing Shopping ads, ecommerce SEO, and systems-driven automation and scaling. Through Ecommerce Paradise, he provides free education via in-depth guides like How to Start High-Ticket Dropshipping, advanced training through the High-Ticket Dropshipping Masterclass, and fully done-for-you turnkey ecommerce services for entrepreneurs who want a faster, more hands-off path to growth. Trevor is known for emphasizing sustainable, real-world ecommerce models over hype-driven tactics, helping store owners build scalable, sellable, and location-independent brands.
