Opening a second practice used to be the exception for UK independents. Increasingly, it’s the plan. The market is consolidating around you — multiples expanding, buying groups recruiting, small independent groups of two and three branches forming where single practices used to stand alone. And the moment you add a branch, you discover something awkward: the practice management software you chose for one shop was never really chosen with two in mind.
Most PMS comparisons are written for the single-site owner. This one isn’t. If you already run more than one branch — or you’re seriously planning to — here’s how to compare multi-site practice management software properly in 2026: what actually breaks when you add a location, the five jobs the software must do, what to ask in the demo, and the red flags that cost practice groups real money.
Why multi-site is the question more UK independents are asking
The UK opticians industry is worth around £5.8 billion in 2026, spread across roughly 5,500 businesses. But the shape of those businesses is changing. Consolidation has been the defining trend of the past few years — larger groups buying up established independent brands, buying groups pulling independents together, and, quietly, successful independents opening or acquiring their second and third practices rather than sitting still.
That last group is the interesting one. A two- or three-branch independent group keeps the local trust that made the first practice work, while spreading fixed costs and giving the owner options a single site never could. We’ve written before about what it takes to open a second optician practice — and one of the conclusions was blunt: the practices that expand well are the ones whose systems were ready before the keys were handed over.
Software is the biggest of those systems. Get it right and two branches feel like one practice with two doors. Get it wrong and you’re running two separate businesses that happen to share a name — with you as the human bridge between them.
What actually breaks when you add a branch
On day one of branch two, five things stop working the way they used to:
Patient records split. Mrs Ahmed has her sight test at your original practice, then walks into the new branch to choose frames near her office. If your PMS can’t show her record there — prescription, history, notes, outstanding balance — your new branch is serving a stranger.
The diary fragments. Reception at branch A can’t see availability at branch B, so they can’t offer the appointment that would actually suit the patient. Every “let me check with the other practice” phone call is friction you invented by expanding.
Stock goes invisible. The frame a patient wants is sitting eight miles away, but nobody knows, so the sale becomes an order, the order becomes a wait, and the wait becomes a cancellation. Multiply that by a full frame inventory and you’re carrying double stock to compensate for missing information.
Reporting doubles in effort and halves in usefulness. You now need two views — each branch on its own, and the group as a whole — and if your PMS only does one site at a time, you’re exporting spreadsheets and stitching numbers together on a Sunday night.
People and permissions get messy. Your locum works Tuesdays at one branch and Thursdays at the other. Your manager needs to see both sites’ figures; your Saturday assistant shouldn’t. Systems designed for one practice tend to treat every user as belonging to one place.
None of these are exotic edge cases. They’re the ordinary Tuesday of every multi-site group — which is why they’re precisely the things to compare.
The five jobs a multi-site PMS must do
1. One patient record, every branch
The foundational job. A patient who visits any of your branches should exist once in the system, with their full clinical and dispensing history visible (permissions allowing) wherever they walk in. Look hard at how the system handles this — some legacy platforms “support” multiple branches by running separate databases and syncing overnight, which means branch B sees yesterday’s version of the truth. A genuinely shared patient records system holds one live record, updated in real time, from every location.
2. A diary that works across sites
Reception at any branch should be able to see, book and move appointments at every branch — and your online booking should let patients pick the location that suits them. This matters more than it sounds: cross-branch booking is how a group turns “no space until Thursday” into “we can see you tomorrow at our other practice, ten minutes away.” That’s a recovered sight test a single-site diary simply loses.
3. Stock visibility and transfers between branches
Your inventory system should answer two questions instantly: what do we have, and where is it? Beyond visibility, look for proper branch-to-branch transfers — stock moved between sites with an audit trail, not a Post-it note and a car boot. Groups that get this right carry less stock overall while saying “yes, we have that” more often. Groups that don’t end up over-ordering at both sites to paper over the blindness.
4. Consolidated and per-branch reporting
You need both lenses. Per-branch, to see which site is thriving and which is drifting — revenue, test volume, dispense rate, recall completion by location. Consolidated, to run the group as one business: total revenue, group-wide banking through your billing and finance reporting, and comparisons that show you branch A converts 15% better than branch B so you can find out why. If producing a group view means exporting from each branch and merging spreadsheets, the software is doing half the job and you’re doing the rest.
5. Users, roles and permissions across locations
Staff should be people, not per-branch logins. A locum who works across sites should carry one identity, with their activity attributed correctly at each. Owners and managers need group-wide visibility; branch staff usually don’t. And when someone leaves, you should be able to switch them off everywhere in one action — a small thing until the day it isn’t.
Cloud changes this comparison completely
We’ve compared cloud and desktop PMS in depth before, but multi-site is where the difference stops being philosophical and starts being financial. A server-based system typically means a server (and its maintenance, backups and eventual replacement) in each practice, plus some mechanism to sync the two — the classic source of duplicate records and overnight-lag surprises.
A cloud system means both branches are simply windows onto the same live database. No sync, no server room in the stock cupboard, no “which copy is right?” Every job in the previous section gets dramatically easier when there’s only one version of the truth. For a practice group, cloud isn’t a preference in 2026 — it’s close to a prerequisite.
How multi-site pricing really works (and where it stings)
Pricing structures vary more for groups than for single sites, so compare like-for-like:
Per-location pricing — a flat fee per branch. Predictable, easy to model as you grow, and you’re not penalised for having a bigger team at one site.
Per-user pricing — costs creep as you add staff, and part-timers and locums complicate the maths. A ten-person group can pay more than a fifteen-person one depending on structure.
Tiered “enterprise” pricing — some vendors treat the second branch as the trigger to move you onto a pricier plan, where multi-site features you’d assume were standard (consolidated reporting, cross-branch stock) turn out to be paid modules.
The questions that matter: what does branch two actually add to the monthly bill? Are multi-site features included or extra? Is there a separate setup fee per location? And what does data migration cost for the practice you’re acquiring? Ask for the total for your specific structure in writing. Vague answers at this stage become invoices later.
Ten questions to ask in the demo
Make the vendor show you, live, not tell you:
1. Show me one patient’s record opened from two different branches. Is it the same live record?
2. Book an appointment at branch B while “logged in” at branch A. How many clicks?
3. Can online booking let the patient choose their branch?
4. Show me where branch A sees branch B’s frame stock — and how a transfer between them works.
5. Show me revenue by branch, side by side, for last month — without exporting anything.
6. Now show me the group total in one view.
7. How does a locum who works at both sites appear in the system?
8. Can I restrict a branch employee from seeing group-wide figures?
9. What exactly does adding a third branch cost — licence, setup, migration, training?
10. Do recalls and patient communications run per-branch, group-wide, or both — and can the patient’s “home” branch be preserved?
That last one is easy to miss. Recall is the revenue engine of any practice, and a group needs recall automation that respects where each patient actually goes — a group-wide blast that invites patients to the wrong branch trains them to ignore you.
Red flags that cost practice groups money
“Multi-site” means synced copies, not one database. If the vendor talks about overnight sync or replication between branches, you’re looking at a single-site product wearing a group badge.
Consolidated reporting is a paid extra. Seeing your own business in one view shouldn’t be an upsell.
Stock transfers are manual workarounds. “You’d just book it out of one branch and into the other” is a shrug, not a feature.
Per-branch support contracts. Some vendors charge support per site while delivering it once. Read the schedule.
The demo only ever shows one branch. If they won’t demo a two-branch setup, there’s usually a reason.
How Raven Vision handles multiple branches
We should declare our interest — and our origin. Raven Vision wasn’t built as a single-site product that later bolted on a “group edition.” Our co-founder Shaukat is an optometrist who runs three practices of his own, and RV was built inside those practices first. Cross-branch records, one shared diary, stock visibility between sites and group-level reporting weren’t roadmap items; they were the daily reality the software had to survive before anyone else ever used it.
Practically, that means one live cloud database across all your branches, every feature included at every site, and pricing that stays simple as you grow: £149 per month per location, everything included — no enterprise tier, no multi-site module, no setup fee, with free data migration for each practice you bring across.
Before you sign anything
Run the short checklist: one live record across branches, cross-site diary and online booking, stock visibility with real transfers, per-branch and consolidated reporting out of the box, sensible user permissions, and a written all-in price for your exact structure — including the next branch you haven’t opened yet.
If you run more than one practice — or you’re planning branch two — it’s worth seeing what this looks like when the software was built by someone who lives it. Book a demo and bring your hardest multi-site questions; we’ll show you everything on this list, live, across real branches.
