Merchant Center Agency Scaling for Up to 1,000 Accounts

You’re adding clients faster, and the immediate question is whether one Merchant Center agency account can keep carrying the portfolio. The harder question is whether your operating model will remain controlled as the account count rises.

Google’s documented ceiling removes one important uncertainty. A Merchant Center for Agencies account can accommodate a large portfolio, but capacity alone won’t prevent confused ownership, unauthorized changes, stalled onboarding, or forgotten offboarding. You need to turn the limit into an account-management plan.

Treat 1,000 as a capacity ceiling, not a growth target

Agency Admins can link up to 1,000 client Merchant Center accounts under one agency account. The maximum was previously undocumented, and its clarification does not introduce new linking functionality.

That distinction matters. The number helps you plan infrastructure, but it says nothing about how many accounts your team can manage well. An agency with unclear ownership can lose control long before it reaches the platform ceiling. An agency with a disciplined operating system can use the available capacity without turning the central account into an unsearchable holding area.

Start by measuring linked accounts as the platform measures them. Your sales team may count clients, contracts, or brands, but the relevant capacity unit is the linked Merchant Center account. Maintain four portfolio figures:

• Current load: accounts that are linked now.
• Committed demand: accounts attached to signed or approved onboarding work but not yet linked.
• Probable demand: accounts likely to enter onboarding from the active pipeline.
• Planned removals: relationships moving through an authorized offboarding process.

Use those figures to calculate headroom rather than waiting for a linking request to expose a capacity problem. Keep committed and probable demand separate. Treating every sales opportunity as guaranteed inflates the forecast, while ignoring signed onboarding work understates it.

The practical trigger is not account number 1,000. It is the point at which forecast demand could consume your remaining headroom before you have approved another structure. That is when leadership needs to make the decision, because account architecture should not be designed in the middle of a client launch.

Build an account registry before scaling the portfolio

The agency interface should not be your only system of record. Maintain a registry that explains why every account is present, who owns the relationship, and what should happen next. This can live in your established work-management system as long as it is governed and consistently updated.

At minimum, give every linked-account record these fields:

• Client name and the exact Merchant Center account identifier.
• Internal lifecycle state.
• Client-side contact responsible for approving access.
• Agency relationship owner.
• Operational owner and backup contact.
• Date and reason for the original linking request.
• Agency Admin who completed the approved action.
• Applicable team, business unit, or portfolio segment.
• Open exceptions or unresolved handoff work.
• Offboarding decision and completion state, when relevant.

The account identifier is especially important. Names change, abbreviations collide, and staff members remember clients differently. The identifier gives onboarding, delivery, and offboarding teams one unambiguous object to reference.

Use internal lifecycle states

Define lifecycle states in your registry instead of assuming everyone interprets a generic status such as active in the same way. A workable internal sequence is:

• Requested: an intake record exists, but the request has not passed validation.
• Approved for linking: the client, account identifier, agency owner, and authority to proceed have been confirmed.
• Admin action pending: the request is ready for an Agency Admin.
• Linked, handoff pending: the administrative action is complete, but operational ownership has not been accepted.
• Managed: the account has a named owner and has entered the agency’s normal workflow.
• Exception: the record has a mismatch, failed handoff, ownership question, or another issue requiring review.
• Offboarding approved: the commercial relationship has ended or changed, and the authorized removal process is underway.
• Closed: the offboarding work and internal recordkeeping are complete.

These are operating labels, not claims about status names inside Merchant Center. Their purpose is to keep a submitted request from being mistaken for a completed handoff.

Make linking a controlled handoff

Because Agency Admins perform the linking action, they can become either an effective control point or an avoidable bottleneck. Give them a complete, validated request rather than asking them to reconstruct missing context.

