Franchise & multi-location operations

Grow the network.
Keep each location in control.

Share the brand and business rules that should stay consistent. Let local teams manage what belongs to their operation.

OrdexisOne connects franchise, branch and holding-company operations through governed location relationships. Each operating location has its own identity, service geography and time zone, with explicit choices about which standards it inherits.

Order Now
A parent operation and a distinct local operation with the dated decision that governs the relationship between them.Illustrative network records for a governed location relationship. The parent operation, Harbour Operations, runs 6 locations, holds the group administrator role and may govern brand, catalog and routes. The local operation, Harbour West at 14 Kestrel Road, keeps a UTC-05:00 time zone, a service area of Area 3 with 3 divisions, and an operating status that opens on 01 April 2027. Relationship request LR-208 was received on 04 March 2027 from the west location administrator, reviewed by the group administrator and approved on 09 March 2027, with the status recorded from 12 March 2027. The status on that date is active, shown beside the other recorded states of pending, suspended, rejected and revoked. The network holds 6 locations with 4 active relationships, 1 pending and 1 independent. Brand and email templates and the service catalog and routes are governed by the parent, while pricing and local customers remain a local decision. A local team can change a permitted domain, lock its editing or separate a local version from the inherited one, and a child location can accept or deny a parent proposal under the enabled policy.FRANCHISE / THE GOVERNED RELATIONSHIPA proposed relationship is approved before it carries authority.PARENT OPERATION · HARBOUR OPERATIONS · LOCAL OPERATION · HARBOUR WEST, 14 KESTREL ROAD · REQUEST LR-208THE TWO OPERATIONSPARENT OPERATION · HARBOUR OPERATIONSLOCATIONS IN OPERATION6GROUP ROLEGroup administratorDOMAINS IT MAY GOVERNBrand · catalog · routesLOCAL OPERATION · HARBOUR WESTADDRESS14 Kestrel RoadTIME ZONEUTC-05:00SERVICE AREAArea 3 · 3 divisionsOPERATING STATUSOpens 01 Apr 2027THE REQUEST AND THE DECISION RECORDED ON ITRELATIONSHIP REQUEST LR-208RECEIVED04 Mar 2027REQUESTED BYWest location administratorREVIEWED BYGroup administratorAPPROVED09 Mar 2027STATUS RECORDED FROM12 Mar 2027STATUS ON 12 MAR 2027PENDINGACTIVESUSPENDEDREJECTEDREVOKEDNetwork on 12 Mar 2027: 6 locations in the group,4 active relationships, 1 pending and 1 independent.DOMAINS THE RELATIONSHIP GOVERNSBrand and email templatesGoverned by the parentService catalog and routesGoverned by the parentPricing and local customersLocal decisionA local team can change a permitted domain, lockits editing, or separate a local version from theinherited one. A child location can accept or deny aparent proposal under the enabled policy.Approval is recorded before authorityStatus, dates and reviewer on the recordLocal control stays explicitPricing and customers stay local decisionsIllustrative group and location records · request LR-208, reviewer roles and dates are recorded service valuesFRANCHISE / THE GOVERNED RELATIONSHIPApproved before it carries authority.Request LR-208 · received 04 Mar 2027Approved 09 Mar 2027 · group administratorStatus active from 12 Mar 2027Governed: brand · catalog · routesLocal: pricing · customersParent operation · 6 locations in the groupLocal operation · opens 01 Apr 2027A local team can change a permitted domain, lock itsediting, or separate a local version from the inherited one.Approval is recordedStatus, dates and reviewer on the recordLocal control stays explicitPricing and customers stay localIllustrative relationship LR-208 · recorded status and dates

Govern the relationship

Connect a location with clear authority.

A location can operate independently or request a relationship with an authorized parent. The relationship has an explicit status: pending, active, suspended, rejected or revoked. Authorized teams approve the connection and decide which business domains it governs.

That gives a branch launch, franchise agreement or holding-company expansion a defined operating relationship inside the system. Sharing a standard does not require giving every location the same control over every part of the business.

Decide what a local team can change.

Where supported, a domain can allow local changes, lock child editing, or let a local edit separate that configuration from its inherited version. A child location can accept or deny a parent proposal under the enabled policy, with relationship and audit information available for review.

Share by business domain

Keep a common standard.
Choose where it applies.

A network may share its brand, give new locations a proven service catalog and leave local pricing independent. OrdexisOne lets you govern those areas separately, rather than applying one inheritance decision to the entire location.

