Ecommerce Website Development in Pune: What Google Merchant Center's 2026 Changes Mean for Your Product Feed

Ecommerce Website Development in Pune: What Google Merchant Center's 2026 Changes Mean for Your Product Feed

If your store shows up in Google Shopping results, on the Shopping tab, or in the free product listings that appear alongside search results, 2026 has been a year of real, structural change to the system behind all of that — Google Merchant Center. Three things happened this year that matter regardless of whether your dashboard "looks the same": the old Content API for Shopping was sunset on 18 August 2026, the "Merchant Center Next" interface was permanently renamed back to plain "Google Merchant Center" on 9 July 2026 (closing the door on the old classic interface for good), and Google added new product-level attributes to the feed specification in April and June 2026. None of this requires you to redesign your website. But if any part of your ecommerce website development in Pune was built or last touched years ago — a custom feed integration, a plugin nobody has opened since launch — this is exactly the kind of change that can quietly break something without anyone noticing until sales from Shopping traffic have already dropped.

This article is written for the store owner or marketing manager, not the developer. It explains what a product feed actually is, why these 2026 changes matter even to a store owner who has never looked at Merchant Center's backend, and gives you a checklist you can run yourself or hand to your developer or agency to confirm nothing has silently broken.

What a Product Feed Actually Is (and Why Shopping Depends on It)

Every product that shows up in Google Shopping — the image, price, title, availability, shipping estimate — comes from a data file called a product feed, not from your website's pages directly. Your ecommerce platform (WooCommerce, Shopify, Magento, or a custom build) generates this feed and sends it to Google Merchant Center on a schedule, or increasingly, through a live API connection. Google Merchant Center is the account and dashboard that receives this feed, checks it against Google's data-quality and policy rules, and hands the approved products over to Google Ads for Shopping campaigns and to the free listings that appear in regular search results and on Google Images.

The critical thing to understand is that this feed is a live, ongoing data pipe, not a one-time upload. If your feed integration stops syncing — quietly, silently, with no error message reaching anyone's inbox — your products don't disappear from your website. They disappear from Google Shopping and from the free listings, while your website itself keeps running and looking completely normal. A store owner checking their own site sees nothing wrong. The actual damage shows up weeks later as a slow, hard-to-diagnose decline in Shopping-driven traffic and sales, at which point tracing it back to "the feed integration broke in August" is a lot harder than catching it in week one.

This is why 2026's changes matter to business owners, not just to developers: several of them directly affect whether that pipe keeps flowing.

The Content API Sunset: The Change Most Likely to Silently Break Something

Google's Content API for Shopping — the older, developer-facing API that many custom-built stores and older plugin integrations used to push product data into Merchant Center — was officially sunset on 18 August 2026. Any integration still calling that old API had to be migrated to its replacement, the newer Merchant API, before that date. Google has also begun a progressive shutdown: requests to the old API started returning intermittent errors from 1 September 2026, with full decommissioning of the remaining endpoints expected by early 2027.

Here is why this specific change deserves attention from a business owner rather than being filed away as "a developer thing." If your ecommerce site was custom-built, or was set up with a Merchant Center integration by a developer or agency years ago and hasn't been touched since, there's a real chance that integration was built against the old Content API. Most mainstream, actively-maintained platform plugins (the official WooCommerce and Shopify integrations, for instance) have already been moved onto the current Merchant API by their maintainers. But a bespoke integration — something written specifically for your store, by a developer who may no longer be involved with the project — doesn't get updated automatically. Nobody pushes a fix to it unless someone asks them to.

The practical risk: a feed built on the sunset API doesn't necessarily fail with a dramatic, visible error the day the deadline passes. Depending on how it was built and whether it had an extension applied, it may keep half-working, sync unreliably, or simply stop updating one category of products while others continue — the kind of partial failure that is genuinely difficult to notice from the outside. The only reliable way to know your store isn't exposed is to have someone with technical access confirm, directly, which API your Merchant Center integration is actually running on, and get written confirmation from whoever built or maintains it that it's on the current Merchant API rather than the retired Content API.