1. Establish authority. Record who requested the relationship and who approved it on the client and agency sides.
2. Validate the target. Match the client name to the intended Merchant Center account identifier before an admin acts.
3. Assign ownership. Name the agency relationship owner, operational owner, and backup before linking.
4. Complete the approved action. An Agency Admin links the validated account and records the outcome.
5. Accept the handoff. The operational owner confirms responsibility, reviews the account in the normal delivery workflow, and closes or escalates any exception.

A successful link proves that the administrative relationship was established. It does not prove that the client account is correctly configured, that its product data is healthy, or that the delivery team knows what it owns. Keep linking confirmation and operational validation as separate checklist items.

Decide whether one agency structure still fits

The newly documented maximum makes one part of the decision simple: a single agency account cannot be your unexamined plan for a forecast beyond 1,000 linked accounts. Below that ceiling, the better structure depends on governance as well as capacity.

Do not create extra agency accounts merely as an assumed workaround. The published maximum defines what one agency account can carry; it does not, by itself, establish which fallback structure Google will support for your organization. If your forecast could exceed the ceiling, confirm the supported arrangement with Google before promising an onboarding path to clients.

Likewise, do not fragment the portfolio solely to make the numbers look tidy. Every additional operating structure introduces another administrator roster, capacity view, reconciliation process, and handoff boundary. Separation should solve a defined capacity or governance problem that is worth that overhead.

Scale controls and exception handling with the account count

Large portfolios usually become difficult at their edges: a request with the wrong identifier, an employee who changes teams, a client that has left but remains in the registry, or a linked account that never received an operational owner. Your control system should make those exceptions visible before they disappear into the total account count.

Assign explicit responsibility for the functions below. One person may hold more than one role, but the responsibility should never be implicit:

• Agency administration: performs validated linking actions and maintains the authorized administrator roster.
• Portfolio ownership: maintains the registry, capacity forecast, and reconciliation process.
• Relationship ownership: confirms that each linked account corresponds to a current, authorized client relationship.
• Operational ownership: accepts the delivery handoff and resolves account-level work.
• Offboarding ownership: coordinates authorized removals and closes the internal record.

Reconcile the registry against the agency view after meaningful change, not only when someone notices a discrepancy. Useful triggers include a batch of onboardings, a change to the Agency Admin roster, an employee departure, the end of a client relationship, an acquisition, or a period of unusually high intake.

Your exception queue should surface conditions that require a decision:

• A linked account has no active relationship owner.
• An onboarding request has no validated account identifier.
• An admin action has no matching approval record.
• A completed link still lacks operational acceptance.
• An offboarding record remains open after the relationship has ended.
• The registry count does not match the visible agency portfolio.
• The capacity forecast has entered the agency’s internally defined buffer.

Track the age and ownership of exceptions, not just their quantity. A small queue of unowned issues is more dangerous than a larger queue in which every item has an accountable person and a clear next action.

Automation can help with reminders, duplicate checks, status synchronization, and capacity warnings if your toolchain supports them. Keep authority with people: linking and offboarding should still trace back to a validated request and an identifiable approver. Automating an incomplete process only makes the resulting ambiguity move faster.

Key takeaways

• One Merchant Center for Agencies account can support up to 1,000 linked client accounts, and Agency Admins perform the linking.
• The 1,000-account figure is a documented ceiling, not evidence that every agency can operate effectively at that scale.
• Forecast linked accounts separately from clients, contracts, or sales opportunities.
• Maintain a governed registry with exact account identifiers, approval records, owners, lifecycle states, and offboarding status.
• Treat linking and operational acceptance as separate steps.
• Design another structure before forecast demand reaches the ceiling, and confirm the supported arrangement with Google rather than assuming an unlimited workaround.

Start with the registry. Reconcile it against your current agency view, name an owner for every account, classify every pending request, and calculate the headroom against committed onboarding work. Once you can explain who owns each link, why it exists, and what happens next, the 1,000-account capacity becomes useful infrastructure instead of a future surprise.

References

• Search Engine Land – Google Merchant Center for Agencies now supports up to 1,000 linked accounts