The three properties
All three are independent, owner-operated, and were fully live on Profitroom Suite at least 18 months before we started. None had prior third-party rate automation running against Profitroom. Rooms sold were pulled through the Profitroom Reservations API weekly; RevPAR is calculated on sold room revenue divided by available rooms, matching Profitroom's own definition inside the Distribution reports.
- Hotel Marszałkowska Grand — Warsaw center, 48 rooms, boutique four-star.
- Kazimierz Boutique Resort — Kraków Old Town, 86 rooms, upper mid-market.
- Motława Aparthotel — Gdańsk, 124 apartment units, aparthotel positioning.
Before / after RevPAR
The baseline window is January–February 2026 (running under the hotel's existing manual rate calendars). The measured window is April–May 2026, six weeks after each module went live. Both windows are shoulder season in Poland — we deliberately picked periods where market-wide occupancy tailwinds were small.
| Property | Baseline RevPAR (EUR) | Measured RevPAR (EUR) | Change |
|---|---|---|---|
| Marszałkowska Grand (Warsaw) | 71.40 | 79.28 | +11.0% |
| Kazimierz Boutique Resort (Kraków) | 84.10 | 90.83 | +8.0% |
| Motława Aparthotel (Gdańsk) | 52.60 | 60.00 | +14.1% |
What Autopricer actually did
Autopricer reads pace, pickup and remaining inventory out of the Profitroom Booking Engine and Reservations endpoints every 30 minutes. It compares your live pickup curve to a rolling 90-day baseline and proposes rate changes — never applies them silently. Each proposal goes into a queue you approve by tapping through, or you can enable auto-apply for specific room types.
At Marszałkowska Grand the rule set was: if pickup 14 days out is more than 20% behind baseline, drop BAR by up to 8%; if pickup 7 days out is more than 15% ahead, raise BAR by up to 12%. Over 8 weeks the module fired 341 rate suggestions, of which 289 were approved by the revenue manager. The +11.0% RevPAR lift came almost entirely from the "raise on strong pickup" half of the rule.
Analytics Dashboard: the channel-mix moment
The Analytics module doesn't move rates; it just reads what Profitroom Channel Manager and the booking engine already track, and stitches it together with realised revenue from the Reservations feed. At Kazimierz Boutique Resort the dashboard made one thing painfully clear: 34% of the direct-website revenue was actually paid-social traffic being logged as direct because of a misconfigured referrer. Fixing the referrer split, then repointing the paid budget accordingly, drove +2.1 percentage points of the total +8.0% uplift.
Google Hotels Booking Sync: 3-month channel ramp
At Motława Aparthotel the third module was the Google Hotels Booking Sync add-on, which pushes availability and rates directly into Google Hotels via the Meta Booking Link programme without going through an OTA. Google Hotels went from 0% of bookings in February to 8.4% of bookings in May, making it the property's #4 channel behind Booking.com, the direct site, and Expedia. The channel is native-Profitroom-integrated, so cancellations feed back into the Reservations API on the same clock as any other channel.
What didn't work
Two experiments failed cleanly enough to be worth documenting. First, we tried an aggressive "min-stay 3" rule at Kazimierz Boutique Resort over Easter — pickup dropped fast enough that we rolled it back inside a week. Second, we tried using Autopricer to blanket-raise weekend BAR at Motława Aparthotel by 6% for two consecutive weekends; occupancy fell 9 points and blended RevPAR was flat. The rule set now requires a pace-based trigger for any upward move.
What we'd do differently at a fourth property
Start Analytics before Autopricer. In two of the three deployments the biggest single insight was in the channel-mix cleanup that Analytics surfaced — and if Autopricer had been reacting to messy channel data during the first two weeks, its own rule tuning would have been slower to converge. If you're evaluating our modules for your own Profitroom Suite account, we usually onboard Analytics in week one and add pricing automation in week three.