Improvements
- Guests / Rooming List Import – AI Assistant. We’ve added a new experimental feature that uses AI to simplify the processing of event rooming lists. Until now, after pasting text from an email or a file from a partner, manual editing was required to meet import requirements—guest names must come first, there must be an “@” for children and their ages, rooms must be separated by a blank line, etc. Now this processing can be performed automaticallyby the new AI assistant:
- Enter the text as usual and click the rightmost button above the field.
- Wait for processing – The AI assistant will convert the text according to the import requirements.
- Review the result carefully. Keep in mind that the AI may make mistakes. At the top, you will see comments and ambiguities that arose during processing.
- You must select the field for the number of guest names (one, two, or three names).
- Continue the process as before.
Currently, this feature is only available during import and cannot be used when updating the rooming list.
- City Tax – varies by Room Type.If your hotel has different Room Types (rooms, apartments, villas) with different City Tax rates, you can now use the new City Tax structure. Instead of a single tax rate, the system now supports multiple rates. Each tax rate is defined in the same way as before, but now has a name for easier identification. When creating more than one tax rate:
- Select which will be the default. It will be used:
- if no specific rate has been selected for a given room type;
- if the calculation is made without a rate (only with a manual price);
- Selecting a default tax is mandatory. If not specified, it will not be included in the calculations. This applies mainly to newly created accounts—no action is required for existing ones.
- For room types with different tax rates, a new field has been added to the room type edit screen where you can select the appropriate rate.
- Select which will be the default. It will be used:
Important: The amount of the City Tax is determined by the room type specified in the rate. If there is no rate in the booking and only a manual price is used, the system will apply the default tax.
- WBE – display of total price for the stay. We have added a new setting in WBE: “Show 'Total Price' instead of 'Average price per night” (in the WBE rates subsection). When enabled, guests will see the total price for the entire stay instead of the average price per night. This display method is preferred by guests, as it gives them a clear idea of the final cost of the booking right from the initial screens—when selecting Room Types and rates.
- Company contracts – deletion option. We have added the ability to delete contracts. A contract can only be deleted if it is not associated with any company.
- Guest Messaging – new Liquid parameter. A new parameter has been added: “Children Ages”.
- Event Document Templates – new Liquid parameter. A new parameter has been added: Event – PAX (offer.event.persons).
- Rate Management / Rates – improvements in Channel Manager – Rates. In the “Channel Manager - Rates” tab, you now have quick access to the rates used in the mapping with Booking.com. Using the Booking.com button, you can open all linked rates to edit or change prices.
Fixes
- Rate and Availability – we improved the creation of bookings with a selected contact person to eliminate errors such as “Attempted to update a stale object…”, which slowed down operations and required a retry.
- Worldline / SIX Payment – we revised the logic for re-redirection from 3DS, where a payment was not reflected in Clock PMS even though it was successful.
- Folio Print – the "Gross" and "Net" columns are now hidden in the "Packaged by Dates / Qty" and "Packaged by Qty" views.
- Events – BEO – we fixed an issue where prices in BEO were empty if the block rate lacked prices for all days of the event.
- Booking charge routing – the Default Company/Agent Folio field did not reflect the manually set default folio in the company/agent.
- Occupancy Forecast – when creating bookings, the default stay set in "Booking fields" was not taken into account.
- Arrivals/Departures Screens – the buttons to navigate to the next/previous date did not function correctly when switching to daylight saving time.
Integrations
- Adyen – upgrade to the Drop-in version and additional improvements.
- OTA interface – Occupancy-based pricing - Guests. We’ve added a new feature to the OTA interface for channel managers – sending prices based on the number of guests in the room (Occupancy Based pricing - Guests). Until now, the interface supported sending a single base price per product (rate). Now you can send different prices depending on occupancy. If the channel supports this feature, it allows you to significantly reduce the volume of mapping and improve synchronization speed. How to use:
- In the rate mapping, leave the “Adults” and “Children” fields blank and use the new “Occupancy-based pricing - Guests” field.
- In this field, enter the number of guests for whom the price should be calculated, separated by commas. For example: 1,2,3 will send three prices to the channel—for 1, 2, and 3 guests per room.
- The price values themselves are determined by the rate —according to its terms and calculation for different occupancy levels:
- if the rate calculates different prices based on the number of guests, different values will be sent
- if the price is the same, the same value will be sent for all occupancy levels
- You cannot use both “Occupancy-based pricing – Guests” and the “Adults” / “Children” fields at the same time – choose one of the two approaches.
- Settings are at the product level – different products can use different methods (Occupancy-based pricing or base price).
- Private Analytics: The daily synchronisation for some data/tables took longer than expected. The synchronization logic has now been optimised to ensure all data and tables are synchronized within 6 hours after the account’s end of day.
- Lightspeed POS K Series: When a bill was transferred to more than one folio, Lightspeed POS K Series generated a “No folio found for sale” error. This issue has now been resolved, and the respective amounts are correctly transferred to each of the selected folios.
- Gastronovi: The End of Day revenue transfer is performed in a designated Clock POS account, isolating the revenue and payments from the hotel’s data. Previously, you had to request the creation of this Clock POS account through our support centre. The process is now automated to speed up operations.