Change Log - 28 April 2026 27-04-2026

Expected deploy: 2026-04-28, 19:00 - 21:00. No downtime expected.

Implemented "Force Cancellation" on the iTicket portal. Force Cancellation bypasses the upcoming possibility to cancel CRS orders on iTicket. Force Cancellation also bypasses any existing refund policy. (ID: 59040)
Released exclusive allotments will now automatically trigger a refresh on the product calendar that uses the main capacity (which is increased by an expired exclusive allotment), ensuring calendars are always up-to-date, without a manual refresh of the price list. (ID: 56940)
Improved UI for accounting dimensions on locations, making it clearer that such location overrides only apply to digital coupons. (ID: 58141)
Added a new checkin configuration rule to allow only Credit and Value Vouchers for pickup. (ID: 58436)
Added support for creating an account at VisitPay through iTicket. (ID: 57092)
Added NetsCloud as a supported payment service provider for POS - configurable on the iTicket portal. (ID: 57093)
When adding tours to event types, we now sort tour codes in alphabetical order. (ID: 52820)

Fixed an issue where the calendar showed "Few left" on all days when price group dependencies were used in combination with mandatory articles. (ID 59278)
Fixed an issue where OTA channels did not respect other exclusive allotments and only considered the main capacity. (ID: 59447)
Fixed an issue where season passes could display “Valid 0001-01-01” instead of only showing the fixed date. (ID: 57549)
Fixed an issue where BF transport products became unbookable if the first leg had no remaining capacity. (ID: 58405)
Fixed an issue where the new iTicket Statistics API could throw errors for some historical dates. (ID: 58466)
Fixed an issue where products using mandatory add-on choices, that dependent on previous article selections, could show the wrong total price. (ID: 58964)
Fixed an issue where revoked value cards were still displayed in document sections and in POS. (ID: 59125)
Fixed an issue where the filter UI was broken on check-in units. (ID: 59178)

Human-reviewed AI was used in the process of writing these release notes.