Live-linked
Continue receiving governed changes from the parent for the selected domain. Use it where a shared standard needs to stay connected as it evolves.
Copy once
Start with the parent's configuration, then manage it locally. Give a new operation a useful starting point without tying its future changes to the parent.
Independent
Manage the selected domain without inheritance. Keep local decisions separate where the location's services, customers or operating requirements call for it.

Brand, commerce and operations each have their own policy.

Brand and communication
Govern branding and email templates separately, so the visual identity and customer messages follow the appropriate location policy.
What the location sells
Set policies for services, categories and Easy Quote; pricing and invoice settings; contracts; and packages and discounts.
How work is delivered
Govern operations, geofences and routes, and staff and users according to the responsibilities of the parent and local team.
Records and sensitive configuration
Customers and financial data, and secrets and credentials, have their own governed domains. Sharing the brand is a separate choice from sharing these areas.
One shared brand and service catalog across two locally distinct operations, with the inheritance mode recorded for each business domain.Illustrative inheritance records for a six-location network. The parent standard, Harbour Operations, applies brand and email templates at 6 locations and holds a service catalog of 24 services in 6 categories and 2 packages. Harbour West and Harbour North each inherit the brand, email templates and catalog, while pricing and territory remain local decisions for each operation. The domain policy recorded per location reads live-linked, edited by the parent, for brand and email templates and for the service catalog; independent and local for pricing and invoice settings, for service geography and routes and for customers and financial records; and copy once, then local, for staff and users. Recorded changes are dated: catalog change set 12 was sent to 4 live-linked locations on 04 March 2027, brand editing was locked for the west location on 09 March 2027, the staff policy was copied once to the north location on 12 March 2027 and a local price list was published for service area 3 on 16 March 2027. No amount and no brand logo is shown.FRANCHISE / SELECTIVE INHERITANCEShare the brand and the catalog; keep pricing and territory local.SIX LOCATIONS · ONE BRAND AND ONE SERVICE CATALOG · PRICING, TERRITORY AND ROUTES HELD BY EACH LOCATIONTHE SHARED STANDARDPARENT STANDARD · HARBOUR OPERATIONSBRAND AND EMAIL TEMPLATESApplied at 6 locationsSERVICE CATALOG24 servicesCATEGORIES AND PACKAGES6 categories · 2 packagesLOCAL OPERATION · HARBOUR WESTINHERITEDBrand · email · catalogLOCAL DECISIONSPricing · territoryLOCAL OPERATION · HARBOUR NORTHINHERITEDBrand · email · catalogLOCAL DECISIONSPricing · territoryBoth locations run the same brand and the same 24-service catalog,while each keeps its own pricing, territory and route divisions.DOMAIN POLICY RECORDED PER LOCATIONBrand and email templatesLive-linked · parentService catalogLive-linked · parentPricing and invoice settingsIndependent · localService geography and routesIndependent · localStaff and usersCopy once · localCustomers and financial recordsIndependent · localRECORDED CHANGES ON THE DOMAINS04 Mar 2027 · catalog change set 12 sent to 4 live-linked locations09 Mar 2027 · brand editing locked for the west location12 Mar 2027 · staff policy copied once to the north location16 Mar 2027 · local price list published for service area 3Live-linked or copied onceChosen per domain, not per locationLocal pricing and territory stay localIndependence is recorded per domainIllustrative domain policy · the modes, locations and 2027 dates are recorded service valuesFRANCHISE / SELECTIVE INHERITANCEShare the brand; keep pricing local.Brand and email templates · live-linkedService catalog 24 services · live-linkedPricing and invoice settings · independentService geography and routes · independentStaff and users · copied once on 12 Mar 2027West and north run the same brand overlocally distinct service operations24 shared services · local prices and territoryLive-linked or copied onceChosen per domain, not per locationLocal pricing and territory stay localIndependence is recorded per domainIllustrative domain policy · recorded per location

Copying during creation, locking child edits, propagating approved changes and previewing impact depend on the enabled domain policy. Dependencies between business domains remain part of the decision.

Explore the location controls

Make every location operationally real

Give each branch its own place to operate.

A location carries its business name, description, address, contacts and operating time zone. Configure a platform subdomain or custom domain, choose whether its host applies to that location or its descendants, and review DNS and SSL setup through the authorized configuration.

During location creation, define the service geography using administrative boundaries, nested areas or named manual extensions. Map and list views let the team select boundaries, organize groups and build route or service-area divisions.

