How does a table order reach the kitchen?
Guests review and confirm their order, and your team receives a table ticket on the staff screen. Staff confirm the first order, move it to In kitchen and mark it Served when the food reaches the table.
What happens to one order from start to finish?
At fictional Casa Olivo, table 12 orders one Grilled Chicken. Follow the first order from the guest’s review through staff confirmation, preparation and service, with the table and status visible at each step.
Fictional example: Casa Olivo, table 12
Review and Confirm
The guest chooses from the menu or orders by chat, reviews the cart and taps Confirm on the order card to send it.
Awaiting staff
Table 12's first order appears on the main and kitchen screens, ready for a staff member to check and accept.
Confirm → In kitchen
Staff select Confirm. The ticket moves to In kitchen, and the table is confirmed for later guest orders.
Served
When the dish reaches table 12, staff select Served. The guest's order view shows Served too.
Who works from which screen?
The main staff screen groups tickets under Awaiting staff, In kitchen and Served. The kitchen screen shows waiting orders and orders in the kitchen, with quantities, dish names, selected options and notes. Prices stay out of the kitchen view, so the team can focus on the food to prepare.
The floor screen brings together waiter calls, check requests and table management. Staff use Ack to acknowledge a service request. For food orders, Confirm moves a waiting ticket into the kitchen, and Served records that the food has reached the table. Each action gives the team a clear way to record its work.
Does every order need staff confirmation?
The first confirmation also confirms the table. Later guest orders at that table can go straight to In kitchen, so an additional dish can join the kitchen's tickets without repeating the first-order step. Show your team both routes before service: a first order and another dish from the same table.
If an awaiting order cannot be accepted, staff can select Reject. For an order already in the kitchen, staff can mark an individual dish Out of stock; that rejected dish is excluded from the bill. Keep the guest informed of the change and help them choose an alternative.
How do staff and guests follow progress?
Guests see the order status update on their phone as staff confirm and serve the order. The chat can explain that status in the guest's language. Staff record the progress as it happens, giving both sides a shared view of where the order stands.
Staff can enable phone notifications on a supported device. An alert prompts the staff app to load the current board; staff still use Confirm or Served to record their action. Assign someone to watch the tickets throughout service.
What should your team try before service?
Decide who confirms the first order, who reads the kitchen screen and who marks food Served. Walk through table 12 together, then add another dish and request a waiter. The order workflow uses staff screens; POS and printer connections are not included. Use your own menu in the demo to see how the screens fit your kitchen and floor routine.