Google's Merchant API Deadline: What It Means for BigCommerce

Who This Doesn't Affect

Worth saying plainly: this migration only touches merchants whose product data flows through the Content API for Shopping. If your feed reaches Google through a scheduled fetch (Google pulling a file from your server on a set schedule), a manual file upload, or a connected Google Sheet, none of this applies to you. Those methods aren't part of the API sunset.

If You Use BigCommerce's Native Google Shopping Channel

BigCommerce's built-in Google Shopping integration is being updated to support the Merchant API directly. If your feed runs through that native channel, BigCommerce is handling the migration on the platform side. Most merchants in this position shouldn't need to take manual action before the deadline.

If You Use Feedonomics

If your Google feed runs through Feedonomics, which BigCommerce owns, the path is even more hands-off. Feedonomics is migrating customers with Google feeds to the Merchant API ahead of the August 18 deadline, rolling migrations out in batches, with no action required on the merchant's end.

One quirk worth knowing about so it doesn't cause a scare: after the migration runs, your Merchant Center account may still list "Content API" as the data source name. That's cosmetic. BigCommerce has confirmed the label can lag behind the underlying system, so if you check your account and still see the old name after the deadline has passed, it doesn't necessarily mean the migration didn't happen.

The One Thing Worth Double-Checking

Here's where we'd push back on any messaging that says, "everyone's covered, don't think about this again." The reassurance from BigCommerce and Feedonomics applies specifically to merchants using the native integration or Feedonomics to manage their Google feed. If your team built a custom integration that talks to the Content API directly, or you're using a third-party feed tool (Channable, DataFeedWatch, GoDataFeed, and similar), that setup won't migrate itself. It's worth a direct email to your feed provider asking whether they support the Merchant API yet and when the switch happens on their end.

Feed labels are the specific risk if you're running Performance Max or Shopping campaigns segmented by label (by region, brand, or margin tier, for example). Labels don't automatically carry over in a migration. If a campaign is built to target a specific feed label and that label doesn't remap correctly, the campaign can end up with zero eligible products and go quiet, often without an obvious error anywhere in the account.

How to Check Your Own Status

Want to see this for yourself rather than take our word for it? In Merchant Center Next, go to Settings, then Data Sources, and look at the Source column for each feed. That column shows which API is currently submitting the data.

The move here is simple: confirm which system actually submits your product data to Google. If it's BigCommerce's native channel or Feedonomics, you're in good shape. If it's anything custom or a third-party feed app, now's the time to check it against the Merchant API before August rolls around.

Bottom Line

For the large majority of BigCommerce merchants, this is a platform-level change happening quietly in the background. It doesn't need a spot on your to-do list. But "most merchants" isn't "all merchants," and a feed disruption in Q3 is expensive to catch late. If you're unsure which category your account falls into, or you're running a custom feed setup, get it checked before the deadline.

If you want a second set of eyes on your Google Shopping setup before August, reach out. We'll confirm what's submitting your data to Google and flag anything that needs attention before it becomes a campaign outage.