Version 5.5

Version 5.5.0 marks a major technology leap for multi-terminal setups: real-time synchronization via Server-Sent Events and the completely redesigned order monitor 2.0.0 fundamentally offload the main POS terminal. This enables reliable operation with significantly more satellite terminals and kitchen monitors than before — ideal for growing businesses and complex venue layouts.

Version 5.5.0

Released: 2026-04-09

🆕 New Features

• Real-time satellite synchronization: Communication between main and satellite POS terminals now uses real-time Server-Sent Events (SSE) instead of polling. This drastically reduces the load on the main terminal, enabling stable operation with far more connected devices and delivering instant updates across all stations.

• Order monitor 2.0.0: The order monitor has been completely rebuilt with a new web UI architecture. The redesigned system communicates directly via WebSockets, offloading the main POS terminal and allowing you to run more kitchen and bar monitors simultaneously without performance degradation.

• Article filtering for order monitors: Configure which articles are shown or hidden on each order monitor, allowing you to display only relevant items per station — e.g. only drinks at the bar, only food in the kitchen.

• Course group query for kitchen displays: Order monitors can now query course groups, enabling kitchen displays to manage courses independently and improve food preparation timing.

• Course group printing: Course group queries are integrated with the print workflow, ensuring synchronized printing when courses are triggered from the kitchen display.

• External article ID integration: Articles can now be identified and searched by external IDs from third-party systems such as ERP or merchandise management solutions, streamlining cross-system article lookup.

• Room list view: Rooms can now be displayed in a flexible list layout in addition to the existing floor plan view.

• Company branding on kiosks: Your company logo is now displayed on scan-only kiosk screens for a more professional customer-facing experience.

✨ Improvements

• Digital invoice design: The digital invoice screen has been refreshed with an updated layout and modern styling.

🐛 Bug Fixes

• Order monitor article group sync: Changes to order monitor configurations now correctly propagate to article groups, ensuring monitors always display the latest settings.

• Discount calculation for zero-quantity items: Discount-only order items are no longer created with zero values. Items that already have correct values are no longer unnecessarily reprocessed, and zero-value discount items are filtered out before saving.

• Discount reset on quantity change: The discount value is now correctly reset when the item quantity changes in the order builder, preventing stale discount amounts.

Version 5.5.1

Release Date: 2026-04-10

This patch release fixes a critical database migration issue that could prevent app updates and improves the order monitor UI.

✨ Improvements

• Order monitor caching: Static assets now use long-term browser caching, reducing load times on subsequent visits.

• Order monitor settings navigation: Navigating back from settings no longer triggers a full page reload.

• Order monitor card layout: Order cards now use square top corners for a cleaner, more consistent appearance.

🐛 Bug Fixes

• Database migration crash on update: Fixed a crash that could occur when updating from a previous version. The database migration now correctly handles column ordering during table recreation, preventing NOT NULL constraint failures and potential data corruption.

• Order monitor sidebar styling: Corrected the items sidebar background and removed unintended rounded corners.

Version 5.5.2

Release Date: 2026-04-22

This patch release addresses several crash and reliability issues — most notably on satellite terminals after a shift change — and fixes an order monitor layout issue with long article or category names.

🐛 Bug Fixes

• Shift change crash on satellites: Fixed an app crash that could occur when closing or changing a shift on a satellite terminal. The transaction reset now runs off the main thread to satisfy Room's thread-safety requirements.

• Open order groups missing after shift change on satellites: After the switch to real-time SSE synchronization, currently open order groups could stay missing on satellites until the next scheduled poll. They are now reloaded immediately after a shift change.

• Loyalty card selection crash: Fixed a crash that could occur if loyalty cards were loaded after the payment screen had already been closed. The selection dialog is now skipped when its screen is no longer available.

• Order monitor layout with long names: Order cards now keep the status indicator, waiting time, and header info visible when article or category names are long. Long names are truncated with an ellipsis instead of pushing other elements off-screen.

Version 5.5.3

Release Date: 2026-04-23

This patch release resolves several data-sync and dispenser issues that affected satellite terminals and beverage dispensing workflows.

🐛 Bug Fixes

• Full sync from settings: On satellites with real-time sync active, the database now repopulates immediately after a full sync instead of staying empty until the next scheduled poll or an app restart.

• Open tables across shifts: Open tables on satellites no longer flicker or disappear when the master ends a shift or starts a new one. The transaction cleanup now runs exactly once per shift-end transition and is no longer interrupted by the sync service lifecycle.

• Dispenser cancellations (E-Protocol, VMPS): Cancelling a transaction on E-Protocol and VMPS dispensers no longer fails with a malformed command. Cancelled quantities are now transmitted as positive values.

Version 5.5.4

Release Date: 2026-04-27

This patch release resolves payment, barcode-scanner, and satellite-terminal issues and adds richer diagnostics to help support investigate customer-display and synchronization problems.

✨ Improvements

• Customer display diagnostics: Route changes, presentation lifecycle events, and previously-silent display errors are now traced, and the app actively detects when a connected external customer display disappears — making it easier to investigate sporadic reports of the cart not updating on the secondary screen.

• Stuck-sync diagnostics: Logs and crash reports for unsynced data now include a per-entity-type breakdown (for example Order=5, Payment=3) when an unsynced state blocks logout or a full sync, and once per foreground visit to the menu while data remains unsynced — so stuck-sync reports on satellite terminals can be diagnosed faster.

• Validation error logging: Validation errors from the customer, address, custom-article, and order-pay screens now record the resource name and localized text instead of an opaque "null" message in file logs and crash reports, so reported handled exceptions can be analyzed.

🐛 Bug Fixes

