Some PMSs are not able to send complete historical data to Atomize, resulting in lack of STLY and LY data the first year after onboarding.
When a new property is onboarded, Atomize will gather as much historical data as possible from the property's PMS account, with the intention to use it as input in the price optimization and for data visualization (comparison of current year's performance to last year's performance).
All PMS vendors are, however not able to send complete historical data, and hence the comparison to same time last year (STLY) and last year (LY) might not be presented. Below, you can study which data is lacking for which PMSs.
Note! For most properties, the historical data is still sufficient to be used in the price optimization. For the ones where it is not (Opera on-premise clients) "priors" are used to simulate historical patterns.
Mews and Nitesoft
Lacking: revenue details of historical cancellations, resulting in inaccurate STLY-data. The issue is not influencing the price optimization.
Final result LY is complete, sent to Atomize, and presented in the dashboard.
Cloudbeds, Protel, Hotsoft, and HotelTime
Lacking: details about when in time a cancellation has taken place, resulting in inaccurate STLY-data. The issue is not influencing the price optimization.
Final result LY is complete, sent to Atomize, and presented in the dashboard.
Opera on-premise (OXI)
Lacking: both STLY data and the final result from last year. Instead, "priors" are produced during onboarding and are used as a replacement for historical data in the price optimization.
Note! After one year using our system, Atomize will have gathered enough data to be able to always present historical data, both for STLY and LY.