Bitrix24 for Franchises and Multi-Location Networks: Setup Guide

Why Franchise Networks Need a Purpose-Built CRM

Franchise networks face a core operational paradox: each unit needs enough autonomy to serve its local customers, while the franchisor needs visibility and consistency across the entire network - and a generic CRM delivers one or the other, never both at the same time. A fitness chain, a food franchise, or a dental clinic network all share the same challenge: sales and customer service must follow brand standards, yet each unit has its own customers, team, and pace. When every franchisee works from a different spreadsheet - or worse, disconnected systems - the franchisor loses visibility, customers notice inconsistency, and support costs spiral.

The most common problems we see in franchise networks before a unified CRM is in place:

• Leads generated by central marketing never reach the right units - or arrive too late.
• Inconsistent sales processes: each franchisee builds their own workflow without following brand standards.
• No consolidated visibility: the franchisor cannot compare performance across units without manually exporting spreadsheets.
• Mixed customer data: a customer record from one region is accidentally exposed to another unit through misconfiguration.
• Slow onboarding of new units: setting up a system from scratch for each franchisee costs significant time and money.

How the Branch Network Works in Bitrix24 (Alaio)

In Bitrix24's native architecture, the franchisor operates as the main portal on the Enterprise plan, and each unit or franchisee is connected as an independent branch - with its own CRM, tasks, and communications, yet visible to the head office through a single navigation widget. Bitrix24 includes a feature called the Branch Network, designed specifically for structures with a headquarters and sub-units - whether regional branches, representatives, resellers, or franchisees.

Here is how the structure works in practice:

• The main portal (franchisor) must be on the Enterprise plan - this is the portal that manages the network.
• Each branch can be on any paid commercial plan; the number of connected branches is unlimited.
• Each branch is an independent Bitrix24 environment: it has its own company structure, CRM, news feed, tasks, chats, and integrations.
• A branch employee cannot see data from other branches or from the main portal - unless explicitly invited to that portal.
• A central administrator can navigate between all portals in the network via a dedicated widget, with no need to log in separately to each one.
• Employees who work across multiple units - such as a regional manager or a group accountant - can be individually invited to whichever portals they need access to.

The information flow between the franchisor and its branches in a typical franchise network:

The main portal (Enterprise) connects multiple independent branches. Centrally generated leads are distributed to units via automation. Regional managers access multiple portals through the widget. The franchisor consolidates reports without branches having cross-access to each other's data.

flowchart TD
 A[" Matriz - Portal Enterprise\n(Gestão Central)"] --> B["Widget Rede de Filiais"]
 B --> C[" Filial / Unidade 1\n(CRM próprio)"]
 B --> D[" Filial / Unidade 2\n(CRM próprio)"]
 B --> E[" Filial / Unidade N\n(CRM próprio)"]
 A --> F["Distribuição de Leads"]
 F --> C
 F --> D
 F --> E
 A --> G["Relatórios Consolidados\n(Matriz)"]
 C --> G
 D --> G
 E --> G
 H[" Gerente Regional"] -- "acesso múltiplo" --> B

Two Architecture Models: Branch Network vs. Single Portal

The choice between maintaining separate portals per unit (Branch Network) or consolidating everyone into a single portal depends on the degree of operational autonomy each franchisee has and the total number of users across the network. Bitrix24 supports two distinct models for multi-unit networks:

Criterion	Branch Network	Single Portal (Enterprise Holding)
Data isolation	Complete - each branch is a separate environment	Partial - configured through departments and roles
Per-unit customisation	High - each branch configures its CRM independently	Moderate - central rules apply to everyone
Navigation between units	Via widget, with context switching	Everything in a single environment
User management	Separate per branch	Centralised
Best suited for	Independent franchisees with distinct processes	Holdings and subsidiaries operating as a unified team
Required plan at head office	Enterprise	Enterprise (Holding mode)

For most franchise networks - where each franchisee has legal and operational independence - the Branch Network provides the isolation required. For holdings in which all group companies function as a single team, the Single Portal reduces IT costs and simplifies management.

