AlpineClubBookingsNZ is an open-source booking, membership, payment, and
lodge-operations platform for small clubs. Members book real beds against real
capacity; admins run the whole club — bookings, membership lifecycle, fees,
Stripe and bank-transfer payments, Xero accounting, lodge chores, even the TV in
the lodge lobby — from one app.
Booking receipts are also recorded in the member-money journal. The
receipt catch-up and census
checks the gap between charge posting and receipt posting before the later
refund-ledger rollout.
One deployment serves one club — and this repository is the generic product
every club deploys, not one club's copy of it. Nothing here encodes which club
you are. Your name, capacity, age tiers, integer-cent rates, policies, wording,
branding, and which capabilities exist at all are values you supply. So the
normal way to adopt this is configure, don't fork, on four levers:
- Module toggle — switch a whole capability on or off for your deployment
(kiosk, chores, waitlist, Xero, bed allocation, lobby displays, and more).
docs/guides/modules.md is the live list, with each
module's out-of-the-box default.
- Setting — every club has the capability, each supplies its own value or
policy. Edited in the app, stored in the database, live immediately; no
redeploy, no
.env edit. Install-time values live in config/club.json.
- Seed default — the value a fresh install starts with. Change it when it is
a poor starting point for a typical club, and send that upstream.
- Code change — only when the behaviour genuinely is not expressible through
the generic model. Build the configuration surface at the same time, and
contribute it upstream rather than
carrying it forever in a fork.
The test that picks between them: would a different club answer this question
differently? If yes, it is configuration, not code.
→ Adopting it? Start at
Run this for your club, and read
Configure, don't fork before you change
any code.
What's in the box
| |
|---|
| 🛏️ Booking engine — bed-capacity availability, NZ date-only lodge nights, waitlist and offers, holds, changes, cancellation rules, refunds, credits, promo and group discounts, exclusive whole-lodge holds → guide | 👪 Membership lifecycle — registration, families and partners, nominations, seasonal membership types and age tiers, annual subscription billing, cancellation with GST-aware refunds → guide |
| 💳 Payments, two ways — Stripe card payments (PaymentIntents + webhooks) and Xero-backed Internet Banking invoices with settlement tracking. Booking pages show additional card asks and dated supplementary invoice amounts with how to pay; card additions also have automatic reminders; a later increase on a place an organiser paid for by bank transfer is invoiced to the organiser → guide | 📒 Xero accounting built in — OAuth, webhooks, retry queues, invoice/credit-note lifecycle, and a native finance dashboard on Postgres snapshots → finance docs |
| 🏔️ Lodge operations — rooms and beds, drag-and-drop bed allocation with per-lodge auto-allocation priorities, chores and rosters, work parties, hut leaders, lockers, inductions, PIN lodge kiosk → guide | 📺 Lobby TV displays — paired read-only screens showing arrivals, rooms, chores, and notices, driven by live booking data with privacy-reduced names → display docs |
| 🏘️ Multi-lodge core — lodge-scoped rooms, seasons, lockers, and chores with a cross-lodge waitlist → multi-lodge docs | 🔐 Granular admin roles — seeded permission bundles (Booking Officer, Treasurer, …), custom roles, full audit log → guide |
This is the beginning of the README. Read the rest at the original. Read the full README ↗
