Release notes: Core platform v3.4.4 (29 September 2026)
29 September 2026 (0965c93)
v3.4.4 is a small corrective release with a single change to how customer details on an order relate to the customer account linked to it. There are no database migrations and no other changes to day-to-day use.
Reservations Portal
Customers and accounts
Editing customer details on an order no longer changes the linked customer account
Jira: V3-422 | FD: 6128
Issue
When staff changed the lead customer's details on an order in the Reservations Portal, for example correcting the email address, the customer account linked to the order could also be updated, including the email address used to sign in to it. No warning was shown. This could leave a customer account carrying another person's email address and sign-in details.
Fix
Changing the lead customer details on an order now updates the order only. The linked customer account keeps its existing details and sign-in email address, and the order stays linked to its original account. The order does not move to another customer account, or appear in that account's My Bookings in the B2C Booking Portal, because its lead email matches that account. To change a customer account's details, edit the account directly in Customer Accounts. This change does not alter accounts that were updated before this release.
Testing
1. In the Reservations Portal, create an order on behalf of an existing customer account.
2. Open the order and change the lead customer's email address to the email address of a different existing customer account.
3. In Customer Accounts, check that the original account's email address and details are unchanged.
4. Check that the order is still linked to the original account, and that it does not appear in My Bookings for the account matching the new email address.
5. Change the lead customer's email address again, to a third address, and check that the result is the same.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article