Change Log - 18 February 2026 17-02-2025

Expected deploy: 2026-02-18, 19:00 - 21:00. No downtime expected.

We completely rebuilt the backend logic how campaign codes are applied. Applied campaign codes are now reserved immediately once they are applied in a basket row and cannot be used by another customer at the same time, unless the usage limits allow it.
- Implemented reservation handling for promo codes so they are reserved before an order is fully committed. (ID: 55989)
- Application of the same usage-restricted promo code on multiple lines in the same order is not possible any longer.
- Ensured that correct campaign usage limits are taken into account at all times. (ID: 55990)
- Updated season pass unlock and multi-use code caching to ensure accurate usage numbers are considered when allowing or refusing application of a campaign code to an order. (ID: 55991)
Corrected the returned error and log when trying to redeem a blocked or expired value voucher. (ID: 51683)
Fixed the GetYourGuide integration so cancelled bookings are correctly processed through the API. (ID: 55498)
Added the possibility to apply value voucher during debt settlement (ID: 56398)

Bug Fixes

Fixed incorrect timestamps for value voucher and credit transactions in the Portal. (ID: 56434)
Resolved missing bookings in Order Management, status mismatches, and empty documents due to an earlier fix around trimmed spaces in article and product codes. (ID: 56526)
Removed “show” and “deactivate” actions from the season pass document context menu. (ID: 56554)
Fixed an issue where newly created tags required a hard refresh before appearing. (ID: 56598)
Fixed an issue where empty dates in value card transactions (Value Vouchers and Credits) displayed null. (ID: 56686)
Fixed UI issues around complementary fields where the data type field was empty and ensured newly created complements work correctly. (ID: 56697)
Corrected VC System calculations for balances and sums when handling negative amounts. (ID: 56838)