The waiter sets down a tray, folds a napkin in half, and starts walking toward the pass with a scrap of paper. Table 12 changed the sauce after the first ticket had already gone in. The kitchen will hear it in person, or it will not hear it at all. A restaurant system for waitstaff that looks polished in a deck, then requires that walk, is not running the floor. It is adding a messenger between the table and the pass.
The dining room does not need “more automation” as a slogan. It needs the modifier and the second round to reach the line without a courier.
The note in the waiter’s pocket
Table service happens in short bursts. A guest asks for a side. The waiter has to capture it before leaving the chair. The kitchen has to read it without ringing the floor. Someone at the pass has to know a plate is ready before the guest flags the next person who walks by.
Start with one Saturday table, not a price grid. Walk-in or reservation, open check, first courses with a comment, send to kitchen or bar, status, another round, split bill, close. If the software only rings items well, the rest returns to a notebook and a chat thread. The mess is rarely “in the POS.” It lives in the gap between what the waiter heard and what the line saw.
How OrderNow works describes a path from table and QR menu to the kitchen. Use it as a reference, not a claim that every floor runs the same way.
Where a feature-rich screen still slows the floor
A long module list does not save a waiter who cannot find the variant. Friction usually is not a missing tile. It is a tile that does not match the pace of the shift.
| Moment | What breaks the rhythm | What should stay in the system |
|---|---|---|
| At the table | hunting a variant, writing on a pad | dish, modifier, and comment in one capture |
| On the way to the kitchen | a note, a call, a sauce question | a complete queue or print, no guesswork |
| Second round | new items as a separate mess | add to the same table and check |
| The pass | the floor does not know what is ready | a visible stage, not a rumour through a door |
| The bill | discount and split take longer than dessert | a clear check and a closed table |
On a full floor those small delays stack into late mains and a tense pass. Waiters should not learn how to outwit the screen. They should leave the table with what the guest actually ordered.
Courses, modifiers, and the round that comes later
A better flow starts with fewer places where someone has to add information by voice.
The waiter opens the table on the live menu. No onion, extra sauce, and “dessert later” go in immediately. Kitchen or bar see items in a queue the shift actually understands. Status returns to the floor before the guest grabs a passer-by. The next round does not split the check into two worlds. After service the manager sees where voids happened, not only turnover.
A small room with a short card may live on a waiter panel and a clear send. A larger floor more often needs a kitchen display, because “did it go?” multiplies with table count. A QR menu does not have to mean self-ordering. It can show the guest a current card before the waiter arrives. The phone view still has to match what the kitchen will cook.
Reservations help when they show occupancy, not only a list of names. A shift report should say which hours jammed the room and where corrections clustered. Revenue alone will not.
Compare the wider module map on OrderNow features. A hotel restaurant, a casual room, and a small dining room do not share the same priority. Formats: industry solutions.
What belongs in month one, and what is not in every plan
Turning everything on at once sounds efficient until the team has private shortcuts and the card disagrees between floor and line. Then start with tables, the waiter panel, and a current menu. Next, a kitchen queue or a calmer pass. Reservations, richer reports, and extra channels once the first path no longer needs paper.
OrderNow splits scope by plan. Start includes a QR menu, KDS, waiter panel, reservations, menu editing, and basic reporting, among other items. Direct online, delivery, sales engine, loyalty, coupons, inventory, and deeper analytics sit in Pro. Direct online is not part of Start. If you need an owned ordering channel from day one, read pricing before you train the floor.
If names on the card drift, waiters use different dish titles, and the kitchen still asks follow-up questions, new software will only show the mess faster. Align names and ownership of the menu first.
OrderNow fits a room that wants tables, kitchen, and sales in one operational flow instead of a separate app for each slice of the night. A short card is not configured like a large reserved room that also does bar collection. Compare the path from first contact with a table to closing the check, not a “full package” label.
Walk your floor scenario in a presentation. Scope and cost again: pricing.
Questions and answers
If we already have a POS, why is a waiter still walking to the kitchen with a note?
Because a modifier did not fit the ticket, or the line cannot see the same version as the table. A screen that only rings a bill is not enough. The path that matters is table, send, status, second round, settlement.
Does a QR menu fight table service?
It does not have to. In many rooms the code shows the current card and extras while the waiter still runs the table. It fights service when the phone menu lives apart from what the kitchen cooks, or when QR is forced as a replacement for the relationship at the chair.
Is a kitchen display pointless if the line is three metres from the room?
Not if those three metres are already full of sauce questions and “is it up?”. With a short card, few tables, and rare corrections, a screen does not have to be the first move. Physical closeness does not fix an incomplete ticket.
Does OrderNow include online ordering in every plan?
No. Direct online is not part of the Start plan. Scope depends on the plan and modules, so check pricing and match the package to whether the floor should also run an owned online channel.