• Stripe card-terminal payments with long company names: Card-terminal payments via Stripe no longer fail with "statement descriptor must be at most 22 characters". The statement descriptor is now sanitized of Stripe-forbidden characters and truncated to fit Stripe's 22-character limit while preserving the invoice number.

• Accidental voucher booking via external USB keyboard: Typing short numeric sequences on a USB keyboard can no longer accidentally book a voucher. Very short keystroke bursts are ignored by the barcode-scanner input path, and voucher sequential-id matching is now restricted to input that is clearly scanned rather than typed.

• Cursor jump in input dialogs: The cursor no longer jumps to the start of the line when typing quickly in the "Set comment", "Set name", and cash deposit/withdrawal dialogs.

• Customer assignment on satellite terminals: Assigning a customer to an order on a satellite terminal no longer creates an unnamed temporary customer that could route bookings to the wrong customer account. Customer management on satellites is restricted to selecting an existing customer (no creating, no editing) until full satellite customer management is available.

Version 5.5.5

Release Date: 2026-04-29

This patch release restores reliable NFC card scanning across all screens, returns the cash payment button to its familiar position on the right, and prevents a startup crash report caused by interrupted open-order backups.

🐛 Bug Fixes

• NFC card scanning works reliably across screens: Customer cards, voucher cards, and other NFC tags presented on the order screen, table view, customer screens, or any other screen are now read reliably across activity transitions, instead of only briefly during app startup.

• Cash payment button restored to the right side: The cash payment button is shown on the right side of the order, group order, and split payment screens again, restoring the long-standing arrangement of cash on the right and card to its left after a recent internal change had unintentionally moved cash to the left.

• Empty or corrupt open-order backups no longer crash startup: Open-order backup files that were left empty or only partially written when the app was killed mid-write are now skipped and removed at startup instead of producing a non-fatal crash report; remaining backups continue to restore as before.

Version 5.5.6

Release Date: 2026-05-01

This patch release fixes a startup crash on the Stripe Tap to Pay flow and restores keyboard and scanner input for very short product codes.

🐛 Bug Fixes

• Stripe Tap to Pay no longer crashes when starting a contactless payment: The themed accent, success, and error colors are now passed to the Stripe Tap to Pay UI as actual color values instead of being misinterpreted as resource IDs, which had caused a fatal crash when starting a contactless card payment after updating from earlier 5.4 versions.

• Short product numbers are accepted again on keyboard and scanner input: Product numbers with only 1 or 2 characters entered via an external keyboard or barcode scanner are processed again, restoring workflows that rely on very short product codes; the minimum input length introduced in version 5.5.4 had unintentionally been blocking these entries.

Version 5.5.7

Release Date: 2026-05-08

This release significantly improves how the Order Monitor handles modifiers and per-monitor step configuration, and fixes a fatal crash on SSE connection failures plus a number of payment and monitor-related bugs.

✨ Improvements

• Modifier articles share their parent's lifecycle on the Order Monitor: A modifier ("ohne Speck", "Salami als Beilage") now always follows the same status step as the dish it belongs to — also when the modifier's own article group is mapped to a different monitor. The mapping decides where the modifier surfaces, never what state it carries, so a side dish for the service monitor no longer appears as "ready" before the kitchen has even started preparing it. Tapping any modifier row advances the entire bon (parent + all modifiers) in one step.

• Per-article step navigation respects each monitor's configuration: The Order Monitor no longer steps blindly through every status that exists in the system. An item's initial step is the smallest active step actually configured for the article on a monitor, forward and backward jump to the next or previous configured step for that specific article, and items whose visible bon contains different states are first aligned to the highest-progressed state before they advance together. Items routed to other monitors are no longer touched when staff advances a bon, and the bon's overall status always reflects the smallest active step across all of its items.

• Display-only parent context: The Order Monitor now also shows bons whose main article is configured for a different monitor as long as one of the modifiers is routed here. The main article is rendered as display-only context so the user can identify what the modifier belongs to, but it cannot be advanced from that monitor.

🐛 Bug Fixes

• Automatic status timeouts on the Order Monitor work again: Orders configured with an automatic timeout on a status now actually advance when the timeout elapses, instead of silently staying on that step. The auto-advance also follows the new per-article-group step navigation, so timed-out items skip steps that no monitor displays for them.

• No more crash on SSE connection failure: The cashier no longer crashes when the SSE connection to the master fails during the initial handshake — for example when the master is unreachable, TLS aborts, or the connection is reset before the upgrade completes. The SSE client now reliably falls back to its retry loop instead of taking the whole app down.

• GPTom card payments recover from payment-app crashes: GPTom card payments no longer get stuck in an endless polling loop when the GPTom payment app crashes mid-transaction. The cashier stops polling on the first binder failure and reports the payment error immediately instead of after the full 5-minute timeout.

• Articles without a configured processing time are accepted by the server again: The API request now sends 0 instead of null for the processing time field, which the server rejected as an invalid integer value.

• Order Monitor card keeps its bon number after updates: Cards keep showing the bon number after subsequent order updates even when the order's external label is reported as an empty string instead of unset; the bon number no longer disappears from the card after the first state change.

• Order Monitor cards disappear correctly: Cards now disappear from a monitor as soon as all items belonging to that monitor have reached a non-visible state, even when modifiers belonging to other monitors are still in progress. Previously a bon could remain stuck on a monitor and cycle through states indefinitely. Modifiers also respect the per-article-group include/exclude filter consistently with the main item.

📋 Compliance

• PIN entry required after fresh login and full sync: The cashier now requires PIN entry directly after a fresh user login or after a full sync, preventing the silent activation of a PIN-protected user that could occur during the brief window when the user state had not yet been loaded.