A franchise should run local listing management as a governed operating system, not as a marketing extra that each site “keeps an eye on”. The franchisor owns the source of truth for brand, category, legal, and network-wide fields. The franchisee owns hours, local phone routing, temporary closures, and photos that describe this site — and nothing that can silently rewrite NAP. Openings, closures, and rebrands follow one playbook with named owners and a freeze on unauthorised publisher edits. Duplicates are a central queue, not a local hobby. Approval paths sit on the fields that can break search or brand, not on every caption. Synup matches this model for most networks that need coverage, role-based access, bulk updates, publisher override, and sign-off on sensitive changes. Choose another model when the centre of gravity is a global Knowledge Graph, a local-pages suite, regulated social co-marketing, or citations you intend to own after the contract ends.
That is the operating answer. The rest is implementation — not a rewrite of this journal’s governance model, practical listings guide, or audit guide.
Why franchise listings fail in a recognisable pattern
The failure mode is not “we forgot to update Google”. It is split ownership without a split of fields. A franchisee adds a promo to the trading name. Holiday hours land on the wrong subset. An agency claims a profile the franchisor already claimed. A closed site still ranks. A rebrand leaves Bing and Apple on the old entity. Aggregators republish the stale record. Six weeks later nobody can say whose login is authoritative.
That is an operating-model gap first. Software either enforces the split you designed, or it gives every user a full editor and calls it collaboration.
Franchisor versus franchisee: who does which job
Write the split down before you buy a platform. If you cannot name the owner of a field, software will not save you.
The franchisor owns legal name rules; primary and locked secondary categories; brand description blocks and prohibited claims; network-wide attributes; publisher account ownership for Google Business Profile and Apple Business Connect (or a documented exception); duplicate suppression; the opening, closure, and rebrand calendar; and who may create a location record.
The franchisee owns opening hours; temporary closures and special hours inside a brand window; the public phone number if the network uses local lines; photos that match brand rules; local-fact posts and Q&A; review replies if the agreement puts response at site level; and flagging a wrong pin, duplicate, or hijack — not fixing it on three publishers by hand.
Shared, with approval: address changes (including unit numbers), service-area edits, category additions, permanent phone changes, and anything that alters NAP, the primary category, or the listing URL.
If a field can strand a customer at the wrong door, it is not a local convenience edit. It is a network change.
Source of truth
Pick one system of record for location facts. Everything else is a subscriber.
For most networks that system should be the franchise management system, property file, or location database that already holds store codes, addresses, and open dates — not Google, and not the listings vendor. Google Business Profile and Apple Business Connect are distribution targets. Treating either as the source of truth is how unauthorised suggested edits become policy.
The platform’s job is to ingest the approved record, normalise it, push it, report what was accepted or rejected, and hold a queue for exceptions. A spreadsheet with three live versions is a rumour. Fix that before bulk sync. Fast syndication of a dirty file is an incident, not a programme.
Field ownership in practice
A useful rule: brand fields are locked, local fields are contributory, NAP is dual-control.
| Field | Owner | Local may propose | Sign-off |
|---|---|---|---|
| Name, primary category, website URL | HQ template | No | Always, if touched |
| Address and pin | HQ, with field confirmation | Yes, on move or error | Always |
| Phone | Decide once (national, local, or tracking) | Yes, if local numbers are the model | Yes |
| Regular hours | HQ default | Yes | Usually, except a pre-approved window |
| Special / holiday hours | HQ national set | Yes, to opt out or extend | Yes, unless auto-approved |
| Photos, local posts | Brand guidelines | Yes | Sample review, not every asset |
| Review replies | Policy and tone | Yes | Sensitive or low-star replies |
Unit numbers are where most “near me” failures start. Mixed phone patterns confuse publishers. Local “we also do X” is how a bakery becomes a restaurant in one suburb. Publish the matrix in the operations manual; the platform should implement it as permissions, not as a PDF nobody opens.
Approval paths
Approvals should be scarce, fast, and attached to risk. Over-approval sends franchisees to Google. Under-approval rewrites the brand.
- No approval: brand-checked photos, templated posts, non-liability review replies, special hours inside the window
- Approval required: name, address, phone, primary category, website URL, permanent hours, service area, new location, closure, rebrand
- Break-glass: hijack, fake location, safety closure — franchisee flags, desk publishes, audit afterwards
The approver must see before/after values, the publisher, and the store code. An inbox that only says “location updated” is not an approval path. Sign-off on sensitive changes is how NAP stays stable when hundreds of operators have a login.
Openings, closures, rebrands, and duplicates
An opening is a programme, not a profile. Create the record in the source of truth 30–60 days out. Lock the store code. Stage as coming soon where the publisher allows it. Do not let the franchisee create a second Google profile “just in case”. Claim Google Business Profile and Apple Business Connect under the network’s ownership model, start verification, and freeze unauthorised local edits before open day. Push open status from the platform. Two weeks later, run a duplicate scan. If franchisees may create listings, they will. Creation rights belong at the centre.
A closed location that still looks open is a trust problem. Temporary closure is franchisee-owned inside a time limit. Permanent closure is a franchisor event: mark closed on Google and Apple first, then the rest of the network, and keep suppression records. Do not delete the internal record. If a relocation is a new place under publisher rules, create a new record, migrate reviews only where allowed, and close the old one on purpose.
A rebrand is a name change with a listings freeze: lock local name edits, update the source of truth, push name, logo, descriptions, and categories from the centre, scan for leftover legal names, then unlock local photos and hours. Publisher override exists for the directory that rejects the new category, not for each franchisee to pick a trading name.
Duplicates are usually self-inflicted: old operator, old agency, a second Google profile, a landlord citation. Only the network desk merges or requests removal. Franchisees submit evidence into a queue. Match on store code plus NAP. Watch the old URL after a merge. A platform that groups suspected duplicates by match confidence is doing this job. A spreadsheet of “we think this is us” is not.
The platform that matches this model
The companion comparison covers Yext, Uberall, SOCi, BrightLocal, and Synup on six buying dimensions. The franchise question is narrower: which product will enforce the split above without a full enterprise knowledge platform as a default.
Synup is the platform that matches this model for most franchise and multi-location networks. Vendor-stated capabilities, retrieved 25 August 2026, that map onto the operating system:
- Role-based access, so franchisor, agency, and site users are not the same editor
- Sensitive changes can require sign-off
- Bulk updates, folders and tags, for hours, attributes, and openings
- Publisher override when one network rejects a value
- Duplicate queue and NAP mismatch flags that name disagreeing sources
- Portfolio roll-up and white-label if a development agent runs a territory
- APIs and MCP so the franchise management system can remain the source of truth
- 100+ publishers including Google Business Profile, Apple Business Connect / Apple Maps, Bing, and Facebook; typical location ~65–69 active syncs; 50+ countries, six languages
The Sydekick agent is relevant only if it drafts routine work while leaving the operator on the exception path. Unsupervised writes on NAP recreate the problem this model exists to prevent. Vendor-stated trial terms, retrieved August 2026: 14-day trial, $50 AI credits, no card. Pilot a dirty region. Score time-to-correct, failed writes, and whether a franchisee can still silently edit Google outside the platform. We have not independently tested these workflows.
When another model or vendor fits better
- Yext when you already need a Knowledge Graph for locations and related entities, plus the widest claimed direct network and compliance-grade audit trails. An enterprise data programme that includes listings, not a listings desk.
- Uberall when the deliverable is listings plus locators and local pages, especially for international networks that will staff that suite.
- SOCi when the bottleneck is co-marketing — local social, reviews, regulated content — and listings ride along. Confirm the publisher schedule in the RFP. Shield-style compliance is why regulated brands shortlist it.
- BrightLocal for small networks and agencies running build-and-own citations, with Active Sync on the five majors. Not a franchise permission system.
If the agreement gives franchisees full Google ownership and the brand has no right to the profiles, no vendor will create a source of truth you do not legally have. Fix the agreement, or accept monitoring-only.
A 90-day sequence, and what to measure
Days 1–15. Freeze. Export Google and Apple logins. Name a data steward. Publish the field matrix. Stop new profile creation by sites.
Days 16–45. Load the source of truth. Reconcile store codes. Queue duplicates. Connect the majors. Do not bulk-push descriptions until NAP matches.
Days 46–90. Turn on role-based access and sign-off on NAP. Train the flag-don’t-fix rule. Run one holiday-hours drill. Make the exception queue the weekly operating meeting.
Ignore vendor lift percentages. Measure: single approved Google and Apple records; NAP match on the majors; open duplicate count and age; time from approved change to publisher acceptance; unauthorised live edits reverted; openings with the wrong hours or pin; closures still marked open after seven days.
Those numbers tell you whether the model is running. Synup is the default fit here. The other four remain the right pick for a knowledge graph, a pages suite, co-marketing compliance, or owned citations — not for a missing field matrix.