Explore service geography
Two neighbouring operating locations with complete bounded divisions, recorded areas and stops, a shared boundary road and a prepared expansion area.A flat service geography for two neighbouring operating locations. The west location at Seven Oaks holds two complete divisions covering 18.6 and 21.4 square kilometres and 44 and 42 recorded stops, 86 stops in total across 40.0 square kilometres. The east location at Millford holds two complete divisions covering 16.2 and 19.8 square kilometres and 38 and 36 recorded stops, 74 stops in total across 36.0 square kilometres. One road is shared at the boundary between the two locations. Both record a UTC-05:00 time zone, an administrative boundary source, 2 named manual extensions and staff routing by division. An expansion area of 2 divisions, proposed from 01 May 2027, is prepared beside the east territory before the new operation opens. No map screenshot, no amount and no people imagery is shown.FRANCHISE / LOCAL SERVICE GEOGRAPHYEach location holds its own bounded territory and route divisions.TWO NEIGHBORING OPERATING LOCATIONS · FOUR COMPLETE DIVISIONS · ONE ROAD SHARED AT THE BOUNDARY · EXPANSION AREA PREPAREDTHE OPERATING FOOTPRINTWEST LOCATION · SEVEN OAKSEAST LOCATION · MILLFORDWEST DIVISION 118.6 km² · 44 stopsWEST DIVISION 221.4 km² · 42 stopsEAST DIVISION 116.2 km² · 38 stopsEAST DIVISION 219.8 km² · 36 stopsEXPANSION · 2 DIVISIONSPROPOSED FROM 01 MAY 2027Division areas in square kilometres · stops recorded per divisionTHE TWO NEIGHBORING LOCATIONSTERRITORY HELD BY EACH LOCATIONWEST · SEVEN OAKS2 divisions · 86 stopsEAST · MILLFORD2 divisions · 74 stopsSHARED BOUNDARY1 road · both locationsWHAT EACH LOCATION RECORDSTIME ZONEUTC-05:00 for bothBOUNDARY SOURCEAdministrative areasMANUAL EXTENSIONS2 named areasROUTE DIVISIONSStaff routing by divisionEach location holds its own territory and routedivisions, and the expansion area is preparedbefore the new operation opens.Territory held by each locationComplete divisions with recorded areasExpansion prepared in advanceA new area before the location opensIllustrative service geography · division areas, stop counts and the 2027 proposal date are recorded service valuesFRANCHISE / LOCAL SERVICE GEOGRAPHYEach location holds its own territory.West · Seven Oaks · 2 divisions40.0 km² · 86 stops recordedEast · Millford · 2 divisions36.0 km² · 74 stops recordedDivision areas 18.6 · 21.4 · 16.2 · 19.8 km²Expansion area · 2 divisionsproposed from 01 May 2027Route divisions assigned per locationTerritory held by each locationDivisions, areas and recorded stopsExpansion prepared in advanceProposed from 01 May 2027Illustrative service geography · two locations, four divisions

Price for the service area.

Configure a geographic modifier as a percentage or fixed amount, then decide whether it is included in the service price or shown as a surcharge. Local service conditions can have an explicit place in the price.

Prepare a new territory.

Set a center pin, combine selected boundaries and create manual extensions during setup. Freehand or follow-along drawing and node editing help define the area the new location will serve.

Manage operating status.

Review locations in a searchable list with details and map context. Set Active, Coming Soon, Closed or Maintenance status, including an opening date for a location preparing to launch.

See before you propagate

Make a change that the network can review.

A revised catalog, brand standard or operating rule can affect more than one team. Govern the proposal, the local response and the rollout with the context needed to understand what is changing.

Review the proposed difference.

Supported three-way comparison, evidence and warnings help reviewers assess the change in context. When a safe field-level comparison is unavailable, reviewers can use the available evidence and warnings to assess the change.

Apply the agreed policy.

Parent proposals and child accept-or-deny decisions operate within the relationship's permissions and domain rules. Review the impact and dependent domains before approved changes propagate where configured.

Keep the rollout history.

Publish parent change sets and review rollout and delivery history. Authorized teams can revisit relationship audit information instead of relying on an informal conversation about which branch received a change.

