Multi-branch

Built for Groups, Not Retrofitted for Them

Software written for a single practice and later extended to several usually shows it — one shared patient list, one price list, and permissions that force a group manager to become an administrator everywhere.

Book Your Free Demo

Branch comparison

This month
BranchRevenueChair use
  • Al Olaya
    182,40092%
  • Al Nakheel
    146,90078%
  • Jeddah North
    98,30061%

Interface languages

EnglishالعربيةFrançaisDeutschРусский

The problem

What a second location breaks

  • Staff at one branch can see and edit everything at the others.
  • One price list has to serve locations with different costs and different insurers.
  • Stock is pooled in the system and separate in reality.
  • Comparing branches means exporting each one and joining them by hand.

What it does

Built for Groups, Not Retrofitted for Them

Branch-level data scoping

Patients, appointments, stock and reporting scoped to the branch, so the day-to-day view is the site someone actually works at.

Per-branch permissions, rooms, price lists and stock

Each site configures what is genuinely site-specific, while remaining part of one group rather than one tenant per location.

Group-level comparison reporting

Revenue, utilisation and staffing compared across branches from one view — the report that exists precisely because it cannot be produced by looking at one site.

Five interface languages

English, Arabic, French, German and Russian, with full right-to-left support. A group with mixed staff does not have to standardise on one language to standardise on one system.

What changes

Opening a location is configuration, not migration

A new branch joins the existing group rather than becoming a separate system to reconcile.

Group questions have group answers

Comparison reporting exists as a feature instead of as a monthly spreadsheet exercise.

Access stops being all-or-nothing

Branch scoping means a site manager gets their site, and only a group role sees across all of them.

Common questions

Can a patient be treated at more than one branch?

Yes — the patient record belongs to the group, so treatment at a second location continues the same history rather than starting a second file.

Is multi-branch an upgrade tier?

Branch capability is part of the platform. What your specific group costs is a conversation on the demo call — we would rather quote your actual configuration than publish a number that does not fit it.

Can each branch print documents in a different language?

Yes. Print language is set independently of interface language in the document designer, so the printed invoice and the staff UI do not have to match.

See this module with your own data

We'll walk your scenarios through the live product — and tell you honestly if PDental is the wrong fit.

Book Your Free Demo