PMS · Properties, rooms and bookings

Your whole property, in one place.

You load the property and the rooms once. Bookings come in through your engine or you enter them yourself, and you run them on the daily board and the calendar. It is a single database: what changes on one screen has already changed on all of them.

01 · Properties

Several properties, one single account.

A hotel in Mendoza and six cabins in Villa La Angostura, under the same login. Each property with its own currency, time zone and team; each person sees only the ones that are theirs.

  • Access by property and by role: whoever runs the front desk at the cabins gets into the cabins, with the front-desk menu; whoever administers sees everything.
  • Workspaces by role — front desk, housekeeping, marketing, revenue — each with its own menu and home screen.
  • Everything else hangs off the property: rooms, bookings, brand, website, LinkHub and reviews load once. Change the phone number and it changes everywhere.
  • The second property copies the first one's structure, and you switch between them with a picker up top, with no logging out and back in.

02 · Rooms

By category or by unit, however you sell.

A hotel sells a superior double and assigns 203 afterward. A complex sells the Alerce cabin, with its photos and its price. Roombir does both, and both at once in the same property.

  • Category pool: the guest buys "a superior double" and the system assigns the room, minimizing gaps or spreading out wear. Or it leaves it unassigned for the front desk to decide.
  • Named unit: the category wraps exactly one unit. The guest books the Alerce cabin, with its photos and its price.
  • Six statuses with history — available, occupied, cleaning, maintenance, blocked and checkout pending —, a board by floor and an occupancy floor plan.
  • Bulk loading in two steps and blocks by half-day, which use the same lock as a booking.

03 · Bookings

Every moment of the shift, its own screen.

Eight views over the same data: moving a booking on the calendar changes the room, frees the night in the engine and shows up in the report.

Daily board

Today's arrivals and departures, with actionable cards. It's the screen the front desk opens the shift with.

All bookings

The list with filters and a side panel that opens without leaving it: summary, activity and notes. From there you assign a room and change the status.

Calendar

Rooms by day. You drag a booking or stretch it, and before you drop it you see if it clashes with another and what happens to the price.

New booking

The one that came in by phone or WhatsApp: guest, dates, occupancy by age, source channel, promotions and notes.

Rates

Base price per category and rate plans with validity dates, currency and minimum stay.

Availability

A traffic light per day — free, partial, full, closed — and restrictions: closed to arrival or departure, minimum and maximum stay.

Promotions

Automatic or with a code, by percentage, fixed amount or price per night, with their presentation ready for your site.

Settings

Currency, confirmation, stay rules, times and how rooms get assigned. Plus the Engine Studio for texts and colors.

Booking engine

8views over the same data to run bookings
10currencies, with blue, MEP, CCL or official for ARS
6room statuses, with history
1lock per unit and night in the database

Three things you will not have to think about

The structural guarantees.

unit + date

A night cannot be sold twice

Every night of every room is a unique lock in the database, not a validation two people booking at once can slip past. Maintenance blocks use the same lock, so they take real inventory out and disappear from the engine.

base · charge · display

The amount charged does not move on you later

Prices live in a base currency, you charge in another, and the guest can look in a third. The conversion stays live until check-in and freezes there. For Argentine pesos you pick which rate to use: blue, MEP, CCL or official.

reservations@roombir.com

You do not configure a mail server

Every guest email — confirmation, token, change notice — leaves from roombir's domain with your inbox as reply-to. It is one of the classic frictions of setting up a PMS and it was removed on purpose.

Frequently asked questions

How do I get paid for bookings?

At check-in, in person. There is no integrated payment gateway yet. What there is is real multi-currency: the guest looks in their currency, you charge in yours and the conversion freezes at check-in.

Does it connect to Booking or Expedia?

Not yet: Roombir has no channel manager. If you sell on OTAs, that availability is reconciled by hand today. The system is built so that the direct booking — your site, your LinkHub, your engine — stops getting lost in a chat.

What happens if two people book the same night at the same time?

One of the two fails. Every night of every unit is a unique lock in the database — the key is the unit plus the date — so the second write does not get in. It is not a validation in the code that can be dodged: it is the database that stops it.

I have cabins and rooms. Can I have both?

Yes, in the same property. Cabins go as named units and rooms as a pool, and they coexist on the same calendar and in the same engine.

Who confirms the booking?

You choose. In one mode the booking is born pending and the guest confirms it with a link that reaches them by email. In the other, it stays pending until the front desk accepts it. Either way, pending bookings expire on their own.

Load the property and the rooms; the engine is ready.

Sign-up is guided and you do it yourself. If you'd rather we walk you through loading the rooms — the step that costs the most — we do it on a short call.

01You create the property and load categories and units.

02You configure the engine in the Studio.

03You share the link and stop losing enquiries in the chat.