A proposed shared service standard reviewed against two distinct local requirements, approved with a recorded rollout history.Illustrative review of change set 14 on the service catalog, published on 09 April 2027, effective 01 May 2027 and in scope for 5 locations. The proposed shared standard moves visit duration from 90 to 120 minutes, the catalog from 24 to 27 services and the checklist from 9 to 11 steps, and is recorded as proposed. The west location requirement allows 12 stops per route across 4 divisions and 160 stops with 2 gated estates, and answers accepted. The north location requirement allows 9 stops per route across 3 divisions and 118 stops with 1 weight-limited road, and answers denied. The review of 09 April 2027 by the group administrator covered 3 differences, raised 1 warning, reviewed two dependent domains with no blocking finding and covered 5 locations in scope. The change set was approved on 09 April 2027 and effective from 01 May 2027, with 4 locations accepting and 1 denying it under a local requirement. The dated history records publication to 4 live-linked locations, the west acceptance, the north denial and the effective date. No amount is printed.FRANCHISE / A REVIEWED NETWORK CHANGEA shared standard is reviewed before it propagates.CHANGE SET 14 · SERVICE CATALOG · PUBLISHED 09 APR 2027 · EFFECTIVE 01 MAY 2027 · 5 LOCATIONS IN SCOPETHE SHARED STANDARD · PROPOSEDLOCAL REQUIREMENT · WESTLOCAL REQUIREMENT · NORTHVISIT DURATION90 → 120 minCATALOG SERVICES24 → 27CHECKLIST STEPS9 → 11STATUSProposedSTOPS PER ROUTE12 maxDIVISIONS4 · 160 stopsACCESS NOTES2 gated estatesREVIEW ANSWERAcceptedSTOPS PER ROUTE9 maxDIVISIONS3 · 118 stopsACCESS NOTES1 weight-limited roadREVIEW ANSWERDeniedREVIEW OF 09 APR 2027 · GROUP ADMINISTRATORTwo dependent domains reviewed · no blocking finding recorded.DIFFERENCES REVIEWED3WARNINGS RAISED1LOCATIONS IN SCOPE5Approved on 09 Apr 2027 · effective 01 May 20274 locations accepted the change set · 1 location denied it under a local requirementROLLOUT AND DELIVERY HISTORY09 Apr 2027 · change set 14 published to 4 live-linked locations12 Apr 2027 · west location accepted the change set14 Apr 2027 · north location denied it · weight-limited road01 May 2027 · change set 14 recorded as effectiveReviewed before it propagatesDifferences, warnings and dependent domainsLocal answers are recorded4 accepted · 1 denied under a local requirementIllustrative change set 14 · durations, step counts, dates and local answers are recorded service valuesFRANCHISE / A REVIEWED NETWORK CHANGEReviewed before it propagates.Change set 14 · service catalogVisit duration 90 → 120 minCatalog services 24 → 27Reviewed 09 Apr 2027 · 3 differences1 warning · 2 dependent domains reviewedApproved · effective 01 May 2027West accepted · north deniedunder a weight-limited road4 of 5 locations in scope acceptedReviewed before it propagatesDifferences, warnings and domainsLocal answers are recorded4 accepted · 1 denied locallyIllustrative change set 14 · recorded dates and answers
Explore activity history and control

One dedicated foundation

Keep the operating context clear.

The ordering business receives a dedicated environment with configured branding, roles, locations and operating rules. Within it, location access still depends on authorization.

An authorized administrator can move into a permitted location context through a controlled handoff. The current operating context stays visible; navigation to another location is denied when authorization is absent.

Explore your dedicated environment
For the parent organization
Manage the shared standards, proposed changes and operating relationships that are within the team's authority.
For the local operator
Work within the location's identity, geography and time zone, with the local or inherited decisions assigned to each business domain.
For an expanding group
Choose an independent location or an authorized parent relationship at creation. Domain setup, inheritance behavior and cross-location navigation follow the enabled configuration and permissions.

Build on the operation you know

Carry a proven service model into the next location.

Expansion starts with decisions your business already makes: what it sells, where it works, how it prices and which team is responsible. Use those decisions to prepare a new operation deliberately.

  1. Define the starting standard.

    Prepare the services, pricing, contract terms, brand and operating configuration worth carrying forward from the original business.

  2. Choose what transfers.

    Select the parent relationship and inheritance policy for each domain. Distinguish a continuing shared standard from an initial copy or an independent local decision.

  3. Establish the local operation.

    Create the location's identity, host, time zone, contacts and service geography. Set its operating status and opening date where appropriate.

  4. Govern ongoing changes.

    Review proposals, local responses, relationship status and rollout history under the authorized policy as the network develops.

Configure your network

Choose the standards you share.
Keep local responsibility explicit.

Review the plan, location configuration and enabled inheritance policies for your organization. Build the network around the way your teams need to operate.

Order Now Understand the purchase