The day you open your second clinic, you think revenue will double. What actually happens: the front desk starts making phone calls.
A client buys a treatment package at Clinic A and shows up at Clinic B for the session. B's front desk has to call A and ask, "How many sessions does she have left?" The same consumable is piling up near expiry at one clinic and running out every day at the other. At month-end, a client was brought in by A and closed at B, both clinic directors have their own argument, and who gets credit for that sale becomes something you have to rule on personally.
Each of these is small on its own. Together they eat a full day of someone's working hours, and usually it's the person you least want to waste — your most senior front-desk staff, or your admin manager.
The conclusion first: the real problem with multiple locations is not "should the data sync." It's "have you decided which data is shared across all clinics and which belongs to each clinic." That is a management decision, not a technical one. If you haven't drawn that line, any system you buy will be a mess, because a system doesn't think up rules for you. It just takes whatever you haven't thought through and amplifies it two or three times, untouched. Most of the cases I've seen follow the same script: the owner assumes a system marketed as a "chain edition" will integrate everything automatically. Three months after go-live, each clinic is still keeping its own private ledger in Excel, because nobody trusts the numbers in the system. The reverse also holds: once the "shared vs. separate" list is signed off and responsibilities are fixed, even a very ordinary system won't make cross-clinic work hurt much.
I'm Johnny Yang of Brightstream Technology in Taiwan. I've led implementation teams for seven years, across 252+ projects in 32+ industries.
Past two locations, it's always these three things
Let me start by taking the opposite side from you: your instinct — "just buy a system that connects everything" — points in the right direction, but in the wrong order. Multi-location pain is highly concentrated, and behind every pain point is a management rule nobody decided.
1. Client entitlements don't carry across
Treatment packages, prepaid balances, points, membership tiers — at their core, these are what you owe the client. With one clinic it didn't matter where you recorded them, because only one place ever touched them. With multiple clinics, the same liability gets touched in two or more places, and the problem upgrades from "record-keeping" to "dispute."
The two most common situations are exact opposites. One is double deduction: the client comes in once and gets charged two sessions. When the complaint arrives, what you lose isn't just that session, it's trust. The other is a missed deduction: B finishes the treatment and forgets to write it back to A's account, so on paper the package never runs out. Your prepaid revenue sits there, the books look great, and it's actually a black hole. Neither happens because the front desk is careless. It happens because you've got two groups of people maintaining one unlocked dataset. I break down the details of session deduction itself in "How to deduct treatment packages without starting a fight". Multiple clinics just multiply the same problem by the number of locations.
2. Each clinic keeps its own inventory
Consumables, injectables, resale products. The most common problem with multiple clinics isn't running out. It's not knowing whether you have stock at all. A's head nurse says it's gone and places an order, while in a corner of B's storeroom there are three boxes with two months left before expiry. HQ sees the total of what each clinic reports, and each clinic reports at a different time, so the sheet in your hand is always what was true three days ago.
There's an instinctive trap here: many owners' first reaction is "then centralize everything." In practice it doesn't work. The front line of inventory is nursing and floor staff. Centralized control means every withdrawal has to go through an HQ process, so staff will work around it, and once they do, the books get messier. The sensible approach: each clinic keeps its own books, HQ sees them in real time, and transfers between clinics are allowed as long as they leave a record. Note: "leave a record," not "get HQ approval."
3. Sales credit fights never end
The first two are data problems. This one is a people problem, and the hardest to solve with a system. A client is brought in by a consultant at A, treated by a doctor at B, and buys an add-on at a follow-up visit at C. How do you split that money? Without a written rule, the system can only record by its default logic — usually "credit goes where the sale closed" — and then you'll find the person who brought the client in stops bringing clients in, because they know the client will get treated at another clinic next time.
The dividing line: draw "shared" vs. "per-clinic" first
This is a table I always do first on multi-location projects, and the owner has to sign off on it personally. It's not a system setting. Write it on paper or in a one-page document and send it to every clinic director. Order matters: this table first, then look at systems.
| Data type | Recommended ownership | What happens if you don't decide first |
|---|---|---|
| Client master record, medical records, consent forms | One shared copy across all clinics | One client ends up with three records; marketing contacts them repeatedly; medical history is incomplete |
| Package balances, prepaid credit, points | Shared, locked in real time | Double or missed deductions across clinics; prepaid revenue doesn't reconcile |
| Pricing and plans | Mostly shared; per-clinic exceptions must be logged | Same treatment, two prices; clients compare them right in front of you |
| Consumable and product inventory | Separate books per clinic, visible to HQ in real time | Expiring in one place, out of stock in another; nobody owns the transfers |
| Treatment rooms, shifts, appointments | Each clinic manages its own | Central scheduling ties down the floor and always gets bypassed |
| Staff and permissions | One shared HR record; permissions granted per clinic | Former employees can still see other clinics' client data |
| Sales and commission | Shared rules, settled per clinic | A fight every month-end until someone quits |
There's no standard answer for this table. What I've given is where most clinics land. You can disagree with a few rows, but you must make a decision for every row, and once decided, someone has to own its upkeep. The worst is "let's go live first and adjust later." Later means never.
Client data must be shared, but shared doesn't mean everyone sees everything
Here's a distinction a lot of people miss: sharing data is one thing, opening up permissions is another.
The client master record and package balances must be a single copy. Not negotiable, or cross-clinic deductions will keep going wrong. But whether B's front desk can see all of this client's purchases and medical records from A is a separate question, and the answer is usually: they see what's necessary, not everything. This goes double for medical data. You're dealing not just with internal management but with compliance and how clients feel about it.
In practice the more stable design has three tiers: what staff must know at the point of treatment, like package balances and expiry dates, is visible across all clinics; business data like spend and marketing tags is for clinic directors and above; full medical records and images follow medical permissions. This isn't hard to build in a system. What's hard is whether you thought about it in advance. Most clinics only go back and patch permissions after a complaint, or after an employee walks out with the leads. By then it's too late.
Sales credit: this is a money-splitting rule, not a system feature
In the multi-location implementations I've done, what stalls things longest has never been technical. It's splitting the money.
You can require a system to support "origination credited to A, execution credited to B, each gets a share." Most systems on the market can do it, but that just translates your rule into configuration values. The prerequisite is that you have a rule, and it has to answer some very concrete questions: who brought the client in first, and how long does that credit last — a year, or forever? If the client switches clinics on their own, does the originator still count? Do you encourage cross-clinic referrals or not, and if you do, where's the incentive?
My advice is blunt: the rule should be simple enough to fit on one A4 page, and it should lean toward keeping clients within the group rather than protecting individual clinic numbers. The business value of multiple locations is precisely that clients can choose the nearest one. If your split rule makes every director want to lock clients into their own clinic, then however many locations you open, you've just opened a few independent clinics poaching from each other.
Once the rule is set, go back and check whether the system can carry it. Do it in the reverse order and it always ends as "the system doesn't support it, so we calculate it separately in Excel." At that moment, the thing you paid for stops meaning anything.
When choosing a system, ask these three questions out loud
Multi-location feature lists all look the same. Every vendor says they support chains. The difference is in the details, and you only get the details by asking.
First: "Are cross-clinic deductions real-time, or synced?" Sounds like the same thing. It isn't. Real-time means the balance is locked the moment B acts on it. Synced means each side has its own copy, reconciled at intervals. If it's the latter, follow up: "What happens when a sync fails, and who finds out?" If a vendor can't answer this clearly, cross-clinic double deductions will happen sooner or later.
Second: "For HQ's consolidated reports, does the system produce them directly, or do we export and merge?" Many systems' multi-location support stops at "each clinic can use it on its own," and consolidated reports are stitched together by hand. That's not necessarily a dealbreaker, but you need to know before you sign, not discover after go-live that someone still works overtime every month-end merging spreadsheets.
Third: "How long does it take to open a new clinic, and how much extra setup?" If you're running multiple locations, you plan to keep opening. If the third clinic means rerunning the implementation and rebuilding the data, that's this system's ceiling. I covered the overall logic of choosing a clinic system in "How to choose a medical aesthetics clinic system". Multiple locations just magnify the cost of every one of those judgments.
When you shouldn't rush to switch systems
I don't like watching people spend money on problems that haven't happened yet.
If your second clinic opened in the last month or two, is still in soft launch, its client base barely overlaps with the first, and cross-clinic treatments come to fewer than five a month — then what you should do now isn't switch systems. Write the rules down, get by with your existing tools, and watch for three months: how many clients actually cross between clinics, which treatments they cluster in, how many inventory transfers really happen. Those numbers decide whether you need a multi-location system, or one system plus a clear operating procedure.
The right time to switch is when you find someone routinely spending more than an hour a day on cross-clinic issues, or when you've already had one deduction dispute big enough to hurt. Before that, getting the management rules running smoothly will make your later implementation much faster — because the most time-consuming part of implementation has never been installation. It's forcing everyone to agree on the rules.
What you can do tomorrow
Take a sheet of paper, copy the table above, and fill in your decision for every row: is this data shared or per-clinic, and who's responsible when it goes wrong. The rows you can't fill in are where your real risk is right now, and where you should spend the most time when you talk to any vendor later.
Second, ask your front-desk supervisor one question: "Last month, how many calls did you make and how many cases did you handle because of cross-clinic issues?" It doesn't need to be exact. The order of magnitude is enough. That number tells you whether to act now or wait.
Third, write your sales credit rules on one page, send it to every clinic director, and let them fight it out. Fighting before implementation is far cheaper than fighting after go-live.
None of these three cost money, and none need anyone to do them for you. Once they're done, look at systems again, and you'll find you're asking completely different questions.
If you already run two or more clinics and are stuck with cross-clinic data that won't reconcile, I offer a free 30-minute diagnostic of your workflow. Walk me through how you do it now, and I'll tell you whether to fix the rules first or switch systems first.




