What happened
Google published a request form letting Content API for Shopping users apply to keep access past the August 18, 2026 sunset. Applicants choose one of two extension windows: October 15 or December 31, 2026. After that, the Content API is done and the Merchant API is the only road into Merchant Center.
The consequence for missing the deadline is spelled out plainly: merchants who hit August 18 without an approved extension will see degraded ad and organic Shopping performance. Note the word approved — this is an application, not an automatic grace period. Filing the form is step one; confirmation is what actually protects you.
The sunset itself isn't news — Google has been steering developers toward the Merchant API for a while. What's new is the escape hatch, and the fact that Google felt it needed one at all tells you how many integrations are still sitting on the old API weeks out from the cutoff.
Why this matters
Feeds are plumbing, and nobody looks at plumbing until it backs up. Plenty of store owners genuinely don't know which API their feed runs through — it's buried inside a third-party feed app, an agency-built connector, or a script a developer wrote three years ago. That ignorance is now a dated liability: degraded Shopping performance means your products losing visibility in both paid and free listings, silently, while you wonder why revenue dipped.
Look hard at the two extension dates before picking. December 31 sounds generous until you realize it schedules your forced API migration for the middle of holiday season. Cutting over a feed integration during Cyber Week, with your year's biggest revenue on the line, is how disasters get written up afterward. October 15 is the honest deadline — and finishing before it is the actual goal, because the extension buys months, not a pardon.
For BigCommerce merchants specifically, the exposure usually sits in whichever app or integration pushes the catalog to Merchant Center. Most maintained apps have migrated or will, but 'probably handled' is not a status you want your Shopping revenue resting on in August.
What to do about it
Identify what your feed actually uses
Ask your feed app vendor, agency, or developer one direct question: does our Merchant Center sync run through the Content API or the Merchant API? If the integration is custom-built, have whoever maintains it check the endpoints. Get the answer in writing this week.
File the extension form regardless
Even if migration is underway, submit the request now — approval takes time and is not guaranteed. Choose October 15 unless the migration genuinely cannot land by then; December 31 puts your cutover inside the holiday selling season, which is the worst possible timing.
Schedule the Merchant API migration like a project
Book the developer time, run the new integration in parallel, and compare product counts, disapprovals, and price accuracy against the old feed before cutting over. A feed migration verified in September is a non-event; one improvised in December is an outage.