Price for the service area.
Set a local price adjustment as a percentage or fixed amount, then choose whether to include it in the service price or show it as a surcharge. Local service conditions can have an explicit place in the price.
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 managed relationships between locations. Each operating location has its own identity, service geography and time zone, with explicit choices about which standards it inherits.
Order NowGovern the relationship
Connect a location with clear authority.
A managed location connects automatically to its main business. An existing independent location can request a connection with an authorized parent, subject to its administrator’s approval. The relationship has an explicit status: pending, active, suspended, rejected or revoked. Authorized teams approve the connection and decide which settings it shares.
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.
For supported settings, allow local changes, lock branch editing or let a local edit separate that setting from future parent updates. Branches can accept or reject parent proposals within your sharing rules, with relationship details and recorded activity available for review.
Choose what each location shares
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
- Keep receiving parent updates for the selected settings. 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 settings independently. 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
- Set separate sharing rules for branding and email templates, keeping visual identity and customer messages aligned with the needs of each location.
- What the location sells
- Set policies for services, categories and quote setup; service prices; contract templates; and packages and discounts. Taxes, invoices and payments remain local.
- How work is delivered
- Share reusable materials and job instructions. Each location keeps its own service boundaries, routes, schedules and team access.
- Records and sensitive configuration
- Customer, staff, job, invoice, payment and signed-contract records stay private to their location. Sensitive connection credentials are never inherited with shared business setup.
Your sharing rules determine whether new locations receive a copy, whether branches can edit settings and how approved changes are delivered and previewed. Review related settings together before making a change.
Explore the location controlsMake 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. Choose a platform subdomain or custom domain, decide whether it applies to one location or its branches, and review domain routing and security certificates with an authorized administrator.
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 geographyPrepare 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.
Where available, compare the versions involved in a change and review supporting details and warnings. If a reliable comparison of individual settings is unavailable, use the available evidence and warnings to assess the proposal.
Apply the agreed policy.
Parent proposals and branch responses follow the relationship's permissions and sharing rules. Review the impact and related settings before approved changes are sent to participating locations.
Keep the rollout history.
Publish approved groups of parent changes and review which locations received them. Authorized teams can revisit relationship audit information instead of relying on an informal conversation about which branch received a change.
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 shared settings chosen for each area of the business.
- For an expanding group
- Choose an independent location or an authorized parent relationship at creation. Web address setup, shared settings and switching between locations follow your setup and access 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.
Define the starting standard.
Prepare the services, pricing, contract terms, brand and operating configuration worth carrying forward from the original business.
Choose what transfers.
Choose the parent relationship and sharing rules for each area of the business. Distinguish a continuing shared standard from an initial copy or an independent local decision.
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.
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 available sharing rules for your organization. Build the network around the way your teams need to operate.