Release Notes – v3.4.6-rc1

30 September 2026 (987dfde)

This is a release candidate; content may change before the final release. v3.4.6 builds on v3.4.5 and concentrates on pay by email: payment links now stay valid when staff clear the basket, missing customer contact details are caught before a request is sent, customers opening a link that is no longer valid are told what to do, and the checkout and confirmation pages keep the branding of the market the order was made in. It also stops session searches failing when a ticket type is not covered by a session's capacity, releases held capacity when a basket is cleared, and adds an API option to remove a customer account from an order.

Changes

Clearing the basket now releases held capacity

Jira: V3-384

Issue

When a basket was cleared, the market was changed, or a bundle or location selection was reset, the items in the basket could stay reserved until the basket's hold expired. Other bookings could then see an add-on as sold out even though it was no longer in anyone's basket.

Fix

Clearing the basket, changing market, or clearing a bundle or location selection now releases the capacity that basket was holding, rather than leaving it reserved until the hold expires. This also applies when the basket is cleared after a price update has failed. The change applies to both the B2C Booking Portal and the Reservations Portal.

Testing

Suggested: 1. In the B2C Booking Portal, start a booking and add an add-on with limited capacity, up to the remaining capacity.

Suggested: 2. Clear the basket using Clear All.

Suggested: 3. In a second browser, start a booking for the same date and time and go to the add-ons.

Suggested: 4. The capacity released in step 2 is available to add, and the add-on is not shown as sold out.

Pay-by-email checkout keeps the branding of the order's market

Jira: V3-353

Issue

For venues with more than one market, opening a pay-by-email link could show the branding (logo, colours and buttons) of a different market from the one the order was made in. The page could show the correct branding at first and then switch once the order had loaded.

Fix

On the pay-by-email checkout page and the manage order page, the branding now follows the market the order belongs to, and a different market in the web address no longer overrides it. On all other pages, including booking links that specify a market, the market in the web address still sets the branding as before.

Testing

1. In the Reservations Portal, create a new order in a market other than your default market, for a future date.

2. Choose Pay via email link and send it.

3. Open the Complete Payment link from the email in a private browser window and wait for the order to load.

4. The page shows the logo, colours and Continue to payment button of the order's market, and they stay that way.

5. Change the market in the web address to a different market and reload the page.

6. Once the order has loaded, the page shows the order's market branding. A brief flash of the other branding while the page loads is expected.

Pay-by-email links stay valid after the basket is cleared

Jira: V3-423

Issue

If staff sent a pay-by-email request and then cleared the basket, or removed its items, in the Reservations Portal, the order was abandoned. When the customer opened their payment link, they saw "Unable to retrieve your order, please try and make your booking again".

Fix

Clearing the basket, or removing its items one by one, no longer cancels an order that is awaiting payment by email. The order stays as Awaiting payment, and the customer can open the link in the B2C Booking Portal and pay. Discarding the order from More Actions still cancels it and invalidates the link, as intended. Clearing a basket that has not been sent for payment by email still releases its capacity as before.

Testing

1. In the Reservations Portal, create an order, go to checkout, choose payment Via Email and send the email.

2. The confirmation "Payment request sent via email" shows, and the order appears in Orders as Awaiting payment.

3. Open the draft order, choose Edit Order, then Checkout, then click the logo at the top left and choose New Order. The basket shows the items from the sent order.

4. Click Clear All. The basket empties, and in Orders the order still shows as Awaiting payment, not Abandoned.

5. Open the "Complete your payment" email and click the payment link. Checkout opens at Contact Details with no error.

6. In Orders, open the draft order and choose More Actions, then Discard order. The order becomes Abandoned and the payment link now shows that it is no longer valid.

Session search no longer fails when a ticket type is not covered by a session's capacity

Jira: CORE-9127

Issue

When a product had a ticket type whose capacity type was not covered by a session's capacity plan, searching for that product's sessions failed. Staff could see an error or an empty list of sessions, and no sessions were returned for the product at all.

Fix

The search no longer fails. Sessions are listed as normal, and a ticket type that a session does not cover is left out of that session's capacity. If a quantity of an uncovered ticket type is selected, the session is shown as unavailable rather than causing an error. Browsing sessions without selecting that ticket type is not affected. The change is in the shared session search, so it applies to POS, the Reservations Portal and the B2C Booking Portal.

Testing

1. Use a product with a ticket type that is only covered on special sessions (for example an overflow ticket type), so that normal sessions do not cover it.

2. In POS, open the product and pick a date this week. The sessions list shows with availability and no error.

