A handheld POS is a device a server carries, so the order goes in at the table rather than at a station across the room. It is one of the few restaurant technology purchases whose benefit is easy to state and easy to measure.
It also does not suit every dining room, and the failure cases are worth knowing before you buy six of them.
What it actually changes
The walk disappears. Without one, a server takes the order, walks to a terminal, queues behind another server, enters it, walks back. Those trips are the single largest use of a server's time in most dining rooms.
The kitchen starts sooner. Sending from the table rather than from the station is typically a couple of minutes earlier per course. Across a service that compounds into meaningfully faster turns.
Fewer transcription errors. An order entered while looking at the customer is more accurate than one entered from memory or a scrawled pad. Modifiers especially — no onions, allergy notes, temperatures.
Payment at the table. The customer never waits for the bill to be fetched, taken away and brought back. That last stretch is often the slowest part of a meal and the most common complaint.
Where the benefit is real
Large rooms, where the walk is long.
High-turn service, where two minutes a table compounds.
Patios and multiple floors, where the walk is not just long but genuinely disruptive.
Anywhere paying at the table matters — either for speed, or because you would rather the card never leave the customer's hand.
Where it does not pay
Small rooms. If the terminal is six steps away, the saving is close to zero and you have added devices to charge, drop and replace.
Rooms where the menu is complex and the screen is small. A long menu with many modifiers on a small handheld can be slower than a full terminal, not faster. Test yours.
Where the wifi does not reach. This is the most common real failure and it is not a POS problem. A handheld is only as good as your coverage in the corners of the room, on the patio, and by the back wall on a full Saturday. Survey it before you buy, not after.
The practical questions
Battery. Does it last a full double, or does someone have to swap mid-service? Ask about real-world hours, not the spec sheet.
What happens when it drops out of coverage? Does the order queue on the device and send when it reconnects, or is it lost? A handheld that silently loses an order is worse than a pad.
Does it take payment, or only take orders? Some do only the first, which removes half the benefit.
What does it cost per device? And is there a per-device software fee on top, which is common and turns six handhelds into a significant monthly line.
How are they charged and stored? Unglamorous and the reason handhelds end up in a drawer six months later.
The honest test
Do not evaluate it on a demo. Run one device, one section, one week.
Measure two things: average table turn time in that section against a comparable one, and the number of order errors. If the turn time does not move and the errors do not fall, more devices will not help.
Most restaurants that do this find the benefit is real but concentrated — one or two sections where the walk is long, rather than every server carrying one.
The gap a handheld does not close
Handhelds make service faster for people already seated. They do nothing for the people trying to reach you.
Your phone rings hardest during exactly the service a handheld is speeding up, and for most restaurants those calls are reservations. A faster turn plus a ringing phone is a restaurant that seats its existing guests efficiently while losing the next ones.
Sonorch puts the register, the handheld side of service and something that answers the phone into one system, which is how we think about that gap. Sonorch POS has the detail, and the pricing page is priced by team size rather than per device.