Real-world experience with Android handheld POS + built-in thermal printer for restaurant automation?

Hey everyone,

I’m building a restaurant automation system and I’m looking for real-world experience with Android handheld POS devices / all-in-one devices that have a built-in thermal printer.

This is not about a simple chatbot or a theoretical setup. I’m trying to find the most reliable and low-maintenance hardware approach for real restaurant operations.

Use case: Restaurant orders come in through WhatsApp and/or an AI phone agent. The order is then processed by an automation/backend.

The restaurant staff should see the incoming order on a dedicated Android handheld POS device or Android tablet and then quickly:

accept the order
reject the order
select a preparation time, for example 20 / 30 / 45 minutes
trigger or receive an automatic kitchen ticket print
avoid duplicate printing on retries
keep the process simple enough for non-technical restaurant staff

The goal is that the restaurant-side flow feels similar to the way delivery platforms handle incoming orders: the device alerts the staff, the staff accepts/rejects, selects the preparation time, and the kitchen ticket prints automatically.

Important architecture point:I do not want the backend/n8n to print directly to a local printer IP inside the restaurant network.

The device should act as a client.

The architecture I’m considering is:

backend / automation creates order → restaurant device receives or pulls the order → staff accepts/rejects and selects preparation time → backend creates print job with a dedupe key → device prints through native printer access / SDK / ESC/POS → device sends printed/failed acknowledgement back to the backend.

Preferred technical direction:

cloud/server-side backend
device connects outward via HTTPS polling, WebSocket, push notification, MQTT, or similar
no router port forwarding
no VPN/tunnel dependency as the standard setup
no local public API on the tablet
no fragile local IP hacks
print jobs should be pulled or received safely by the device
print jobs need dedupe / acknowledgement logic
if the device restarts, it should recover cleanly
ideally kiosk mode or app pinning
ideally app auto-start after reboot
ideally printer status / paper-out / print failure detection

What I’m trying to figure out:Has anyone here used Android handheld POS devices with integrated 58mm thermal printers for something similar?

I’m especially interested in devices like:

SUNMI V2s / V2 Pro / V2s Plus
iMin Swift / iMin M2
Urovo handheld POS devices
PAX Android SmartPOS devices, if custom APK access is possible
MUNBYN Android POS
H10P / Senraise / Hosoton / similar OEM handheld POS devices
or any other Android handheld POS device with a reliable built-in printer

I am not looking for marketing claims. I’m looking for what actually works in practice.

Questions:

Which handheld POS device did you use, and would you buy it again?
Did you run a native Android app, a PWA in the browser, or a WebView-based app?
Could your custom app access the built-in printer directly?
Did printing work through a vendor SDK, ESC/POS, Android service, raw commands, or something else?
Was the built-in 58mm printer reliable enough for kitchen/order tickets?
Could you detect print success, print failure, paper-out, or printer errors?
Did you have problems with Android sleep mode, Wi-Fi reconnect, app restart after reboot, or kiosk mode?
Did you use polling, WebSockets, push notifications, MQTT, Firebase, or another pattern to get orders onto the device?
How did you prevent duplicate tickets when the backend retried a job?
Would you recommend handheld all-in-one POS devices, or is a tablet + separate LAN/WLAN printer more reliable in practice?
If you used a PWA/browser-based interface, how did you handle printing reliably?
If you used a native Android app or print bridge, how much extra development effort was it?