Version 4.2.15 brings the go~mus platform many new features for more flexible event triggers, improved shop integration and extended POS functionality. Highlights include the extended automation-rule event triggers with weekday filters, which let you steer communication even more precisely. On top of that come important security updates, many small usability improvements and a significantly evolved self-checkout system with more intuitive navigation.
The update rolls out in waves between 25 May and 15 June 2026, as usual. Some features are optional or can be enabled on request, for any questions please reach out to support@giantmonkey.de.
Features
Withdrawal button
From 19 June 2026, an electronic withdrawal button becomes mandatory for almost all online shops in the EU and Germany. Contracts concluded online should be just as easy to withdraw from as they are to enter. go~mus therefore ships a dedicated withdrawal workflow with its own placeholders, email template and many further details that also make it possible to distinguish withdrawals from cancellations.
Event triggers for automation rules
With the extended event triggers you can steer communication even more precisely. Automation rules can now be restricted to specific weekdays, so reminder emails go out only on working days, for example. You can also test triggers manually and include unpaid bookings. New as well: monthly scheduling that fires a trigger on a specific day of the month.
Email templates for booking events
Email templates in the "Visit information" category can now use BOOKING_ and TOUR_ placeholders when triggered by booking events such as confirmations, cancellations or rebookings. This lets you send automatically personalised messages with all relevant booking details.
Multilingual salutations
Salutations in multilingual web shops now display correctly translated. Via the API, salutations can be filtered per language, so "Herr" automatically becomes "Mr." and "Frau" becomes "Ms.".
Improved Bundesmuseen Card integration (AT)
Each scan point can now use its own Bundesmuseen Card token instead of relying on the global token. This allows individual configuration per entry point with an automatic fallback to the global token.
Annual-pass holder management
For family annual-pass holders, one personalisation can now be marked as the main card. The export shows new columns for first name, last name and main-card status, which significantly simplifies analysis or the creation of specific mailings via external tools.
Helpdesk improvements
Search in the new helpdesk has been significantly improved: smarter search logic with word-boundary detection, contextual excerpts around the search term and direct links to matching headings. The new helpdesk is being rolled out instance by instance during this release.
OTIpass integration
The system now recognises both NFC serial numbers and the new dynamic QR codes from OTI and validates accordingly. The transition runs in parallel with existing NFC passes.
New origin analysis
The origin query at the POS (POS 2.0) and the automatic data generation from sales across all sales channels now have their own analysis. Origin data can be evaluated, visualised and exported by visit and sales date.
Security
We have implemented important security updates. Several vulnerable software components have been updated, including bcrypt, json and loofah. A vulnerability in the table quick filter has been fixed. The back-office login has been hardened with rate limiting, and the go~mus version number is now hidden from unauthenticated users. In addition, an open-redirect patch was applied to the login functionality.
Performance
The global search at the top of the navigation bar has become noticeably faster in many use cases. Customer email address lookups have also been sped up across many views.
Interfaces
PayPal webhook processing has been overhauled for better error handling and automatic refunds for cancelled orders.
The Korona integration has been further optimised: customers are only created on demand, which prevents duplicates. Prices by service date are now also calculated on demand using the concrete appointments, so date-based import from the Korona POS system is supported based on the visit date. Note: this feature has to be enabled separately.
In addition, action-token discounts are now correctly displayed in the receipt export. For Adyen, an initial Balance Account model with admin UI has been implemented, which automatically synchronises with the Adyen API.
go~mus + Shop
A new shop type "webcomponents" has been introduced for Svelte-based front ends, with simplified key structure and adapted defaults.
You can now assign and remove tickets directly from the shop without navigating to each individual ticket. The default shop selection has been technically improved and now uses a boolean flag instead of a hard-coded ID.
In addition, the withdrawal functions have been implemented in the shops and will be enabled successively in all German shops by 19 June 2026.
go~mus + POS
The POS system has been extended in several areas. Cashiers see a preview before redeeming a discount code, showing the concrete items the discount will apply to. A new "Validate" button per barcode enables paperless validation without printing and scanning. The self-checkout system (SCO) user interface has been reworked: instead of a flat ticket catalogue, there is now a configurable, hierarchical navigation that can be created in the new admin editor. The complete SCO interface has been redesigned with improved accessibility.
In addition, a ticket-return flow has been implemented for POS 2.0 that automatically triggers KORONA goods returns and allows already-paid tickets to be returned simply at the POS.
Design V5
The 4 in our version number stands for the UI generation. The step from 3 to 4 was a big jump back then. For Layout V5 we are taking a different path: new modules are built in the new framework, like the origin query mentioned earlier or the new helpdesk. Existing modules will gradually be migrated to the new layout framework. A first step towards unifying go~mus UI, SCO and POS is the use of a common icon library and the recurring particle design. Further improvements on the way to go~mus 5.0 will happen step by step to ensure a smooth transition.