Google Merchant Center for Franchises: Centralized vs. Per-Location Account Structure

The Core Decision Every Franchise Faces

Franchise and multi-location retailers hit a structural question that single-location sellers never have to answer: should every location share one Merchant Center account, or should each location (or franchisee) run its own? This isn't a cosmetic choice — it affects suspension blast radius, reporting granularity, franchisee autonomy, and how quickly problems at one location can be isolated versus how they cascade across the whole network.

We see franchise brands make this decision by accident more often than by design — usually whichever structure the first location happened to set up becomes the default for every location that follows, without anyone evaluating whether it's actually the right fit at 5 locations versus 50.

The Centralized Account Model

One Merchant Center account, one feed, with location-specific variants handled through Local Inventory Ads (LIA) or per-location product identifiers within a single feed. This is the model most large franchise brands with corporate-run marketing eventually converge on.

Advantage	Trade-off
Single point of policy compliance management — one team enforces standards	A policy violation or suspension affects the entire network at once
Consistent branding, pricing display, and promotional messaging	Individual franchisee pricing autonomy is harder to reflect accurately
Economies of scale in feed management and campaign optimization	Local/regional performance nuances get averaged out in reporting unless segmented carefully

The Per-Location Account Model

Each franchisee or location operates its own independent Merchant Center account, typically still meeting brand standards through a shared feed template or franchise-provided base feed that each location customizes. This model is common in franchise systems where franchisees own significant marketing autonomy and their own advertising budgets.

The clear advantage is isolation: one location's suspension doesn't touch any other location's ability to advertise. The clear disadvantage is that brand consistency, policy compliance quality, and technical feed hygiene now depend on each individual franchisee's competence and diligence — which varies widely in most franchise systems, and corporate marketing loses visibility into aggregate performance unless every account is linked into a manager account for reporting.

The Hybrid Model: Multi-Client Account (MCA)

Google Ads-style manager account structures have an analog for Merchant Center: each location keeps its own Merchant Center account (preserving suspension isolation) but all accounts are linked under a single advertiser/business identity for reporting, and a franchise-standard feed template is pushed to every location's account programmatically. This gets most of the benefit of both models — isolation plus consistency — at the cost of more technical setup work upfront.

For franchise systems above roughly 15-20 locations, this hybrid model is usually worth the setup investment. Below that threshold, the centralized model is often simpler to manage and the blast-radius risk is more tolerable given the smaller footprint.

Decision Framework: Which Model Fits Your Business

• Choose centralized if: corporate controls all marketing and pricing, locations are company-owned (not independently franchised), and you have a dedicated team monitoring compliance across the whole feed daily
• Choose per-location if: franchisees have significant pricing and marketing autonomy, locations under 15-20 total, and franchise agreements already require independent advertising accountability
• Choose hybrid (MCA) if: you're above 20 locations, franchisees have some autonomy but corporate wants aggregate reporting and standard feed templates, or you've already experienced a network-wide suspension from the centralized model

Franchisee Autonomy vs. Brand Consistency

Regardless of account structure, franchise brands should maintain a corporate-owned feed template covering non-negotiable elements — brand name usage, required disclosures, prohibited claim language, and image standards — while leaving location-specific fields (address, local pricing where legally variable, local promotions) open for franchisee input. Document this split explicitly in your franchise operations manual; ambiguity here is what causes individual locations to introduce policy-violating language that then triggers a compliance review, centralized or not.

Implications for Local Inventory Ads

Local Inventory Ads require accurate per-location stock and pricing data, which is naturally easier to maintain correctly in a per-location or hybrid structure where each location's own systems feed their own account directly. In a fully centralized model, LIA requires a local feed layer on top of the primary product feed, mapping store codes to each location's actual inventory — this is a common point of data staleness in centralized franchise setups, since it requires an extra sync step that per-location models get for free.

Corporate Tooling: Feed Templates, DSPL, and Content APIs

Whichever account structure you choose, the operational burden of keeping dozens or hundreds of location feeds accurate falls on your feed infrastructure, not just your account architecture. Franchise brands managing this well typically build a corporate-owned "master feed" using the Content API for Shopping, generating per-location feed slices programmatically from a single source of truth (product catalog, pricing rules, location data) rather than maintaining separate spreadsheets or manual feed files per location. This matters more as location count grows — a chain of 5 locations can survive manual feed management, but a chain of 100+ locations without programmatic feed generation will accumulate stale data and inconsistencies that eventually surface as policy or performance issues at individual locations.

Regardless of the underlying account structure, invest in this tooling early. It's far easier to build a robust feed pipeline while you have 10-15 locations than to retrofit one onto 150 locations after inconsistent manual processes have already taken root at the franchisee level.

Reporting Roll-Up Across a Hybrid Structure

For hybrid (MCA) structures specifically, set up your manager account reporting roll-up before you need it for a board meeting or franchisee performance review, not after. Google Ads and Merchant Center manager account linking supports aggregate reporting across linked accounts, but the setup — particularly conversion tracking consistency across every linked account — needs to be standardized centrally so that location-to-location comparisons are actually apples-to-apples rather than skewed by inconsistent tracking implementations at the franchisee level.

How to Migrate From One Structure to Another

1. Audit current account history for each location — don't merge accounts with recent suspension history without addressing the root cause first, since the same issue will resurface in the new structure
2. Build the shared feed template before migrating any location, including required and optional field definitions
3. Migrate a pilot group of 2-3 locations first and monitor for 30-45 days before rolling out network-wide
4. Maintain the old structure in parallel (paused, not deleted) for at least one full billing cycle in case rollback is needed

Onboarding New Locations Into an Established Structure

As a franchise system grows, standardize the process for bringing a new location's Merchant Center presence online — whether that's a new sub-account provisioned from your master feed template in a hybrid structure, or a new independent account set up against your franchise operations manual's feed standards. Document this as a checklist step in your broader location-opening playbook so it doesn't get treated as an afterthought handled inconsistently by whichever regional manager happens to be onboarding that location.

A useful practice: require every new location to pass a pre-launch feed and policy review — verifying return policy pages are live and match the corporate template, tax settings are correctly configured for the new jurisdiction, and any location-specific promotional claims comply with brand and Google policy standards — before their Merchant Center account (or sub-account) goes live with active Shopping campaigns. Treating this as a hard gate rather than a "fix it later" item prevents a large share of the early-stage compliance issues that new locations otherwise generate in their first few months.

Decommissioning Closed Locations

The reverse process matters too: when a franchise location closes, its Merchant Center account or feed segment should be deactivated promptly rather than left running with stale inventory and outdated store information. Abandoned, unmaintained location feeds are a quiet source of policy and data-quality issues that can persist for months if closure isn't built into the same operational checklist as opening a new location.

Frequently Asked Questions

If one franchisee's account gets suspended, does it affect the others?
Only in a fully centralized single-account model. In per-location or hybrid (MCA) structures, suspensions are isolated to the individual account.

Can we use one feed file but split it into multiple Merchant Center accounts?
Yes — this is essentially the hybrid model. A single master feed can be filtered and pushed to multiple accounts programmatically, which is the recommended approach for franchise systems.

Does Google offer a native "franchise" account type?
Not exactly, but multi-client account linking (used for agencies) works well for this purpose and is the standard workaround franchise brands use today.