Managing Shopping campaigns across multiple clients without a structured Merchant Center operational model is a recipe for recurring fire drills. A disapproved product here, a feed sync failure there, a policy violation that goes unnoticed for three weeks and quietly kills a client's bestseller visibility. Merchant Center for Agencies is Google's attempt to give agencies better tooling for exactly this problem.

Whether it is worth adopting depends on how many ecommerce clients you manage, what your current feed governance looks like, and whether you have the internal process to use the visibility the tool provides. This guide covers both the technology and the operations layer.

What Merchant Center for Agencies actually is

Merchant Center for Agencies is a management layer built on top of Google's existing multi-client Merchant Center structure. It provides a consolidated dashboard for viewing diagnostic health, access permissions, and feed status across all linked client accounts without having to log into each one individually.

It also introduces structured access management, making it easier to provision and revoke permissions for team members across the account portfolio without client-by-client configuration.

Who should use it and who should not

ProfileShould use?Reason
Agency managing 5+ active ecommerce clientsYesCross-account diagnostics justify the setup cost
Agency managing 1–2 clientsOptionalStandard MCA access is likely sufficient
In-house team managing a single brandNoNo multi-client management benefit
Freelancer managing 3 clients with simple feedsMaybeUseful for diagnostics cadence but not critical
Agency managing large catalog clients with frequent product changesYesFeed governance tooling is a strong fit

How it differs from the old multi-client workflow

The traditional multi-client approach required logging into each sub-account to see diagnostic issues, manually tracking which clients had active policy violations, and relying on email alerts that were easy to miss or mis-categorize. Cross-account reporting required manual data pulls or custom API work.

Merchant Center for Agencies surfaces these issues in a single view with severity classification, making it possible to triage across the entire client portfolio in one session rather than checking each account individually.

Recommended operating model for agencies

Ownership and permissions

Each client should have their own Merchant Center account with the agency holding admin access and the client holding owner or standard access. Use the Merchant Center for Agencies access panel to provision team members at the appropriate permission level — analysts get read access, account managers get standard, senior staff or the agency account get admin.

Avoid giving junior staff admin access to client accounts by default. A misconfigured feed setting or accidental account change at the admin level can have immediate Shopping campaign impact.

Diagnostics cadence

Set a non-negotiable weekly diagnostic check. The consolidated dashboard makes this fast — a ten-minute review of cross-account diagnostic status is sufficient for most portfolios. Flag anything in the "Disapproved" or "Pending review" categories for same-day investigation. Policy violations that sit unresolved for more than a week compound: products lose visibility history and can take longer to recover even after the issue is fixed.

Escalation rules for feed issues

Define clear escalation paths before a problem occurs. A disapproved product for a pricing discrepancy between feed and site is a client escalation. A disapproved product for a GTIN format error is an agency-side fix. A policy violation for a prohibited product category is a legal or compliance escalation. Without these definitions, feed issues generate circular conversations that delay resolution.

What it solves well

  • Cross-account diagnostic visibility without account-by-account login
  • Structured access management across a large team and client portfolio
  • Faster triage of active policy violations and feed health issues
  • Consolidated alerting for accounts with active product disapprovals
  • Better audit trail for access changes and permission updates

What it still does not solve

  • Feed quality improvement — you still need to work with clients on data source quality
  • Automated policy violation resolution — understanding and fixing violations still requires human judgment
  • Campaign optimization — this is purely Merchant Center management, not Google Ads campaign management
  • Cross-client benchmarking with statistical rigor — the dashboard is operational, not analytical

Ecommerce example: catalog-heavy retailer

A fashion retailer with 15,000 SKUs and daily price changes is a high-maintenance Merchant Center client. Feed sync failures happen when prices update on the site but the feed export job fails silently. Product condition declarations get flagged when the feed uses "new" for items that are technically refurbished. GTIN coverage is incomplete for house-brand products. Merchant Center for Agencies gives the account team a daily diagnostic view that catches these issues before they affect campaign performance. The weekly check catches 90 percent of issues within 24 hours rather than waiting for performance reports to flag a problem.

Lead gen note: when this is irrelevant

Merchant Center is only relevant if you are running Shopping campaigns or have product inventory to list. Pure lead generation accounts — legal, financial services, home services, B2B — have no need for Merchant Center. If a lead gen client is also running a small ecommerce component, they need their own Merchant Center account, but it will not be a primary operational concern.

A weekly feed governance workflow

Monday: Cross-account diagnostic review — flag any disapprovals or new policy violationsMonday–Tuesday: Resolve agency-side feed issues; escalate client-side issues with specific instructionsWednesday: Verify resolution of prior week escalations; follow up if still pendingFriday: Weekly feed health summary to relevant clients — include product approval rate, disapproval count, pending review itemsMonthly: Full feed quality audit per client — GTIN coverage, image quality, description completeness, price accuracy

KPI dashboard recommendations

  • Product approval rate by client (target: above 95%)
  • Active policy violations count with average days open
  • Feed sync success rate for automated feed sources
  • Products disapproved by reason category (to identify recurring upstream data issues)
  • Impression share by product category correlated with approval rate (to quantify impact of feed issues on campaign performance)

Final recommendation

Merchant Center for Agencies is worth adopting if you manage five or more active ecommerce clients with Shopping campaigns. The operational efficiency gain from consolidated diagnostics pays for the setup time within the first month. The more important investment is defining the internal process — the escalation rules, the weekly cadence, the ownership model — that makes the tool useful rather than just another dashboard that gets checked sporadically.