Setting Up Order Tablets for Restaurants Without an IT Person

A restaurant order tablet needs to do one thing reliably during the busiest ninety minutes of the day, and come back by itself when the power flickers. That is the entire specification. Everything in the setup should serve it.

The configuration is kiosk mode, screen always on, and a recovery path that does not require anyone to know a password during service.

Start by counting the device types

Most small restaurants have more than one kind of tablet and treat them all the same, which is where the mess starts.

Counter or till tablets run the ordering or point-of-sale app all day. Fixed position, mains powered, used by staff.

Customer-facing tablets, if you have self-order or a feedback screen. Same lockdown, higher hostility, needs physical security.

Kitchen display screens running a ticket app. Usually never touched, and the most sensitive to a reboot loop.

Manager or back-office devices doing rotas, stock and reporting. These are not kiosks and should not be configured as one.

Three groups covers it: counter, kitchen, back office. Attach policy to the group rather than to each device, so replacing a broken tablet is one action.

The kiosk configuration

One app, no launcher. The tablet boots into the ordering app and cannot leave it. No home screen, no browser, no store, no settings. This is the difference between a tool and a tablet that slowly fills with games.

Screen stays on while charging. The most common complaint about a new counter tablet is that it keeps going dark mid-order. Set it to stay awake while powered, and make sure it actually is powered.

Automatic return after a reboot. Power cuts happen in kitchens. The device must come back into the app with nobody typing anything. Test this by pulling the plug before it goes into service, not after.

Volume and brightness left available, if useful. Kiosk does not have to mean everything is locked. Kitchen staff adjusting screen brightness is fine; kitchen staff reaching wifi settings is not.

Only approved apps installed. If the tablet needs a payment app as well as the ordering app, allow both. Keep the list to two or three; past five you are building a general purpose device with extra steps. The trade-offs are in our kiosk guide.

The things that break during service

Wifi. The most common cause of a dead tablet is not the tablet. Put the tablets on a separate network from the guest wifi, so a full dining room does not slow your tills. If your ordering app works offline and syncs later, confirm that rather than assuming.

Updates at the wrong time. Set the maintenance window overnight. An app or system update at seven in the evening is a very bad ninety seconds. Note that no Android device management can force an OS update on demand; you are choosing a window, not pressing a button.

No exit route. Somebody needs to get out of kiosk mode to troubleshoot. Decide who, make sure at least two people on any shift can do it, and do not write it on the back of the tablet.

Nobody owning it. Counter devices are shared, which means nobody notices when one stops checking in. A weekly look at the device list catches the tablet that has been dead in a drawer since Saturday.

Front of house versus back office

Do not give the manager a kiosk device. Back-office work needs a normal managed tablet: enforced screen lock, an approved app list, encryption, and remote lock and wipe if it goes missing.

That device probably holds supplier details, staff information and sales reports, which makes it the most sensitive device in the restaurant despite looking like the least interesting one. Treat it accordingly.

Physical security

Kiosk mode stops somebody using the tablet for something else. It does nothing about somebody walking out with it.

Stands and tethers for anything customer-facing. For staff tablets, a routine of putting them somewhere specific at close, and a quick count.

Have lost mode set up in advance with a lock screen message and the restaurant’s number. A tablet that leaves should be unusable and obviously yours.

What to do this week

1. Pull the plug on one tablet and watch what happens when it boots. If it needs a person, fix that before the next busy service.
2. Check the screen timeout on every counter device. This is the complaint you are already hearing from staff.
3. Look at your device list and find the tablet that has not checked in for a week. There usually is one.

FAQ

Can staff get out of the ordering app?

Not in kiosk mode. The launcher is replaced and settings are unavailable. Leaving requires an administrator action, which is why at least two people per shift should know how.

What happens when the internet goes down?

The device stays in kiosk mode, because the policy is applied locally. Whether orders still work depends on your ordering app, which is worth asking your provider before you need to know.

Can I use cheap tablets?

Yes, provided they run Android 8 or newer and support Android Enterprise. Check before buying a batch, because the cheapest tablets sometimes ship with a version too old to enroll.

Do I need a separate tablet for card payments?

That depends on your payment provider, and it is their rules rather than a device management question. Ask them before combining ordering and payment on one device.

How many tablets before this is worth it?

Two. The saving is not really security; it is that both tablets are identical, come back after a power cut, and cannot be turned into something else.

A counter tablet that always works and always comes back is worth more to a restaurant than any security feature. Kiosk mode is mostly how you get there.

See the restaurants and retail setup, or start a free trial.