Kitchen Display System Setup Guide

I make MenuMog. This is how its kitchen display is set up, what it does during a service, and what it does not do. An earlier version of this post described printers, stations and settings MenuMog does not have; this one describes only what is there.
What the kitchen display is
A web page. It lives at menumog.com/kitchen/your-venue, it opens in any browser, and it shows the orders your staff send, as they send them. There is nothing to install, no box to buy and no printer to pair.
The other half is the ordering page, menumog.com/order/your-venue, which your staff open on their own phones. They pick a table, tap the dishes, and send. Guests do not order through MenuMog: the QR code on the table gives them the menu to read, and your staff take the order as they do now.
What you need
- A screen for the kitchen: a tablet, a laptop or a small computer with a screen, anything with a current browser.
- A stand or a wall mount, somewhere it can be seen from the pass and will not be splashed.
- Power, not battery. It runs all service.
- Wi-fi that reaches the kitchen. Orders arrive over the internet; this is the one thing to test before anything else.
Setting it up
- Create a venue. In MenuMog, under Venues: a name, the number of tables, and a PIN of four to six digits. The venue gets its two addresses, one for ordering and one for the kitchen.
- Open the kitchen address on the kitchen screen and enter the PIN. The screen stays unlocked for the day; after sixteen hours it asks for the PIN again.
- Make it a screen, not a tablet. Turn off sleep and auto-lock, put the browser in full screen, and on a tablet turn on its kiosk or guided-access mode so a stray elbow cannot swipe the orders away.
- Give your staff the ordering address and the PIN. They open it on their phones once and are ready.
During service
A new order appears on its own, with a short beep, a moment after a server sends it. Nobody refreshes anything. Each order shows its table, its dishes and quantities, and the notes the server added, on a dish (no onions) or on the whole order.
The kitchen moves each order along: pending, confirmed, preparing, ready, completed, or cancelled. A single dish can be moved on its own, for when the soup is ready and the mains are not. Servers can add another round to a table that already has an open order, and it arrives as part of the same order.
Test it before the first real service
Hand two people a phone each, give them the ordering address, and have them send a dozen orders in a couple of minutes while someone works the kitchen screen. You will find out whether the wi-fi holds in the kitchen, whether the screen is where people look, and whether the beep is loud enough over the extraction fan. Fix those three, and the setup is done.
What it does not do
- No printer. MenuMog does not print tickets. The screen is the ticket.
- No till, no payments. It does not connect to your POS, and nobody pays through it. If your till already sends orders to the kitchen, running both means entering an order twice: decide which one the kitchen follows.
- No stations. Every kitchen screen of a venue shows every order. Two screens are two views of the same list, not a grill screen and a salad screen.
- One PIN per venue, not a login per person, so there is no record of which server sent which order.
- No offline mode. If the kitchen loses the internet, new orders do not arrive until it is back.
What it costs
Nothing today. MenuMog is free while I build it out, the ordering system included; it is badged as part of a paid tier planned for later, and I have not set that price. The kitchen display guide on the site has the same steps with pictures of the screens.
Share this article
Ready to create your digital menu?
Join restaurants and cafes using MenuMog for QR menus, ordering, and more.
Get started free