BUMERANG · RESTAURANT

A system for the noise
in front of the kitchen.

A guest request should not circulate until someone decides it is theirs, and daily checks should not live in anybody's memory. Requests open, land on a department and run against a clock; tasks arrive every morning and are recorded as they are done.

Restaurant daily tasks screen with opening, walkthrough, measurement and safety sections

Guest requests: from QR to the right department

The guest scans the QR on the table and picks what they need. Every request type is bound to a department, so the moment a request opens it lands on that department's screen and on staff phones. Who picked it up, when it opened, how long it has waited — all visible in the list. If a request type is bound to no department, the panel warns you separately: a request nobody can be routed to never disappears quietly.

Daily tasks and checkpoints

The moment you open the module, a ready task template and checkpoint list are created — you do not start from a blank page. Tasks reach the right staff during the day, get ticked off and are recorded. Reports show which task was done on which day and which one was skipped.

  • A ready list with opening, walkthrough, measurement and safety sections
  • Temperature readings with limits: fridge 0–5 °C, freezer −25 to −18 °C, hot line 63–90 °C
  • Photo evidence where you need it, and repeats on the clock (09:00, 12:00, 15:00, 18:00, 21:00)
  • Ticked off in the staff app, reflected in the panel instantly
Restaurant daily tasks screen with opening, walkthrough, measurement and safety sections

The checkpoint board: the whole venue at a glance

Toilets, kitchen equipment, the bar, the dishwash area, the dining room — each one is a checkpoint. The tiles speak in colour: green means fine, orange means something needs doing, red means urgent. Staff tap a tile to change its state; the manager looks at the board and sees where the venue stands right now.

Restaurant checkpoint board with colour-coded status for toilets, kitchen equipment and areas

SLA: let the delay announce itself

You define a time rule per request type. The engine scans open requests every five minutes and notifies the manager when one runs over. Delays surface without anyone having to watch the list.

The report tab keeps the last seven days: every row carries who completed the task, when, and with which reading — and it cannot be deleted. Tasks not done that day are listed separately.

Restaurant task report showing missed tasks and who-when-which-reading records
Request types mapped to departmentsAutomatic or pool-based assignmentSLA time rules and overdue alertsDaily task templateCheckpointsTable call and kitchen display (KDS)Order from the tableStaff mobile app

Staff on the floor, the panel in their pocket

Staff do not have to sit down at a desk. From the staff app they see requests, take them on and close them, and tick off their daily tasks. Managers get a summary on the same screen. When someone is added, a password is generated and sent to them by SMS or WhatsApp — nobody hands out credentials.

Staff app module →

Staff mobile app with requests, tasks and floor view

Setup finishes on one screen

You create the restaurant profile; departments, request types, staff and SLA rules are filled in from the same wizard screen. If the venue has a menu, the QR menu link appears there too. Any unfinished step stays flagged in the list.

The QR menu is part of the same system

The restaurant module runs operations while the QR menu carries sales: guests read the menu in their own language, order from the table and call a waiter. Orders and calls land in the same staff app.

Explore the QR menu →

Bumerang QR menu screen

Try it for a day in your restaurant.

Let us set up your request types and daily task list together in a demo environment.

Frequently asked questions

Does the guest need an app to open a request?
No. The guest scans the QR on the table with the phone camera and picks the request in the browser.
Who does a request go to?
Every request type is bound to a department and reaches that department's staff. You can also enable direct assignment to a specific person; the default is a pool model, where whoever picks it up first owns it.
Do I have to write the daily task list from scratch?
No. When the module is created, a ready task template and checkpoint list are set up for you to edit.
How do I notice delays?
You define a time rule per request type. The engine scans open requests every five minutes and notifies the manager when one runs over.
Are the QR menu and the restaurant module bought separately?
They are parts of the same platform and work together: orders and waiter calls from the menu arrive in the same staff app that carries requests and tasks.