A second venue should not mean a second everything
Most platforms treat the group as an afterthought: separate accounts, separate customer lists, separate logins, and a portal laid over the top that can read all of it and change none of it.
One customer, however many of your doors they walk through
Customers, vouchers, rate cards, message templates and reporting definitions are shared across the organisation unless you say otherwise. A regular at one site is a known regular at the next one, with their history attached.
Sharing is switchable per level, so the things that genuinely differ can differ. A venue can keep its own pricing while using the group's templates. A region can share a rate card that head office does not impose everywhere else.
The default matters because siloed data is not a setting you can turn off later. It is a shape you are stuck with.
Set the scope once and every view respects it
Choose one venue, a region or the whole group, and that choice persists across the diary, the run sheet, reporting, customers and exports until you change it.
You are never re-selecting the same three sites in four different screens, and you are never looking at a number without knowing which venues are in it. Every figure states its own scope.
Per-venue timezone and currency inside one organisation
A Perth site and a Melbourne site are on their own clocks. An Auckland site takes New Zealand dollars. The booking is stored against the venue's local time and its own currency, so a session at seven in the evening is at seven in the evening for the people running it.
Group reporting still adds up, with conversion applied at the rate in force on the day rather than today's rate rewriting last winter. Most platforms cannot do this at all, which is why operators end up with one account per country and no group view worth reading.