Short-stay hosts managing 20 or so listings often update prices by hand across Airbnb and Booking.com, usually late and usually flat. A nightly pricing engine reads occupancy, events and seasonality, then pushes fresh rates and minimum stays to every platform automatically.
Typical results
81%
Occupancy, up from 71%
40
Calendars synced nightly
5.5 hrs/wk
Pricing work saved
Figures reflect typical results for this kind of automation.
The challenge
Twenty listings times two platforms times 365 nights is too many prices for one person. Rates got set once a season and forgotten: festival weekends sold out months early at everyday prices, while orphan midweek nights sat empty at rates nobody would pay. Every manual sweep took an evening, so the calendar was permanently out of date.
Before and after
RevPAR
+22%Occupancy
+14%Pricing work
−92%The automation
We built a pricing rule engine on Make that runs every night. It pulls each listing's occupancy, scans local event calendars, and applies seasonality curves, then computes a rate and minimum stay for every date — discounting gap nights, raising event weekends. Floor and ceiling prices per listing keep results sane. Updates push to Airbnb and Booking.com before midnight, and every Monday the host gets a digest showing pickup, RevPAR, and which rules fired.
How it works
- 01
Signals collected
Every night the engine pulls each listing's occupancy, local event calendars, and seasonality curves.
- 02
Rules applied
A rate and minimum stay are computed for every date — gap nights discounted, event weekends raised.
- 03
Guardrails checked
Floor and ceiling prices per listing keep results sane; anomalies are flagged instead of published.
- 04
Pushed everywhere
Updated rates and minimum stays sync to Airbnb and Booking.com before midnight.
- 05
Weekly digest
Every Monday the host gets a summary of pickup, RevPAR, and which pricing rules fired.
Starts from
- Occupancy & seasonality
- Local events feed
Delivers
- Rates to Airbnb & Booking
- Minimum-stay rules per date
- Weekly performance digest
The impact
RevPAR can climb around 22 percent in a season with the same 20 listings. Occupancy typically rises from about 71 to 81 percent as gap nights fill, event weekends stop underselling, and price editing drops from six hours a week to a half-hour review of the Monday digest.
Questions about this automation
What data does the nightly pricing run use?
For each listing, it pulls current occupancy for the dates ahead, a local events feed and seasonality curves the host sets. Rules then compute a rate and a minimum stay for every date, for example discounting single gap nights and raising prices on event weekends, before anything is published.
How does the engine avoid publishing a bad price?
Every listing has a floor and a ceiling price. A computed rate outside those limits, or a sudden jump compared with the previous night's run, is held and flagged for the host instead of being published. Only rates that pass the guardrails sync to Airbnb and Booking.com before midnight.
How does the host see what the engine changed?
Every Monday the host receives a digest with booking pickup, revenue per available night and a list of the pricing rules that fired during the week. The rules sit in a simple table the host can edit. This is a multi-step build, usually rolled out in stages, with rules tested on a few listings first.