Merchant Center operations for agencies

Use Google's supported agency and account access model. Give staff only the access required for their role, maintain client ownership boundaries, and review access when relationships change. Do not solve portfolio convenience by sharing credentials.

A useful agency view identifies which client needs attention and why, while preserving a separate workspace for each account. It should not blend products, billing, alerts, or Merchant credentials across tenants.

• Client-level health and latest complete check
• New, expanded, and resolved issues
• Traffic-aware priority where identity matching is deterministic
• Connection and repeated sync failures
• Clear store context before any investigation
• Role-aware team access and an audit-friendly history

Use a consistent severity and impact workflow, but keep Google's issue, affected destinations, product set, and official guidance visible. Agency operators should be able to explain why one client or issue ranks ahead of another.

Near-real-time product-status events can shorten detection for supported changes, while scheduled reconciliation supplies a complete safety net. Lifecycle tracking makes it possible to communicate not only that a problem appeared, but also that it expanded or Google later reported recovery.

CommerceVigil Agency provides separate client workspaces, portfolio attention, Merchant issue monitoring, alerts, and read-only access. It does not take ownership of client Merchant accounts, edit feeds, or replace the agency's corrective work and client approvals.