Skip to main content

Reservations & availability

Reservations in Avero come from three pieces: experiences (what guests book), capacity (how many people can book, when), and the reservation book itself.

1. Define experiences​

Experiences are your bookable products — a seated tasting, a tour, a reserve flight. Manage them at /admin/experiences, and shape each one in the Experience builder (/admin/experiences/:experienceId/builder): schedule, pricing, and availability. The admin area has four tabs — Experiences, Templates, Rules, Capacity.

2. Open capacity​

Bookings are closed by default

New experiences take no reservations until you generate capacity. If your availability looks empty, that's expected — open it up first.

Availability is built from slot templates (reusable time-slot configs) and slot rules (which experience runs on which days at which location). A manager then generates capacity for a date range, which creates the bookable inventory.

Capacity is measured in people, not reservations — a slot with capacity 20 can hold one party of 20 or ten parties of 2.

3. Manage the book​

  • /reservations — the daily reservation list.
  • /reservations/new — create a booking.
  • /reservations/:id — booking detail: guest, party size, notes, and check-in.

Checking a guest in adds them to the floor queue so they can be seated — see Floor & seating.