Costs
Part of Can multi-location marketing work without one reliable location registry?
Durable location IDs for franchise marketing and territory records
Multi location marketing best practices for franchise systems: rules for durable location IDs, platform identifiers, merging and retiring IDs, and keeping territory and prospect records linked but separate.
What to take away
- Give every location one opaque ID that never changes, is never reused, and carries no name, state or address.
- Map each platform's own identifier back to that ID in a crosswalk, and give every critical field an accountable owner.
- Keep territory and prospect records separate from the location record, and link them only through dated, explicit fields.
- Test accessible customer journeys and exception paths across representative locations.
For franchise systems, multi location marketing depends on connecting a stable internal location ID to current public records. If a location changes its public name, a name-based record can split its history or leave stale listings behind; a durable ID keeps the record linked while the display name changes.
Rules that make an ID durable
A durable ID survives every change a unit goes through. Six rules do most of the work:
- Opaque:use a prefix and a sequence number, such as LOC-000142. Do not encode the state, city or franchisee, because those change. An ID like US-TX-0142 breaks the moment a unit relocates across a state line.
- Assigned once, early:issue the ID when the unit is approved, before opening, so pre-opening listings and recruiting records attach to it.
- Never reused:a retired ID stays reserved forever, so an old listing can never point to a new unit.
- Survives relocation:a move keeps the same ID. Store the address history with effective dates.
- Survives transfer:a franchisee change keeps the same ID. The owner is a separate field, also dated.
- Retired, not deleted:on closure, set the status to closed, keep the record, and redirect the location page.
If a closed unit reopens as a new unit at a new site, issue a new ID and record the old one as its predecessor.
Platform identifiers and the crosswalk
Each platform has its own identifier, and none of them should be your master ID. Keep a crosswalk table that maps each one to the durable ID. Google Business Profile lets you set a store code of your own, and also has a location ID and a separate Place ID that Google assigns. Apple Business Connect, Bing Places, Yext, Uberall and SOCi each assign or accept their own identifiers.
Use the store code or entity ID field, where a platform offers one, to hold your durable ID. That gives you a join key in every export. The example rows below use placeholder platform IDs.
| Durable ID | Platform | Platform ID (example) | Location |
|---|---|---|---|
| LOC-000142 | Google Business Profile | 1234567890123 | Austin, TX store 0142 |
| LOC-000142 | Apple Business Connect | 1420009876543 | Austin, TX store 0142 |
| LOC-000142 | Yext | yext-0142-austin | Austin, TX store 0142 |
Merge duplicates and retire IDs
Duplicates appear when a listing is created by a customer, an agency or a platform. To merge, choose the survivor, usually the oldest verified record, and have the platform merge or suppress the duplicate. In your registry, mark the other ID as merged into the survivor. Never delete it, so any old report still resolves.
To retire an ID, set the status, record the date and reason, and keep the crosswalk rows. Log every create, merge and retire event with who did it and when.
Connect IDs to territory recruiting
A franchise territory moves through stages before a unit exists: available, held by a candidate, awarded, open. The location ID does not exist for most of that. Keep a separate territory ID and a separate prospect record, and link them only when a defined workflow needs it, with an effective date.
| Event | What happens to the location ID | What to record |
|---|---|---|
| Territory awarded | Issued when the unit is approved | Territory ID, award date, candidate |
| Unit relocates inside the territory | Unchanged | New address, effective date |
| Franchisee transfer | Unchanged | New owner, transfer date |
| Territory boundary changes | Unchanged | New territory link, effective date |
| Closure | Retired, never reused | Closure date, redirect target |
Do not use a location's marketing record as evidence that a territory is available. Territory mapping tools differ in how they export boundaries; see franchise territory mapping software compared and how to map franchise territories. Relocations near a boundary can raise encroachment questions.
Assign field ownership
Assign each field an owner and cadence.
| Field | Owner | Cadence |
|---|---|---|
| Legal name and address | Brand operations | On change, plus annual audit |
| Hours and holiday hours | Location manager | Quarterly, exceptions immediately |
| Phone and call routing | Franchise support | Monthly, and before campaigns |
| Offers and promotions | Marketing lead | Weekly, expire on date |
| Accessibility notes | Compliance lead | On change, plus annual review |
| Capacity and lead times | Regional operator | Daily in peak season |
Separate the internal location ID from platform IDs, names, addresses, phone numbers, owners and agencies. Grant view, edit, publish, spend, export, invite, transfer and delete rights according to the job rather than one broad administrator role. For administrator and owner accounts, use phishing-resistant authentication such as passkeys or hardware keys, as described in NIST's SP 800-63B, with secure recovery.
Make local journeys accessible
Franchise locations that serve the public fall under Title III of the Americans with Disabilities Act. The Department of Justice has long taken the position that this covers their websites, without adopting a technical standard for private businesses, and WCAG 2.2 level AA is the common benchmark. Section508.gov's accessible web design guide gives practical checks for form labels, focus order and error recovery.
Test location pages, booking, ordering, directions, calls, forms, chat, offers and notices with keyboards, screen readers, high zoom, mobile devices and clear error recovery. Include disabled people in research. An accessible template can still fail when local images, labels, documents or third-party widgets change.
Keep truth fresh
Practice / Control
- Location facts
- Source, owner, effective time, expiration, and fallback
- Local content
- Distinct material, proof, rights, and approval
- Exceptions
- Fast declaration, distribution, confirmation, and expiry
- Capacity
- Include, slow, reroute, or pause demand
- Measurement
- Location data accuracy: share of locations matching source address, hours, and phone in a monthly audit
- Recovery
- Owned accounts, exports, backups, and rehearsed exit
- Preview high-risk and bulk changes by location
- Use canaries before network-wide release
- Monitor broken links, calls, forms, feeds, and routing
- Remove old users, agencies, integrations, offers, and temporary data
- Review customer complaints as operating evidence, not only reputation
- Publish exceptions and corrections through one governed process
Report data accuracy for a cohort of franchised locations open more than 90 days in the same market, not for the network as a whole.
Common questions
How much local control is appropriate?
Give locations authority over facts and actions they can verify, inside brand, claim, security, data, and measurement controls.
Should every location use identical content?
Shared facts and design can be consistent; local pages should add verified material that helps customers decide and act.
What should be audited most often?
Urgent facts, destinations, response routes, capacity, access, and exceptions deserve the shortest review cycles.
