Build your venue.
Then run it for a minute

Any number of boards, tables or cabanas, any capacity. Nothing about the fleet is in code.

Sittings per day type, generated on a rolling horizon rather than booked as arbitrary times. The demo has three fixed sittings; the generator itself is in the schema, not here.

Both modes on the same inventory, with the conflict between them resolved rather than ignored.

Whole-board only until a cutoff. If nobody takes it, seats open automatically at the cutoff.

Inventory is validated inside the lock at confirmation, never at cart time. Lives in the real booking engine. This prototype simulates availability and has NO such protection.

Draft to confirmed to checked in to completed, with an inventory hold that expires on its own. States are shown; the hold expiry job isn't built.

Phone, WhatsApp and walk-up intake, at whichever rate class the caller qualifies for.

Confirmations, butler names and changes on the channel people actually read, email as fallback.

Every party, by session and board, with party size, spend and what they pre-ordered.

One tap per party, and the sheet reflects who is actually on the water.

Assign a named person to a party; the guest gets the name before they arrive.

Weather or maintenance closes a sitting and flags everyone on it, offering the sessions still open.

Admin, host, butler and partner, each reaching only what their job needs. Built in the real back office. Not modelled in this prototype.

Who changed a price, forced a booking or closed a session, and when.

Name and a phone number at checkout. No sign-up, no password, no app to install.

An opaque per-booking link does the job a login would, so a walk-up never has an account. Built in the real customer surface.

Hold back a share of a peak sitting, with an automatic release so held seats never sail empty. Enforced, and the back office counts it exactly off the run sheet. The guest surface simulates how much of the share has gone, because a browse screen has no run sheet to count against. Note the cap can only ever apply between seats opening at T-48h and the hold releasing at T-24h — a one-day window.

Inside the release window every unsold seat opens to anyone, so a held seat never sails empty.

Held back, sold out and somebody's standing slot read differently, and a hold names the day it lifts.

A public price that stands on its own, separate from anything a member or resident pays.

Staying here is worth something at the beach, and the gap is a number you set.

At the size where a whole board costs about what seats cost, the app hands you the board.

An in-house guest settles at checkout instead of paying on the water.

Each package belongs to exactly one supplier, so an order always has an owner.

A configurable cutoff before the session, and anything inside it is flagged for the kitchen to accept. Late orders are flagged; the cutoff isn't computed from the session time.

What to make, for whom, by when — tracked from sent to picked up.

An outside company gets a login that reaches its order feed and nothing else. Built in the real back office as a role.

Per board, per session, per guest and whole-business lines. Everything starts at zero.

What today's prices demand, and what price today's occupancy demands. Both on one screen.

Name the profit you want and see the occupancy or the price it needs.

Two cost structures side by side while you negotiate, and a link that carries one.

Seats forgone when a held slot sails empty, priced separately so it never hides in occupancy.