What changed in Merchant Center Next
The practical differences merchants notice in Merchant Center Next, the consolidated UI, renamed sections, automatic behaviours, and what it means for how you manage feeds.
Merchant Center Next is the current Merchant Center, the classic interface has been retired. Most of your product data and feeds carried over unchanged, but the navigation, the naming, and some default behaviours moved. This is a map of what shifted, so the muscle memory from classic Merchant Center doesn't send you looking for menus that no longer exist.
The short version
Merchant Center Next is the current, and only, Merchant Center. Google consolidated the classic interface into a simpler, more automated one and retired the old version. Your account, products, feeds and the product data spec all carried across: the spec attributes you submit did not change. What changed is where things live and how some defaults behave. If you learned Merchant Center on the classic UI, this is the map to the new one.
What merchants actually notice
- "Feeds" became "Data sources." The concept is identical (a primary data source supplies products, a supplemental data source patches attributes on top by
id) but the menu label and location moved. - A consolidated home / overview. Performance, product status and account health surface together on landing rather than being scattered across separate tabs.
- Products and Diagnostics are simpler and closer. Item issues are more front-and-centre; the workflow to find why a product is disapproved is shorter.
- Automatic behaviours are more prominent by default. Automatic item updates and image improvements are surfaced (and in some cases on) more readily than in classic: worth an explicit look. See automatic improvements.
- Store-level and website context is more integrated. Merchant Center Next leans harder on your verified website, and can infer more product data directly from the site than classic did.
- Business information and settings were reorganised: shipping, tax, and account settings sit in different places than the classic muscle memory expects.
Terminology that shifted
| Classic Merchant Center | Merchant Center Next |
|---|---|
| Feeds | Data sources |
| Primary feed | Primary data source |
| Supplemental feed | Supplemental data source |
| Feed fetch / schedule | Data source fetch settings |
| Products list | Products |
| Diagnostics | Products → Item issues / Needs attention |
The mechanics behind each pair are the same. A supplemental data source still joins on id and overrides attributes on top of the primary: nothing about the supplemental feed model changed except the name.
Deep dive What Next automates, and why a clean feed still wins
The defining shift in Merchant Center Next is how much it will do for you if you let it: and that's exactly what an advanced merchant needs to be deliberate about.
- It infers more from your website. Next can build or supplement product data by reading your verified site, not just your feed. Convenient for merchants with no feed at all; a source of surprise for merchants who do run a curated feed and suddenly see attributes they didn't submit. If your feed is the source of truth, make sure inferred data isn't quietly contradicting it.
- Automatic improvements sit closer to default-on. Automatic item updates (price and availability corrected from your site) and automatic image improvements are more prominent and more readily enabled. They're a safety net for a stale feed, and a source of drift for a clean one: because they change what Google serves without changing your feed. The trade-offs are covered in automatic improvements.
- The account leans on your site as a live signal. Because Next cross-checks the site more aggressively, feed-vs-site consistency matters more than ever. A feed that lags the site on price or stock triggers corrections (or disapprovals) faster.
The through-line: Merchant Center Next is optimised for merchants who don't have a clean, complete feed, and it will paper over gaps automatically. If you do control your feed properly, the automation is something to configure on purpose rather than inherit: because a served catalog that's a blend of your feed, inferred site data, and automatic corrections is one nobody can fully account for. The advanced posture is unchanged from classic: submit complete, accurate, well-structured product data so Google has nothing to guess at, and treat the automatic layers as fallbacks you've consciously decided to keep or switch off.
What did not change
The parts that matter most for feed quality are untouched:
- The product data spec: the same attributes, the same requirements, the same identifier rules.
- Feed delivery: scheduled fetch, upload, and the Content API / delivery methods all still work.
- The supplemental-feed model: join on
id, override attributes on top of a primary. - How a served feed URL is consumed: a hosted feed URL still registers as a primary data source exactly as before.
So the migration is mostly relearning the map. The discipline that produces a healthy feed (complete identifiers, specific categories, accurate pricing) carries over one-for-one.
Frequently asked questions
Did my feeds and product data change when I moved to Merchant Center Next?
The underlying data carried over, your products, identifiers, and the product data spec are unchanged. What moved is the interface, where feeds live in the menu, what they're called, and how some sections are laid out. The attributes you submit are the same.
Where did "Feeds" go?
Feeds now live under Data sources. A primary feed is a "primary data source" and a supplemental feed a "supplemental data source", but they behave the same way, a primary supplies products, a supplemental patches attributes on top by id.
Is classic Merchant Center still available?
No. Merchant Center Next is the only version. Any guide still referring to the classic layout is describing menus that no longer exist.