Feature Requests

Allow patients to indicate their dietary preferences in advance, for example, through a link sent via SMS. Currently, patients can place their own orders, but cannot manage their dietary profile independently. This feature would enable patients to set up their dietary restrictions, allergies, preferences, etc., before placing orders, improving the ordering experience and ensuring dietary requirements are captured accurately from the start.

In some locations, room names include extra characters like "216F" or "216 f" (F = fenêtre, P = porte). But when a nurse searches just “216”, the system shows an error — even though the room exists. We want to improve this by introducing "Did you mean..." suggestions. 💡 Instead of no result, the terminal will show clickable suggestions like: 👉 Did you mean: 216 f These suggestions will appear in a tag-style button, so the user can simply tap to auto-correct their search.

When selecting a product on the order-taking screen, several customizable fields appear at the bottom: quantity, comment, portion size, texture, and consistency. Currently, it's hard to spot when one of these options differs from the default. To improve visibility, we’re exploring a blue line highlight (instead of grey) to signal any non-standard selections. This would help users quickly recognize customizations at a glance — no more missed changes or unnoticed portion sizes!

To prevent any risks due to missing or incomplete ingredient data, it would be good to have a new report that lists all ingredient-based dietary restrictions alongside patient room numbers. This will allow teams to cross-check and ensure that patients are not served meals containing allergens, even when ingredient data is incomplete.

This could be an email automation service to send a specific report with a specific date filter to a designated user.

Right now, the automated order feature only works with a default quantity of 1. I’d like to be able to set custom default quantities for each item, so the system uses those instead when generating orders automatically.

We could build a feature for schools to select a date range to show the menus, making sure that school closures (e.g. Christmas holidays) don't interrupt the collection intervals. Desired user flow User accesses integration link or collection link that contains 1 or more integration links with a date range picker User sees date range User selects a date range Menus following that template or ruleset (depending on how the integration link is set up) is displayed if they are contained in the selected date range If one or more menus is are not ready, our existing error message is displayed This should affect the collection and integration link in such a way that the client can fiddle the URL link to immediately have the date range of their choice when they sends emails to their clients.

We could link the KDS with the canteen terminal, so that tickets would be auto-marked as done after X seconds. The flow would be: 1) canteen scan → 2) triggers order to be fired (ordered is skipped) → 3) is auto-marked as done after 15 seconds.

For some users (e.g. Kitchen) it makes sense for all names to be hidden (and can be unhidden upon a click, like a banking app). Activate/deactivate on the Consumers screen, the Orders screen and the Menu ordering top bar. This setting must be saved per user, not per session.

Ensure that products selected in the cart remain visible and unchanged when a user switches the interface language mid-order, allowing continuity in the ordering process without losing previous selections.