Release notes: POS 3.0.18

21 September 2026

This release brings three improvements to the POS app, covering all changes since version 3.0.17.2. Staff can now remove or replace an existing promotion when amending an order, so a discount that no longer applies can be taken off and the difference charged. Cancelling a booking or pass now prints the cancellation receipt on its own, without a ticket carrying a scannable QR code. A new check prompt on the walk-up screen asks staff to confirm any quantity above 10 for a single ticket type before it is recorded, helping to catch mistyped figures before they reach reporting. There are no database changes in this release; staff who record walk-ups may find it helpful to be shown the new prompt.

POS

Orders and amendments

Remove or replace a promotion when amending an order

Jira: EXN-296

Issue

When amending an existing order on POS, either directly or by choosing Edit from the scan result screen, staff were not offered any way to remove the promotion already applied to the order. Where a customer turned out not to qualify for a discount, the difference could not be charged.

Fix

When amending an order, staff can now remove the existing promotion or replace it with a different one. Removing a promotion reprices the basket and the difference becomes payable. Re-applying the promotion within the same amendment returns the total to the discounted amount without double counting, with a refund rather than a charge if payment has already been taken. The change is saved with the order, and the order and receipt show the promotion removed with the correct new total. Where the scan check for applied promotions is configured, a ticket no longer prompts for a promotion check once the promotion has been removed and the difference paid. Applying and clearing a promotion on a new sale works as before.

Testing

1. Create a booking with a promotion applied. Note the total before discount, the discount value and the amount paid.

2. On POS, scan the ticket, choose Edit from the scan result and remove the promotion. The promotion line disappears, the total rises by the discount value and the difference becomes payable.

3. Take the payment, then redeem the ticket. The payment completes and the ticket redeems. The amount charged equals the original discount exactly, and the order and receipt show the promotion removed with the correct new total.

4. On a new booking, open the order for amendment directly in POS without scanning, remove the promotion, then save and reopen the order. The promotion remains removed.

5. On a new booking, remove the promotion and re-apply it within the same amendment. The total returns to the discounted amount with no double counting.

6. On a new booking, replace the existing promotion with a different one, then save and reopen the order. The new promotion is applied.

7. Amend an order without changing anything and try to submit it. It still cannot be submitted.

Tickets and communications

Cancelling a booking no longer prints a ticket with a QR code

Jira: EXN-367

Issue

With automatic printing switched on, cancelling a booking or pass on POS printed the cancellation receipt correctly, but also printed a ticket with a scannable QR code. This happened even when no refund was given.

Fix

Cancelling a booking or pass now prints the cancellation receipt only, whether or not money is returned to the customer. When only some of the tickets on a booking are cancelled, the receipt is printed and the tickets that remain valid are not printed again; the customer keeps the tickets they already have. Suspending a ticket also prints the receipt only. Selling a booking is unchanged: the receipt and tickets print as before.

Testing

1. Make sure automatic printing is switched on in POS Settings, then sell a booking with two tickets. The receipt and both tickets with QR codes print.

2. Cancel that booking and skip the refund. Exactly one cancellation receipt prints, with no ticket or QR code.

3. Cancel another booking and take the refund. Exactly one cancellation receipt prints, and nothing else.

4. Cancel a pass, once without a refund and once with one. Each time, exactly one cancellation receipt prints.

Suggested: Cancel only some of the tickets on a booking. The cancellation receipt prints and the remaining tickets are not printed again.

Scanning

Redemption and attendance

Check prompt when entering large walk-up quantities

Jira: CORE-9141 | FD: 4985

Need

Walk-up attendance is entered by hand on the walk-up screen, and there was no check on the quantity entered for a ticket type. A mistyped figure could be recorded in full and appear in attendance reporting.

Change

When a quantity above 10 is entered for a single walk-up ticket type, a "Check ticket quantity" prompt now appears before the walk-up is submitted, listing each ticket type above 10 with its quantity. Staff can confirm to submit, or cancel to return to the selection screen with their quantities kept. The check applies to each ticket type separately, not to the total, so 10 or fewer of each type submits straight away. The prompt works in the same way when the device is offline. Where a walk-up ticket type has a maximum quantity set, the quantity entered is also limited to that maximum.

Testing

1. On the walk-up screen, enter 11 of a single ticket type and submit. A "Check ticket quantity" prompt appears, naming the ticket type and quantity.

2. Confirm the prompt. The walk-up is submitted.

3. Enter 11 of a ticket type again, then cancel the prompt. Nothing is submitted and your quantities remain on the selection screen.

4. Enter exactly 10 of a single ticket type and submit. It submits without a prompt.

5. Enter 11 of one ticket type and 11 of another, then submit. One prompt lists both ticket types with their quantities.

6. Enter 11 of one ticket type and 3 of another, then submit. The prompt lists only the ticket type above 10.

7. Enter 5 each of two ticket types and submit. It submits without a prompt, as the check applies to each ticket type rather than the total.

8. Check your attendance reporting after each accepted walk-up. The counts match what was entered.

9. With the device offline, enter 11 of a ticket type and submit. The prompt behaves in the same way. Once the device reconnects, the entry reaches reporting with the correct count.