Can one Merchant Center account serve multiple stores?

Merchant Center ties an account to a verified and claimed website. That claim is exclusive, which is the constraint that shapes everything else: two accounts cannot both claim the same domain, and one account is not designed to represent two unrelated storefronts.

So the first question to answer is what you actually have. Two brands on two domains are two stores. One brand serving Canada and the United States from one domain is one store with two markets. One brand with a separate wholesale portal on a subdomain is a judgement call that depends on whether the catalogue, pricing and policies differ.

Getting this wrong in the direction of too many accounts causes problems, because duplicate accounts representing the same business are a policy concern and can affect all of them. Getting it wrong in the other direction causes practical pain, since settings, policies and diagnostics that should differ end up shared.

When there genuinely are several stores, the structure Google provides is an advanced account holding sub-accounts, one per store, with the parent used for administration rather than for selling.

This structure suits four situations. Agencies and in-house teams managing several unrelated merchants, where each merchant needs its own domain, policies and diagnostics but the team wants a single place to work. Groups with multiple brands, each with its own storefront and identity. Businesses operating separate legal entities per region with their own tax registration, returns handling and terms. And franchise or dealer networks where each location or franchisee sells independently.

What you gain is separation where it matters and consolidation where it helps. Each sub-account carries its own website claim, its own feeds, its own shipping and returns settings and its own diagnostics, while the parent gives a single sign-in, a consolidated view and a place to manage users.

What it does not give you is protection from policy problems. Enforcement is assessed against the business and the site, so a serious issue in one sub-account can affect how the others are treated, particularly if they share ownership, infrastructure and contact details. Treating each store's compliance as genuinely separate work is the safer posture.

Linking to Google Ads is done per sub-account, which is usually what you want, since campaigns and budgets belong to each store.

Selling into several countries from one domain is the most common. One account can hold feeds targeting different countries and languages, with country-specific pricing, shipping settings and delivery times configured for each. You do not need an account per country, and creating one usually makes maintenance harder rather than easier.

Multiple currencies are the same story. A feed can specify currency per target, and where a store serves several markets from one catalogue the usual approach is one primary feed plus country feeds or supplemental feeds carrying the differences.

A store using subfolders or subdomains for markets, such as a Shopify Markets setup, is still one store. The claim covers the domain, and the market structure is expressed in feeds and targeting.

The genuine dividing lines are a different domain, a different legal entity, materially different policies, or a catalogue and pricing that have nothing to do with each other. When only one of those is true, look hard at whether a second account is really necessary before creating it.

One further case worth naming: a store that also sells on a marketplace does not need an account for the marketplace presence. That listing belongs to the marketplace operator.

Claim each domain once, in the account that will actually serve it, and grant access to people rather than creating parallel accounts for different teams. Where an agency needs access, add them as users on the existing account or link the account to their advanced account rather than duplicating it.

Keep business information consistent within each store: the name, address, contact details and policy pages in the account should match what appears on the site, because mismatches are a common source of trouble during review.

Configure shipping, returns and tax per store rather than copying settings between them. Two brands with different fulfilment realities that share one set of settings will generate mismatch issues in whichever one the settings do not describe.

Document the structure somewhere your team can find it: which account claims which domain, which Ads accounts are linked, who has access at what level, and which feeds serve which countries. This sounds administrative and it prevents the most common failure, which is a store quietly running on an account nobody remembers owning.

If you inherit a tangle of accounts, resolve it deliberately. Consolidate to the account that holds the verified claim and the performance history, move feeds across, confirm approvals, and only then close what is redundant.