Expo

Expo is a third operational screen next to the kitchen (KDS) and POS: the workstation for the person at the pass who hands ready orders to couriers. Open Admin Panel → "Handoff (Expo)" — that is exactly what the sidebar item is called.

The screen solves a very concrete problem: six bags on the shelf, three couriers at the door — who takes which bag?

The handoff queue#

The screen shows pickup/delivery orders in the "ready"/"awaiting pickup" status — that is, after the kitchen but before being handed to a courier. Each order card shows:

• a channel badge — Glovo / Wolt / Yandex Eda / own website / own courier, detected automatically from the order source;
• the courier's name and phone, once assigned;
• an ETA (estimated courier arrival time) or a "courier has arrived" highlight;
• time elapsed since the order became ready — so you can see which order is already getting cold;
• a one-line order composition summary.

Cards are sorted by courier ETA (soonest arrival on top), falling back to arrival order (FIFO) when ETA is unknown.

Handing an order to a courier#

When a courier picks up the order, expo staff mark the handoff with one tap:

• for own delivery — the order moves to "delivering" status (the same transition as in Own Delivery);
• for aggregators (Glovo/Wolt/Yandex Eda) — the card is marked as locally handed over and drops off the queue; the aggregator itself confirms the actual pickup on its side.

Updates arrive live via WebSocket, with a polling fallback in case of a dropped connection — the same as on the kitchen screen.

If the location has an external courier service connected, an own-delivery order card carries a "Call a courier" button — a courier can be summoned right from the pass, without switching sections. No service connected means no button; aggregator and pickup orders never show it either. See Own Delivery.

Printing the manifest and bag stickers#

Two documents print from the handoff screen — both through Cenaly Hardware Bridge:

• the bag manifest — a slip inside the bag with the order contents: order number, channel, guest name, items with quantities and an "Items: N" total. Courier and guest check completeness against it, and a "you didn't pack an item" dispute with an aggregator is closed with printed evidence;
• 60×40 stickers — labels for the bag and for individual boxes, so bags don't get mixed up between couriers.

If there is no bridge, the manifest prints through the browser. Printing details, the job queue and code pages — Kitchen and front-of-house printing.

In the current version the manifest prints item names and quantities; modifiers ("no onions", "oat milk") go onto the item sticker printed by the kitchen when a ticket is bumped to "ready".

Fullscreen mode#

Like KDS, the Expo screen is designed for a monitor that stays on at the pass:

• fullscreen mode and screen wake-lock;
• a sound chime when a new order arrives in the queue.

What you need to get started#

• A tablet or monitor with a browser — the handoff screen opens next to the shelf of ready orders.
• Pickup and delivery orders — expo shows exactly those.
• Ready station tickets — assembling an order builds on item readiness from the kitchen display.
• The bridge and a printer — for bag labels and the shift manifest (Printing).
• A secure connection (HTTPS) — the handoff code is computed with browser cryptography and is simply not shown over plain http.

Limitations#

• Dine-in orders do not enter the expo queue. They are marked handed over with the "Given to the customer" button in the order details — a hall mode ("handing over to a server by table") on the handoff screen itself is planned but not built.
• Only orders in handoff statuses and without a handover mark are shown — earlier statuses live in Orders and on the kitchen display.
• The list of aggregator channels is fixed (Glovo, Wolt, Yandex Eda); "own courier" is detected by the presence of a courier name.
• The screen is a cloud surface — it does not work without the internet (If the internet goes down).

Troubleshooting#

An order is missing from the queue. It is either dine-in, or has not reached a handoff status yet, or is already marked as handed over.

The handoff code chip is not visible. The screen is open over an insecure connection — open it over https.

A bag label does not print. Check the bridge and the selected label printer; labels are currently printed as a raster on a receipt printer.

A courier took the wrong bag. That is exactly what the handoff code and handover confirmation are for — make them part of the shift routine.

Related sections#

• Kitchen (KDS) — the kitchen screen an order comes from before reaching the expo queue
• POS — order intake and payment
• Own Delivery — the venue's own courier screen
• Kitchen and front-of-house printing — manifest, stickers and the print queue

FAQ#

Is Expo useful if the venue only has its own couriers?#

Yes — the screen is useful anywhere there's delivery or pickup. It shows both your own couriers and aggregator couriers on one screen, which helps with a mixed delivery channel.

Do dine-in orders show up on Expo?#

No, the screen only collects pickup and delivery orders — dine-in orders are handled through POS and the kitchen without a courier handoff.

How does the screen know an aggregator courier's ETA?#

ETA and courier data come from the order data, updated via the aggregator's webhooks, or from own-delivery data — Expo simply displays it.