Ecommerce Website Development in Pune: Why Google's Merchant API Replacing Content API Matters for Your Product Feed in 2026

Ecommerce Website Development in Pune: Why Google's Merchant API Replacing Content API Matters for Your Product Feed in 2026

Google retired the Content API for Shopping on 18 August 2026, and any store that pushed product data to Google through code — rather than uploading a file or a Google Sheet — needed to be on the new Merchant API before that date. If your team handles ecommerce website development in Pune and your store's product feed was built as a custom integration, a PIM connector, or certain Shopify/WooCommerce apps, this deadline has already passed and it is worth checking, right now, whether your Shopping listings are quietly going stale.

This is not a future warning. It is a diagnostic problem for anyone reading this after the fact: prices that stopped updating in July, sold-out products still showing a live "Buy Now" button on Google, or a Merchant Center account that has gone unusually quiet. We will walk through how to tell which feed method your store actually uses, what a broken feed looks like from the outside, why an out-of-stock buy button is now a suspension risk rather than a cosmetic bug, and what the Merchant API's modular structure means in practice for a custom-built site versus a Shopify or WooCommerce store.

Why this matters even though the deadline is behind us

A feed that stopped syncing on 18 August does not throw an error your team notices immediately. Google Shopping listings degrade gracefully at first — old prices, old stock levels, disapproved items dropping out one by one — and by the time someone notices a dip in Shopping traffic, the account may already be carrying data quality flags or, worse, a misrepresentation strike. The fix itself is usually a day or two of developer time once you know what broke; the expensive part is the weeks a store spends not knowing.

Ecommerce website development in Pune: what actually changed on 18 August 2026

The Content API for Shopping was the interface Google had offered for over a decade to push products, inventory, and account settings into Merchant Center programmatically. As of 18 August 2026 it stopped accepting updates entirely — there was no grace period and no soft landing. Any code, script, or third-party app still calling Content API endpoints after that date started getting rejected calls instead of silently degraded ones, but a surprising number of integrations were written to swallow API errors and keep running, which is exactly how a feed goes stale without anyone getting an alert.

The replacement, the Merchant API, had already been live for some time before the cutover, and Google had even split its own rollout into two phases: merchants who had already moved to the early v1beta version of the Merchant API had a separate, earlier deadline of 28 February 2026 to move onto the stable v1. If your developer migrated early and only got as far as v1beta, that migration was not actually finished — worth checking the version string in your integration code or app settings.

Who was actually affected

This is the detail most owners get wrong, and it is worth being precise about because panicking over the wrong feed method wastes developer time. Google drew a clear line between two categories of merchants.

Stores that fed Merchant Center through the Content API — meaning a developer, a PIM tool, or a feed-management platform was calling Google's API directly to push product data — had to migrate. This includes most custom-built ecommerce sites with a bespoke Google Shopping integration, several third-party Shopify and WooCommerce apps that used the API under the hood, and dedicated feed-management tools that connected programmatically rather than exporting a file.

Stores that used a manual file upload (uploading a spreadsheet or XML file by hand into Merchant Center), a scheduled URL fetch (Merchant Center pulling a feed file from a URL on a schedule you set), or a Google Sheets feed were not directly affected by the 18 August cutover. Those methods never touched the Content API — they use Merchant Center's file-processing layer, which Google did not retire.

How to tell which feed method your store is actually on

Most site owners genuinely do not know which category they are in, because the integration was set up years ago by a developer or agency who has since moved on, or it came bundled inside a Shopify/WooCommerce plugin nobody has opened since installation. There are three places to check.

First, open Merchant Center and go to Products then Feeds. Click into your primary feed and look at the "Fetch schedule" or "Input method" column. If it says "Google Sheets," "Scheduled fetch," or "Upload," you were not directly affected by the Content API retirement. If it says "API" or shows no scheduled fetch at all because updates arrive continuously through calls, you were on an API-based integration.

Second, if you are on Shopify or WooCommerce, check which app is managing your Google Shopping connection. The official Google & YouTube channel app for Shopify and the Google for WooCommerce plugin both talk to Google's API layer, and their publishers pushed updates ahead of the deadline — but only if the store had auto-updates enabled or someone manually updated the plugin. A plugin last updated before mid-2026 is a strong signal it needs attention.

Third, if the feed was built as part of a custom ecommerce website development project — a bespoke integration written specifically for your store — ask whoever maintains the codebase whether the integration calls content.googleapis.com endpoints (the old API) or merchantapi.googleapis.com endpoints (the new one). That single string is usually enough to settle the question.

