A franchise store locator built on your territories
A customer types a ZIP code and needs one answer: which location serves me? FranOps answers from the territories you already manage, so the customer reaches the location that holds the rights to their area.
Read the transcript
In FranOps, every location owns a territory: a list of ZIP codes, or a radius around the store.
A customer in ZIP code 80209 wants to know who serves them.
The locator finds the location whose territory covers that ZIP.
Castle Rock is not inside any territory.
So instead of a dead end, the customer gets the nearest locations, ranked by distance.
And from the answer, one click opens the full location record.
The problem
Most store locators sort pins by distance. In a franchise network, the closest location is often not the one that holds the territory. Leads go to the wrong franchisee, a protected territory loses business it was promised, and head office settles the dispute by hand. A separate locator also has to be kept in step with every territory change, and it drifts.
Matched by territory, not by distance
When a customer enters a ZIP code, FranOps finds each active territory assignment that covers it: a ZIP-code territory that lists the ZIP, or a radius territory whose circle contains it. Those locations come first. Each result names the territory and its type, and gives the distance, so staff can see why that location was chosen.
No dead end at the edge of your coverage
When no territory covers the ZIP code, the locator returns the nearest active locations within 100 miles, ranked by distance, up to ten. A customer just past the edge of your territories still reaches a location. Beyond 100 miles the locator returns no result, rather than send a customer to a location too far away to serve them.
One answer, wherever the question is asked
Staff search by ZIP code or by coordinates inside FranOps. Your website asks the same question through the location search API, with an API key that can only read locations, and the GraphQL API offers the same search. An AI assistant connected over MCP can find the serving location for a ZIP code, held to the permissions of the person using it.
Change a territory, and the locator follows
There is no second copy of your coverage to maintain. The locator reads the locations, franchisees, and territory assignments you manage on the territory map, so a reassignment or a redrawn boundary is in the next search. A PO-box ZIP code is placed at the center of the ZIP area around it, so that customer still gets the nearest locations by distance.
What you get
- Search by ZIP code, or by latitude and longitude
- In-territory matches from your radius and ZIP-code territories
- The nearest active locations within 100 miles when no territory covers the ZIP code
- Each result names the location, its franchisee, the territory, and the distance
- The same search in FranOps, through the REST and GraphQL APIs, and over MCP
Frequently asked questions
- How is this different from a distance-based store locator?
- A distance-based locator sends the customer to the closest pin. FranOps sends the customer to the location whose territory covers their ZIP code first, and uses distance only when no territory covers it.
- What happens when no territory covers a customer’s ZIP code?
- The locator returns the nearest active locations within 100 miles, ranked by distance, up to ten. Beyond 100 miles it returns no result.
- Can I put the store locator on my own website?
- Yes. Your website’s server calls the location search API with an API key that can only read locations, and shows the results in your own design. Staff see the same answers inside FranOps.
- Do I keep a separate list of locations for the locator?
- No. The locator reads the locations and territory assignments you already manage in FranOps, so a change on the territory map is in the next search.