Your Floor Staff Stop Walking Back to the Terminal
RestioX Staff App lives at /staff-app and installs to a phone’s home screen straight from the browser. Waiters take orders at the table, cashiers run refunds and voids with a manager PIN, the kitchen 86s an item and every phone on the floor knows before the next order goes in.
0
App-store submissions. Staff open a link and add it to the home screen
11
Staff surfaces in one install — orders, money, attendance, handover, chat, 86s, alerts, deliveries
100%
Of money actions re-checked server-side against the signed-in role, never trusted from the phone
1 tap
To revoke a lost phone — that device is signed out and stops receiving orders
Service is won on the floor, not at the till
A waiter who has to walk to the terminal to add two glasses of wine is out of their section for a minute, twice a table, all night. The order reaches the kitchen late, the guest waits longer than they should, and half the time the upsell is quietly dropped because it was not worth the trip. The staff app puts the order screen, the money screen and the kitchen’s 86 list in a pocket, so the decision and the action happen in the same place.
- Take a brand-new order at the table, or add items to one that is already open
- Fire straight through to the kitchen — nothing gets re-keyed at the terminal afterwards
- Cashiers refund, discount, void and reverse a drawer entry without leaving the guest
- Clock in and out from the phone, and leave a written handover for the next shift
- The kitchen marks an item 86 and every phone on the floor sees it in seconds
- Push notifications for new and changed orders, so nothing sits unread on an unwatched screen
It is one progressive web app, served from your own RestioX installation. There is no separate build for Android and iPhone, no store review to wait on, and no version stuck on the one handset nobody remembered to update.
One install, every job the floor actually does
-
Order taking, at the table
Open a table, build the order from the live menu with modifiers and kitchen notes, and send it. Or pull up an order that is already running and add tonight’s second bottle to it without reprinting the whole ticket.
-
A real cashier surface
Not a cut-down version of the till. Full and partial refunds, discounts, voids on lines that have already gone to the kitchen, and cash-drawer reversals when a payment was rung to the wrong tender — each one permission-gated and recorded.
-
Attendance and handover
Clock in and out on the phone, and write the handover the next shift reads before they start.
-
Kitchen 86 updates
The pass marks a dish unavailable and the floor is told at once, instead of after a table has ordered it.
-
Chat and emergency alerts
Staff-to-staff messages for the ordinary things, and a one-tap alert that reaches everyone on shift for the ones that cannot wait.
-
Deliveries, assigned to a person
Delivery staff see the runs that are theirs, with address and contents, and mark each one off as it leaves and lands.
The order is taken where the guest is sitting
The waiter view opens on the section, not on a menu tree. Tap the table, tap the dishes, add the modifier the guest just asked for, send. Items the kitchen has 86’d are already greyed out, so nobody promises a sea bass that ran out ten minutes ago. What has been sent and what is still a draft in your hand are visibly different, which is the difference between a double-fired round and a clean ticket.
- Pick items from the live menu with modifiers and free-text kitchen notes as the guest speaks
- Add a round to an order that is already open and fire only the new lines
- Sold-out items are greyed out the moment the kitchen 86s them
- A waiter’s device can take and extend orders — and nothing on the money side
Mains out
Adding
Free
Ordering
Bill due
Free
The money screen goes to the table too
A guest disputing one dish on a four-cover bill does not need to be walked to the counter. The cashier surface handles the correction where the conversation is happening: refund the line, apply the discount, void what should never have been fired, or reverse the drawer entry when a card payment was rung as cash. The guest watches it resolved instead of watching someone disappear behind a terminal.
- Refunds against the original payment, full or partial, line by line
- Discounts on a single line or the whole bill, inside the limits the role allows
- Voids on lines that have already gone to the kitchen, with the reason recorded
- Cash-drawer reversals when a payment was taken against the wrong tender
Every money action is re-checked on the server by an order-build guard and the staff member’s role permissions before a cent moves. A waiter’s device cannot perform a cashier’s action even if someone gets clever with it, and the actions you consider sensitive can be set to demand a manager PIN entered on the spot.
Give the floor its hands back
The staff app ships with RestioX. Start a trial and you can have a phone working the pass tonight.
What each person sees when they sign in
Roles are yours to define — every row below is a separate permission you can grant or take away. This is how most kitchens set it up on day one, and it is enforced on the server rather than in the screens.
| Action | Waiter | Cashier | Kitchen | Manager |
|---|---|---|---|---|
| Take a new order at the table | Yes | Yes | No | Yes |
| Add items to an order that is already open | Yes | Yes | No | Yes |
| Apply a discount to a bill | No | Yes | No | Yes |
| Void a line that has already gone to the kitchen | No | Manager PIN | No | Yes |
| Refund a payment | No | Yes | No | Yes |
| Reverse a cash-drawer entry | No | Manager PIN | No | Yes |
| Mark an item 86 for the whole floor | Sees it | Sees it | Yes | Yes |
| Clock in and out, and read the shift handover | Yes | Yes | Yes | Yes |
| Raise an emergency alert to everyone on shift | Yes | Yes | Yes | Yes |
| See another branch’s orders, takings or staff | No | No | No | No |
The last row reads the same for every role, managers included. Orders, tables, deliveries, chat, attendance and the money screens are filtered to the branch a staff member belongs to, and that filter lives in the data layer rather than screen by screen — so there is no forgotten view that quietly serves up a neighbouring branch.
The parts of a shift that usually run on shouting
A dinner service is held together by information that never reaches a screen — what ran out, who is on a break, which run is late. These are the surfaces that carry it.
- Kitchen 86 updatesThe pass marks the last portion gone and the floor sees it before the next table is offered it.
- Emergency alertsOne tap reaches everyone on shift at once — a fall on the stairs, a walkout, a fire in the fryer.
- Staff-to-staff chatAsk the bar for a re-pour or tell the host table 12 is clear, without leaving your section.
- Assigned delivery runsDrivers see only their own runs, with address and contents, and mark each one off as it lands.
- Push notificationsNew and changed orders push to the phones that need them, so a modification is never missed.
- Per-device registrationEvery phone that signs in is registered to a person. Lost handset? Revoke it and it goes quiet.
From a link on a phone to a working service
-
1
Minute one
Open the link, add to home screen
Staff sign in at /staff-app in the phone’s own browser and choose Add to Home Screen. It takes an icon next to their other apps and opens in its own full-screen window. No store listing, no review queue, no installer file being passed around on WhatsApp.
-
2
Minute two
The device registers itself
The phone is recorded against that staff member the first time it signs in, so you have a list of exactly which handsets are carrying your order screens. If one goes missing you revoke it from the admin and it is signed out and stops receiving order notifications.
-
3
Before service
Set what each role can reach
A waiter gets order taking. A cashier gets the money surface. The kitchen gets 86 and alerts. The app only draws the buttons a role is allowed, and the server re-checks the permission again when the action actually arrives.
-
4
During service
The floor works from the phone
Orders go in at the table and fire straight to the kitchen. New and updated orders arrive as push notifications. The kitchen 86s the last sea bass and every phone knows. A guest disputes a dish and the cashier refunds that one line at the table, with a manager PIN if your rules ask for one.
-
5
After service
Clock out and hand over
Everyone clocks out from their own phone, so attendance is not a sheet on a clipboard. The outgoing shift writes the handover — what broke, what ran out, which table is coming back tomorrow — and the next shift reads it before they touch a table.
Where the phone earns its place fastest
Busy dine-in floors
Sections spread over two rooms and a terrace, where the terminal is always the wrong side of the room. Waiters keep their tables in view and rounds land in the kitchen while the guest is still deciding on dessert.
Multi-branch groups
One app, one sign-in, and staff who only ever load their own branch’s data. Roll a new site out by sending a link to a group chat instead of scheduling an install day.
Delivery-heavy kitchens
Riders pick up their assigned runs on their own phones, with address and contents in front of them, and mark each drop off as it happens instead of calling the pass for an update.
The things restaurateurs ask before they hand out phones
No. The staff app is a progressive web app. Staff open /staff-app in the phone’s browser, sign in, and use Add to Home Screen. It gets its own icon and opens full-screen like a native app. Because it is served from your own RestioX installation, an update reaches every phone the next time it is opened — there is no store review to wait on and no version stranded on somebody’s handset.
Not unless you have granted that permission. Money actions are checked on the server by an order-build guard and the signed-in staff member’s role, not by the phone. If a waiter’s device asked for a refund, the server would refuse it. Sensitive actions can additionally require a manager PIN entered on the spot, so approval is a deliberate act by a named person.
Every device registers itself against a staff member the first time it signs in, so you have a list to work from. Revoking a device signs it out and stops it receiving push notifications for new and updated orders. Disabling the person’s account closes every device they hold at once.
No. The app is branch-scoped throughout. Orders, tables, deliveries, chat, attendance and the money screens are all filtered to the branch a staff member belongs to, and that filter lives in the data layer rather than in each screen, so there is no view that quietly leaks a neighbouring branch.
No. The kitchen marks the item 86 in the app and every staff phone picks the change up, so a waiter sees the dish is gone before they offer it. Emergency alerts work the same way — one person raises it and everyone on shift is told at once, instead of the message travelling table by table.
Any modern phone with a current browser, Android or iPhone, and tablets too if you prefer a larger screen for the cashier surface. Because it is a web app there is no minimum OS version to chase and no separate build per platform, so most restaurants run it on the devices staff already carry.
Put the till in your team’s pocket
Start a free trial, open /staff-app on one phone, and run a single section from it tonight. If it saves your waiters the walk, roll it out to the rest of the floor tomorrow.
Start Free Trial