Symptoms of a broken or stale feed

If you suspect your integration was affected and nobody actioned the migration, look for these signs, roughly in order of how easy they are to spot.

Prices in Google Shopping ads or free listings that do not match your live site. This is the fastest tell — pull up your own product on Google Shopping and compare the price shown against the price on your product page. A mismatch of more than a day or two's staleness usually means the feed stopped pushing updates around the time of the cutover.

Sold-out products still showing as purchasable in search results or Shopping ads. This is the most serious symptom, covered in more detail below, because Google now treats it as a policy violation rather than a simple data error.

A falling or flat count of active products in Merchant Center's Diagnostics tab, without a corresponding change in your actual catalogue. If you added twenty products in August and Merchant Center's active count did not move, new items are not making it through.

Disapproved items accumulating with "missing" or "mismatched" data quality warnings that reference fields your feed used to populate correctly — this often happens when the Merchant API renamed or restructured a field the old Content API integration used to send in a different shape.

A Merchant Center account status of "Limited" or "Suspended," or an email from Google referencing a policy or account issue you did not previously have.

The misrepresentation risk: why a stale feed is now an account-level problem

For years, an out-of-stock product still showing an active buy button on Google Shopping was treated as a data quality nuisance — the listing might get disapproved, but the rest of the account kept running. That has changed. Google now classifies a pattern of active purchase buttons on out-of-stock products as a misrepresentation issue, and misrepresentation is enforced at the account level, not the item level. In practice this means Google can suspend the whole Merchant Center account — not just disapprove the affected listings — and misrepresentation suspensions can land without the warning period other policy issues get.

This is precisely the failure mode a stalled feed migration produces. If your inventory sync broke in August because the integration stopped talking to Google, your store's actual stock levels changed after that point but Merchant Center never heard about it. A product that sold out in September still shows as available and buyable on Google, because the last data Google received said it was in stock. The underlying cause is a plumbing problem, but Google's enforcement treats the symptom — a misleading buy button — as a trust and safety issue.

The practical fix is to make sure availability and inventory sync is the first thing you verify after any feed migration, ahead of price or description accuracy. If your store runs on the Merchant API's inventory sub-API, confirm it is actually being called on every stock change, not just on a nightly batch — a nightly sync still leaves a same-day sellout showing as buyable for hours.

What the Merchant API's modular structure means for your store

The old Content API was a single, monolithic interface — one API surface covering products, inventory, accounts, and reporting together. The Merchant API splits these into separate sub-APIs that a store connects independently: a Products API for catalogue data, an Inventory API specifically for stock and price changes, an Accounts API for Merchant Center account and settings management, a Data Sources API for managing where product data comes from, and a Reporting API for performance data.

Why the split matters practically

For a custom-built ecommerce site, this is a genuine improvement once the migration is done. A developer can wire up just the Inventory API to push real-time stock and price changes throughout the day, without needing full account-management permissions or touching reporting at all. That narrower scope is easier to secure, easier to debug when something goes wrong, and cheaper to run because you are not authenticating against capabilities you never use. If your original Content API integration was built years ago as one large permission block, a Merchant API migration is a reasonable moment to also tighten API credentials down to only the sub-APIs your store actually needs.

For a Shopify or WooCommerce store using an official app, this modularity is mostly invisible — the app handles which sub-APIs it calls. What matters to you as the store owner is confirming the app itself has been updated and reconnected, and that the reconnection did not silently drop settings like feed labels, which Google's own migration notes flag as not carrying over automatically and needing to be manually reattached.

A note on the field-level changes

Beyond the API split, some fields were renamed or restructured between Content API and Merchant API (availability values, certain shipping and tax fields, and how product identifiers are grouped). If your team did the migration by pointing existing code at new endpoint URLs without checking field names, that is a common source of the "disapproved item, missing field" errors mentioned above — the request succeeds but a field silently arrives empty because it was mapped incorrectly.

The September 2026 policy consolidation — organizational, not a new restriction

Separately from the API migration, Google is folding its Shopping ads and free-listings help-center policies into a single, unified policy set in September 2026. It is worth flagging so you do not mistake it for a fresh compliance burden: Google has described this as a housekeeping change, merging two previously separate policy documents that largely said the same things about prohibited content, misrepresentation, and data accuracy into one reference. It does not introduce new restrictions or a stricter enforcement bar on its own. The reason it is relevant here is that misrepresentation enforcement — the out-of-stock buy button issue above — sits inside that unified policy set, so it is a reasonable moment to read through the current version once, rather than relying on notes from whichever older document your team originally reviewed.

