Release Notes for October 6th, 2026

Modified on Wed, Oct 7 at 6:50 AM

The following improvements and bug fixes have been released. Review the changes below to learn what’s new and what has been resolved.

LA Improvements and Bug Fixes:

New Dispatch - We have addressed an issue when a reservation with a Company Alias assigned (either manually set or tied to the account) is updated from New Dispatch via Quick Edit or Dispatch Notes, the alias is incorrectly removed.
LA NET - When farming out a trip via LA Net, operators previously had a single "Include Notes/Comment when transferring" checkbox that transferred both Trip Notes and Dispatch Notes together. This has been split so operators can choose to transfer Trip Notes without also transferring Dispatch Notes.
LA NET - When farming out a trip via LA Net with the "include notes/comments" option checked, notes/comments from the originator previously landed in the executor's Trip Notes field — and any updates from the originator would overwrite the executor's own trip/dispatch notes. Notes from the originator will now instead be placed in the executor's Partner Notes field, leaving the executor free to add and update their own Trip and Dispatch Notes without risk of them being erased.
LA - Attempting to VOID an invoice after overcharging it, adding trips, and clicking "Recalculate" fails with a database error referencing usp_API_ReservationPayment_GetInvoiceDistributed_v7. This has been fixed.
LA NET - When an originating affiliate updates an existing child seat to a different seat type on a trip farmed out via LA Net, the executing affiliate incorrectly receives an additional child seat rather than having the original one replaced — leaving the outdated seat type still on the trip alongside the new one. After this release, the child seats will update correctly on the executor’s side.
R&A - Dispatch Notes is now available as a selectable field in Reporting and Analytics, allowing users to pull dispatch-level notes alongside trip data in custom reports and exports — without needing to open each reservation individually.
PWA - On the PWA checkout page, if a guest user attempts to register using an email address already tied to an existing account, no error message is shown — the booking silently fails to go through, leaving the user unaware of why. After this release, a clear error message, "Email address already in use," will be displayed in this scenario.
PWA - The PWA now supports booking a Quote when pricing is unavailable or turned off, based on the operator's "If pricing not found/turned off, allow user to submit" setting. If Quote is the only option available, the credit card form no longer loads, and Form of Payment is not required to submit a quote. When a user clicks "Get a Quote," mandatory fields (passenger information) are highlighted if incomplete.

If the operator setting is "Quote and Book," users can choose to book either a Quote or a Trip without a price when pricing isn't available.