Skip to content
  1. Hospitality franchise management software
  2. Franchise administration

Administration · Orbit OS by Operator Systems · whole network

Run the franchise relationship: invite, approve, suspend, message

Orbit OS gives head office the administration of each franchise connection: invite a franchisee, approve the connection once their business identity, contact and authority checks pass, suspend or resume it, end it, and message them — each action audited and behind a fresh sign-in.

The top of the Franchise view in Orbit OS for a demo business: the network name, the period picker, the Invite franchisee button and the Overview, Stores, Analytics, Franchisees, Invitations and Chat tabs

The Franchise view’s administration row on a demo business. Fictional names.

The problem

Bringing a franchisee onto a shared system means either giving them a login in your account or getting nothing from their separate one.

What head office sees

Pending invitations, each connection’s stage — accepted, awaiting approval, active, suspended, ended — and a message thread per connection.

What it can do

Invites by email, approves once the franchisee’s business checks pass, suspends, resumes or ends a connection, messages the franchisee, and revokes an unaccepted invitation.

The outcome

A franchisee runs their own business on their own account, and the connection — not shared ownership — is what head office administers.

Who does what

Head office sets it. The store runs it.

What head office controls

  • Invites a franchisee by email. The franchisee chooses which of their stores join and from which date reporting starts.
  • Approves the connection once the franchisee has accepted and their business identity, contact and authority checks have passed.
  • Suspends, resumes or ends a connection, and revokes an invitation that has not been accepted.
  • Messages any connected franchisee in a thread scoped to that connection.
  • Chooses which administrators hold the Franchise view: on by default for administrators, switchable off for a role or a person, never held by a store manager.

What the franchisee decides

  • Whether to accept, which stores join, and the first date the network reports from — never earlier than the invitation proposed.
  • What stays shared after connecting, and whether to end the connection.
  • Everything inside their own workspace: people, roster rules, approvals, payroll.

The workflow

How it works, step by step.

  1. Invite

    Head office sends an invitation to the franchisee’s email. The link is minted once and never shown again.

  2. Accept

    The franchisee accepts inside their own Orbit workspace: stores, reporting start date, sharing — able to narrow the invitation, never to widen it.

  3. Check and approve

    The connection waits for approval while the franchisee’s business identity, contact and authority are confirmed. Head office then approves it.

  4. Run it

    Suspend, resume or end the connection when the relationship changes. Each action is audited and asks for a fresh sign-in. The franchisee can end it from their side too.

Questions

Asked before a demo.

  • Can head office change what a franchisee shares?

    No. Sharing is the franchisee’s setting. It starts with everything on, and only the franchisee narrows it.

  • Can a store be transferred to a franchisee inside Orbit?

    A transfer can be drafted and cancelled in the Franchise view; the change of ownership itself is recorded as a store handover, which keeps the pre-handover weeks with the previous owner.

Orbit OS by Operator Systems

See it on your own network.

Book a demo