Glider Garden — how an order flows

From a guest's thumb to paper at the pass — every hop, in order.
📱
1 · The guest ordersTable QR (dine-in) or order.glidergarden.au (pickup). They send item choices only — never prices.
☁️
2 · Your cloud prices itThe server looks up real prices + GST, applies loyalty, writes the order to the tamper-evident log. Card payments confirm with Stripe here.
🔥
3 · Fired to the kitchenThe order appears instantly on the Kitchen Display and the Waiter tablet, and the Today screen counts it.
🖥️
4 · The print bridge picks it upThe mini PC at the café polls the cloud every few seconds and pulls any docket jobs — the cloud never needs to reach into your network.
🖨️
5 · Paper at the passThe bridge pushes the docket to the right Epson (Front / Food / Waiter, per your routing) and confirms back — you can see every printer's last-OK on the Network map.
🗓 Why a booking doesn't print: reservations aren't food. A booking request lands on the dashboard (Today + Reservations) for confirmation and emails the guest — the kitchen only hears about it when the party sits down and orders.