> ## Documentation Index
> Fetch the complete documentation index at: https://docs.riservahq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

The words you meet in Riserva, in plain language, A to Z. Each entry says
what the word means here and points to the article that explains it best.
For every badge and status, see [Statuses: what every badge means](/reference/statuses).

***

### Active

An experience that is live: guests and staff can book it. The experiences
list and the experience's own page both say **Active**.

See: [Publish an experience](/getting-started/publish-an-experience)

### Add-on

An optional extra a guest can add to a reservation, such as a cheese plate
or a reserve pour. Each add-on is sold as its own Shopify product, priced per
party, per guest, or each (the guest picks how many).

See: [What guests see, end to end](/guest-experience/what-guests-see)

### Archived

An experience you have retired. It cannot be booked and is hidden from the
experiences list unless you filter for it; its past reservations and
reports are untouched.

See: [Publish an experience](/getting-started/publish-an-experience)

### Arrival pacing

An optional limit on how many new guests may start a visit at a venue in any
15-minute window, so the bar never gets a rush all at once. Set it on the
venue as "Max new guests per 15 minutes"; blank means no limit.

See: [Set up locations and venues](/getting-started/locations-and-venues)

### Assigned

A table a host chose for a party, or a suggestion a host pressed **Keep**
on. Riserva never moves an assigned table.

See: [Running service with the Host view](/daily-operations/host-view)

### Attendance

Who of a party actually came, counted in guests beside the party size — "3 of
4 here", then "3 of 4 arrived" once the visit is completed. Hosts record it
with **Partial check-in…** or **Edit guests here**; a party checked in as a
whole counts as all here. It changes neither the party size nor the money.
Reports has an **Attendance** card with the show-up rate.

See: [What each report answers](/reports/what-each-report-answers)

### Awaiting payment

A payment state: an order or payment link exists for the reservation, but
the money has not arrived in full. It turns into Paid by itself once it does.

See: [Statuses: what every badge means](/reference/statuses)

### Blackout period

Dates you close to new reservations — a holiday, a private event, harvest —
for a whole venue or chosen experiences. Reservations already on those dates
stand; guests simply see no times.

See: [Set up locations and venues](/getting-started/locations-and-venues)

### Booked after its time

A red badge on a reservation whose online order was paid after its visit had
already ended — for example one left in a cart for days. Riserva keeps the
reservation so the money is not lost, but sends the guest no confirmation and
never marks it a no-show by itself. It sits in **Needs attention** until you
move it to a new date with **Edit reservation** (which clears the badge) or
cancel it to refund the guest.

See: [Statuses: what every badge means](/reference/statuses)

### Booked value

In Reports, what the reservations in a range are worth once every balance is
settled: **Collected** plus everything **Still due**. No-shows' unpaid
balances are left out, because nothing will collect them.

See: [What each report answers](/reports/what-each-report-answers)

### Booking widget

The booking button, booking window and experiences grid your guests use on
your storefront. You add it to your theme as a theme block.

See: [Add the booking widget to your theme](/getting-started/add-the-booking-widget)

### Buyout

One party booking a whole venue, such as a private dinner. In Riserva this is
the **Whole venue** capacity strategy, and it has one flat price for the
venue, not a price per guest.

See: [Capacity strategies explained](/core-concepts/capacity-strategies)

### By visit date / By booking date (the lens)

The two ways Reports can count, chosen with one button called the lens. It
moves every figure on the Overview. **By visit date** (the default) files each
reservation and its money on the day of the visit. **By booking date** files
it on the day it was made, which lines up with Shopify's own order figures.

See: [What each report answers](/reports/what-each-report-answers)

### Cancellation policy

The rules for what a cancellation refunds and whether guests may cancel or
reschedule online. Your shop has one policy (Settings → Policies); any
experience can have its own custom rules instead.

See: [Set your cancellation policy](/getting-started/cancellation-policies)

### Capacity strategy

How an experience limits reservations: **Manual capacity**, **Venue floor map**,
**Whole venue** or **Open (no limit)**. It decides whether a reservation uses
up places, a table, or the whole room.

See: [Capacity strategies explained](/core-concepts/capacity-strategies)

### Card on file

A payment state: the guest's card was saved at an online checkout and is
charged when you check the party in — or, on an experience charged **At the
visit**, when the visit is closed out, unless the register settles the fee
first.

