Selecting franchise software with requirements that can fail

Choose franchise software only after identifying what the agreement already mandates and what the local operator may control. The useful output is a short requirement set and a repeatable demonstration script, not a catalogue of appealing features. The tools and supplier guide shows where this step sits.

What to take away

Define which systems the franchisor imposes and which you select locally before choosing software.
Write requirements as tasks with conditions, so each can be scored as shown, described, promised or failed.
Check tax software compatibility on the official GOV.UK finder, not on vendor claims.
Match the depth of your security check to the data you hold, using the NCSC cloud approaches.
Decide with exit in viewask for a three-year cost and a sample data export before you sign.

Define the boundary

Draw the existing stack: point of sale, customer records, bookkeeping, payroll, stock, training, support desk and royalty reporting. Mark each system as imposed by the franchisor, selected locally or undecided.

For every connection, name the data that moves, its direction and who resolves errors. The operating workflow gives a map to start from.

This prevents two expensive mistakes. One is buying a second tool for a job the brand platform already performs. The other is assuming two products integrate because both mention an application programming interface.

Write requirements that can fail

Replace "easy to use" with a task and a condition. For example, a site manager must correct a duplicated sale without changing another unit's figures, and an accountant must export the correction history. Give each requirement a label: mandatory, scored or later.

Include volume and role assumptions. State the number of companies, locations, users, bank accounts, products and monthly transactions in the scenario. Use the same assumptions for every supplier, as the strategy and planning guide advises, so price and performance stay comparable.

Check tax software compatibility

Businesses in scope of Making Tax Digital need to keep digital records in software compatible with HMRC's systems. For VAT, the GOV.UK finder for compatible software lets you check which packages keep VAT records and submit VAT returns.

All VAT-registered businesses should now be signed up, and compatible software is needed to keep VAT records and file returns. Record the exact product, edition and supported obligation. Do not treat a parent brand appearing in a list as approval of every package it sells. A supplier comparison for accounting software should carry the same record.

Make the demonstration do real work

Give vendors a script before the meeting. Run these steps in the same order for each one:

Create two locations with different permissions.
Import a small prepared file.
Correct an error and show the correction history.
Produce the agreed report.
Export the record again, then repeat one step after a failure such as a disconnected integration or a departing manager.

Score each requirement as shown, described, promised or failed. A roadmap answer is not a working feature. The table defines the labels, and a selection checklist can hold the scores.

Label / Meaning

Shown: Done live in the demonstration, on the plan quoted
Described: Explained, but not demonstrated
Promised: Stated as future or roadmap
Failed: Attempted and not completed

Capture the version demonstrated and the plan needed, then send disputed notes to the vendor for written correction.

Test security against the information held

Two approaches exist for deciding whether a cloud service meets your security needs: a full principles-based approach, and a lightweight distillation of the principles.

Which one you use depends on the level of confidence you need. That is set by how you plan to use the service and how sensitive the data is.

The NCSC guidance on choosing a cloud provider points to the 14 cloud security principles for judging how well a service is designed, built and operated. Ask about authentication, permissions, audit logs, backups, recovery and customer responsibilities in the quoted plan.

If the provider handles personal data for you, the contract must meet the UK GDPR. The commercial aspects are for the parties. Check what details of the processing the contract must include, and what it says at the end of the contract. Compare the provider's supporting documents with the contract, not with a generic security statement.

Decide with exit in view

Request a three-year cost for the same locations, users, modules and usage. Include set-up, training, integrations, support and data export.

Ask for a sample export before signature and identify who can read it. The strongest selection record states why an option fits, which claims remain untested and how the business can leave without losing its operational history. Run vendor due diligence on exit terms before you sign.

Before you act

Draw the existing stack and mark each system's control.
Replace vague requirements with tasks and conditions.
State volume and role assumptions for all suppliers.
Give vendors a demonstration script before the meeting.
Score each requirement as shown, described, promised or failed.
Request a three-year cost and sample export before signature.

Common questions

Why write requirements that can fail?

A requirement with a task and condition can be scored as shown, described, promised or failed. A phrase like easy to use cannot. It also stops you buying a second tool for a job the brand platform already performs.

How should tax software compatibility be checked?

Use the official GOV.UK finder, and record the exact product, edition and supported obligation. Do not treat a parent brand's presence in a list as approval of every package it sells.

What should a buyer ask about security and data protection?

Ask about authentication, permissions, audit logs, backups, recovery and customer responsibilities in the quoted plan. Use the NCSC approaches to choose the depth of assessment, and check the processing contract terms if personal data is involved.