Do I need a tablet per bar?

One screen per bar is the comfortable setup, but any device with a browser works. The screen installs as an app and opens straight onto the queue.

Does it update itself?

Yes. Changes arrive from the database over an open connection, without reloading and without polling. If it drops, it reconnects with spaced retries.

Yes, over USB from the browser with a thermal printer. Failing that, the browser's printable ticket remains.

Module

Anyone can build a list of orders. The hard part is a screen that decides the order of work, warns in time and knows when to stop taking more.

Arrival order, no arguments
The queue is strict by payment time. Each order carries its target and changes colour as it approaches or passes it, with a single audible warning at the crossing.
Several bars, one queue
On arrival each order goes to the bar with the lightest live load. Each screen sees its own; the panel sees the whole.
Rush mode
As orders pile up or several run late, the view compacts itself so more fits without scrolling.
Per-product view
Groups identical lines from different orders. Twelve of the same drink are made in one go and ticked off by units.
Stock and substitutions
Marking something out of stock removes it from the menu at once. Swapping one line for another is recorded on the order.
Capacity brake
With a cap on live orders, reaching it pauses intake and notifies staff. It reopens by itself below 80%, and never lifts a manual pause.

Do I need a tablet per bar?: One screen per bar is the comfortable setup, but any device with a browser works. The screen installs as an app and opens straight onto the queue.
Does it update itself?: Yes. Changes arrive from the database over an open connection, without reloading and without polling. If it drops, it reconnects with spaced retries.
Can I print dockets?: Yes, over USB from the browser with a thermal printer. Failing that, the browser's printable ticket remains.