The first site you run by standing in it. You know the day is going badly because you can feel it.
The second site removes that entirely, and most owners try to solve it by driving between the two, which works until it does not. What changes is not really the hardware. It is that you now need to see a building you are not standing in.
Build them identically
The most valuable and least exciting decision here.
Same tablet, same stand, same position on the counter. Same terminal. Same label printer. Same paper in the same drawer. Same wifi naming.
Why it matters: staff cover across sites. Somebody who works at Site A on Tuesday and covers Site B on Saturday should not have to relearn anything, and should not be the reason a payment is taken wrong. Identical builds turn a transfer into a non-event.
Write the build down. A one-page list of exactly what is at a counter, with model numbers, so site three takes a day rather than a fortnight.
One system, not one per site
The temptation is to let each site run its own thing, especially if you acquired the second rather than opening it. Resist it hard.
Two systems means two customer databases, and a customer who books at the wrong site is invisible. It means two sets of numbers you reconcile by hand. It means a gift voucher sold at one site that cannot be redeemed at the other, which is the single most common way a multi-site business annoys its own customers.
One system, with sites as locations inside it. That is genuinely what Petboost is built for and we are going to say so plainly: it is our product, we make money if you use it, and this is the case where the argument is strongest. Price the alternatives, and when you do, the question to ask each one is not whether they support multiple locations but whether a customer, a voucher, a package and a report cross between them without anybody typing.
Access, and taking it away
At one site, everyone has every key and every password and it is fine. At two, that stops being fine.
A password manager with shared vaults per site. Staff get access to what they need. When someone leaves you revoke once instead of trying to remember what they knew.
Roles in your booking system, so a casual cannot issue refunds and a manager can.
Physical keys tracked, with a tracker on each set and a written record of who holds what.
A leaver checklist. Written down, run every time. Building access, system access, phone, group chats, shared drives. Businesses get burned here and it is always because it was in someone's head.
Network and remote support
The same network kit at both sites, so when something breaks you already know how to fix it.
Remote access to both. Being able to check a camera, a router or a screen from home is the difference between a phone call and a drive.
Separate internet accounts, same failover approach. 4G failover at each site. When one site's connection drops, that site keeps taking payments.
A NAS or a cloud drive as the shared file layer, with the same folder structure at both. Photos, policies, rosters, supplier invoices.
Reporting stops being optional
This is the real change.
At one site you manage by walking around. At two you manage by looking, and if the numbers are not there daily you will find out about a problem a month late.
What you want to see, per site and combined: bookings taken, capacity used, revenue, no-shows, average spend, and staff hours against revenue. Weekly is enough for most of it. Capacity you want daily, because an empty Tuesday at one site while the other turns people away is a fixable problem that is invisible without the comparison.
Then the harder one: compare the sites and be honest about why they differ. It is almost never the suburb. It is usually the roster, the opening hours, or one person.
What breaks at two sites, specifically
Stock. Shampoo at one site, none at the other, both ordering separately. Centralise ordering, even informally.
Consistency. The same service delivered differently. Same templates, same report cards, same checklists.
Culture. Two teams who never meet become two businesses with your name on them. This is not a technology problem and technology makes it worse if you let it: a group chat is not a substitute for people meeting.
You. The owner at two sites is the bottleneck for every decision. The fix is written processes, not a better phone.
What does not change
Everything in the main stack still applies, per site: counter tablet, booking-integrated terminal, label printer, ink tank printer, mesh wifi, failover, UPS, cameras.
You are not buying different things. You are buying two of the same things and one system over the top.
Shop this list
Opens Australian shopping results on Google. Not affiliate links, and we earn nothing if you buy.
Where our interest lies, plainly. We have no affiliate arrangement with any brand named here and we earn nothing if you buy. Petboost is our own product, we make money if you use it, and this post recommends it as the single system across sites. Price the alternatives, and ask them the crossing-between-sites question above.