3. In the Reservations Portal, pick a normal session and add one standard ticket. The session is available and the ticket adds to the basket.

4. In the Reservations Portal, select one of the special-session ticket type plus one standard ticket on a normal session. The session shows as unavailable, with no error.

5. Book a normal session end to end, and check that sessions and availability for other products look unchanged.

Pay by email or SMS now checks the customer's contact details

Jira: V3-432

Issue

When booking on behalf of a trade partner in the Reservations Portal, the customer's contact details could be lost if the contact step was skipped. Staff could then send a pay-by-email request with no customer email address. The confirmation said the request had been sent, but no email went out and Re-send Payment Email was not available on the order.

Fix

The trade partner's contact details are now saved to the order when the contact step is skipped, so the payment email is sent and Re-send Payment Email is available.

If the customer has no email address (or no telephone number, for pay by SMS), the request is refused with the message "A customer email address is required to send a payment link" or its SMS equivalent, and staff are taken back to the contact details step where it is available.

Customers who open a payment link that is no longer valid, for example because the order was discarded, now see "This payment link is no longer valid" with advice to contact the venue for a new one, instead of being asked to make their booking again.

When booking on behalf of a trade partner, checkout now uses the trade partner's address where one is held.

Testing

1. In the Reservations Portal, choose Place Order On Behalf, select a trade partner and a person, add a product to the basket and go to checkout.

2. Fill in Booking Details, continue to payment, choose Via Email and send the email.

3. The email is received, and the order shows the lead customer and a Re-send Payment Email option.

4. Discard the order (Orders, More Actions, Discard order) and open its payment link.

5. The page shows "This payment link is no longer valid", with no Start again button.

Pay-by-email confirmation page keeps the order's market branding

Jira: V3-437

Issue

After a customer paid through a pay-by-email link, the confirmation page could switch to the branding of a different market from the one the order was made in.

Fix

The checkout now always applies the branding of the order's market, including on the confirmation page after payment and when the customer returns from a hosted payment page. This extends the pay-by-email branding change above to the confirmation step.

Testing

1. Create an order with pay by email in a market other than your default market, and check that the checkout shows that market's logo.

2. Complete the payment from the email link. The confirmation page shows the order's market logo.

3. Refresh the confirmation page. The correct logo still shows.

New API option to remove a customer account from an order

Jira: PROD-18

Need

Staff could move an order to a different customer account through the API, but could not remove an order from a customer account altogether.

Change

A new API option removes the customer account from an order, leaving it as a guest order. The order's items and the staff member who sold it are unchanged, and the usual order updated webhook is sent. It uses the same permission as moving an order to another customer account. It cannot be used on draft orders, orders not linked to a customer account, or orders that contain a membership. There is no change to any screen.

Testing

Suggested: 1. Using an API user with permission to change an order's customer account, remove the customer account from a completed order that has no membership items.

Suggested: 2. The order is returned without a customer account, and its items are unchanged.

Suggested: 3. Try the same on an order containing a membership. The request is refused.

Release Notes – v3.4.6-rc2

1 October 2026 (4bb3fdc)

This is a release candidate; content may change before the final release. v3.4.6 is a patch release built on v3.4.5. Most of the changes concern pay by email and checkout. Payment links now stay usable after staff clear the basket, payment requests by email need a customer email address, and checkout and confirmation pages keep the branding of the order's market. The release also fixes card payments that ended on an order retrieval error, booking searches that failed for certain ticket types, and trade partner sign-in on new devices, and adds an API action to remove a customer account from an order.

Changes

Clearing the basket now releases held places straight away

Jira: V3-384

Issue

When a customer or staff member cleared the basket, changed market, or cleared a bundle or location selection, the items they had chosen could stay reserved until the hold expired. In the meantime, other bookings saw those items as sold out. This could also happen after an error in the basket.

Fix

Clearing the basket, changing market or clearing a bundle or location selection now releases the held places immediately, so they are available to other bookings. This applies to the B2C Booking Portal and the Reservations Portal. Baskets for pay-by-email orders that have already been sent are handled differently; see "Pay-by-email links keep working after staff clear the basket" below.

Testing

1. Add an item with limited remaining capacity to the basket.

2. Clear the basket using Clear All.

3. Start a new booking for the same session in another browser and check that the item is available again, not sold out.

Pay-by-email checkout keeps the order's market branding

Jira: V3-353

Issue

For venues with more than one market, opening a pay-by-email link could show the checkout page in the branding of a different market from the one the order was made in.

Fix

