> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/front-office-module/fo-masters/faq-on-masters/what-are-the-rules-for-overbooking-percentages.md).

# What are the rules for overbooking percentages

**What are the rules for overbooking percentages?**

To configure **overbooking percentages**, you must set the rules in the **Room Type Master** under the **Front Office** module.

The configuration rules are as follows:

#### **1. Enable Overbooking**

* For each room category where overbooking is permitted, enable the **Overbooking** option.

#### **2. Enter the Overbooking Percentage**

* After enabling the feature, specify the **overbooking percentage** allowed for that room type.
* This determines how many additional reservations can be accepted beyond the available physical rooms for that category.

#### **3. Select the Overbooking Parameter**

* Choose the appropriate **system parameter** that defines how the system applies and manages the configured overbooking limits.

#### **4. Define Occupancy Limits**

Overbooking rules work alongside other room type settings, including:

* **Maximum number of adults** allowed.
* **Maximum number of children** allowed.
* **Maximum occupancy** (total persons permitted) for the room type.

Configuring these settings ensures that overbooking is managed according to the property's operational policies while maintaining room occupancy limits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rbsgo.com/front-office-module/fo-masters/faq-on-masters/what-are-the-rules-for-overbooking-percentages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.