Standardised Funnels and Processes Across Units

Standardising sales funnels across the entire network is the greatest operational gain for the franchisor: when every unit follows the same stages, training is faster, audits are simpler, and reports are directly comparable. In a typical franchise network implementation, the configuration team builds a template portal that includes:

• A sales funnel with standardised stages (e.g., New Lead - Contact Made - Proposal Sent - Negotiation - Closed);
• Service scripts and checklists linked to each stage;
• Automations (robots and triggers) that send reminders, create tasks, and notify supervisors when a deal stalls;
• Mandatory fields that ensure the data required for franchisor reporting is always captured;
• Document templates (proposals, contracts) carrying the network's visual identity.

This template is then replicated to each branch during onboarding. New units joining the network receive the same pre-configured environment, reducing activation time significantly compared to individual manual setups.

Automation also reinforces standardisation day to day. For example: if a deal remains in the "Proposal Sent" stage for more than 48 hours with no recorded action, a robot automatically notifies the unit supervisor - without the franchisor needing to monitor this manually.

To learn more about structuring funnel automations, see the article on sales funnel design in Bitrix24.

Data Isolation and Permissions by Franchisee

In the Branch Network model, data isolation is total by default: a manager at Unit A cannot see the customers or deals of Unit B, even though both belong to the same network. Within each branch, access control is granular and configurable by role:

• Sales Manager role: sees only their own deals and contacts;
• Unit Supervisor role: sees all deals within their unit and can reassign ownership;
• Branch Administrator role: full access to their own branch, no access to any other;
• Head Office Administrator: can navigate between portals via the widget, but each portal still requires explicit access.

Employees who need to work across multiple units - such as a regional manager or a group accountant - are individually invited to each portal where they require access. This ensures that any additional access is intentional and auditable, not an architectural side effect.

Additional security features available on the platform:

• IP-based access restriction: employee logins can be limited to specific IP addresses - for example, only from the unit's office network. This reduces the risk of unauthorised access from outside a controlled environment.
• Session control: configurable session expiry times and limits on simultaneous active devices per user.
• Access history: a login log per user for audit purposes.

In contexts that require compliance with data protection regulations - such as the LGPD in Brazil, GDPR in Europe, or the PDPL in the UAE - branch-level isolation is a technically sound argument: each unit's customer data is segregated and access is fully traceable. Read more on CRM compliance in CRM em Conformidade com LGPD/GDPR: Por Que Bitrix24 Self-Hosted Vence.

Lead Distribution to Units

Leads captured centrally - through the network's website, marketing campaigns, or a central contact centre - can be automatically routed to the correct unit based on rules such as region, product interest, or availability, with no manual intervention from the franchisor. This is one of the highest-impact areas for franchise networks: central marketing invests in demand generation, but it is the local unit that serves the customer. A breakdown in this handoff - a lead that takes hours to reach the franchisee - is one of the leading causes of lost conversions.

Lead distribution mechanisms available in Bitrix24:

1. By geographic origin: leads from a specific postcode, city, or region are automatically directed to the branch responsible for that area.
2. By entry channel: leads from a specific WhatsApp number go to the branch linked to that number; leads from a regional website form go to the corresponding unit.
3. By product or service type: in networks where units specialise by category, the lead is routed according to the interest declared by the prospect.
4. Round-robin across franchisees: when multiple units cover the same area, the system distributes leads in rotation to balance the workload.

Within each branch, internal assignment rules work in the same way: the lead is assigned to the available salesperson based on configured criteria - territory, specialisation, or service queue.

For a technical breakdown of capture and distribution mechanisms, see Lead Management in Bitrix24: Capture, Distribution and Scoring.

Consolidated Reporting for the Franchisor

You cannot manage what you cannot measure: Bitrix24 enables the head office to build dashboards that aggregate performance data from all units - conversion rates by branch, deal volume, average cycle time - without relying on manual exports. In the Branch Network model, each portal's data is independent by design. Consolidation for the franchisor happens through two main approaches:

1. Native per-branch reports with central administrator access The head office administrator, who has access to each portal, can navigate between them and pull individual reports. This works for smaller networks but does not scale well as the network grows.

2. BI Constructor for consolidated dashboards Bitrix24 includes a BI builder that allows custom reports to be created from multiple data sources. In network projects, the most common approach is to connect the BI Constructor to a centralised data layer (via API or data integration), which aggregates metrics from all branches into a single executive dashboard.

Typical metrics tracked by the franchisor across a franchise network:

Metric	What it reveals
Lead volume by branch	Effectiveness of regional vs. central marketing
Conversion rate by unit	Service quality and process execution
Average time to close	Funnel efficiency; units with bottlenecks
Revenue per franchisee	Network performance ranking
Leads with no action after X hours	Compliance with service SLAs
NPS or satisfaction score by unit	Consistency of the customer experience

For a full overview of the platform's analytical capabilities, see Bitrix24 Reports Every Manager Needs to Run a Data-Driven Operation.

The AI-powered call analysis feature is also valuable in franchise networks: it allows the franchisor to audit service quality at any unit without listening to recordings manually. Learn more in AI Call Analysis in Bitrix24.

Security and Access Control Across the Network

In franchise networks, the security risk is not only external: a departing employee must not retain access to customer data, and a franchisee leaving the network must not be able to take the contact database with them. Bitrix24's independent branch architecture is designed to mitigate these risks by default. However, certain explicit configurations are essential:

• Centralised access revocation: when an employee leaves, the branch administrator revokes access within that portal only. If the same employee had access to multiple branches, access must be revoked in each one separately - an important step that should be built into the network's offboarding process.
• Per-unit IP restriction: each branch can configure its own permitted IP ranges, ensuring that access can only occur from the unit's physical environment.
• No data transfer between branches without deliberate action: in the branch network architecture, data does not flow automatically from one branch to another. Any sharing requires an explicit user invitation or a configured integration.
• Access audit trail: login history is available per user, making it possible to identify access outside expected hours or from unusual locations.

For networks that process significant volumes of customer personal data, it is worth reviewing the applicable data protection regulations in your jurisdiction: the LGPD in Brazil, GDPR in Europe, or the PDPL in the UAE.

Which Bitrix24 Edition to Use for Multi-Unit Networks

The Branch Network feature requires the franchisor's portal to be on the Enterprise cloud plan or the on-premise Enterprise edition; branches can use any paid commercial plan, and the number of connected branches is unlimited.

Cloud options for the franchisor

The Enterprise cloud plan supports the Branch Network functionality. For holdings that prefer to keep all users in a single portal, the Enterprise Holding mode accommodates multiple legal entities within a single environment, with access control managed through departments and roles - scalable from 1,000 up to 10,000 users.

On-premise option for networks that require data sovereignty

For networks operating in regulated sectors - healthcare, finance, education - or those required by law or contract to keep customer data on their own infrastructure, Bitrix24 on-premise offers the Business and Enterprise editions.

• Business: from US$ 3,590/year including 50 users, with tiers for 100, 250, and 500 users. Suitable for smaller networks that prefer to consolidate everyone in a single self-hosted portal.
• Enterprise: from US$ 24,990/year for 1,000+ users, with support for multiple branches, web cluster, and 24/7 support. Recommended for larger networks with high-availability requirements.

The annual renewal of an on-premise licence corresponds to 50% of the edition's list price (in effect since October 2024). After expiry, there is a 14-day grace period before the product is locked. For current pricing, visit bitrix24.com/prices/self-hosted.php.

For a full breakdown of implementation costs based on your network's size, the article on Bitrix24 implementation cost and timeline provides reference data drawn from real projects.

ACP Group, a Bitrix24 Gold Partner with hands-on experience delivering multi-unit network projects in Brazil, Portugal, and the UAE, can assess the architecture best suited to your network's profile and lead the full implementation - from template portal configuration through to unit onboarding.