The pay-by-email checkout page and the manage order page now take their branding from the order's market, even when the web address names a different market. On other pages, such as booking pages opened from a link that names a market, the market in the web address still sets the branding.

Testing

1. In the Reservations Portal, create an order in a market with its own branding and choose Pay via email link.

2. Open the Complete Payment link from the email in a private browser window and wait for the order to load.

3. Check that the logo, headings and Continue to payment button show the order's market branding, and stay that way.

4. Change the market named in the web address to a different market and reload. Once the order has loaded, the page shows the order's market branding. A brief flash of other branding while the page loads is expected.

Pay-by-email links keep working after staff clear the basket

Jira: V3-423

Issue

If staff sent a pay-by-email request and then cleared the basket in the Reservations Portal, the order was cancelled behind the scenes. The customer's payment link then showed "Unable to retrieve your order".

Fix

Clearing the basket, or removing its items one by one, no longer cancels a pay-by-email order that has already been sent. The order stays at Awaiting payment and the customer can open the link and pay. Discarding the order from the Orders screen still cancels it and stops the link working, as intended. Baskets without a sent payment request are released when cleared, as before.

Testing

1. In the Reservations Portal, create an order, choose payment Via Email and send the email.

2. Open the draft order from Orders, choose Edit Order, go to Checkout, then return to New Order. The basket shows the items that were sent.

3. Click Clear All. The basket empties and Orders still shows the order as Awaiting payment.

4. Open the payment link from the email. Checkout opens at Contact Details with no error.

5. Discard the order from Orders > More Actions, then open the payment link again. It no longer opens the order.

Booking search no longer fails for some ticket types

Jira: CORE-9127

Issue

If one of a product's ticket types used a type of capacity that a session's capacity plan did not cover, the whole search for sessions could fail. Staff on POS or in the Reservations Portal saw an error or an empty list of sessions.

Fix

The search now completes. If a ticket type you have asked for is not covered by a session's capacity plan, that session is shown as unavailable instead of the whole search failing. A ticket type that is listed but not selected no longer affects which sessions are available.

Testing

1. On POS, open a product that has a ticket type only some sessions cover, and pick a date this week. Sessions list with their availability and no error.

2. In the Reservations Portal, add one standard ticket for a normal session. The session is available and the ticket adds to the basket.

3. Select one ticket of the type only some sessions cover, plus one standard ticket, on a normal session. The session shows as unavailable, with no error.

4. Book a normal session from start to finish, and check that other products show sessions and availability as before.

Pay by email now needs a customer email address

Jira: V3-432

Issue

On some bookings made on behalf of a trade partner in the Reservations Portal, checkout skipped the contact step without saving the customer's details. Staff could then send a pay-by-email request and the screen said it had been sent, but no email went out and there was no option to resend it.

Fix

Checkout now keeps the trade partner's contact details when it skips the contact step, and uses the trade partner's address where there is one. A payment request by email is refused with a clear message if the order has no customer email address, and checkout returns staff to the contact step where that step is available. Requests by SMS without a phone number are refused in the same way. Customers who open a payment link for an order that has been changed or cancelled now see that the link is no longer valid and are asked to contact the venue for a new one, instead of being told to book again.

Testing

1. In the Reservations Portal, choose Place Order On Behalf, select a trade partner with full contact details, add a ticket and go to Checkout.

2. Fill in Booking Details, continue to payment, choose Via Email and send the email.

3. Check that the email arrives, and that the order shows the lead customer and a Re-send Payment Email option.

4. Discard the order from Orders > More Actions, then open its payment link. The page says the payment link is no longer valid and does not offer Start again.

Confirmation page keeps the order's market branding after payment

Jira: V3-437

Issue

After a customer paid through a pay-by-email link, the confirmation page could switch to the branding of a different market.

Fix

The checkout confirmation page now always uses the branding of the order's market. This includes pay-by-email payments and returns from a card payment page, and the branding stays the same if the page is refreshed.

Testing

1. Create a pay-by-email order in a market with its own branding.

2. Pay through the link in the email.

3. Check that the confirmation page shows the order's market branding, and still does after a refresh.

New API action to remove a customer account from an order

Jira: PROD-18

Need

The API let staff systems move an order to a different customer account, but not remove the account from the order altogether.

Change

The Reservations API now lets an authorised system remove the customer account from a placed order, which leaves it as a guest order. The order's items and the staff member recorded against the sale are unchanged, and the usual order-updated webhook is sent. Draft orders, guest orders and orders that include a membership cannot have their account removed. The action needs the same permission as moving an order to another account. There is no change to any screen.

Testing