If you're not sure whether your existing site was even built with Shopping and Merchant Center properly wired in from the start, our guide to ecommerce website development in Pune: platforms, cost and process for 2026 is a good place to start before this feed-specific conversation.

Merchant Center Next Has Just Become "Merchant Center" — There's No Classic Version Left

Since May 2023, Google had been gradually rolling merchant accounts from the old "classic" Merchant Center interface onto a redesigned version called "Merchant Center Next." On 9 July 2026, Google closed that migration out by simply renaming Merchant Center Next back to "Google Merchant Center" — dropping the "Next" label from the interface, help documentation, and communications. Google's own guidance is that this is a naming change only: accounts, product data, and running campaigns are unaffected, and login links and bookmarks continue to work.

The reason this is still worth flagging to a Pune ecommerce business owner is less about the rename itself and more about what it confirms: there is no more "classic" Merchant Center to fall back to. If your store, or your developer, had been putting off getting comfortable with the newer interface — perhaps because a workflow, a report, or a custom process was still being run through the old classic dashboard — that option is now closed. Anyone managing your feed day-to-day needs to be operating in the current interface, full stop. If your agency relationship has been dormant since your store launched, this is a reasonable moment to confirm whoever has admin access to your Merchant Center account is actually looking at it in its current form.

The New 2026 Attributes: Concrete Fields Worth Filling In, Not Just Background Noise

Starting 14 April 2026, Google added new attributes to the Merchant Center product data specification. These aren't abstract technical changes — they're specific fields in your feed that, filled in correctly, can change how competitively your listing displays against other Shopping results.

handling_cutoff_time. This attribute lets you specify, at the product or feed level, the exact daily deadline by which an order must be placed to be processed and shipped that same day. Filling this in accurately is what allows Google to show a more precise, same-day delivery estimate on your listing rather than a vaguer shipping window. Leaving it blank doesn't break anything, but it means Google falls back to less specific delivery messaging — a real disadvantage next to a competitor's listing that does show a confident same-day cutoff. This is purely a feed-configuration field about how your website's checkout and fulfillment process is described to Google; how your actual dispatch operations are run internally is a separate, operational question outside the scope of what your feed can control.

minimum_order_value. Previously, a minimum spend threshold could only be set as one account-wide rule in Merchant Center. The new attribute lets you set this per product or per product group in your feed instead — useful if, for example, a specific supplier or product line genuinely requires a different minimum order value than the rest of your catalogue. Again, this is a data field describing a commercial policy, filled in through your product feed; it is not itself a pricing, tax, or shipping decision, and any actual minimum-order or shipping charge policy your store applies should be confirmed against what your business has actually agreed with customers and, where GST or tax treatment is involved, with your chartered accountant — not decided by what looks tidiest in a Merchant Center field.

The optional video link (video_link) attribute. Introduced in the same April 2026 specification update, this lets you submit up to several product videos per listing (Google specifies 720p minimum resolution, roughly 6 seconds to 4 minutes long, and either a direct video file URL or a YouTube link). From 30 June 2026, videos submitted this way became eligible to actually display in Shopping ads and listings, subject to a policy and quality check. A validation issue with a specific video shows up in Merchant Center's "Needs attention" section, and importantly, a video-specific error only blocks that video from serving — it does not pull down the rest of that product's listing. For a Pune D2C brand that already produces product photography or short reels for Instagram, repurposing that same video content into the feed is a genuinely low-effort way to make a listing stand out against text-and-photo-only competitors.

None of these three attributes are mandatory. But an empty field is a missed opportunity next to a competitor who filled theirs in, and all three are the kind of detail an agency doing proper ongoing feed maintenance should be checking and populating as a matter of course — not something a store owner should have to discover in a blog post.

If You Run WooCommerce or Shopify: What "Current Integration" Actually Looks Like

