It should look like your business, not like ours
Your staff look at this software more hours a week than they look at your website. It should carry your name, and so should everything it sends to your customers.
Logo, palette, typography, charts and navigation
Your logo in the interface and on every confirmation, reminder and receipt. Your colours, applied as a theme rather than as a header strip. Your typeface where a typeface can be licensed for it. Charts drawn in your palette instead of a default one that fights it.
Navigation is set per organisation as well. A group that never uses one part of the system does not have it in the sidebar, and a venue that lives in one screen opens on that screen.
Included at one venue as well as at twenty
Branding costs the same to build whether one venue uses it or a hundred do. Holding it behind an enterprise tier is a pricing tactic, not an engineering constraint, and we would rather say that plainly than pretend there is a technical reason.
So a single site gets the same theming a group of twenty gets. It is part of the product, not a line item, and it does not move you up a plan.
The words your team already uses, rather than ours
Run sheet or calendar. Players or adults or guests. Rate card or pricing sheet. Room, lane, bay, grid or table. Host, game master, coach or duty manager.
These are set per organisation and used everywhere: on screen, in reports, in exports and in the messages your customers receive. Nobody has to translate in their head, and training a new starter does not begin with explaining that the software calls it something else.
Underneath, the definitions do not move. Two venues can call the same thing by two different names and their numbers still add up to the same group total, because the label is a display decision and the metric is not.