Skip to main content

Karenderia Waiter App

A dedicated mobile app for restaurant waiters and servers, fully integrated with Karenderia.

The app would allow waiters to take and manage customer orders directly from an Android device while serving customers at their tables.

Proposed Features

  • Select restaurant table

  • View table status and current orders

  • Create new orders for a table

  • Add additional items to an existing table order

  • View menu items, categories, addons, and item options

  • Send orders directly to the kitchen/KOT

  • View and update order status

  • Request or generate customer bill

  • Accept/manage payments

  • Print customer bills using a Bluetooth printer

  • View table order history

  • Multiple waiters can manage restaurant tables

  • Real-time synchronization with Karenderia POS and restaurant orders

Example Workflow

Waiter selects table → Takes customer order → Sends order to kitchen → Customer adds more items if needed → Waiter requests bill → Payment → Print receipt → Close table

The goal is to give restaurant staff a fast and simple way to manage dine-in customers without having to return to the main POS terminal for every order.

Vote for this request if you would like to see a dedicated Karenderia Waiter App developed.

Status: In Progress35 comments

Log in to comment and vote

Comments35

  • Shams Sk

    •

    Sep 24

    I strongly support this request. In addition to the proposed features already mentioned, I would suggest considering the following features based on real restaurant workflows:

    • Order Type: Allow the waiter to select Dine-in, Takeaway, or Delivery when creating an order. Because customer sitting at a table may order food to eat at the table and also request additional items as takeaway or delivery to their home. The app should support these different order types within the same customer/table interaction.

    • Delivery customer details: For delivery orders, allow the waiter to select or enter the customer's name, phone number, delivery address, and delivery notes.

    • Quick table view: Show occupied, available, reserved, and bill-requested tables at a glance.

    • Item-level notes: Allow special instructions for individual items, such as “no onion,” “less spicy,” “sauce on the side,” etc.

    • Hold / Fire: Allow items or courses to be held and sent to the kitchen later.

    • Split bill: Split a bill by item, quantity, or equally between customers.

    • Merge / split tables: Useful when customers move tables or when multiple tables need to be combined into one order.

    • Transfer table/order: Allow a waiter to transfer a table or order to another waiter.

    • Move order between tables: For example, when customers move from Table 5 to Table 8.

    • Discount / promotion handling: Allow authorized waiters to apply available discounts or promotions, with appropriate permission controls.

    • Favorites / frequently ordered items: Make common items faster to access, reducing the number of taps during busy periods.

    • Quick search: Search menu items by name without having to navigate through multiple categories.

    • Notifications with sound: Notify the waiter when a KOT is ready, when a customer requests assistance/bill, or when an action requires attention.

    • Real-time synchronization: Changes made by one waiter should appear almost instantly on other waiter devices and the main POS.

    • Offline capability (Important): The app should remain usable during a temporary Wi-Fi/network interruption and synchronize once the connection is restored.

    • Large-button mode / Simple UI: A simple interface optimized for tablets/phones and fast use during busy restaurant hours. Most importantly, the interface should be optimized for speed and minimal taps. A waiter should be able to take an order while standing beside the customer without navigating through complicated screens.

    • Order confirmation before sending: Option to quickly review the order before sending it to the kitchen, especially for large orders.

    • Smart QR integration: This is important because customers who order through the Smart QR menu may still need waiter assistance. For example, instead of using their phone while eating, they can simply ask the waiter to add or remove items, make changes to the order, or place additional orders through the waiter app. The waiter should be able to see and manage these customer-generated orders alongside regular waiter orders.

    • SUNMI V2S compatibility: Please ensure the waiter app is fully compatible with sunmi V2s including its built-in thermal printer, so waiters can print the bill directly at the table and hand it to the customer for payment at the cash counter.

    The main goal should be to make the app extremely fast and require as few taps as possible during actual table service. If developed well, this could become a very useful and high demand extension of Karenderia for restaurants with dine-in, takeaway, and delivery operations.

  • basti bach

    •

    Sep 23

    count me in

  • Shams Sk

    •

    Sep 24

    I recommend developing the waiter app in Flutter with an offline-first architecture. Since Karenderia is cloud-based, the cloud should remain the main source of truth, while SQLite/local storage is used only for temporary working data and the offline queue (such as active orders and pending changes). Automatic cleanup should remove old cached data after it has been successfully synchronized, to avoid unnecessary storage usage on devices like SUNMI V2S.

    • Victor87

      •

      Sep 27

      This could be considered. I use sunmiv2 for merchant app. The RAM and store is limited

  • Ferran

    •

    Sep 26

    This is a very nice idea. Congrats!. Currently, most popular multi-vendor scripts on CodeCanyon don’t have this feature. However, without offline functionality, it may not work well in real-world restaurant environments because waiters are constantly on duty and may face internet connectivity issues. So, proper offline functionality with automatic online synchronization is a must.

    • ceazar

      Team•

      Sep 26

      thanks mate for voting , i agree with you for offline functionality

  • Xiaru

    •

    Oct 8

    😍 Thank you. This is the real, essential tool for a restaurant system.

  • Jo@

    •

    Sep 26

    Basti rocks! Super initiative, you always deliver very useful modules for us.

    Please make sure to realize this via Flutter or Native instead of a WebView merchant shell—otherwise performance stutters under heavy peak load. Also we strictly need:

    • Full Android Tablet & iPad support

    • Multi-waiter concurrent ordering

    • Kitchen thermal printer integration

    • Real-time sync via WebSockets/gRPC (so Table 4 updates instantly across all devices without pull-to-refresh)

    Thanks basti.

    • ceazar

      Team•

      Sep 26

      thanks for voting mate will do surely noted of your suggestions

  • foodclick

    •

    Sep 27

    Was waiting for this 😄 But how it will work when people use smart qr table ordering?

    • ceazar

      Team•

      Sep 27

      it can be both use 😀 , example guest goes to restaurant and don’t have phone internet connections so guest cannot use the smart qr table app, now the waiter app will be come handy

      • foodclick

        •

        Sep 27

        Awesome 🤩😍 , so it works offline just like a native app? That’s great!

        Quick question about how waiters interact with Smart QR table orders: Can a waiter modify an active order placed by a guest using Smart QR menu? For example, if a guest orders via QR code and then asks a nearby waiter next time for a bottle of water, can the waiter pull up that live order (QR dine in order) and add the water to it? In short, can all waiters view all live QR orders and add or remove items as needed?

        • ceazar

          Team•

          Sep 27

          The idea would be exactly like your example:

          Guest orders via QR → waiter opens the same active table/order → adds a bottle of water → sends the additional item to the kitchen/KOT.

          This would allow authorized waiters to see active table orders and assist customers without creating a separate order.

          I’ve added the Waiter App to the feature request page, so please vote for it if you would like to see this workflow implemented. 👍

          • foodclick

            •

            Oct 3

            Thanks a lot.

  • Aghmed

    •

    Sep 27

    Hey team, this new feature is really interesting! To make it even better, could we get a PIN login for waiters? Typing in a full email and password every single time slows things down on the floor, so a quick code would be a massive time-saver.

    It would also be amazing if we could install the full app on a main touchscreen with a printer mounted in a central spot or on the wall. That way, all incoming orders are centralized in one place, but individual waiters can still handle their own tables and QR orders seamlessly through their personal tablets.

    • ceazar

      Team•

      Oct 1

      we surely do take note of your suggestion thank you 😀

  • [Deleted User]

    •

    Sep 28

    Good plan @basti👍Will this work with marchant application?

    • ceazar

      Team•

      Oct 1

      Yes all is connected with main kmrs

  • Beloma

    •

    Sep 30

    Sinceramente, me gusta mucho. Usamos Volt en nuestro restaurante, pero lamentablemente no tienen una aplicación para camareros. Ahora mismo, solo mostramos el menú y tomamos los pedidos. Sería fantástico tener una aplicación para camareros como esta, fácil de usar e inteligente, que nos facilitaría mucho el trabajo.🎉 😍

    • ceazar

      Team•

      Sep 30

      alright :) its already plan it will be release soon , it will not be long 🙂