More than one site
One site or a hundred, on the same system from day one.
Running several places is not an upgrade you buy later. It is how the whole thing is built, which is why it does not cost you anything extra to grow into.
Head office view
The dashboard on an HQ account showing figures rolled up across sites.
What head office gets
- Everything, in one view. Sales, attendance, memberships and guests across the whole group, without anybody exporting a spreadsheet and emailing it in on a Monday.
- Set it up once, send it everywhere. Push a product, a price or a ticket design out to whichever sites you choose — and see which ones took it.
- Decide who can do what. Detailed staff permissions managed for the whole group from one place, covering the till, the gate, refunds, products, reporting, customer data and settings.
- Suspend or close a site without losing it. A site can be made read-only or archived, and head office keeps full access to its history either way.
What each site keeps
- Its own books. A site sees its own sales, its own guests and its own cash-up — and genuinely cannot pull group-wide numbers. That is enforced by the system rather than hidden from the screen.
- Its own settings where it matters. Opening hours, tills, staff, currency, receipt wording and what the local team is allowed to change.
- Its own guest list, that still rolls up. Local reporting stays accurate while head office still sees one customer rather than one per site.
Sites working together
- One guest, not one per site. Someone who visits the aquarium in June and the boat tour in August is a single customer with a single history and a single lifetime value.
- Admit each other's tickets. When both sites agree to it, and with both getting credit for the visit. Staff at one site need no account at the other.
- Credit and memberships that travel. Store credit can be spent across the group when the issuing site allows it, and a membership can be honoured wherever you decide it should be.
- One place to manage a booking. A guest can find and change any of their bookings from one portal, while each booking keeps the rules of the site that actually sold it.
Pushing a product out
Organization → cascade, choosing which sites receive a product or ticket design.
See it running on your own products.
Bring one activity, one ticket type and one price. We will show you what it looks like in a real checkout.