Skip to main content

May 2026 Product Updates

List of updates and bug fixes for May 2026

Written by Kevin Soo

New ✨

  • New Housekeeping β€” now live for everyone: The redesigned housekeeping page is now the default for all customers, and this month we've shipped a few enhancements to it:

    • Modify status on occupied suites: You can now update the status of a suite even while it's occupied.

    • Collapse and ungroup room categories: Collapse room state groups to focus on what matters, or use the new setting to ungroup room categories entirely. Your view preferences are saved per browser.

    • Smarter closure vs departure priority: Rooms with a closure the day after a booking ends now display as departures instead of closures, so the priority is clearer on the grid.

Enhancements πŸ₯³

  • Smarter guest matching by phone number: Returning guests are now also matched by phone number when email isn't available or differs (common for OTA bookings). Matching is format-tolerant β€” 0412 345 678 and +61412345678 are treated as the same number. Surname must also match to confirm a duplicate, and email matches still take priority over phone. Helps reduce duplicate guest records.

  • Webhooks (API): Updated documentation explaining how to use webhook security features, plus webhook registration limits.

Bug fixes 🧰

  • Setup checklist: Fixed broken checkboxes in the setup checklist.

  • Email templates: Fixed an error when duplicating templates.

  • Suites available: Fixed a bug where a room with both a booking and a closure on the same day was only counted as one unit β€” it now correctly counts as two.

  • Guest export: Fixed totals doubling up on the guest export.

  • OTA bookings: Fixed a rare race condition when an OTA booking and a direct booking were created in the same second.

  • Suite closures: Fixed an error when saving closures with certain invalid data.

  • Verification prompts: Fixed an issue where the system would sometimes ask you to verify again unnecessarily, or block an action as unauthorised when it shouldn't.

  • Refunds: Fixed an issue where some refund records stored the wrong transaction reference.

  • Chrome on iOS: Fixed a sign-in security check incorrectly flagging Chrome on iOS.

Did this answer your question?