See: [Payment policies and money states](/core-concepts/payment-policies)

### Charge later

Paying by a card saved at checkout instead of paying at checkout. Set
under **When is it charged?** on a priced experience: **Before the visit —
charged automatically** (the **charge lead** sets how many hours before),
**At check-in — charged automatically**, or **At the visit — charged when
closing out, or settled at the register**. It works for online reservations
only.

See: [Payment policies and money states](/core-concepts/payment-policies)

### Charge now

A button on a reservation's Payment card that charges a saved card straight
away instead of waiting for its scheduled time.

See: [Payment policies and money states](/core-concepts/payment-policies)

### Channel

How a reservation was made: **Online** (your storefront), **Phone** or
**Walk-in** (your team, in the admin), or **POS** (at the register). Parties
seated from the waitlist are Walk-in.

See: [Statuses: what every badge means](/reference/statuses)

### Check in

Recording that a party has arrived. It moves them to **On property**, and it
charges a saved card that is still waiting for its charge date (except on an
experience charged **At the visit**, whose card waits for close-out). When
only part of the party is here, use **Partial check-in…** instead. A check-in
pressed by mistake can be taken back with **Undo check-in**.

See: [Running service with the Host view](/daily-operations/host-view)

### Checkout rule

A rule in Shopify's Settings › Checkout, under Checkout rules, that can stop a
checkout. Riserva adds one called **Check reservations at checkout**
and turns it on by itself: it refuses a checkout whose cart still holds a
reservation for a day that has already passed, or a reservation whose quantity
no longer matches its party, and tells the guest what to fix. Payment links and visits later today are never blocked. If you switch it
off there, Riserva leaves it off.

See: [What guests see, end to end](/guest-experience/what-guests-see)

### Collected (Collected revenue)

In Reports, the money actually taken for the reservations in a range, with
refunds already taken out. The **Collected revenue** figure at the top of the page is
the same number; money still owed is not in it.

See: [What each report answers](/reports/what-each-report-answers)

### Collection run

Riserva collects scheduled saved-card charges once an hour, so a charge due
at 2:00 PM lands within the following hour. Screens say "collected within
the hour" for this reason.

See: [Payment policies and money states](/core-concepts/payment-policies)

### Combinable tables

Tables that can be pushed together for a party too big for either one, such
as two four-tops making a six. Set it in a table's **Combinable with** list.

See: [Tables and the floor map](/getting-started/tables-and-floor-map)

### Communal table (seat pool)

A table or bar that seats several parties at once, booked by the seats left
rather than taken whole by one party. Tick **Communal seating** on the table;
the reservation page calls it a **seat pool**.

See: [Tables and the floor map](/getting-started/tables-and-floor-map)

### Cover

One guest. A party of four is one reservation and four covers. A table's
"1–4 covers" means it seats parties of one to four.

See: [What each report answers](/reports/what-each-report-answers)

### Customer

A Shopify customer record. A reservation can be linked to one: its Guest
card then offers **View customer profile**, and whether the guest is a
member comes from the customer's tags.

