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

# Restoo Key Concepts

> Overview of key concepts used throughout the Restoo API documentation.

The following sections describe the main entities, relationships, and business rules that define Restoo’s reservation and venue management model. Understanding these concepts is essential before interacting with the API endpoints.

## Core entities

### Tenant

The Restoo entity that represents a [Venue](#venue). It is identified by its unique `Restoo Account`.

### Venue

The physical location associated with a Restoo [Tenant](#tenant).

### Work day

Defines the operational day for the [Venue](#venue).

It starts at `05:00:00` on a given calendar date and ends at `04:59:59` on the following calendar day, according to the venue’s local time zone.

This design accommodates venues that operate past midnight and may accept reservations in the early hours (e.g., 01:00 AM) of the next calendar day, yet consider it part of the previous day’s service.

*Example: When requesting availability for the date `2025-03-20`, all [Time Slots](#time-slot) from `05:00:00` on `2025-03-20` up to `04:59:59` on `2025-03-21` will be included.*

### Shift

The time period during a [Work Day](#work-day) which the [Venue](#venue) accepts bookings, allowing availability and capacity to be managed separately for different parts of the day.

Examples:

* **Lunch** — 13:00 to 17:45
* **Dinner** — 18:00 to 23:30
* **Cocktails** — 23:45 to 01:00

<Note>
  Shifts cannot overlap within the same work day, with a minimum gap of 15
  minutes.
</Note>

### Floor plan

A layout that contains a set of [Tables](#table) and decorative elements of the [Venue](#venue).

Each [Shift](#shift) may have one or more floor plans.

<Note>
  Floor plans are not visible to customers and are intended solely for the
  venue’s internal organization.
</Note>

### Floor plan area

Sections inside the [Venue](#venue), made up of groups of [Tables](#table), that customers can choose when booking a reservation.

Examples:

* Indoor
* Terrace
* Bar

<Note>
  Each floor plan area may or may not accept online bookings, depending on the
  venue’s settings.
</Note>

### Table

A spot where a booking can be physically placed.

Each table can belong to only one [Floor Plan](#floor-plan) and one [Floor Plan Area](#floor-plan-area).

### Time slot

The minimum bookable unit, defined by the combination of:

* A start time during which the [Venue](#venue) accepts reservations.
* An optional [Floor Plan Area](#floor-plan-area) and/or Experience.

***

## Bookings and operations

### Booking Types

* **Booking** — A planned reservation made in advance. The start time always aligns with 15-minute intervals.
* **Walk-In** — A customer who arrives without a reservation and is seated immediately at an available table.
* **Walk-In Waiting** — A customer who arrives without a reservation but cannot be seated immediately and is placed on a waitlist.

### Booking size

The total number of people in a Booking: `pax` plus `paxChildren`.

Rules expressed in booking size always use this total, never `pax` on its own.

### Booking and Customer

Only **Walk-In** Bookings may not be linked to a Customer profile, depending on the [Tenant](#tenant) settings.

All other Booking types **must** be associated with a valid Customer profile.

### Booking and Tables

For **Walk-In** Bookings, at least one Table **must** be assigned.

For all other Booking types, assigning a Table is **optional** and depends on each venue's operational preferences.

### Adult and children differentiation

Some [Tenants](#tenant) require distinguishing the number of adults and children in a Booking. This feature must be explicitly enabled in the Tenant's settings.

<Info>
  If children are included in a Booking request for a venue that does not
  support this feature, they will be added to the PAX count.
</Info>

***

## Cancellation policies

Restoo’s cancellation policies are designed primarily to reduce no-shows and last-minute cancellations.

### Cancellation policy types

There are two main types of cancellation policies:

* **Guarantee authorization** — The customer provides a credit card to guarantee the booking. Charges apply only in cases of no-shows or cancellations within the penalty period.
* **Prepayment** — The customer pays an amount in advance to confirm the booking. It is deducted from the final bill.