Google updated its Merchant Center help pages on Aug. 14, 2026 to state that Merchant Center for Agencies accounts can link up to 1,000 client Merchant Center accounts. That single line removes a key unknown for agencies running large retail portfolios: a concrete ceiling that changes how you plan account architecture, onboarding and automation at scale.
Why this matters now
For agencies that consolidate product feeds, manage numerous inventories or automate feed maintenance across clients, an undocumented account ceiling created operational uncertainty. The newly documented 1,000-account limit doesn’t add features, but it does set a practical threshold for growth planning.
Knowing the cap lets teams decide when to split client sets across multiple agency accounts, rework onboarding templates, or reconfigure integrations before hitting a hard limit during a peak campaign or onboarding wave.
What to audit immediately
Start with an account-count audit. Confirm how many client Merchant Center accounts are linked to your agency-level account and tag clients by revenue, product complexity and integration dependencies. That will reveal which accounts are candidates for consolidation and which would be costly to move.
Check your shared infrastructure: onboarding scripts, feed-processing jobs, permission roles, reporting pipelines and any automation that assumes a single agency-level account. Identify automations that will break or become harder to maintain if you split clients across multiple agency accounts.
Review external integrations—ads platforms, analytics connectors, inventory or PIM integrations—that reference Merchant Center links. Map which clients rely on cross-account joins or shared data flows so you can test migration scenarios without interrupting live campaigns.
Options and trade-offs
There are two straightforward operational responses: consolidate compatible clients under fewer Merchant Center accounts where business rules allow, or distribute clients across multiple agency-level accounts to stay below the 1,000 limit.
Consolidation reduces fragmentation but isn’t always viable due to ownership, reporting or catalog differences. Running multiple agency accounts preserves isolation at scale but increases complexity for cross-client reporting, single-pane-of-glass dashboards and permission management.
Either approach requires governance: version-controlled onboarding playbooks, automated tests for integrations, and reporting adapters that can normalize data across multiple agency accounts.
Limits the notice doesn’t cover
The documentation change lists the linked-account ceiling but does not clarify related constraints such as API quotas, per-account product-item limits or other performance caps. Treat the 1,000 figure as a planning parameter, not a guarantee that other limitations have been raised.
Validate API quotas, item thresholds and rate limits in Google’s developer documentation or via your Google contacts before making large-scale architecture decisions.
Practical next steps and what to watch
1) Run the audit this quarter. Assign an owner to produce an account-count dashboard and a sensitivity analysis for the top 5 migration risks.
2) Model two scenarios: conservative (consolidate where possible) and distributed (split across agency accounts). For each, estimate the operational overhead—reporting, access control, testing—required to maintain SLAs.
3) Add monitoring and escalation triggers. If your linked-account count approaches 800–900, start migrations early; don’t wait for the hard cap to force reactive moves during peak season.
Watch Google’s Merchant Center updates and developer docs for changes to API quotas or product limits. Any change there could affect which scenario makes sense for your agency.
Actionable clarity is the value here: Google has set a visible boundary. Your next job is to map the operational work required to manage around it—before it becomes a bottleneck.
