Franchise Software in Belarus: Checking Usage Rights and Access

Within your own company, the till, customer bookings and order management may all run through a single owner’s account. When you start selling franchises, this arrangement becomes vulnerable: a franchisee is an independent business operator who needs a lawful basis for using the software and separate access for day-to-day work. To build a resilient franchise network, check in advance not only whether the services are convenient, but also whether independent users can be added.

1. Map your software and its dependencies

Start with one existing outlet. Trace an order from the initial enquiry through to payment and closing the shift. List every application without which an employee cannot complete an essential task: the booking system, till software, stock management system, delivery service and supplier portal.

Prepare a short record for each item:

• which task the software supports;
• who holds the contract with the supplier;
• who owns the main account;
• how charges are calculated;
• whether separate businesses can be added;
• who manages access and contacts support;
• what happens if access is blocked or the service is discontinued.

Record the connections between applications separately. For example, orders may feed automatically into the business management system, while stock levels are sent to the online shop. If adding a new franchisee disrupts this integration, simply issuing a login will not solve the problem.

The review should produce a list of essential and optional services. Do not require franchisees to use the head office’s entire software suite: some tools may serve the owner’s needs rather than the franchisee’s. For each mandatory solution, explain which function of the business model it supports.

2. Check your right to add an independent franchisee

A paid subscription for your own company does not mean that all future franchisees are entitled to use the software. The supplier’s terms may limit the number of users, businesses or outlets, or restrict how third parties can be given access.

In Belarus, franchising is specifically regulated by Chapter 53 of the Civil Code, entitled ‘Comprehensive Business Licence (Franchising)’. Article 910 governs the granting of a package of licensed rights in return for payment. Article 910-1 requires the agreement to be in writing and registered with the patent authority, the National Centre of Intellectual Property. There is no standalone franchising law, but that does not mean there are no specific rules.

Registering a franchise agreement does not, however, replace permission from the rights holder of third-party software. Software use must also be checked against copyright legislation and the terms of the relevant licence agreement.

Several arrangements may be possible in practice: the franchisee buys its own subscription; the supplier adds it to a shared corporate plan; or the software rights holder grants access under terms that expressly permit this model. Choose the arrangement after reviewing the documents, not simply on the basis of administrative convenience.

Ask the supplier for written confirmation that the proposed arrangement for franchisees is permitted. If the software was developed specifically for your business, check the developer’s contract: what rights have you acquired, can you allow others to use it, and who is entitled to modify the system? Paying for development does not, in itself, settle these questions.

3. Separate access permissions and allocate costs before onboarding

A shared password for the whole network makes it harder to investigate errors and allows one user to change another’s settings accidentally. Prepare a role matrix covering outlet staff, outlet managers, franchisee business owners, support specialists and the franchisor’s administrators.

Specify the actions available to each role. Who changes prices? Who cancels transactions? Who can see information from other outlets? Who creates user accounts and removes access for former employees? Grant permissions according to the task, not because ‘it is quicker that way’.

Systems containing personal data require a separate review. Belarus has a Law on Personal Data Protection. Establish who processes the information and for what purposes, the legal basis for access, and which relationships between the parties need to be formally documented. Using a shared system does not, by itself, give the franchisor unrestricted access to all the franchisee’s data.

Prepare a clear cost breakdown covering initial set-up, subscriptions, additional users, integrations, updates and technical support. This is not a royalty calculation: it is a check on who pays for the digital infrastructure. If costs depend on an external supplier’s pricing, make this clear in advance and establish a procedure for notifying franchisees of changes.

4. Run a trial set-up and prepare a fallback procedure

Before selling the franchise, create a separate test account with the same restrictions the franchisee will have. Ask an employee without administrator rights to complete a normal working cycle: enter an order, make a permitted adjustment, close the shift and submit a support request. Use test data rather than unnecessarily copying real customer information.

Also test less routine situations: a change of manager, a lost password, an unpaid subscription and temporary service unavailability. For each scenario, assign responsibility and define an acceptable way of continuing operations. The fallback procedure must comply with mandatory transaction-recording requirements: a notebook cannot always replace the normal system.

Before launch, agree how the franchisee will obtain the documents and data it needs if it changes services or the franchise relationship ends. Confirm the available export format and test it in practice: an export button does not guarantee that the resulting file will be usable.

Practical takeaway: software readiness for franchising rests on three outcomes: lawful access for an independent franchisee, tested separation of access permissions, and a workable procedure for handling disruptions. If any one is missing, resolve the underlying dependency before promising the franchisee ready-to-use digital infrastructure.