--- title: "The six apps, explained: who gets which screen and why | GoSufra" description: "Manager dashboard, POS, kitchen display, waiter, driver and customer app — what each one is for, who logs into it, and how one order moves through all six." url: "https://gosufra.com/en/blog/six-connected-apps/" language: "en" source: "https://gosufra.com" --- # The six apps, explained: who gets which screen and why Manager dashboard, POS, kitchen display, waiter, driver and customer app — what each one is for, who logs into it, and how one order moves through all six. 2026-08-31 · 7 min read ![Illustration of six tiles wired back to one hub](https://gosufra.com/blog/six-connected-apps.svg) ## Key points - Each role gets a screen built for its job, not a cut-down copy of the manager's screen. - All six write to the same database, so nothing has to be re-entered or synced by hand. - A cashier never sees payroll; a chef never sees margins. Roles decide the view. - You do not have to switch all six on at once — start with two and add the rest as you grow. “Six apps” sounds like six things to learn. It is the opposite: it is one system that stops pretending a chef, a cashier and an owner want the same screen. ## Why not one app for everyone A single interface for every role has to be generic, and generic is slow. A cashier at the counter needs three taps and no scrolling. A chef with wet hands needs large tiles and no keyboard. An owner needs charts nobody would want to look at during a rush. Splitting the interface does not split the data. It splits the **attention**. ## The six, one line each | App | Who uses it | What it is for | | --- | --- | --- | | Manager dashboard | Owners, managers, accountants | Menu, stock, staff, books, reports, settings | | POS | Cashiers | Ringing up orders, taking payment, shift cash | | Kitchen display | Chefs, kitchen staff | Live tickets, prep status, station queues | | Waiter | Floor staff | Tables, orders at the table, calling the bill | | Driver | Delivery riders | Assigned jobs, addresses, delivery status | | Customer | Your guests | Menu, ordering, loyalty points, order tracking | The dashboard runs in a browser. The other five are mobile and desktop apps — Android, iOS, Windows, Linux and macOS — and the POS also runs perfectly well on a cheap Android tablet. ## Following one order through all six A guest sits down at table 12. 1. **Waiter app** — the waiter opens table 12, taps three items, adds “no onions” to one, and sends. 2. **Kitchen display** — the ticket appears at the grill station within the same second. The salad line sees only its own items. 3. **Manager dashboard** — stock for the three items has already moved; the plate cost is already booked against the sale. 4. **POS** — the guest asks to pay by card at the counter. The bill is already there; the cashier splits it in two and takes payment. 5. **Customer app** — the guest’s loyalty points land, and the receipt is in their history. 6. **Driver app** — meanwhile a delivery order from the same kitchen has been assigned to a rider, with the address and the fee. Nobody re-typed anything. No integration ran. There was one order and six views of it. ## What each screen deliberately hides This is the part owners underestimate. The apps are not just different layouts — they are different **permissions**: - The POS shows today’s shift, not last month’s profit. - The kitchen display shows what to cook, not what it costs. - The waiter app shows their own tables, not the branch’s payroll. - The driver app shows the delivery address, not the customer’s full history. - The customer app shows the guest’s own orders and nothing about your operation. Nine role levels sit behind this, and a branch manager sees only their own branch. That is what makes it safe to hand a tablet to a new starter on their first shift. ## Start with two, not six You do not switch on all six on day one. A typical order of adoption: - **Week one:** dashboard + POS. That is a working restaurant already. - **Week two:** kitchen display, once the menu and prep stations are set. - **Week three:** waiter app if you have table service; driver app if you deliver. - **Later:** the customer app and your own ordering channel, when you want the orders you are currently renting from an aggregator. Each one you turn on makes the others better, because they all read the same data. But none of them requires the others to be useful first. ## The part that matters The number six is not the point. The point is that a single fact — this item, sold, at this moment — is written once and read by everyone entitled to see it, in the shape their job needs. That is the difference between six apps and six systems. - restaurant apps - POS app - kitchen display - waiter app ## In the product ### [Point of Sale & Orders](https://gosufra.com/en/features/restaurant-pos/) Explore ### [Kitchen Display System](https://gosufra.com/en/features/kitchen-display-system/) Explore ### [Tables, QR & Reservations](https://gosufra.com/en/features/table-management-and-qr-ordering/) Explore ## Run all of this from one system POS, kitchen, inventory, recipe costing, staff and accounting — connected, and free to start. [Create your free account](https://app.gosufra.com/register?lang=en) ## Related articles ![Illustration of stacked screens sharing one system](https://gosufra.com/blog/what-is-a-restaurant-operating-system.svg) How it works 2026-09-01 · 8 min read ### [What a restaurant operating system is — and why a POS is only part of one](https://gosufra.com/en/blog/what-is-a-restaurant-operating-system/) A POS records the sale. A restaurant operating system records the sale and everything the sale sets in motion: the kitchen ticket, the stock, the plate cost, the wage and the journal entry. Read article ![Illustration of live kitchen tickets with a done tick and a prep timer](https://gosufra.com/blog/kitchen-display-system-explained.svg) Kitchen 2026-08-29 · 7 min read ### [The kitchen display system, explained: stations, priority lanes and prep timers](https://gosufra.com/en/blog/kitchen-display-system-explained/) What a KDS actually replaces, how tickets reach the right station, what Rush and VIP lanes are for, and why prep timers change kitchen behaviour more than any rule posted on a wall. Read article ![Illustration of a key beside a tree of permissions](https://gosufra.com/blog/roles-and-permissions.svg) How it works 2026-08-25 · 7 min read ### [Nine roles, one system: who can see and do what](https://gosufra.com/en/blog/roles-and-permissions/) How role-based permissions work in practice, why a branch manager should not see another branch, and what an audit trail is actually for when something goes missing. Read article [← All articles](https://gosufra.com/en/blog/) [Contact us](https://t.me/GoSufraSupport)