Dual-axis analytics
Creation axis — when it was booked — with direct and OTA revenue, cancellations, lead time, searches and pickup. Stay axis — when it is slept — with occupancy, ADR, RevPAR and revenue. Many systems mix the two and confuse people.
Revenue · RMS
A suggested price you can audit.
Eight revenue-management tabs embedded in the desktop: dual-axis analytics, pace against your own history, comp set, demand events, a rules engine with a dry run, and a decision document per date that explains every number.
Superior Double · suggested rate
$84.000$96.600+15%
occupancy78% · rule threshold 70%
pace+18% vs. your own history (Sat · March · 15-30 days)
eventVendimia Festival · in 3 days · impact 72
comp setcomp-set median $101,400 · 4 of 5 loaded
ruleHigh occupancy + event → +15% adjustment
capmaximum $120,000 · not applied
Accept and push to the engineReject
Decisions
The answer to “why are you suggesting this?”
There is a document per property and per date with the full trace: what inputs the engine saw, what the base rate was, what it suggested, which rules matched, whether a cap applied, and a readable log line by line.
- Occupancy, demand index, availability, competitor rates, pickup and events: everything that went into the sum, 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 lifecycle: suggested, accepted or rejected, applied, by whom and when.
Superior Double · suggested rate
$84.000$96.600+15%
occupancy78% · rule threshold 70%
pace+18% vs. your own history (Sat · March · 15-30 days)
eventVendimia Festival · in 3 days · impact 72
comp setcomp-set median $101,400 · 4 of 5 loaded
ruleHigh occupancy + event → +15% adjustment
capmaximum $120,000 · not applied
Accept and push to the engineReject
Scenarios
Thirteen variables, and a dry run.
Each rule evaluates a variable against a reference, inside a lead-time window, and applies an action. They run in order and the last match wins. Before turning any of them on, the dry run shows you what it would have done.
- Variables: occupancy, demand index, availability, competitor 1 to 5 rate, pickup 7d, pickup 30d, event impact, days to the nearest event and pace index.
- Operators: greater, greater or equal, equal, less or equal, less.
- Actions: percentage adjustment over the base, or a rate plan change.
- Caps for minimum and maximum rate, applied after everything else.
01occupancy ≥ 70% · window 0-14 days+8%
02event impact ≥ 60 · window 0-7 days+15%
03pickup 7d ≤ 2 · window 0-21 days−10%
04competitor 1 rate ≤ base · window 0-30 daysplan B
They run in order and the last match wins. The dry run shows what each one would do before you turn it on.
Competitors
A comp set that is mixed and honest.
Competitors that also use bookfer contribute a real rate. External ones are discovered on their own by proximity and similarity score, and you load their rate — as a fixed reference or by date, which takes priority.
- Similarity score by type, category, size, tier and area.
- Your own hotel profile, synced from the PMS unless you override it by hand.
- A grid of competitor rates by date.
- Ready for Lighthouse, RateGain, PriceLabs and KeyData; not connected today.
Hotel del Parque · youown$96.600
Posada del Lagobookfer$104.200
Hostería Los Álamosmanual$101.400
Cabañas Ruca Huemanual$88.000
Apart Cordillerano data—
Automatic discovery by proximity and similarity. External rates are entered by hand: we do not invent a number we do not have.
The other tabs
Everything there is besides the price.
Pace
Sales pace against your own property's historical behaviour, split by weekday, month and lead-time bucket. With a curve, pickup and fast- or slow-selling alerts with configurable thresholds.
Events
Holidays, fairs, concerts and sports, ingested automatically and curated by you: suggested, approved or discarded. An approved event is not overwritten by re-ingestion. With a relevance score and expected impact.
Recommendations
Current rate, suggested rate, delta and reason. Full lifecycle: suggested, accepted or rejected, applied, expired or replaced, with owner and date.
Demand signals
Besides bookings, the demand index takes the engine's searches, including the ones that found no availability — the most underrated signal a small property has.
Settings
Comp set, location synced from the PMS with a manual override, hotel profile, pace thresholds, event radius and horizon, and rate caps.
Frequently asked questions
I have little history. Is the RMS still useful?
It is, but it will tell you. The pace benchmark is built from your own history, grouped by weekday, month and lead-time bucket, and the interface exposes the sample size. If a cell was computed from three bookings, you will see it. We prefer that to showing you a confident curve built on nothing.
Where do competitor rates come from?
Two places. If the competitor also uses bookfer, the rate is real. If it is external, the system discovers it on its own by geolocation and similarity score — type, category, size, tier, area — but you load the rate, as a fixed reference or by date. The connection to automatic providers is prepared and not yet connected; we are not going to say otherwise until it is.
If I accept a recommendation, do I have to copy the price somewhere else?
No. On acceptance, the recommendation pushes a rate override into the booking engine, which becomes step 0 of the price chain. The loop closes inside the system. In most stacks that step is a person copying a number from one screen to another.
Is it included or does it cost extra?
It depends on the plan. In the large systems the RMS is almost always an add-on quoted separately; here it is one more product in the catalogue. Look at the plans to see which one it is in.
Price stops being a hunch.
The RMS starts being useful as soon as you have history of your own, and while you do not, it says so to your face instead of inventing a curve.
01You load inventory and base rates.
02You build the comp set and approve the events in your area.
03You write two or three rules and dry-run them.