Run the day
Room types, and the actual rooms
Two Sea View doubles is a type. 204 and 205 are rooms. Most software only models the first.
Availability at the type level is fine until you have two of something. Then a guest asks for the quiet one, or the one with the new aircon, or the one they stayed in last time — and the software has no way to answer, because as far as it knows you have “two doubles”.
The workaround is a note in a booking and a person who remembers. It survives until that person is off.
Rooms & unit inventory is one of the modules included in the MangoHost platform — every plan has all of them, so nothing on this page is an upsell.
The workflow
How it works
The type holds the price and the pitch
A room type carries its name, capacity, bed configuration, size, features and photos. It is what you sell and what you price — a base rate and its seasonal overrides live here.
The units underneath are the real rooms
Each type owns the individual rooms inside it, labelled the way your building is: 204, 205, Casita 3. A booking can be assigned to a specific one, or left unassigned until the morning of arrival.
Housekeeping works at this level too, because a room board that says “one of your two doubles is dirty” is not a room board.
Retire a room without losing its past
A unit can be made inactive — taken out of sellable inventory and out of the type's count — while every booking that ever touched it stays intact. That is what you want when a room is being renovated, and what you need when you look at last year.
Photos and features live on the type
Bed configuration, size, capacity, the feature list and the photo gallery all sit on the room type, because that is what a guest is choosing between. Change them once and every unit underneath inherits it.
The same content is what publishes to a connected marketplace, so the description you write for your own records is the description a traveller reads.
Every operation is checked against your hotel
Rooms and units are the most-referenced objects in the system — a booking, a housekeeping card, a work order and a rate all point at one. So every operation that touches them verifies the room belongs to the hotel making the request, rather than trusting the id that arrived.
In a multi-property account that is the difference between a switcher and a leak.
Room count is what occupancy divides by
Your active room count is the denominator for occupancy and for RevPAR. That is why retiring a unit takes it out of the count rather than deleting it: a room under renovation should not drag your occupancy down, and last year's numbers should not change because of it.
It is a small piece of modelling that decides whether a whole page of analytics is trustworthy.
In detail
| Room types | Name, capacity, beds, size, features and photos. |
|---|---|
| Units within a type | The individual rooms, labelled and ordered. |
| Unit-level assignment | Put a guest in a specific room, or leave it for later. |
| Inactive units | Removed from inventory; history preserved. |
| Ownership guards | Every room and unit operation is checked against the hotel making the request. |
| Feeds occupancy | Room count drives occupancy, ADR and RevPAR. |
Who this is for
You have more than one of any room type
That is the point at which type-level availability starts telling you things that are not true.
Guests ask for a specific room
Returning guests do this constantly, and it is one of the cheapest ways to be remembered.
See it on your own property
Thirty minutes with the IslandLink team, your rooms and your rates. No card, nothing to sign.