Orders arrive by hand.
With paper, the items reach the kitchen only after someone carries the note there.
Soup, hot meals or snack platters: Bierblock shows the kitchen the food items assigned to its station. Drinks go to the bar. The kitchen team moves each item from Open to In progress and marks it ready. Ready means prepared, not collected or paid. Agree with the service who collects the food. The devices need a connection for the shared view.
The Problem
Kitchen and bar may be apart, so a shared status can help the teams coordinate.
With paper, the items reach the kitchen only after someone carries the note there.
Without a shared view, it is harder to see which recorded portions remain open.
Without separate steps it is unclear whether a dish is only prepared, already with the guest or already paid.
The Solution
The kitchen sees only the food items assigned to its station in the browser. An incoming round appears in the Open column; the team moves it to In progress and marks it ready. Drinks run through the bar, and service confirms collection separately.
The kitchen signs in with its configured station access and lands directly on the monitor. Event management sets up the station and product assignment beforehand.
“Prepare” starts the work, “Mark ready” finishes preparation. The status says nothing about collection or payment.
Service confirms collection at the table; checkout is a separate step. The kitchen sees its food, the bar its drinks.
The kitchen opens its configured station access in the browser and lands on the monitor. Event management has assigned the food items to the “Grill” station; drinks do not appear there. Order no. 1 for table 41 sits in the Open column: 1× Berner Würstel Pommes and 1× Kasnudel Salat.

After “Mark ready”, preparation is complete. Service sees the Kasnudel Salat from the same order under “Serve” and confirms collection there. “Checkout” is another separate step. The kitchen status alone does not say whether the food has reached the guest.

The station analytics show the quantities and order values recorded for the kitchen in the example. These are ordered quantities, not a measure of portions actually handed out, consumption, profit or team performance. For the debrief, compare them with your own notes.

Benefits at a glance
Fictional rehearsal: A table orders soup and two drinks. The soup is assigned to the kitchen and the drinks to the bar. After submission, the kitchen team checks whether the soup appears at its station, moves it to In progress and then marks it Ready. Service confirms collection at the table; checkout is a separate step. If the soup is missing at the station, the responsible person checks product assignment and connection before anyone re-enters the same order. This is a test workflow, not a customer story.
Frequently asked questions
Everything about setup, usage and costs.
Ready?
Open the public demo to explore order taking, the kitchen and the bar. No account is needed. To prepare your own setup, start a test event afterwards.
Start without an account. Register to save. Your own demo events allow up to 20 test orders.
See pricing