> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gridbeds.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Rooms and room types
> Room types, capacity and beds, numbered rooms, their statuses, and how to take a room off sale.
A property sells **room types** ("Standard Double Room"). A room type says how many guests fit, which beds it has and how many rooms of that kind exist. The actual rooms — 101, 102, 103 — are the type's **units**, if you choose to manage them one by one.
Everything happens in **Properties** → the property → the **Room types** tab ("Configure the room types and available units for this property"). To add, change or delete room types and rooms you need permission to manage properties — by default only **Owner** and **Admin** have it; everyone else sees the tab without buttons.
## Add a room type
Click **Add type** (or **Add first type** on a property with no rooms). The **Add room type** form has three steps:
**Name**, **Description** ("Optional - Will be shown on booking website") and **Number of rooms** ("How many rooms of this type exist"). The number of rooms is a whole number, 1 or more: anything else is refused on this step, with "Enter a whole number of rooms, 1 or more." under the field.
**Maximum occupancy** (total people), **Max adults**, **Base occupancy (adults the price covers)** (optional: each adult above it adds the rate plan's extra-adult price — see [Prices by number of guests](/en/rates#prices-by-number-of-guests)), **Max children** (2-12 years) and **Max infants** (0-2 years). Under **Bed configuration**, **Add bed** for each bed: Single bed, Double bed, Queen bed, King bed, Sofa bed, Bunk bed, Murphy bed, Futon or Crib. **Extra bed** allows extra beds, with **No. extra beds** and **Extra bed price**.
**Price per night**, **Currency** (the property's currency), an optional **Size (m²)** and **Active** ("Room type is available for bookings"). Check the **Summary** and click **Create**.
Together with the room type, Gridbeds creates a default rate plan, "\{name} — Standard", at the price you gave. The room type's **Price per night** and that plan's **Base price** are **the same number**: change it in either place and the other follows, and it is the price guests are quoted from then on and the price sent to the connected channels — see [Rates and availability](/en/rates).
Bookings already made keep the price they were sold at. A day that has its own price in the calendar's **Rates** view, or one you fixed, keeps that price too. The room type's other rate plans (non-refundable, with breakfast…) keep their own base prices. If the default rate plan is priced in a different currency from the room type, the save is refused with a message asking you to set the room type's currency to the plan's.
**Extra bed price** is saved but does not go into the price today.
Neither **Max adults** nor **Max children** can be more than **Maximum occupancy**: on **Continue** the Capacity & Beds step says which limit to lower or which to raise, and the room type is not saved until they agree. **Max infants** is not counted in the occupancy, so it can be higher.
### When it cannot be created
A subscription plan limits the total number of rooms (the sum of **Number of rooms** across all room types). Over the limit, creating a type or raising its number of rooms fails. The form shows only "Error creating room type" (or "Error updating…"), without the reason — if you have many rooms, check the limit in [Plans and prices](/en/plans).
## The room type card
Each type is a card: the price per night, how many guests, the beds (or **Not configured**), the number of rooms, the size and any **+1 extra bed**; a type that is switched off shows **Inactive**. The **Edit** and **Photos** buttons, and the ⋮ menu with **Edit**, **Photos**, **Rate plans**, **Packages** (see [Fixed charges, packages and extras](/en/fixed-charges#packages-what-the-rate-includes)), the room management mode and **Delete**.
An **inactive** type no longer shows in availability. **Delete** asks for confirmation ("This action cannot be undone").
### Photos
**Photos** opens **Photos - \{name}**: upload JPEG, PNG or WebP, up to 10 MB each, up to 30 at a time. The first photo is shown first; drag a photo by its handle, or press its ◀ ▶ arrows, to change the order. We recommend at least 5 photos. A photo that is too small is flagged: "… is smaller than channels accept — it will not reach Booking.com or the other OTAs."
#### Order, cover and alt text
The property's own **Photo gallery** works the same way: the first photo is the cover (**Cover**), and **Make … the cover** moves a photo to the front. The whole order is saved at once; if it cannot be saved, the photos go back where they were. With the keyboard, press Space or Enter on a photo's handle, move it with the arrow keys and press Space or Enter again (Escape cancels); a screen reader hears where it went.
The pencil on a photo opens **Alt text and caption**: the alt text (up to 125 characters) tells someone who cannot see the photo what it shows; the caption describes the photo. For a property on [Channels](/en/channels), the new order reaches the channels within a minute, cover first. Booking.com may still reorder photos while Smart ordering is on in its extranet.
## Simple or room-by-room management
The room type's ⋮ menu switches between two modes:
| Mode | What it means |
| - | - |
| **Simple management** — "Without individual rooms (101, 102...)" | You sell a number of identical rooms. A booking does not get a particular room. |
| **Room-by-room management** — "Enable rooms: 101, 102, 103..." | Every room has its own name, shows on the housekeeping board and can be assigned to a booking. |
When you switch room-by-room on, Gridbeds creates one unit for each room in **Number of rooms**, named "\{type} - 01", "\{type} - 02" and so on. If you then raise **Number of rooms**, the missing units are added; if you lower it, the last units with no current or future stay are removed.
For single-unit properties (apartment, house, villa and so on), a type with a single room is set to room-by-room automatically, with the unit named after the type. In a guesthouse or a hotel, a new room type starts in **Room-by-room management**, with one unit per room; switch it to **Simple management** if you sell it as a pool. See [Property types](/en/getting-started/property-types).
Going back to **Simple management** is not possible while the rooms have active bookings; the window then shows "Error updating settings". When it works, the units are removed and the type's bookings are left without an assigned room.
## The rooms (units)
In room-by-room mode the card has **\{n} rooms**, which opens the list. **Add** (or **Add first unit**) asks for:
* **Name** — for example 101 or Room A; unique within the room type;
* **Internal code** — for example A-101;
* **Location** — free text, for example "Floor 1, Building A";
* **Notes**.
Only people allowed to manage properties can change the name and the internal code; others can change the location and the notes.
**Rename** names every room at once: a **Pattern** with \{n} for the number (for example "Room \{n}", numbered 01, 02…), **Start from**, **Preview**, then **Apply**.
A room with a current or future stay cannot be deleted: move the stay to another room first.
The **floor** is set in the housekeeping setup (**Dashboard → Housekeeping → Setup**, **Sections and rooms**: tick the rooms and put them on a floor or in a section), not here — see [Housekeeping](/en/housekeeping#setup).
### A room's status
From a room's ⋮ menu you choose:
| Status | What it does |
| - | - |
| **Available** | Sold as normal. |
| **Maintenance** | Not sold and gets no cleaning jobs. |
| **Blocked** | Not sold. |
| **Retired** | Out of use for good; not sold and gets no cleaning jobs. |
Only **Available** rooms count in availability: a room taken out lowers the type's sellable rooms by one. A booking cannot be put in such a room ("Unit is under maintenance and cannot be booked."). The status has no end date: you set it back to **Available** yourself.
This is not the cleaning status (Dirty, Cleaning, Clean, Inspected), which changes on the [Housekeeping](/en/housekeeping) board.
From the [staff app](/en/mobile), a high-severity **Report a problem** has the switch **Take the room out of order** ("It is not sold until it is available again."): the room goes to maintenance and a maintenance task is created. Setting it back to **Available** is done on the web only.
## Blocking dates
In the top bar, the arrow next to **New booking** → **Block dates** (or Ctrl/⌘+B in the calendar) opens **Block period**: the property, the dates, a **Reason** (Maintenance, Personal use, Owner use, Renovation or Other) and notes. **Sync with distribution channels** closes the period on Booking.com, Airbnb and the other channels too; it is off by default. A block is lifted from the calendar, by clicking the blocked day. You need permission to manage bookings.
**Coming soon:** a block closes **the whole property**. To take a single room off sale for a few days, set it to **Maintenance** or **Blocked** and set it back to **Available** afterwards.
## What reaches the channels
If the property is connected to [Channels](/en/channels), a new room type and changes to its name, description, number of rooms and capacity are sent to Channex on their own, and so are its photos and their order. Deleting a type deactivates it on the channel. Each OTA's rooms are mapped to yours in the Channex configurator (**Map channels**).
## What you cannot set yet
**Coming soon:**
* a room type's **amenities** — meanwhile, the property's amenities are added on the **Details** tab, under **Amenities** → **Add amenities**, and whatever a room type has on top goes in its **Description**;
* the order of room types and rooms in the lists;
* a different capacity or beds for a single room of a type — if one room differs, give it a room type of its own.
## The property's restaurants
The property's **Restaurants** tab (with the Restaurants module in your plan) lists the restaurants that belong to it and, for members with **Restaurants** — **Manage**, links and unlinks them — see [The restaurant and its property](/en/restaurants#the-restaurant-and-its-property).
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.