Data and integrations
Deep read access. A very narrow write.
The platform joins internal hotel data with external market signals, with clear ownership of every source and a written record of every change it publishes.
Hotel Data
- Reservations
- Occupancy
- Inventory
- Cancellations
- Booking pace
- Room types
- Rate plans
- Restrictions
Market Data
- Competitor rates
- Competitor availability
- Events
- Holidays
- School breaks
- Regional demand signals
- Weather where relevant
Platform Data
- Daily snapshots
- Forecasts
- Recommendations
- Manager approvals
- Overrides
- Published rate changes
- Measured outcomes
Misterbooking Integration
Our initial integration is being developed for Misterbooking-based multi-property hotel groups. The planned integration will securely retrieve hotel performance data and support controlled rate and restriction updates, subject to partner approval and available API permissions.
Additional PMS integrations will be introduced based on customer demand.
Integration scope
What the platform reads, and the very short list of what it writes.
A revenue layer needs deep read access and narrow write access. Keeping the write side small is what makes the integration safe to approve.
Read from the PMS
Reservations
The booking curve for every future date is built from creation dates, not just stay dates.
Cancellations and no-shows
Without these the forecast overstates demand on exactly the dates that matter most.
Inventory and availability
Remaining rooms by type set the constraint the optimiser solves against.
Room types
Rates are recommended per room type, and the relationships between them are held consistent.
Rate plans and rate codes
Determines which rate the platform is permitted to move and which it must leave alone.
Existing restrictions
Minimum stay and closed-to-arrival rules already in place are respected, not overwritten.
Write back to the PMS
Rate updates
The core action: a new price for a room type on a date, published after it clears the policy layer.
Restriction updates
Minimum length of stay and arrival rules, where the hotel has enabled them. Optional.
Nothing else
No changes to reservations, guest records, invoices, inventory counts or distribution settings.
Every write is logged with the recommendation that produced it, the person who approved it where approval applied, and the PMS response. Failed updates raise an alert rather than failing silently.
External signals
What is added to the hotel's own data.
Each external source is optional and independently configurable. A property can run on PMS data alone, and the platform will say so rather than implying a fuller picture than it has.
Competitor rates
Published rates and availability across a comp set the hotel defines, drawn from licensed rate-shopping providers rather than collected directly.
Rate by room type and date, availability signals, parity across channels
Events and congresses
Conferences, trade shows, festivals and sporting fixtures within a radius of each property, weighted by expected impact rather than counted equally.
Event dates, venue distance, expected attendance band, category
Calendar signals
Public holidays and regional school-holiday calendars, including zone-based schedules that move leisure demand differently across a country week to week.
Public holidays, school-break zones, bridge days, term dates
Market demand signals
Where a hotel has access to market-level pace or benchmarking data, it is used as an additional input. Where it does not, the forecast runs on the hotel's own history and comp-set signals.
Market pace, occupancy benchmarks, segment mix where available