Release notes: POS 3.0.19

23 September 2026

This release focuses on everyday reliability at the till. Pass amendments that change the product now keep the original start date when the relevant setting is on, and scanning a new booking from the basket no longer carries the previous customer's details across. Refunds on A920 devices no longer leave the screen loading, and every device now shows a refund completion screen. It is also now possible to make the phone number optional for voucher purchases, on request. Front-of-house teams should note one change in behaviour: scanning a new booking while a basket is in progress now clears that basket automatically.

POS

Booking and checkout

Phone number can be made optional when selling vouchers

Jira: EXN-303

Need

When selling a voucher, POS always required a phone number in the buyer's personal details, even for venues that do not collect one.

Change

Whether a phone number is required for voucher purchases is now configurable, available on request. Where it has been made optional, the field is labelled "Phone Number" without an asterisk and the sale can continue with it left empty. First name, last name and email are still required, and the confirmation checkbox must still be ticked. A phone number remains mandatory by default, and the requirements for gift memberships are unchanged.

Testing

On a POS where the phone number has been made optional:

1. Start a voucher purchase and go to Buyer Personal Details. The phone field reads "Phone Number" with no asterisk, while First Name, Last Name and Email still show asterisks.

2. Fill in first name, last name and email, tick the confirmation checkbox and leave the phone field empty. Next becomes available and the purchase can be completed.

3. Complete another voucher purchase with a phone number entered. The phone number is saved against the order.

4. Add a voucher to the basket, then go back in and edit its buyer details. The phone field is still optional and the details already entered are kept.

5. Leave first name, last name or email empty in turn. Next stays unavailable each time.

On a POS with the default setting:

6. Start a voucher purchase, fill in every field except the phone number. Next stays unavailable until a phone number is entered.

7. Start a gift membership purchase. The phone field is still mandatory, as before.

Payments and refunds

Refunds on A920 devices no longer stay on the loading screen

Jira: EXN-469

Issue

On A920 devices, after a refund was processed and the receipt printed, the screen stayed on the loading indicator.

Fix

Completing a refund now opens a refund completion screen, on all devices, showing the refund amount and total. The receipt prints automatically where automatic printing is enabled, or can be printed from the completion screen. On A920 devices the loading indicator now clears once the refund is complete. Pressing Back from the completion and printing screens returns to the appropriate screen without undoing the refund.

Testing

1. On an A920, amend a booking so that a refund is due and continue to the refund screen.

2. Complete the refund. The refund completion screen appears, showing the refund amount and total, and no loading indicator remains on screen.

3. Print the receipt from the completion screen, or check that it prints automatically if automatic printing is enabled.

4. Press Back. You return to the previous screen and the refund remains in place.

5. Repeat for a full and a partial refund, and for bookings that include tickets, memberships or extras.

Orders and amendments

Pass start date kept when an amendment changes the product

Jira: EXN-402

Issue

When amending a pass and using Change Product to move it to a higher-value product, the start date changed to today, even with the "Keep original time (even if past) during amendment" setting turned on. The originally booked date was lost.

Fix

With that setting on, Change Product now keeps the originally booked start date, including when it is in the past, and the amendment can be saved. The date stays visible while the new product loads, rather than briefly going blank. Amending without changing the product continues to keep the original date, and with the setting off the date defaults to today, as before. If the original date cannot be used for the new product, POS may select today or the first available date instead, so check the start date before saving.

Testing

1. Make sure "Keep original time (even if past) during amendment" is turned on in POS settings.

2. Open an active pass whose start date is in the past and amend it.

3. Use Change Product to select a higher-value pass. The start date stays on the originally booked date and does not change to Today. The date button shows a date throughout while the new product loads.

4. Complete and save the amendment. The order shows the original start date.

5. Repeat with a pass whose start date is today, and one whose start date is in the future. The original date is kept each time.

6. Turn the setting off and repeat step 3 with a past-dated pass. The date defaults to today, as before.

Scanning a new booking from the basket no longer carries over the previous customer

Jira: EXN-403

Issue

With a booking already in the basket, scanning the next customer's booking with the hardware scan button or the scan icon in the top bar did not clear the basket. The previous customer's details carried across, and saving could record one customer's name and email on another customer's booking. Returning to the home screen before scanning already cleared the basket correctly.

Fix

Scanning a booking with the hardware scan button or the top-bar scan icon now clears the basket automatically and shows only the scanned customer's details. Any basket in progress is discarded when a new booking is scanned. Opening the scanner and closing it without scanning keeps the basket as it was. While a card payment is in progress, the scan does not open and a message explains why, leaving the basket and payment untouched. Pressing Back after a scan returns to the home screen, and the previous customer's screens no longer reappear.

Testing

1. On a device with a hardware scan button, such as the A920, put a booking in the basket, then press the scan button and scan a different customer's booking. The basket is cleared and only the scanned customer's details are shown.

2. On a device with the top-bar scan icon, such as the E700, repeat step 1 using the scan icon. The result is the same.

3. With a booking in the basket, open the scanner and close it without scanning. The basket is kept exactly as it was.

4. Start a card payment and, while it is in progress, press the scan button or scan icon. The scan result does not open, a message explains why, and the basket and payment are untouched.

5. After scanning from inside a basket, press Back from the scan result. You return to the home screen and the previous customer's screens do not reappear. Pressing Back repeatedly leaves the app usable.

6. With a booking in the basket, return to the home screen instead of scanning. The basket is still cleared, as before.