Most Pune ecommerce stores we see run on WooCommerce or Shopify rather than a fully custom build, and the good news is that the official platform tools have already absorbed most of this year's changes for you — provided you're actually using the official, current tool rather than a legacy plugin nobody's updated.

For WooCommerce specifically, the official Google for WooCommerce extension now syncs your product catalogue to Merchant Center in near-real-time: a price change, a stock update, or a new product in your WordPress admin reflects in Merchant Center without a scheduled batch upload or a manual re-submission. The same extension also supports tagging products from your catalogue for YouTube Shopping, letting viewers buy directly from tagged products in your videos, Shorts, and live streams (YouTube's own channel eligibility requirements, such as a subscriber threshold, apply separately from anything on the Merchant Center side). If your WooCommerce store is still running an older or third-party feed plugin instead of the official Google for WooCommerce extension, that's worth a direct comparison — older plugins built before this year's API changes are exactly the kind of integration at risk from the Content API sunset described above.

Shopify's native Google & YouTube sales channel is maintained directly by Shopify against Google's current APIs, so most Shopify stores using that built-in channel are less exposed to the Content API sunset specifically — the main thing worth confirming is simply that you're using Shopify's official channel rather than a legacy third-party feed app that hasn't been updated recently.

If your store is a custom build — Node, PHP, or any framework without an off-the-shelf Google integration — none of this happens automatically, and the responsibility for confirming your feed sync is current sits entirely with whoever built and maintains your site. This is also where a full platform review is worth having: if you're weighing whether your current setup still fits your business at all, our piece on whether headless commerce is worth it for a growing Indian store in 2026 covers that broader architecture decision, and if you're evaluating newer distribution channels alongside Google Shopping, whether your store should integrate with ONDC in 2026 is a related read.

A Summary Table: The 2026 Merchant Center Changes and Their Effective Dates

Google has already flagged further product-data changes for early 2027 as part of its own announced timeline, so it's worth treating feed maintenance as an ongoing task rather than something you fix once and forget.

A Product Feed Health Checklist You Can Actually Run

You don't need to be technical to ask the right questions here. This is a checklist you can either work through yourself with access to your Merchant Center account, or hand directly to your developer or agency and ask for a straight answer against each line:

• Confirm the API your feed integration runs on. Ask directly: "Is our Merchant Center feed integration running on the current Merchant API, or is any part of it still calling the old Content API for Shopping?" If nobody can answer this confidently, that's the first thing to get resolved.
• Check sync frequency and last-updated timestamps. In Merchant Center, product data should show as recently synced — hours, not weeks. A feed that hasn't updated in a long stretch is a warning sign even if no error is showing.
• Review the "Diagnostics" and "Needs attention" sections for error and warning counts. A rising count of disapproved products or unresolved warnings, especially anything video-specific if you've started submitting product videos, needs a look rather than being left to accumulate.
• Check whether the new attributes are actually populated where relevant — handling_cutoff_time if same-day dispatch is genuinely part of your operations, minimum_order_value if that applies to any part of your catalogue, and video_link if you already have usable product video content sitting unused.
• Confirm which plugin or extension is actually connected, particularly on WooCommerce — is it the official, actively maintained Google for WooCommerce extension, or an older third-party feed tool?
• If you're on a fully custom build, get written confirmation from your developer or agency of when the Merchant Center integration was last reviewed against Google's current API and specification, not just when the store itself was last updated.

None of these checks require touching your website's design or storefront. They're entirely about the data pipe running quietly in the background — which is exactly why they're easy to overlook until the sales numbers start telling a story nobody can otherwise explain.

Frequently Asked Questions

How do I know if my store's Merchant Center feed is still using the old Content API?

The most reliable way is to ask whoever built or maintains your feed integration directly, and ask for written confirmation rather than a verbal assurance — this is a backend, developer-level detail that isn't visible from the Merchant Center dashboard's everyday screens in an obvious way. If your store uses the official WooCommerce (Google for WooCommerce) or Shopify Google & YouTube channel, those are already maintained against the current Merchant API by their respective platforms. If your integration was custom-built years ago and nobody has actively maintained it since, treat that as a reason to get it checked rather than an assumption that it's fine.

Will my Google Shopping listings disappear if my feed integration isn't migrated?

Not necessarily immediately, and not necessarily all at once — which is actually what makes this risk harder to catch. A feed built on the sunset Content API may keep partially working, sync unreliably, or fail silently for certain products or categories rather than throwing an obvious, visible error. The safest assumption is that any integration not confirmed as running on the current Merchant API should be checked directly rather than left until traffic numbers start showing an unexplained decline.

Do these Merchant Center changes affect my website itself, or just the backend feed?

Just the backend feed and the data pipe to Google — your website's storefront, pages, and checkout are unaffected by any of this. The changes are entirely about how your product data reaches Google Merchant Center and, from there, Google Shopping and free listings. That said, if your feed was originally built as part of your website's development, the same developer or agency relationship that built your site is usually the right one to check and maintain it.

Should I fill in the new handling_cutoff_time and minimum_order_value attributes even if they don't apply cleanly to my business?

Only fill them in where they genuinely reflect how your store actually operates — these are feed-configuration fields describing real commercial facts to Google, not settings to game for a better-looking listing. If same-day dispatch cutoffs or per-product minimum order values are things your business already applies operationally, populating them accurately in the feed is worth doing. If they don't apply, leaving them blank is the correct choice; just don't confuse a blank feed field with your store lacking a shipping or minimum-order policy of its own, which is a separate operational and, where relevant, tax question your accountant should confirm.

Is this the same thing as GST or tax compliance for my online store?

No — this article is entirely about the technical feed-configuration side of Google Merchant Center: keeping your product data syncing correctly and filling in the newer optional attributes Google added in 2026. Some of these attributes (like minimum order value) touch commercial settings that also have tax implications, but the actual GST and tax treatment of your sales is a separate matter that should be confirmed with your chartered accountant — nothing in a Merchant Center feed field is tax advice or a substitute for that conversation.

Where This Fits Into Your Broader Ecommerce Setup

A healthy, current product feed is the foundation underneath any Google Shopping or Performance Max advertising spend — if the feed is stale or broken, ad spend on top of it is working against a handicap regardless of how well the campaigns themselves are built. If Shopping and search advertising are a serious part of your growth plan, it's worth having your feed reviewed alongside your campaign structure; our Google Ads management work includes exactly this kind of feed-and-campaign alignment check. Feed health also intersects with technical SEO more broadly — structured data, page speed, and crawlability all affect how your free listings and organic Shopping presence perform, which is the territory our technical SEO service covers.

At Govindani Infotech, this is the kind of unglamorous, easy-to-postpone technical maintenance we handle as part of ongoing ecommerce website development in Pune work for our clients — not just building the storefront once, but making sure the data feeding Google Shopping keeps working quietly in the background as Google's own platform keeps changing under it. If you're not sure whether your store's Merchant Center integration is current, or you'd simply like someone with technical access to check it against everything above, get in touch through our contact page or message our team directly on WhatsApp and we'll take a look before assuming anything is fine.

Sources:

• Latest updates | Merchant API | Google for Developers
• Google Merchant API migration: What changes before the August 2026 deadline
• Google's Content API for Shopping sunsets in August 2026 | PinMeTo
• Merchant Center Next is now Merchant Center - Google Merchant Center Help
• Google drops Next from Merchant Center Next - Search Engine Land
• Merchant Center product data specification update 2026 - Google Merchant Center Help
• Handling cutoff time [handling_cutoff_time] - Google Merchant Center Help
• Google Shopping Gets Video on June 30. Will Your Products Have Any?
• Google for WooCommerce - WooCommerce Marketplace
• YouTube Shopping is live for WooCommerce - WooCommerce