Preparing for Store System Failures and Offline Trading Before Franchising in China

When an established business moves into franchising, it often focuses on system functionality but overlooks how stores will keep working if those systems fail. Company-owned stores may be able to arrange help from head office on an ad hoc basis; franchised stores need clearly defined authority, procedures and support commitments. For a franchise network, a tested system failure contingency plan is an important safeguard for keeping a standardised operating model running.

1. Define which activities can continue offline

Simply stating “process transactions manually if the internet goes down” is not enough. Assess whether transactions can still be completed safely in each operational scenario, including taking payments, accepting orders, checking stock and ordering supplies. Loss of internet access, failure of a single terminal and an outage on the head office platform should each have their own decision-making process.

Create an offline trading checklist specifying, for each activity, the affected function, alternative procedure, authority to activate it, conditions for stopping and person responsible for recovery. Focus on three questions:

• Can the terms of the transaction be verified? If the price, product status or available quantity cannot be confirmed, staff should not complete sales based on memory alone.
• Can payment be verified? If payment status is unclear, check it through official payment channels. A customer's screenshot alone is not proof that funds have been received, and customers should not be asked to pay again without verification.
• Can a complete record be kept? Temporary orders should have unique reference numbers and record the items, amount, time, staff member handling the transaction and fulfilment status, to prevent duplicate orders when systems recover.

Offline trading does not mean unrestricted trading. Any activity that depends on system checks to ensure safety or compliance should be explicitly suspended, rather than leaving every decision to staff on site.

2. Simulate failures in company-owned stores, rather than just testing software

Article 7 of China's Regulations on the Administration of Commercial Franchising requires franchisors to have a mature business model and the capacity to provide ongoing operational guidance, technical support, business training and related services. System failure drills are not a separate entry requirement expressly listed in the regulations, but they can help a business establish whether those capabilities work in practice.

Run drills during controlled periods, with safeguards in place beforehand to protect live transactions and avoid disrupting customer payments. Scenarios could include a store losing internet access, delayed order synchronisation or temporary loss of access to the back-office system. Ask the store manager to respond using only the contingency plan, while head office observes rather than taking over.

Record the time taken to identify and report the problem, switch procedures and resume trading. Also check whether staff know when to stop accepting orders. Pay particular attention to orders paid for before the outage but not yet prepared or delivered: these must not be overlooked or fulfilled twice.

Do not simply mark the drill as “passed”. Keep a record of the issues identified, revised procedures and retest results. If recovery depends on the founder personally contacting the software provider, the support process is not yet established, and the business should not promise franchisees reliable incident handling.

3. Document the responsibilities of head office, franchisees and software providers

Article 11 of China's Regulations on the Administration of Commercial Franchising requires written franchise agreements to specify the content and delivery methods of services such as operational guidance, technical support and business training. For store systems used across the network, incident support should be covered in the agreement or an expressly referenced service schedule, rather than left as a verbal promise from franchise recruitment staff.

At a minimum, specify:

• Scope of support: Which systems head office supports, and which networks or terminals the franchisee must maintain.
• Fault reporting: Which alternative channels stores can use to contact the person responsible if they cannot log in to the system.
• Response arrangements: Who determines incident severity, when an initial response will be provided and how often progress updates will follow.
• Decision-making authority: Who may activate offline procedures, suspend order-taking or authorise a return to trading.
• Costs and responsibilities: Who pays for backup connectivity, on-site repairs and recovery support, and how disputes will be investigated.

Distinguish between a commitment to respond and a guarantee of recovery. Head office should not guarantee a recovery time that the software provider has not committed to and that head office cannot itself control. Nor does maintenance by a software provider automatically release head office from support obligations it has undertaken towards franchisees.

The terms of use, charges and support arrangements for shared systems should be consistent with pre-contract disclosures. China's Regulations on the Administration of Commercial Franchising require the statutory disclosure information and the contract text to be provided in writing at least 30 days before the agreement is entered into. Important restrictions affecting trading must not be left until training to be explained.

4. Check outstanding transactions before returning to normal operation

Being able to access the system again does not mean the incident is over. The operating manual should distinguish between “technical recovery” and “operational recovery”, with designated staff checking data synchronisation before normal order-taking resumes in stages.

Review temporary records from the outage one by one and label their status, for example: unpaid, paid but not yet fulfilled, or fulfilled but awaiting entry into the system. Before entering a transaction, check whether it already exists in the system. Afterwards, retain the original record and its corresponding system reference. Staff should not independently delete or amend irregular refunds, duplicate orders or payments whose status remains uncertain.

Avoid collecting unnecessary customer information in temporary records, and do not circulate complete transaction details in personal messaging groups. Staff must not share user accounts because of an outage, and any changes to access permissions after recovery should leave an audit trail.

After each incident, head office should summarise the cause, scope of impact, departures from procedures at store level and improvements required, then update the manual. Franchisees should receive findings relevant to their operations, not merely a message saying “the system is back up”.

Practical takeaway: Before recruiting franchisees, complete an offline trading checklist, run a system failure drill in a company-owned store and prepare a support responsibilities schedule. A contingency plan is ready to be rolled out only when staff can follow it, head office can meet its response commitments and all transactions can be fully reconciled and restored to the system.