Google Merchant Center Next is the platform every retailer now uses to manage product data, feeds, and Shopping diagnostics, replacing classic Merchant Center entirely. All accounts were migrated automatically, with no rollback available, so understanding the new terminology and add-ons model is no longer optional. This guide walks you through what changed and exactly what to check first.
TL;DR:
- The migration to Merchant Center Next was completed on September 30, 2024, with all accounts automatically transitioned to the new interface.
- Terminology changes include “data sources” replacing feeds, “marketing methods” for destinations, and “needs attention” for diagnostics, with advanced features now called add-ons.
- Setting up Merchant Center Next correctly requires verifying business and site ownership, enabling relevant add-ons, and fixing high-impact policy or pricing issues first.
- Diagnostics and performance reports are now centralized under specific menus, with regular weekly and daily checks essential for maintaining account health.
- Product Studio is available only in select markets like the US, UK, Canada, Australia, Japan, and India, and generated imagery should supplement, not replace, authentic product photos.
Table of Contents
- What is Google Merchant Center Next and when did it launch?
- What changed between Merchant Center Next and classic?
- How do you set up Merchant Center Next correctly?
- Where do diagnostics and reports live now?
- Is Product Studio available in your market yet?
- Why do disapprovals and suspensions still happen?
- Oxedent’s view: make product data everyone’s job, not just marketing’s
- Where to check the official guidance yourself
- Sources
What is Google Merchant Center Next and when did it launch?
Merchant Center Next is the default interface for managing your product catalogue, feeds, and Shopping diagnostics with Google. If you log into Merchant Center today, this is what you see. There is no separate “classic” version to switch back to.
Google completed the migration to Merchant Center Next, with classic Merchant Center retired on 30 September 2024. Every merchant account moved across automatically. You didn’t need to request the upgrade, rebuild your feeds, or reconfigure campaigns.
That doesn’t mean anything changed on your end. The rebrand carried real structural shifts in how Google talks about your data and where you go to fix problems:
- Your existing feeds, campaigns, and linked accounts carried over intact.
- Terminology changed across the interface, including how “feeds” and “diagnostics” are labelled.
- Advanced functionality moved behind an add-ons system rather than sitting in the main menu.
- Historic performance data and account structure remained accessible, just relocated.
If your team still trains new starters on screenshots of the old dashboard, that documentation is now actively misleading. Update it before it causes a setup mistake.
What changed between Merchant Center Next and classic?
The terminology swap is the first thing that trips up experienced feed managers, because the concepts are familiar but the labels aren’t. Google renamed three core areas of the platform, and if you’re searching your account for the old menu item, you’ll come up empty.
Here’s the direct mapping:
- Feeds → Data sources. The input mechanism for your product data now covers files, the Content API, and website crawling under one umbrella term.
- Destinations → Marketing methods. Where your products can appear, such as free listings or Shopping ads, is now called a marketing method.
- Diagnostics → Needs attention. Your error and warning dashboard sits under this new tab.
- Advanced features → Add-ons. Promotions, local inventory, and advanced data source management are now opt-in modules rather than default menu items.
Beyond naming, Merchant Center Next introduced a unified product list that supports omnichannel selling (online and in-store) from one view, rather than segmented feed-by-feed reporting. It also enables automatic website crawling in eligible accounts, meaning Google can detect and add products directly from your site’s structured data without you uploading a file at all.
Google’s own data shows merchants using the new experience have seen increased product additions and higher engagement since the migration completed, largely because the crawl-based detection catches products that manual feeds missed.
How do you set up Merchant Center Next correctly?
Most disapprovals and missed sales trace back to a handful of setup steps that got skipped during migration, not to genuinely new problems. Work through this checklist in order, because later steps depend on earlier ones being correct.
- Verify your business information and claim your site. Confirm your business name, address, and site ownership are accurate. This underpins every marketing method you’ll enable later.
- Set up People & Access. Give the right team members and any agency partners the correct permission level, from standard access to admin.
- Confirm your data sources. Check that your primary data source (file, API feed, or crawl) is live, and that languages and target countries are set correctly for every market you sell into.
- Enable the add-ons you need. Turn on advanced data source management if you use attribute rules or supplemental feeds, plus promotions and local inventory if relevant to your business.
- Set shipping, tax, and returns policies. These sit at account level and affect every product, so errors here cascade widely.
- Configure your marketing methods. Confirm free listings and Shopping ads are both switched on where appropriate.
- Run a full Needs attention check. Fix account-level and policy issues first, since these can block your entire catalogue rather than individual products.
Pro Tip: Don’t fix Needs attention issues in the order Google lists them. Sort by potential impact instead, tackling account-wide policy blocks and price mismatches before cosmetic attribute warnings that affect a handful of SKUs.
Where do diagnostics and reports live now?
Needs attention is your central triage board, found under the Products menu. It groups issues by severity, and a View setup tab sits alongside it to confirm your account-level configuration is complete. Diagnostics history moved too: check Products > Needs attention > View history for a timeline of past issues rather than digging through old email alerts.
Analytics also relocated. Reports like Popular products and Price insights now sit under Analytics > Products, consolidated with performance data rather than scattered across separate tabs, according to Google’s transition FAQ.
On cadence, treat this like stock control, not a monthly chore:
- Review Needs attention weekly at minimum, more often during peak trading.
- Check price and availability daily for volatile SKUs, since mismatches here are a leading disapproval cause.
- Pull Popular products monthly to spot catalogue gaps before a competitor fills them.
Is Product Studio available in your market yet?
Product Studio is Google’s free, AI powered imagery toolkit for product listings, covering background removal, image upscaling, and basic animation effects. It’s built for merchants who need more creative volume than their photography budget allows.
Availability is currently limited. Product Studio works for merchants in the United States, United Kingdom, Canada, Australia, Japan, and India. If you trade elsewhere, the feature simply won’t appear in your account yet.
Treat generated imagery as a supplement, not a replacement:
- Use it for background swaps and quick variations on lower-priority SKUs.
- Keep genuine photography for hero products and anything where texture, scale, or colour accuracy drives conversion.
- Test generated assets against your existing creative before rolling them out account-wide.
Why do disapprovals and suspensions still happen?
Price mismatches between your data source and live site remain the single most common disapproval cause, closely followed by missing or malformed GTINs and policy violations on restricted categories. None of that changed with the migration.
Triage inside Needs attention first, fixing account-level policy flags before individual product warnings, since a policy block can suppress your whole catalogue while a single bad attribute only hits one listing. Google’s own guidance on the transition to Merchant Center Next confirms this severity grouping is intentional, not arbitrary.
Pro Tip: If a suspension appears with no clear cause listed, check your data source freshness before appealing. A stale feed often looks like a policy violation to Google’s systems.
- Escalate to a formal appeal only once you’ve confirmed the underlying data issue is genuinely fixed.
- If suspensions recur across multiple SKUs or categories, that’s usually a structural feed problem worth a full audit, and our guide to suspension fixes that last covers the recovery sequence in detail.
Oxedent’s view: make product data everyone’s job, not just marketing’s
Too many teams still treat Merchant Center as the marketing department’s problem, updated when a campaign breaks rather than maintained as infrastructure. That’s backwards. Your product data feeds every Shopping and Performance Max campaign you run, so a stale attribute or missing GTIN doesn’t just trigger a warning, it quietly caps how much revenue that SKU can ever generate.
The teams getting this right lean hard on automation: attribute rules and API-based data sources to remove manual fixes, add-ons switched on deliberately rather than left dormant, and a genuine weekly Needs attention review rather than a reactive scramble when sales drop. Daily price checks on volatile SKUs are non-negotiable if you sell anything with fluctuating stock or margin. Oxedent has pulled accounts out of suspension and back into profitable Shopping and Performance Max scaling often enough to know the pattern: the merchants who struggle aren’t short on effort, they’re short on ownership of the data itself.
— Biplab
Where to check the official guidance yourself
For the primary sources behind this guide, read Google’s rollout and terminology changes and the full transition FAQ. For hands-on help scaling campaigns once your setup is clean, see Oxedent’s guide to Performance Max for ecommerce.
Sources
A data source is any input Google uses to build your product list, whether that’s a file, the Content API, a website crawl, or a supplemental source layered on top. Products get created the moment Google reads valid data from any of these, which is a meaningful shift from the single-feed mindset most merchants grew up with.
Choosing between them depends on how often your catalogue moves:
- Frequently asked questions about the transition to Merchant Center Next
For anyone running high-SKU-count or high-change catalogues, the Content API is genuinely the only scalable option long-term. A Google Shopping feed setup guide is worth revisiting if your current data source was built for the old feed model rather than this one.