What to check this week if you suspect your feed was affected

Start in Merchant Center's Diagnostics tab (Products > Diagnostics), which lists item-level and account-level issues with dates, so you can see whether problems started clustering around mid-August. Cross-check the account status banner at the top of Merchant Center — a "Disapproved," "Limited," or "Suspended" status needs immediate attention regardless of the feed method question.

Next, pull five to ten of your best-selling products and compare their live Google Shopping listing against your actual site: price, availability, and image. This is the fastest way to catch a stale feed without waiting for Google's own diagnostics to flag it.

If you find your feed was affected, the remediation work itself is usually not large — repointing API calls to the correct Merchant API endpoints, remapping any renamed fields, reconnecting feed labels, and verifying inventory sync frequency, typically a few days of focused developer work for a custom integration, or a plugin update plus reconnection for Shopify/WooCommerce. The bigger cost is usually the weeks a store loses in Shopping visibility before the problem is even diagnosed, which is why checking now — even months after the deadline — is worth the hour it takes.

Frequently Asked Questions

My store uses a Google Sheets feed to Merchant Center. Do I need to do anything?

No. Google Sheets feeds, manual file uploads, and scheduled URL fetches were not directly affected by the Content API retirement, because they never used that API in the first place. It is still worth checking Merchant Center's Diagnostics tab periodically for unrelated data quality issues, but the 18 August 2026 deadline did not apply to this feed method.

How do I know if my Shopify store was affected?

Check whether the Google & YouTube channel app in your Shopify admin has been updated since mid-2026 and whether it shows as connected without errors under its settings page. If the app auto-updated and reconnected cleanly, you are likely fine; if it has not been opened or updated in months, treat it as at risk and verify a handful of live product listings against your storefront.

What is the fastest way to check if my current Shopping listings are stale?

Search for five or six of your own products on Google Shopping and compare price and stock status against your live site. A mismatch, especially on availability, is the clearest and quickest signal, faster than waiting for Merchant Center's own diagnostics to surface the issue.

Is the out-of-stock buy button issue something Google warns about first?

Not necessarily. Google now treats a pattern of active purchase buttons on out-of-stock products as a misrepresentation issue, which is enforced at the account level and can result in suspension without the advance warning that other, lower-severity policy issues typically receive. This makes inventory sync accuracy a higher priority than it was previously.

Does the September 2026 policy consolidation change what I need to comply with?

Not materially. Google has described it as merging its separate Shopping ads and free-listings policy documents into one unified reference, not as introducing new rules or a stricter enforcement standard. The underlying misrepresentation and data-accuracy requirements are the same ones already in effect.

Where to go from here

The single most useful thing you can do today is open Merchant Center's Diagnostics tab and read through it line by line, checking dates against 18 August 2026 for anything that looks like it stopped updating around then. If you do not have login access or have never been shown how to read that tab, that itself is worth fixing before the next migration or policy change catches your store off guard.

We build and maintain ecommerce sites for Indian D2C brands as part of our ecommerce website development work, and product feed health is one of the recurring maintenance items we check on client sites — not as a one-time migration project but as something to verify each time Google changes how Merchant Center talks to a store's backend. If your product pages themselves need work alongside the feed — clearer stock messaging, better structured data, faster load times — that overlaps with what we cover in our piece on ecommerce product page design and in our broader website creation process. For stores still deciding between platforms or wondering how a Shopify versus WooCommerce choice affects how easily this kind of API migration gets handled, our Shopify vs WooCommerce comparison is a useful starting point, and our guide to ecommerce website development in Pune covers platform and cost trade-offs in more depth. Feed integrity also matters for the newer agentic shopping surfaces we covered in our piece on agentic commerce and product pages, since those systems read the same product data Google Shopping does. If you want a second set of eyes on your Merchant Center diagnostics or your current feed integration, get in touch and we can walk through what is actually happening on your account.

Sources:

• Merchant API compatibility overview - Google for Developers
• Merchant API latest updates - Google for Developers
• Google Merchant API migration: What changes before the August 2026 deadline (and how to prepare) - Productsup
• Google Merchant Center announcement - Support
• Misrepresentation policy - Google Merchant Center Help
• Google Merchant API Migration: Key Changes, Deadlines, and How to Prepare - Dataslayer