Franchise hierarchy: network, franchisees, territories, one model

What does the capability do?

It makes the shape of the network, including its awkward realities, first-class structure rather than configuration folklore.

• Three tiers plus sites. Franchisor, franchisee, and territory are distinct entities, with sites beneath territories. Each carries its own slug for clean scoped URLs across the admin.
• Directly-operated sites, no workaround. A network that runs some locations itself models them as franchisee records flagged directly operated, so they appear in network views, permissions, and finance through the same machinery as franchised sites.
• Master franchises. A franchisee can own child franchisees through an explicit parent relationship, and a dedicated scope guard grants master-scoped users access to their direct children while head-office tiers pass through.
• Territories with substance. Territories carry their country, currency, geographic boundary data, and status, and their ownership is recorded as dated assignment history with reasons, so a resale or handover preserves the timeline.
• Attribution at the transaction. Every charge, payment, and refund records its franchisee and territory, derived at creation from the site it occurred at. Network reporting aggregates real transactions rather than self-reported summaries.

Why attribution at creation is the load-bearing detail

Network finance is only as trustworthy as the moment of attribution. If revenue is mapped to territories by a report join written later, every site move and territory resale silently rewrites history. Stamping the franchisee and territory onto each transaction as it is created, from the site where it happened, makes the financial record match the network as it stood at the time, and the dated territory history explains every change since.

Why it matters

Most franchise software models the franchisor’s view and improvises the rest; most operational software has no concept of a network at all. Modelling the hierarchy, its exceptions (directly operated, master franchise), and its history as data is what lets one platform serve both head office and franchisees, the gap explained in our guide on franchise management versus franchise operations software. Combined with scoped permissions, the hierarchy is also the boundary that keeps each franchisee’s data their own.