The app offers to turn notifications on by itself — it explains what for, then asks the browser for permission. Permission is granted per device and browser: the waiter's phone, the counter tablet and the kitchen display each subscribe separately.
If it's a bad moment, put the offer off with "Later" — it comes back.
Once permission has been declined, the app can no longer ask — that's a browser rule, not a Qreaty limit. You can only unblock it in the browser's own settings (the lock icon in the address bar → Notifications → Allow), and then come back to the app.
Notifications go out for three events: a guest places an order, an order is ready to run, a guest calls a waiter or asks for the bill.
First of all the system checks whether the table is assigned to a waiter (who serves the table): if the assigned waiter can receive push, the event goes to them alone — nobody else will see it. From there the chains differ slightly per event.
A guest places an order:
An order is ready to run, a waiter call or a bill request:
That way events don't go unseen even in a venue that runs no shifts and assigns no tables: an unassigned table always has the wider circle of recipients.
Tapping a notification opens the recipient's home screen, in the right venue: Orders for a cashier or a manager, Hall with the order's table in focus for a waiter, Kitchen for a cook, its own screen for a shared device. A member with no work screen at all lands on the order card itself (home screen).
{warning} Shifts matter more than they seem: until someone has started their shift, they are not in the first circle of recipients — orders on their tables go to other people (shifts).
{warning} An assigned table "keeps" its notifications to itself. While table 5 is assigned to Minh and Minh is on shift, the push about a new order on table 5 goes to Minh alone — nobody else will see it, even on shift with notifications on. If it looks like "push doesn't arrive", first check whether the table is assigned to a colleague (your tables and other people's).
{info} If nobody has notifications on, no push arrives at all — the order is only visible on the screens. Notification texts still come in English, whatever the interface language.
{info} A shared tablet (the Orders screen at the counter, the Kitchen screen) receives no push: notifications are something a person turns on for themselves, and a station belongs to no one. It does not need them — orders and guest calls are visible and audible right on its screen (calls on Orders).
Each screen listens for its own thing:
A new guest order and a guest call ("call the waiter" or "ask for the bill") sound anywhere in the app — while you edit the menu, while you read the analytics. Whoever takes orders hears them; the kitchen hears its own on its own screen.
Tickets already on the screen stay silent: when a screen opens it simply remembers the state, and only new things sound.
{warning} The browser allows no sound before the screen is first touched. On a tablet that has just been opened or woken up the first alert may not sound — touch the screen and the sound arms itself.
Three cases the app treats as important enough to keep reminding about until somebody reacts. Such an alert sounds like a smoke detector: a short beep every second without a break, getting louder over time.
One siren per screen: while Orders is wailing at an unconfirmed order, a call waits its turn in silence — two identical alarms at once say nothing.
{info} If sound is off on the device there will be no alerts — but the banners and cards are still there to see.
Settings → Notifications: the Sound alerts switch, the Alert volume slider and Test sound — you can listen to the alert without waiting for an order. These settings live on this device.
{info} The slider controls the volume inside the app. It doesn't change the tablet's system volume — if the kitchen is noisy, turn that up as well.
The app is honest about two different states:
{info} On poor Wi-Fi this is the first thing to look at when someone complains that orders aren't coming through.
Open qreaty.com/install on the device — or «Install as an app» in the account menu, in «More» and in the device settings. In Chrome, Edge and Samsung Internet that page has a single «Install the app» button. iPhone and iPad have no such button: the page shows the «Share → Add to Home Screen» path, and its own path for Safari on a Mac and for Firefox. The QR code on the page moves the install from a computer to a phone. Once installed, the app opens in its own window like a normal app.
A waiter needs it above all for notifications: on iPhone, push only works for an app added to the home screen.
{info} Updates install themselves. The app reloads into a new version only during a pause: when nobody has touched the screen for a minute, no dialog is open and no new order is being put together. For the venue's kiosk tablet, see Kiosk setup.
Next to the search box in the admin — and in the left rail on a computer — there is a bell. That is where we announce new features, improvements and scheduled work.
It is deliberately silent: no chime, no pop-up, no push. The "new order" alarm has to stay the only sound that pulls staff off the floor, and a note about food cost does not qualify.
A dot on the bell means there is something unread. It clears once you open the list; the "New" markers on the rows stay for the rest of the session so you can still see what had arrived. Nothing disappears — the list is the archive of recent news.
The bell belongs to whoever runs the venue: the owner, a manager, and anyone with rights to settings, staff, reports or the menu. Waiters, cooks and the venue's shared tablet do not get one; none of this is theirs to act on.
{info} Read state follows the person, not the venue: read an item at one café and it is read at the other too.