Skip to content
MasaKasa

Should staff take orders on their own phones?

3 min read

Short answer

Yes, if your till runs in a browser and staff sign in with their own code. It saves buying handheld terminals and makes adding a new starter free. Agree it with your team first, make sure your Wi-Fi reaches every table, and keep a shared device or two for anyone who would rather not use their own phone.

Handheld ordering terminals are one of the larger lines on many EPOS quotes. Meanwhile every member of staff already carries a capable touchscreen computer in their pocket. It is a reasonable question whether you need to buy more.

What makes it possible

Two things have to be true.

The till runs in a browser. If staff can open a web page and take an order, there is nothing to install on their phones and nothing that depends on whether they use an iPhone or an Android.

Everyone signs in as themselves. A personal code means the till knows who took each order, and someone who leaves can be removed in seconds without touching their phone.

If either is missing, staff phones become awkward quickly.

The case for

It costs nothing per person. A new starter is ready the moment they have a code.

People are fast on their own phones. They know the screen, the keyboard and the size.

Nothing to charge, lose or replace. Handsets on a shared shelf have a habit of being flat at the start of service.

It scales with the day. Two extra staff on a Saturday means two extra ordering devices at no cost.

The case against

Not everyone wants to. Some staff do not want to use their own phone for work, and that is a fair position. It is a people decision, not a technical one.

Battery and data. A phone used all shift needs a charger in the staff area. If your system works over your own Wi-Fi, it does not use their mobile data, which is worth checking.

Distraction. A personal phone in hand during service also has messages on it. Most teams manage this fine; some prefer a clear rule.

Old phones. Very old devices may not run a modern browser. Check the minimum version your system needs before you promise it will work for everyone.

What to agree with your team first

  • That using their own phone is a choice, and what happens if they choose not to.
  • That the till does not install anything and cannot see anything else on the phone.
  • How they sign in and out, and what happens to their access when they leave.
  • Where to charge a phone during a long shift.

Saying these things out loud before day one avoids most of the awkwardness.

A sensible middle ground

Many cafés end up with both. Staff who want to use their own phones do, and one or two shared devices live behind the counter for anyone who prefers not to, or whose phone has died. That keeps the saving without forcing anyone.

Check the Wi-Fi before anything else

The commonest problem is not the phones at all. It is the signal at the table by the window or out in the garden. Walk the room with a phone before service and try loading a page at every table. If one spot struggles, a second access point usually costs less than one handheld terminal.

Where MasaKasa sits

MasaKasa runs in the browser, so staff use the phones they already have. Each person signs in with their own code, nothing is installed on the phone, and a new starter costs nothing in hardware. It needs a modern browser: Chrome 111 or later, Safari 16.4 or later, or the equivalent, which almost every phone from the last few years has. Waiters see what they need to take orders and nothing they do not.

The short version

Staff phones work well when the till runs in a browser and everyone signs in with their own code. Agree it with your team, keep a shared device for anyone who prefers it, and walk the room checking the Wi-Fi before you rely on it.