1. Using an API user with permission to change an order's customer, remove the customer account from a placed order that is linked to an account.

2. Check that the order is now a guest order and its items are unchanged.

3. Try the same on a draft order and on an order that includes a membership, and check that both are refused.

4. Try the same with a user without the permission, and check that it is refused.

Card payments no longer end on "Unable to retrieve your order"

Jira: V3-452

Issue

Sometimes, after a customer who was not signed in paid by card, the card payment page reloaded the checkout. The payment had gone through and the order had been placed, but the customer saw "Unable to retrieve your order. Please try and make your booking again", which could lead them to book a second time.

Fix

Checkout now keeps the customer's access to their order when the page reloads, so it ends on the order confirmation. The page may flash or reload once after payment. This fix was already in earlier release lines and is now included in v3.4.

Testing

1. Without signing in, make several bookings paid by card, including some on a mobile phone and some that ask for extra card verification.

2. Check that every payment ends on the confirmation page showing the booking reference, and never on "Unable to retrieve your order".

Trade partners can sign in from a new device

Jira: V3-419 | FD: 6116

Issue

Some trade partner users could not sign in to the Trade Portal on a new device or after clearing their browser data. They saw a message asking them to raise a ticket with the service desk to have their permissions set up, even though the same account still worked on a device where it was already signed in.

Fix

If the trade role is missing from a user's sign-in details, the Trade Portal now checks their user profile for it, so these users reach the portal as normal. Users with no roles at all still see the service desk message, and users without trade access still see "You do not have access to this application."

Testing

1. Sign out of the Trade Portal, clear the site data for the portal, then sign in with a trade partner user.

2. Check that you land on Explore as normal.

3. Sign in again from a private browser window and check that it works the same way.

4. Sign in with a staff user who only has Reservations Portal access, and check that you see "You do not have access to this application."

Add-on cancellations follow the venue's refund rules

Jira: V3-443

Issue

Where online refunds were switched off, a customer could cancel an order containing only add-on items in the B2C Booking Portal and be taken to the refund page. Clicking Complete refund then did nothing and showed no error.

Fix

Where refunds are switched off, cancelling add-on items or reducing their quantity now shows the same "refunds not allowed" message as cancelling a ticket, and the order is not changed. Adding items or increasing quantities works as before. Separately, if a refund fails on the refund page, the customer now sees the reason.

Testing

1. On a venue with online refunds switched off, open an order with add-on items in the B2C Booking Portal and go to amend the order.

2. Remove an add-on or reduce its quantity, and check that the refunds not allowed message appears and the order is not changed.

3. Add an add-on or increase a quantity, and check that the change goes through as normal.

4. Check that cancelling a ticket still shows the refunds not allowed message as before.

Add-ons panel opens at the top of the list

Jira: V3-363

Issue

When choosing add-ons in the B2C Booking Portal, the add-ons panel could open scrolled to the bottom, so customers saw the last add-on first and had to scroll up.

Fix

The add-ons panel now always opens at the top of the list. The problem occurred when an add-on's description contained a link set up in a particular way; the panel now opens correctly whatever the descriptions contain.

Testing

1. In the B2C Booking Portal, add a ticket for a product with add-ons so that the add-ons panel opens.

2. Check that the panel opens at the top of the list and that you scroll down to see more add-ons.

3. Close and reopen the panel, and check that it opens at the top again.

Booking portal keeps the right market when none is in the web address

Jira: V3-451

Issue

For venues with more than one market, pages with no market in the web address, such as account pages after the browser cache was cleared, fell back to the first market in the list and showed its branding.

Fix

The B2C Booking Portal can now be set up with a default market, available on request. When the web address does not name a market, the portal keeps the market already in use; if there is none, it uses the default market, and only then the first market in the list as before. Links that name a market still open that market, and the staff portals are unchanged.

Testing

1. On a venue with a default market set, sign in to the B2C Booking Portal and go to Account > Contact Information.

2. Clear the browser cache and reload the page.

3. Check that the page shows the default market's branding.

4. Open a booking link that names a different market, and check that the page shows that market.

Printed membership cards keep the venue's card design

Jira: V3-446

Issue

Since v3.4.0, membership cards printed on a computer running an older version of the card printing app could come out in a default design instead of the venue's own card design.

Fix

Print jobs now include the information that older versions of the printing app need to choose the venue's card design. There is no change for computers already on the current printing app.

Testing

1. In the Reservations Portal, open an order with a membership, or select memberships in Search Entitlements, and choose Print.

2. Go through the card printing steps on a computer with an older version of the printing app.

3. Check that the cards print in the venue's own design.