Two calendars in one
By booking date — when they bought — and by stay date — when they sleep. Many systems mix the two and confuse people.
Revenue
It tells you the price and why.
A document per date with the full trace: what data it saw, which rule matched and which cap applied. It looks at your own history and your destination — holidays, events, flight routes, weather — with the source in view. And when you accept, the rate goes into the engine on its own.
Decisions
The answer to "why are you suggesting this?"
There's a document per property and per date with the full trace: what data the system saw, what the base rate was, what it suggested, which rules matched, whether a cap applied, and a log you can read line by line.
- Occupancy, demand, availability, competitor rates, new bookings and events: everything that went into the count, with its value.
- Which rule matched and in what order, because the last one wins.
- Whether the minimum or maximum cap applied, and what it was.
- The recommendation's life cycle: suggested, accepted or rejected, applied, by whom and when.
Your destination
What moves demand, with its source.
Demand signals come from fifteen public sources per destination, swept around your property and not from a fixed list of cities. Events get suggested on their own and you approve them: an approved one doesn't get overwritten by the next update.
- Events in your radius: sports, culture, conferences and fairs, with their expected impact and days remaining.
- Holidays and long weekends, which pricing rules can use as a variable.
- Observed flight routes arriving in your area, and the exchange rate of the markets that visit you.
- Searches with no availability from your own engine: the most underrated demand signal a small property has.
Scenarios
Thirteen variables, and a dry run.
Every rule looks at a variable, compares it against a value inside a lead-time window and applies an adjustment. They're evaluated in order and the last match wins. Before you turn any of them on, the dry run shows you what it would have done.
- Variables: occupancy, demand index, availability, competitor 1 through 5 rate, new bookings in 7 and in 30 days, event impact, days to the nearest event and pace index.
- Comparisons: greater than, greater than or equal, equal, less than or equal, less than.
- Adjustment as a percentage over the base rate.
- Caps for minimum and maximum rate, applied after everything else.
Competitors
A comp set that's mixed and honest.
Competitors who also use roombir contribute their real rate. Outside ones get discovered on their own by proximity and similarity, and you load their rate, as a fixed reference or by date.
- Similarity score by type, category, size, tier and area.
- Your own hotel's profile, taken from the system unless you change it by hand.
- A grid of competitor rates by date.
- Ready for automatic rate providers; not connected today.
The other tabs
Everything there is besides the price.
Pace
Sales pace against your own property's past, by day of week, month and lead time, with fast- or slow-selling alerts.
Events
Suggested on their own and curated by you: suggested, approved or discarded, with a relevance score and expected impact.
Recommendations
Current rate, suggested rate, difference and reason. They get accepted or rejected, and can apply themselves if you turn that on.
Demand signals
Besides bookings, the demand index takes your engine's searches, including the ones that found no availability.
Settings
Competitors, location, hotel profile, pace thresholds, event radius and rate caps.
Frequently asked questions
I don't have much history. Is it still useful to me?
It is, but it will tell you so. Pace is compared against your own history, grouped by day of week, month and lead time, and the screen shows the sample size. If a cell was calculated from three bookings, you'll see it. We'd rather do that than show you a confident-looking curve built on nothing.
Where do competitor rates come from?
From two places. If the competitor also uses roombir, the rate is real. If it's external, the system discovers it on its own by location and similarity, but you load the rate, fixed or by date. The connection to automatic providers is prepared and not yet connected; we won't tell you it is until it's true.
If I accept a recommendation, do I have to copy the price somewhere else?
No. Once you accept it, the rate goes into the booking engine and becomes the first rung of the price for that date. In most systems that step is a person copying a number from one screen to another.
The price stops being a hunch.
Revenue starts being useful as soon as you have history of your own, and while you don't, it says so to your face instead of inventing a curve.
01You load the inventory and base rates.
02You build your comp set and approve the events in your area.
03You write two or three rules and dry-run them.