Improvements
- Booking Search (Arrivals/In Hotel/Departures screens)
- We've improved the main search field: we've increased the interval at which the search automatically starts; at least 3 characters are required for the search; you can now start it with Enter as well; if started, the marker remains in the field, unlike before.
- A new search field has been added for room number. The separate field ensures that you only find bookings in that room and not other matches, such as by booking number.
- A quick button has been added to return to the current date
- In the Mass Functions, under the 'Folios' section, a Multi-Folio view has been added
- WBE (Web Booking Engine) - Price Breakdown on the last page - We often received reports that this breakdown was unclear and mostly led to confusion instead of helping guests. So, we changed the approach. Currently, the guest only sees the final amount of the booking (against each room and in total), as well as a note that the amount includes all taxes and charges. The guest can see the breakdown for each room using an icon next to the room amount. The breakdown has also been changed so that the entire amount for the rate (package) appears against the Rooms line item, and the remaining services remain in Additional services - either selected by the guest or charged by the system, but not through the rate/package - charge templates for room types or surcharges. If this approach is well-received, we will change the confirmation emails in the same way.
- New report - Fire list - The report has been added under 'All Reports' - 'Bookings'. The report has no filters and shows all checked-in bookings with room numbers, floors and guests. There is also a total by floor. It is intended for checking guests against a list if needed. The report has been added to the Bookmark list and can be displayed in the navigation menu;
- Payments with Credit Cards and Voided Folios - In certain very rare situations, it could happen that while the transaction was being processed by the bank, the folio could be voided by the user. This very rare situation led to discrepancies in the log reports. We have improved the logic, and currently, if such a situation occurs, the payment will be added to a newly created folio instead of the voided one.
- We've added categorisation of OOS types - For the moment, this categorisation is not used anywhere by the system, but it will be used in new reports we are working on. You do not need to change the settings at the moment. If you decide to change them, assign one of the three categories for each type: Out of order (unexpected problems), Out of service (intentionally stopped from sale - savings, renovation), House Use.
- Automatic deletion of old To-Do tasks - To prevent the accumulation of unnecessary information that slows down the operational screens, we have added automatic deletion of To-Do tasks older than 1 year. More precisely: If the task has a due date, we keep it for 1 year after that date. If the task does not have a due date, we keep it for 1 year after the date of creation.
- Rate and Availability screen and Contact Person - Bookings can now be created via the Rate and Availability screen with a contact person who does not have an email address entered. This makes it easier to work when you do not have contact information for the guest.
- Room Calendar - three small improvements regarding visualisation
- We have improved the pop-up screen of the booking, which is now much more compact and takes up less space on the screen.
- In the filter screen, we have added an option to stop showing the same pop-up screen if you are performing operations where it interferes.
- The filter screen has also been changed, and with long room type names, the columns do not overlap.
- Issuing key cards - The suggestions for key card validity when there is a room move have been changed. The default value is now the date of the move and the time of arrival.
- Channel manager settings (new screens) - a new field "Guest email is masked" has been added to the Company mapping. For the direct interface with Booking.com, the field is one - in the channel settings. For SynXis - there is no such setting. The new field aims to mark in the Guest Profiles coming from a given channel whether their email is "normal" (personal) or "masked" (official, issued by the channel). This information will be used in the future, such as when merging profiles or in online check-in to request a personal email.
- Booking.com - additional information on stopped products (user/time) is displayed in the maps. This makes it easy to find out when and by whom certain products were stopped without searching for information in the logs. This information will only be visible for those stopped from now on.
- Links to the Company - We have replaced the links to the Company to show the new Company screens
Fixes
- Advanced Booking Search
- A problem related to searching by guest name only with a large database of profiles has been fixed.
- Copying key cards sometimes did not give a message, even though the operation was successful.
- Manual allocation of room number - worked depending on the time zone and sometimes did not function correctly.
- Charge quantities are now rounded to the 3rd decimal place to make the amount calculations more predictable, as well as due to the requirements of various fiscalisations.
- Rates and Availability - When creating a reservation, the guarantee policy set at the rate level was applied, but not if one had been set at the season or day level.
- OTA interface - In certain very rare situations, we were sending updates for yesterday's date, which in turn caused an error on the partner's side.
- POS/PMS closures - Payments - Summary - the breakdown was not displayed if the total payments was 0.
- In the rate editor, rates that are used as base rates but were archived were not displayed with their full name.
Integrations
- Private Analytics / Google BigQuery Export - A new field "person\_title" has been added to the "Guests" table. It contains the title of the guest and complements the existing field "person\_title\_id".
- Clock API - A new endpoint has been introduced – booking\_booking\_charge\_template\_schema. It allows you to read, create, update and delete daily charges for bookings. For more details, please see the API documentation.
- Gastronovi POS Integration - We have updated the integration logic. Disabling the “Transfer Tips” option will now only affect the End of Day revenue transfer. Tips will always be transferred to the corresponding guest, company, or event folios.
- PEPPOL / Billit.be Integration- To improve data accuracy and reduce rounding differences between systems, the export logic has been enhanced. Depending on the account’s tax mode, different values are exported:
- For:
- Tax not included in prices, rounding – per line
- Tax not included in prices, rounding – total
→ NET values are exported, allowing TAX to be added on top.
- For:
- No tax
- Tax included in prices, rounding – per line
- Tax included in prices, rounding – total
→ GROSS values are exported, with VAT calculated from the gross amount.
We recommend using rounding – per line, as it minimises rounding differences most effectively.
To ensure consistency between the Clock document printout and the PEPPOL document layout, we enhanced the logic when Compact mode is enabled. The transferred charges (from Clock POS, LighSpeed POS L series) are compacted based on their source (Bill number), not the print text, even if they have one
- Private Analytics / Google BigQuery Export - A new field person_title has been added to the Guests table. This field contains the guest’s title and complements the existing person_title_id.
- QuickBooks Online Integration - The data exchange logic has been optimised to reduce errors in export logs. If a document or payment fails to export successfully after three attempts, it will no longer be retried. This prevents unnecessary errors and delays.
- Clock API - A new endpoint, booking_booking_charge_template_schema, has been introduced. It allows you to read, create, update, and delete booking Daily Charges. For more details, please refer to the API documentation.