Release notes: Core platform v3.4.3 (24 September 2026)

24 September 2026 (c135bd)

v3.4.3 is a small maintenance release on the v3.4 line. It contains two fixes: one to standard search results in the B2C Booking Portal, and one to amending existing orders in the Reservations Portal. It also withdraws one change introduced in v3.4.2, which locked customer name and email details at checkout for bookings made against a customer account. There are no database migrations in this release.

B2C Booking Portal

Booking and checkout

Hidden products no longer appear in standard search results

Jira: V3-411 | FD: 6107

Issue

Products set up to be sold only through a dedicated bundle link could appear in the standard booking search for the same route and date, after someone had opened that bundle link. Customers could then book these products through the standard booking flow at the wrong price.

Fix

Standard searches now show only products that are available to search. Products sold through a bundle link still appear on their own bundle page and can be booked from there as before.

Testing

1. Open a bundle link for a product that is hidden from standard search, let the page load fully, then close it.

2. Within 30 minutes, open the B2C Booking Portal in a new window and search the same route and date. Only the standard fares are listed; the hidden product does not appear.

3. Repeat step 2 in a private or incognito window. The hidden product still does not appear.

4. Open the bundle link again. The hidden product is shown on its own page, priced correctly, and can be taken through to checkout.

5. From the bundle page, select New Order and search the same route and date. Only the standard fares are listed.

6. Search a date for which no bundle link has been opened. Only the standard fares are listed.

7. Complete a standard booking. It completes at the correct standard price.

Reservations Portal

Orders and amendments

Amending orders no longer fails because of how a stored postcode is formatted

Jira: V3-417

Issue

Some existing orders hold a UK billing address with a postcode stored in a non-standard format, for example older or imported bookings. Since the v3.4 upgrade, amending one of these orders failed with the message "Adding to cart failed", even when nobody had edited the address.

Fix

When checking whether a postcode has changed, the platform now ignores differences in spacing. An unchanged postcode no longer blocks the amendment. A postcode that has actually been edited is still checked against the UK format, as before. This applies to both billing and shipping addresses. Cancellations and addresses outside the UK are not affected.

Testing

New orders cannot be created with the affected postcode format, so the steps below confirm that creating, amending and cancelling orders work as expected.

1. In the Reservations Portal, create a booking with a valid UK billing address and complete it. The order is confirmed and the address is shown correctly.

2. Amend that order, change a passenger count and complete the amendment. The amendment is accepted and confirmed.

3. Amend again and change the billing postcode to an invalid value, such as OXY 5UF, with the country set to United Kingdom. The change is rejected with the UK postcode validation message.

4. Amend again, change the billing postcode to sw1a1aa and complete. The change is accepted and the postcode is stored as SW1A 1AA.

5. Amend an order twice in a row without touching the address. Both amendments go through.

6. Amend an order that has both a billing and a shipping address, without editing either. The amendment goes through.

7. Cancel an order. It cancels without any address error.

Customers and accounts

Withdrawn: lead name and email lock at checkout

Jira: V3-377

Issue

v3.4.2 locked the lead customer's first name, last name and email on the Billing details step of checkout for route-based bookings made against a customer account. This applied to bookings made on behalf of a customer in the Reservations Portal, and to signed-in customers in the B2C Booking Portal.

Fix

This change has been withdrawn in v3.4.3 and will return in a later release. Until then, these fields can be edited on the Billing details step, as they could before v3.4.2. The lock on other checkout types is unchanged.

Testing

Suggested: 1. In the Reservations Portal, start a route-based booking on behalf of a customer account that has a name and email on file, and go to the Billing details step. The first name, last name and email fields can be edited.

Suggested: 2. In the B2C Booking Portal, sign in as a customer, start a route-based booking and go to the Billing details step. The same three fields can be edited.

Suggested: 3. Make a guest booking with no customer account selected. All fields can be edited, as before.