# Reservation Management Guide

This guide is the shortest path from an empty venue configuration to a reliable
daily reservation operation. The full reference lives in
[Reservations and Waitlists](/reservations).

## Build the inventory first

Create reservable seat tables with honest capacities, areas, and only the table
combinations staff can physically use. Check automatic allocation against the
inventory and intended service. Explicit staff selection must still include
every conflict-free table, even when excluded from online booking, automatic
capacity fit, or a selected area. Test that typical parties receive an efficient
table rather than consuming an unnecessarily large one.

See [Tables & Allocation](/reservations/tables-and-allocation).

## Configure the normal booking

In **Settings → Location settings → Reservations → General**, set duration, slot
interval, advance window, party range, enquiry inbox, online areas, and
reservation tags. Leave the built-in Standard offering in place unless guests
genuinely need different choices or operational rules.

See [Reservation Settings](/reservations/reservation-settings).

## Add only meaningful service choices

Use offerings for choices such as Food & drinks or Drinks only when duration,
pacing, or eligible tables differ. Use spaces for rooms, distinct table
footprints, booking requests, or enquiry-only hires. These additions sit on top
of the existing reservation workflow; they do not change its statuses or core
booking model.

See [Offerings](/reservations/offerings) and
[Rooms, Groups & Private Hire](/reservations/spaces-and-private-hire).

## Shape demand around service

Add shifts with first and last arrival slots, closing constraints, and realistic
turn times. Apply total-shift, concurrent-cover, or rolling pacing limits only
where they protect a real constraint. Offering pacing weights can distinguish a
light drinks visit from a kitchen-heavy menu without pretending the party has a
different number of seats.

See [Shifts, Pacing & Turn Times](/reservations/shifts-pacing-and-turn-times).

## Set guest policies

Choose whether to collect an upfront deposit or verify a card for possible
late-cancellation/no-show fees. Configure refund, cancellation, and modification
cutoffs and review any shift overrides. Use plain guest-facing wording that
states the amount and timing.

See
[Deposits, Cancellations & Changes](/reservations/deposits-cancellations-and-changes).

## Publish and test

Enable reservations, then use the Integration tab to test the published booking
and waitlist pages and widget. Use an agreed safe test for direct, request,
enquiry, payment, modification, cancellation, full-slot alert, and waitlist
journeys that your venue enables. Confirm every result appears correctly in
Console and App.

Use the complete [Setup Checklist](/reservations/setup-checklist).

## Run each service

Before service, resolve pending requests, review table assignments, groups,
rooms, dietary details, tags, and payment requirements. During service, keep
party sizes, seating, wait estimates, and statuses current. After service,
resolve cancellations, no-shows, fees, and waitlist entries.

Use [Managing Bookings](/reservations/bookings),
[Waitlist & Availability Alerts](/reservations/waitlist), and
[Reporting & Daily Routine](/reservations/reporting-and-daily-routine) as the
host and manager playbooks.

## Improve with evidence

Review booked versus seated covers, cancellations, no-shows, top offerings, top
tags, and waitlist results. Adjust one table, turn-time, pacing, or policy rule
at a time, then compare similar services. If a booking result is unexpected,
follow [Troubleshooting](/reservations/troubleshooting) before widening
capacity.

Before a consequential request acceptance, cancellation, no-show fee, message,
or table move, review the exact target and outcome. Verify saved booking,
financial, notification and table states separately. Test transactions and
messages only through the intended authorised test process.