Currently in Pricelabs, if an OR client limits their calendar availability to 365 days using ownerrez settings, the Pricelabs calendar will incorrectly display that property's availability - extending for two years or more. We are told by OR tech support that the reason this inaccurate view of availability is happening in the Pricelabs calendar is because the API data point that sends calendar availability data to Pricelabs is not readable by Pricelabs. The API data that OwnerRez shares with Pricelabs shows blocked or booked dates, but not the timeframe reflecting calendar availability - these are different things. OwnerRez settings are are still correctly limiting calendar availability on public-facing booking platforms. It is just affecting the view of availability that we see when we are in the Pricelabs calendar view.
The reason correct availability views in PL matters is that we as revenue managers support 500+ clients in PL and every week we are helping clients with issues that can affect their revenue. Sometimes we see clients in PL who accidentally have their calendars open too far forward, which will sometimes result in people getting bookings they don’t want well-past the 1 year mark. We let them know when we notice issues like that so they can correct potential problems in their PMS software settings.
PL availability displays are correct for every other PMS linked to PL except for OR (we manage hundreds of accounts and haven’t seen this issue with any other linked PMS in PL). It makes it harder for us to confidently diagnose real calendar-availability problems vs seeing incorrect data in PL for OR-linked clients.
OR should fix/create the API endpoint to correctly send availability data that PL can see and represent on their calendar accurately.
