> 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/how-do-i-set-up-a-room-rate-code.md).
# How do I set up a Room Rate Code?
To set up a Room Rate Code, follow these steps:
1. **Navigate to the Menu:** Go to **Front Office >> Masters >> Rate >> Room Rate Code** and select New.
2. **Add New Code:** Click the Add button to begin creating a new entry.
3. **Define Core Details**: Enter the Rate Code Id, Rate Code Name, and specify the Nature of the rate.
4. **Configure Dependencies:** Click on Master Rate of Dependent to define how this rate might interact with or depend on other rates.
5. **Set Weekend Parameters:** Use the provided screen to update the Week End Days applicable to this Room Rate code.
6. **Finalize:** Click the Save button to successfully update and store the new rate code.
Once these codes are established, they can be utilized in several ways across the system:
* **Company Rates:** You can link a specific Rate Code to a company profile to provide fixed corporate pricing.
* **Daily Rates:** Rate codes are selected when defining or viewing daily rates in the Bar calendar.
* **Derived Rates:** You can use an existing rate code as a base for Derived Rate Codes, which automatically calculate new prices based on stay duration or market segments.
* **Analysis:** The system uses these codes to generate Rate Code Analysis reports, helping you track revenue contribution and room nights by rate category.
---
# 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/how-do-i-set-up-a-room-rate-code.md?ask=&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.