See: [A reservation's page](/daily-operations/reservation-page)

### Cutoff

How close to the visit something stops being allowed online. The **Online
booking cutoff** on an experience closes online booking that many minutes
before each start time; your policy can also set how close to the visit
guests may still cancel or reschedule online. Staff are never held to
either.

See: [Party size, cutoffs and who can book](/core-concepts/party-size-and-visibility)

### Day sheet

A printable list of a day's arrivals for the host stand: guests, phones,
party sizes, tables, payment state and notes. **Print day sheet** is under
**More actions** on the Host page.

See: [Running service with the Host view](/daily-operations/host-view)

### Draft

An experience that is not bookable yet, or has been taken off sale. Every
new experience starts as a draft.

See: [Publish an experience](/getting-started/publish-an-experience)

### Draft order

Shopify's word for an unpaid order your team prepares. Riserva uses one for
every payment link: the guest pays it as an invoice, and it then becomes the
reservation's order.

See: [Payment policies and money states](/core-concepts/payment-policies)

### Early-arrival window

How far ahead of its reservation a party can check in before Riserva asks
whether to move the reservation to now. The default is 60 minutes; a party
that is on time or late is never asked. Set it in Settings → Reservations →
Early arrivals.

See: [Waitlist, early arrivals and ending visits](/daily-operations/waitlist-early-arrivals-and-ending-visits)

### Ends by itself

A checked-in or seated party is marked **Completed** automatically, at the
moment Settings → Reservations → Ending visits names: after its reservation's
end time plus a grace period (15 minutes unless you change it), at the end of
the day (midnight, property time), or never. Nothing announces it while a party
is on time; once it is past its end, the **Running over** badge's tooltip on
Host says when ("Ends by itself at 2:45 PM", or "Ends by itself at the end of
the day").

See: [Waitlist, early arrivals and ending visits](/daily-operations/waitlist-early-arrivals-and-ending-visits)

### Entry fee

An experience that charges guests to reserve — the answer **Yes** to "Are
you charging for entry?". The other answer is **Free to book**.

See: [Payment policies and money states](/core-concepts/payment-policies)

### Event

An experience whose schedule is pinned to one date, such as a harvest
dinner. Each event date sells its own tickets and can sell out on its own.

See: [Experiences and one-off events](/core-concepts/experiences-and-events)

### Experience

What a guest reserves: a tasting, a tour, a dinner, an event. It carries the
schedule, capacity, price and rules, and is sold through its own Shopify
product.

See: [Create your first experience](/getting-started/create-your-first-experience)

### Fee credit (bill credit)

A reservation fee that comes off what the guest buys during the visit — the
tasting fee waived with purchase. Turn it on with **Credit the fee toward
the guest's bill**; rows then show a badge like "Credit \$50", and staff
apply it at the register with the **Bill credits** tile in Shopify POS.

See: [Payment policies and money states](/core-concepts/payment-policies)

### Floor map

The drawing of a venue's tables and seat pools in the floor-map editor.
Experiences set to **Venue floor map** take their capacity from it.

See: [Tables and the floor map](/getting-started/tables-and-floor-map)

### Free to book

An experience that costs nothing to reserve; guests pay for what they buy
during the visit. A free experience never carries a hidden price.

See: [Payment policies and money states](/core-concepts/payment-policies)

### Guest questions

Your own questions guests answer when they book online, such as the occasion
or dietary needs. The answers appear on the reservation's page.

See: [Ask guests your own questions](/guest-experience/intake-questions)

### Guests here

How many of a checked-in party have arrived, when not everyone has. Set it
with **Partial check-in…** or **Edit guests here**; **All here** sets it back
to the whole party. The lowest it goes is 1 — a party nobody came for is a
no-show.

See: [Running service with the Host view](/daily-operations/host-view)

### Hold

When a guest presses **Reserve**, Riserva holds their time for 12 minutes so
nobody else can take it while they pay. On the Host Timeline a hold is a bar
reading "Checking out", which the key calls "In checkout". One visitor can
make up to 20 holds in 10 minutes; past that, the booking window asks them to
wait a few minutes.

See: [What guests see, end to end](/guest-experience/what-guests-see)

### Host

The page your team keeps open during service, for one location at a time.
Its tabs are **Arriving** (booked, not checked in yet), **On property**
(checked in or seated and still here) and **Waitlist**.

See: [Running service with the Host view](/daily-operations/host-view)

### Join link

The web address the join button in the members-only notice sends non-members
to, usually your wine club's signup page. A non-member sees that notice when
they press Book on a members-only experience. Set it under Settings →
Memberships → Members-only experiences, with the words on its button ("Join to
book" unless you change them). Left blank, the notice offers Sign in only.

See: [Party size, cutoffs and who can book](/core-concepts/party-size-and-visibility)

### Late

A party more than 10 minutes past its start time that has not checked in.
The Host Timeline and Map draw it yellow, the party panel shows a yellow
**Late** badge, and the register shows a "Late" badge, all on the same
10-minute rule.

See: [Statuses: what every badge means](/reference/statuses)

### Let Riserva choose

The link in the party panel's Table section that hands an assigned table
back to Riserva, so it becomes a suggestion Riserva may move again. (It was
called **Auto-assign** until 2026-10-08.)

See: [Running service with the Host view](/daily-operations/host-view)

### Location

A property — a winery, a tasting room, an estate. Locations come from your
Shopify locations; Riserva mirrors them and you set each one's time zone.

See: [Set up locations and venues](/getting-started/locations-and-venues)

### Locked

A table that is assigned and cannot be changed by anyone until someone
presses the padlock again ("Unlock the table") in the party panel's Table
section. Use it when you have promised a guest a table.

See: [Running service with the Host view](/daily-operations/host-view)

### Manual capacity

A capacity strategy where you set how many guests each start time can take,
like tickets. Each start time sells on its own, even when visits overlap.
Suits tours, classes and ticketed tastings.

See: [Capacity strategies explained](/core-concepts/capacity-strategies)

### Mark paid on-site

A button on the Payment card for a guest who paid at the counter or in cash
outside Riserva. The reservation becomes Paid and the amount is recorded as
"Paid on-site".

See: [Payment policies and money states](/core-concepts/payment-policies)

### Max groups per slot

An optional cap on how many separate parties can start at the same time,
whatever their size. It sits under **Advanced** on the experience.

See: [Party size, cutoffs and who can book](/core-concepts/party-size-and-visibility)

### Member

A guest recognised as a club member from their Shopify customer tags. They
carry a **Member** badge, and only members can book a **Members only**
experience online.

See: [Member benefits](/memberships/member-benefits)

### Member tag

A Shopify customer tag that marks a customer as a member, such as
"club-gold". You list your member tags under Settings → Memberships → Member
recognition.

See: [Member benefits](/memberships/member-benefits)

### Members only

A setting under **Who can book**: online, only recognised members can book
the experience. Your staff can always book it. Non-members see it on your
store's Experiences list with no times, and its Book button opens a
"Reserved for members" notice with a join button — unless the experience is
set not to show it to them at all.

See: [Party size, cutoffs and who can book](/core-concepts/party-size-and-visibility)

### Needs attention

The reservations-list tab of reservations someone has to act on: Pending
payment, Overbooked, Booked after its time, Payment due and Charge failed.

See: [The reservations list](/daily-operations/reservations-list)

### No-show

A party that never came. Mark it from the reservation, the Host page or the
register before they check in — or let Riserva mark parties that never check
in by itself, a set time after their reservation or at the end of the day
(Settings → Reservations → No-shows; off unless you turn it on). The guest is
not emailed and nothing is charged automatically. **Undo no-show** takes it
back if they walk in after all.

See: [Waitlist, early arrivals and ending visits](/daily-operations/waitlist-early-arrivals-and-ending-visits)

### Notify

The waitlist button that tells a party their table is ready by email. It
needs an email address; there is no text message.

See: [Running service with the Host view](/daily-operations/host-view)

### Open (no limit)

A capacity strategy with no cap on each start time, unless you set an
optional maximum. Party-size limits and arrival pacing still apply.

See: [Capacity strategies explained](/core-concepts/capacity-strategies)

### Order

Every reservation that takes money settles as a Shopify order, on your own
payment providers. The reservation's Payment card links to its order or
orders.

See: [A reservation's page](/daily-operations/reservation-page)

### Overbooked

A badge on an online reservation whose time filled up while the guest was
paying. Riserva keeps the paid reservation and flags it for you to sort out.
A time your team overbooks on purpose does not get this badge.

See: [Statuses: what every badge means](/reference/statuses)

### Party

The group on one reservation. **Party size** is how many guests are in it;
each experience sets the smallest and largest party it takes online.

See: [Party size, cutoffs and who can book](/core-concepts/party-size-and-visibility)

### Partial check-in

A party that checked in with only part of it here — "2 of 4 here". Chosen
from the arrow on the **Check in** button in the admin, or the **Partial
check-in…** button beside **Check in** on the iPad, or set afterwards with
**Edit guests here**. The status badge reads **Partial
check-in** in yellow with a half-filled circle until **All here**. The party
size and what was paid do not change.

See: [Running service with the Host view](/daily-operations/host-view)

### Partial no-show

In Reports' **Attendance** card, the guests missing from a party that did come
— two, for a party of four where only two arrived. The party itself counts as
a visit, not a no-show, so the No-show rate is unaffected.

See: [What each report answers](/reports/what-each-report-answers)

### Payment due

Money is owed on a reservation and nothing has been collected yet — normal
for a reservation your team books on a priced experience. Collect it with a
payment link, at the register, or with Mark paid on-site, or forgive it with
Waive payment.

See: [Payment policies and money states](/core-concepts/payment-policies)

### Payment link

A Shopify invoice for exactly what a reservation owes, made from its Payment
card. Copy it, open it, or email it to the guest; when they pay, the
reservation turns Paid.

See: [Payment policies and money states](/core-concepts/payment-policies)

### Payment policy

When a priced experience collects its money — the answer to **When is it
charged?**: at booking, before the visit, at check-in, or at the visit
(when the visit is closed out, unless the register settles it first).

See: [Payment policies and money states](/core-concepts/payment-policies)

### Plan

Riserva's monthly subscription, billed through Shopify, with a 14-day trial
and no fee per reservation. Settings → Plan shows yours.

See: [Plans and billing](/getting-started/plans-and-billing)

### POS tile

A button Riserva adds to the smart grid — the grid of tiles on your Shopify
POS home screen: **Reservations** (the host stand), **Book reservation** and **Bill
credits**. You add the tiles in the POS editor.

See: [Reservations in Shopify POS](/daily-operations/pos)

### Refund owed

A refund Riserva tried to send that did not complete. The reservation's
Payment card shows it with **Retry refund** and **Mark handled in
Shopify**; the register shows it as "Refund due".

See: [Cancellations and refunds](/daily-operations/cancellations-and-refunds)

### Reorder

The **Reorder** button on the Experiences page sets the order guests see in
your store's Experiences list and staff see on the POS Book tile. Events are
in the list too, so you can place them; on the Experiences page itself they
keep their date order in the Events card. Until you reorder, experiences are
listed alphabetically.

See: [Experiences and one-off events](/core-concepts/experiences-and-events)

### Reservation

One party, one experience, one time. It is what a guest books and what your
team checks in.

See: [A reservation's page](/daily-operations/reservation-page)

### Reservation ID

The code a guest receives and staff read over the phone, such as RES-7K4M.
It is also added as a tag on the reservation's Shopify order.

See: [A reservation's page](/daily-operations/reservation-page)

### Reservation ID prefix

The letters at the start of every new reservation ID — "RES" unless you
change it to 1–5 letters or numbers in Settings → Reservation IDs. Codes
that already exist never change.

See: [What guests see, end to end](/guest-experience/what-guests-see)

### Running over

A checked-in or seated party past its reservation's end time, or past the
extra time a **Still here** press gave it. It is a badge on the Host list and
in Shopify POS, and an amber edge on the party's bar or table on the Timeline
and Map. Press **Still here** if they are lingering (it clears until the new
end passes), or **Complete** if they have left.

See: [Waitlist, early arrivals and ending visits](/daily-operations/waitlist-early-arrivals-and-ending-visits)

### Seat

The step after check-in that records the party has sat down. It does not
choose a table; tables are chosen separately.

See: [Running service with the Host view](/daily-operations/host-view)

### Self-service

Guests cancelling or rescheduling a reservation themselves, from the link in
their confirmation email. Your cancellation policy decides whether they may,
and until when.

See: [Guests managing their own reservations](/guest-experience/guest-self-serve)

### Shopify Flow

Shopify's automation app. Riserva gives it reservation triggers and an
action that adds a note to a reservation.

See: [Shopify Flow](/integrations/shopify-flow)

### Show-up rate

The big number on Reports' **Attendance** card: of the guests whose visit has
come, the share who actually walked in — Arrived ÷ (Arrived + Partial no-shows

* No-shows), shown with a line like "show-up rate · 120 of 130 guests came".

See: [What each report answers](/reports/what-each-report-answers)

### Slot

A start time a guest can book, such as 2:00 PM. A weekly schedule sets the
first and last slot and how often a new one starts ("Slot every 30 min").

See: [Experiences and one-off events](/core-concepts/experiences-and-events)

### Special requests

A free-text note a guest can add when booking online, up to 500
characters. Hosts see it behind a note icon on the guest's row.

See: [A reservation's page](/daily-operations/reservation-page)

### Still due

In Reports, money the reservations in a range still have to bring in: saved
cards not charged yet, and Payment due balances.

See: [What each report answers](/reports/what-each-report-answers)

### Still here

The Host button for a party that is running over and still at the table. It
moves their expected end out by 30 minutes, as many times as you like, and
the automatic end waits for it. It never stops online guests booking the
times after.

See: [Waitlist, early arrivals and ending visits](/daily-operations/waitlist-early-arrivals-and-ending-visits)

### Suggested

A table Riserva picked for a party when the reservation was made. It may
move it to fit another party until the party arrives. Drawn with a dashed
outline.

See: [Running service with the Host view](/daily-operations/host-view)

### Tags

Labels Shopify keeps on orders and customers. Riserva tags every reservation
order with "riserva-booking" and the reservation ID, and reads member tags
from customers. Experiences carry tags of their own too, set on the
experience page under **Organization**, so an Experiences list block on your
store can show only the experiences with one tag.

See: [Member benefits](/memberships/member-benefits)

### Theme block

A piece you add to a page of your theme in Shopify's theme editor. Riserva
has two: **Experience booking** (a button or form for one experience) and
**Experiences list** (a search bar and a grid of everything bookable).

See: [Add the booking widget to your theme](/getting-started/add-the-booking-widget)

### Timeline

Two things share the name. A reservation's **timeline** is its history:
every change, payment and email, with who did it. The Host **Timeline** is a
view of the day laid out left to right, one row per table or experience.

See: [A reservation's page](/daily-operations/reservation-page)

### Turn time

The reset time after each visit — clearing and resetting the table — set as
**Buffer / turn** on the experience. The visit's **duration** plus the turn
time is how long a reservation holds its table or room; guests are shown
only the duration.

See: [Experiences and one-off events](/core-concepts/experiences-and-events)

### Unassigned

A party on a floor-map venue that has no table, usually because the time is
too full. It sits in an Unassigned row at the top of its venue on the Host
Timeline.

See: [Running service with the Host view](/daily-operations/host-view)

### Undo check-in

Taking back a check-in pressed by mistake. The party goes back among those
arriving, as Confirmed (or Pending payment, if that is what it was checked in
from). Riserva refuses it when the check-in already charged the guest's
saved card or marked the reservation's order fulfilled.

See: [Running service with the Host view](/daily-operations/host-view)

### Undo no-show

Taking back a no-show called too soon — by a host or by the automatic
No-shows setting — when the guest walks in after all. The reservation goes
back to Confirmed (or Pending payment, if that is what it was marked from)
and can be checked in. It is in the reservation page's menu and on a no-show's
page in the Done tab of the Reservations tile in Shopify POS. Nothing refuses
it, because no money moves on a no-show.

See: [Waitlist, early arrivals and ending visits](/daily-operations/waitlist-early-arrivals-and-ending-visits)

### Unlisted

A setting under **Who can book** for private events: the experience has no
listing and no product page online, and only your staff can book it.

See: [Party size, cutoffs and who can book](/core-concepts/party-size-and-visibility)

### Unseat

Taking back a Seat pressed by mistake: the party goes from Seated back to
Checked in and stays on property.

See: [Running service with the Host view](/daily-operations/host-view)

### Upcoming

The Reports tab that looks forward: what is on the books from today through
the next 7, 30 or 90 days. The reservations list has an Upcoming tab too.

See: [What each report answers](/reports/what-each-report-answers)

### Venue

A bookable space inside a location: a tasting bar, a restaurant, a cave, a
lawn. Experiences run in venues, and a venue can have a floor map.

See: [Set up locations and venues](/getting-started/locations-and-venues)

### Venue floor map

A capacity strategy where the venue's tables and seat pools set the
capacity. A reservation holds its table for the visit plus the turn time.

See: [Capacity strategies explained](/core-concepts/capacity-strategies)

### Waive payment

A button on the Payment card that forgives the whole outstanding balance —
for a comp, goodwill or a mistake. Part of a balance cannot be waived.

See: [Payment policies and money states](/core-concepts/payment-policies)

### Waitlist

The list of walk-in parties waiting for a table on the Host page and the
register. You quote a wait, **Notify** them when a table is ready, and
**Seat** them into a real reservation. If you turn it on, guests can also
join it online when today is fully booked.

See: [Waitlist, early arrivals and ending visits](/daily-operations/waitlist-early-arrivals-and-ending-visits)

### Walk-in

A party that arrives without a reservation. Book them as a Walk-in in the
admin, or add them to the waitlist and seat them from there.

See: [Booking a reservation for a guest](/daily-operations/book-a-reservation)

### Whole venue

A capacity strategy where one reservation takes the entire venue for its
visit and turn time, at one flat price. Used for buyouts and private events.

See: [Capacity strategies explained](/core-concepts/capacity-strategies)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.