Skip to content
English
Suggest a New Article Customer portal Sign in
  • There are no suggestions because the search field is empty.

30 July 2026_Release Note

We are delighted to share with you our release notes including improvements

🚀 What's New This Release

  • ⚡ Klook: Handled bookings with missing "payments" field
  • ⚡ PMS API: "On Request" bookings are no longer notified to PMS until confirmed
  • ⚡ Surcharge Display: Implemented several updates to resolve unclear surcharge information and incorrect surcharge amounts in payment requests
  • ⚡ Booking Cancellation Email: "Refundable Amount" field is now hidden when the refundable amount is zero
  • ⚡ Create Booking: Fixed an issue where saving a booking was not possible when replicating multiple booking items before saving

💡 Click on each function for more details

Improvement ⚡ Klook
Handle bookings with missing "payments" field
  • Current situation: Bookings from Klook are processed as fully OTA-handled, with the payment method determined as follows:
    • If card information is present → Klook Handles the Payment (With Virtual Card Info)
    • If card information is not present → Klook Handles the Payment
    However, cases where Klook does not send the payments field at all were not handled, leading to incorrect payment method assignment.
  • Solution: We've improved the handling logic so that when Klook does not send the payments field in the booking payload, the system now treats it the same as the "no card information" case and sets the payment method to Klook Handles the Payment.
Improvement ⚡ PMS API
Do Not Notify "On Request" Bookings to PMS Until Confirmed
  • Current situation: The system was sending notifications for "On Request" bookings to the PMS. When the partner called the API to retrieve the booking details, the system returned empty data because the booking had not yet been confirmed, causing confusion for the partner.
  • Solution: We've updated the workflow so that "On Request" bookings are no longer sent to the PMS. The system will now notify the partner only after the booking has been confirmed.
Improvement ⚡ Surcharge Display
Implemented several updates to improve surcharge display and payment accuracy
  • Current situation: Surcharge information was displayed unclearly, and incorrect surcharge amounts were being sent when processing payment requests.
  • Solution: We've implemented several updates to resolve unclear surcharge information and incorrect surcharge amounts, ensuring surcharge details are displayed accurately and payment requests reflect the correct amounts. To learn more about these updates, read this article.
Improvement ⚡ Booking Cancellation Email
Hide "Refundable Amount" field when the refundable amount is zero
  • Current situation: The cancellation email always displayed the "Refundable Amount" field, even when the cancellation policy applied a full charge (100% penalty), resulting in a misleading zero value being shown to guests.
  • Solution: The "Refundable Amount" field will now only appear in the cancellation email when the refundable amount is greater than zero. When the refundable amount is zero, the field will be hidden.
Improvement ⚡ Create Booking
Cannot save booking when replicating booking items
  • Current situation: When creating a booking, if a user added the first booking item and then replicated it multiple times without saving in between, the system did not allow the booking to be saved.
  • Solution: We've updated the logic so that bookings with multiple replicated items can now be saved correctly without requiring intermediate saves.