Kitchen (KDS) — the cook's screen

Kitchen (KDS) in cenaly.ge shows the cook what to make, for which table and with which requests. New orders and changes arrive automatically.

The cook marks dishes ready, and the pickup staff mark the actual handover to the guest or courier. These are different actions: "Bump" in the kitchen does not mean "order handed over".

What is needed to start#

• A tablet, or a computer with a monitor and a browser. For a TV, use a connected computer or a media box with a browser and a convenient input device.
• Internet and power so the screen can run all the time.
• Kitchen access for the employee: the "Cook" role opens the kitchen screen right after sign-in. To connect a device without typing a password every time, see QR codes and devices.
• Orders sent to the kitchen. By default a guest order waits until an operator accepts it in "Orders"; the location setting "Guest order before acceptance" changes this.
• Menu categories, if you want to split dishes between stations. A single shared screen does not need station presets.

A printer is only needed for paper tickets and stickers; the screen itself works without one.

Connect a kitchen screen#

1. On the device open the admin panel and sign in as an employee with kitchen access.
2. Open "Kitchen (KDS)". In "Location" choose the right location.
3. Press "Fullscreen" and turn on sound with the bell button if the cook needs signals.
4. Send a test order to the kitchen and check that the number and dishes are readable from the workstation.

The screen tries to keep the device awake. If the browser cannot do that, turn off auto-lock in the device settings. For a TV without convenient controls connect a keyboard or a compatible bump-bar.

Account, location and device settings#

Web screens in one account share kitchen settings. Changing "Text size" therefore affects all its screens, including those at other locations. If another monitor still shows the old appearance, refresh its page.

For a chain, first choose "Location", then categories in "Stations", and save a preset such as "Centre — hot station". Repeat for the other location and open the matching links on its monitors. The preset's location selects the venue's orders; categories select the station's dishes. These are separate filters.

For an overview, choose "All locations" on an unlocked screen: it will show the locations the employee can access. A preset without a location does not by itself guarantee this mode — check the selected location before locking the screen.

Configure cards and sound#

Open the "Settings" gear on the kitchen screen. In the monitor settings click the part of the sample card you want to change: header, dish row, note or buttons.

The appearance is saved for the account. Settings in the "This screen only" block belong to the device: "New-order chime", "Late alert", "Volume", "Repeat" — "Once" or "Until started".

If you cannot hear anything, tap the page once after it opens and check the device volume. Test the setting on one new order before the shift.

The timer shows the age of the order. If a promised ready time is known, urgency takes it into account; a separate setting shows the countdown. Warning and late thresholds, pulsing and colour are set in "Timers & urgency".

Split the kitchen into stations#

1. Open "Stations" and choose the menu categories for this screen, for example drinks for the bar.
2. In "Device presets" press "Save current as preset" and give it a clear name.
3. Press "Copy link" or open the QR code on the right device: the screen is locked to that station.
4. For categories not covered by any preset, mark the fallback station "Other".

Without a fallback station, categories without a preset are shown on every station screen, so the kitchen never loses those dishes. Check the warning about categories without a station.

If a link points to a deleted preset, you will see "Unknown station link — showing all orders". Copy a valid link. If dishes go to the wrong station, check the dish category and the preset categories — there is no separate "station" field in the dish card.

In "Station printers", choose who prints the ticket: "POS, when sent to kitchen", "This KDS screen, on arrival" or "Not printed". You can assign a "Backup printer". Tickets and 60×40 item stickers are configured separately — Kitchen printing.

Station schedule and its own screen look#

Each station preset has a “Schedule & look” button.

1. Turn on “Station works on a schedule”, tick the days and hours, e.g. the bar from 10:00 to 23:00. The window may cross midnight (18:00–02:00).
2. In “Look of this screen” set the columns, text size, theme, density and urgency thresholds — they override the common settings only on this station’s screens. For example, the bar reads from a distance in a large font while the hot line keeps a small one.
3. Click “Save”.

The time is taken from the kitchen screen’s clock. A station closed right now is marked “closed now” in the preset list.

Station sets: banquet, breakfast#

A set is a named list of stations with its own look and thresholds, e.g. “Banquet” without the bar and with a 30-minute late threshold.

1. Open “Stations” and pick a location in the screen filter.
2. In “Station sets” click “+ New set”, name it, tick the stations and, if needed, set its own thresholds and font.
3. Click “Make active” or pick the set in the “Station set” list in the kitchen screen header.

A location has one active set. A set without a location applies where the location has no active set of its own. An employee with access to one location switches sets of that location only.

Switch the set from the till#

The set can also be changed at the till without walking to the kitchen screen: “Hardware” → “Kitchen station set” block → pick a set or “All stations”. Below the list you see which stations are closed right now — by the set or by their schedule.

Switch the set in the kitchen and till apps#

In the Cenaly KDS and Cenaly POS apps for Android, Windows and Ubuntu the set is switched right where people work:

• Kitchen screen — tap the “🗂 Set: …” chip in the header (if no set is on, the chip says “All stations”) and pick a set or “All stations”.
• Till — “☰ Till menu” (the side menu on Windows and Ubuntu) → “🗂 Kitchen station set” → pick a set or “All stations”.

The window shows which stations are closed right now. After you pick, the app re-reads the kitchen settings at once and shows the new set; the other screens of the location pick it up within a minute.

How sets and schedules affect printing from the till#

If the till prints a station’s tickets (“Station printers” → “Till, when sent to the kitchen”), the same rule as on the screen applies:

• a closed station — outside the set or outside its hours — prints no ticket;
• its dishes are printed by the fallback station “Other”, if there is one and it is open;
• without “Other”, these dishes are printed by every open station — an extra slip is better than a lost dish;
• “Other” also prints categories that are not in any preset. Without “Other” such dishes are not printed, as before.

“Send to kitchen again” from the till is printed by open stations only too.

Sets, schedules and colours in the KDS apps#

The Cenaly KDS apps for Android, Windows and Ubuntu read the same settings:

• a screen locked to a station gets that station’s look: columns, text size, theme, density and thresholds. The location’s active set is applied over the common look first, then the station’s own look;
• a closed station shows the banner “⏸ Station closed by schedule (Mon–Fri 10:00–23:00)” or “Station is not in the active set “Banquet””. Its dishes go to “Other” by the same rule as on the web KDS;
• the header shows the name of the active set — “🗂 Set: Banquet”;
• a ticket is tinted with its order type colour: a stripe along the top and a coloured “Pickup” or “Delivery” label. Item rows get a stripe in their category colour.

The set can be switched right in the app — with the “🗂 Set: …” chip in the header (see “Switch the set in the kitchen and till apps”). The app picks up a set change made on another screen or a schedule edit within a minute; a station opens and closes by the clock of the tablet or computer. A station screen without a signed-in account reads the settings through the cloud with the station key.

On iPad (the Cenaly KDS app for iOS) all of the above works the same: the station look, the closed-station banner, “Other”, the active set name in the header and ticket colours. To lock an iPad to a station, tap “Stations” in the header and pick it in the “Station presets” row — the button becomes “🔒 Hot”, category chips stop responding and the location is taken from the station. “Unlock” removes the lock but keeps the screen on the station’s categories. If the station is deleted in the back office, the iPad unlocks itself and shows all tickets. The “warn” and “late” thresholds in “⚙” come from the account, set and station by default (the “From account” chip is on); set your own and they apply to this iPad only. The set itself cannot be switched on the iPad — only from another screen, the till or the back office.

Several screens for one station#

To let two hot-station cooks see the same work, open the same preset link on both monitors. The expediter can open a general KDS without a category filter to watch every station's readiness.

A row's readiness belongs to the order: marking it "Ready" on one screen automatically appears on the others when the update arrives. There is no need to mark the dish on every monitor. If the connection drops, changes can be delayed — check the connection indicator and pending queue. Record the actual handover separately in Expo.

Two lines of one station: claim and transfer a ticket#

When a station runs two lines (for example, two grills), each line takes its own orders instead of cooking the same ones.

1. Create two presets with the same categories — "Grill 1" and "Grill 2".
2. On each, press "Chain & lines" and enter the same "Line group", for example "Grill".
3. Open the preset links on the line screens.

The ticket gets a line strip: "Shared" — nobody has the order yet, "Mine" — this line took it. "✋ Claim" assigns the order to the line and it disappears from the other line's screen. "Back to shared" shows it to both again.

"Transfer to…" sends the ticket to any station of the same location — the other line or another station. The receiving station sees the transferred dishes even if their categories are not its own, marked "From Grill"; "↩ Give back" returns them. A single station without a group can transfer too.

At the top of a line screen choose which tickets to show: "Mine and shared" (default), "Mine only", "Shared only" or "All lines" — the last view also shows the other line's orders, so you can claim them if that line has closed.

Station chain: grill → assembly → expo#

When an order passes several stations in turn, set the order instead of keeping all screens in parallel.

1. On the "Assembly" preset press "Chain & lines".
2. In "After station" choose "Grill" and save.

Now dishes that the grill takes appear on assembly only after the grill presses "Bump". For the grill itself "Bump" means "pass on": the ticket shows "Next: Assembly", a passed line looks done, and tapping it brings the line back to the grill. Dishes that assembly does not take, the grill finishes as usual. Dishes become ready for the floor after "Bump" on the last station of the chain; you can add a third station after assembly the same way.

Cook and hand over an order#

1. Read the items, modifiers and notes. A combo is expanded into its dishes; cancelled rows are struck through. If the order belongs to a virtual brand, its name is on the ticket.
2. Press "Start" to start your ticket's items, or tap a single dish.
3. Tapping a row moves it through "Queued" → "Preparing" → "Ready". The "Bump" button completes the items of the ticket that can be cooked.
4. Pass the food to the pickup point. Hand over delivery and pickup orders in Expo; for dishes going to tables, open its "Dining room" view and mark "Served" after handover.

Payment alone does not make the food ready. If dishes were added to the order, the kitchen has to cook the add-on too.

If you pressed "Bump" by mistake#

Open "Recall", find the recently finished ticket and press "Recall" next to it. It comes back to work; the recall list survives a page reload.

To recall one dish instead of the whole ticket, press "Items" on the finished ticket and "Recall item" on the line you need — for example, a pizza to remake. The other dishes stay ready. The same "Items" button simply shows what was on the ticket without recalling anything. Items already served to the guest are shown as "served" and cannot be recalled.

If the order was not finished by mistake but should not be cooked at all, ask the cashier or manager to correct it in the till or in "Orders". Recalling a ticket does not cancel the sale. When a message about cancelled orders or items appears, read the changes and press "Got it".

To make fewer mistakes, turn on "Confirm before bump". If the ticket is not among the recently finished ones, find the order in "Orders".

Pin a ticket so it is not bumped by accident#

Press 📌 in the card header (or L on the selected ticket). While the ticket is pinned, the "Bump" button is inactive, and Enter and the bump-bar do not clear it — the screen reminds you to unpin it. All kitchen screens see the pin, and it survives a page reload. Press 📌 again to unpin.

Card statuses and badges#

Send a request from the till and read it in the kitchen#

1. After sending the order to the kitchen, open "Message to kitchen" at the till. Type, for example, "table 5 is in a hurry", or choose "Quick messages".
2. Choose "Station" or "All stations" and press "Send".
3. The cook sees a "Message" banner on the card. After reading it, they press "Read"; the till shows the acknowledgement in "Messages for this order".

Default templates: "Guests are in a hurry", "Speed up the hot dishes", "Serve the next course", "Allergy — check with the waiter", "Hold the order for now", "Guests are seated — start cooking". Custom quick messages are saved for the location: use "Edit" or "Save as quick message" in the message window.

If the message is missing, check the order, addressed station and connection. "Read" acknowledges reading, not completion of the request.

If an action has not been sent yet#

The "⏳ N not sent" badge means commands are waiting in the device's queue. Even if its card has changed, other screens may not have received the action yet. Restore connectivity, wait for sending and check the order status; do not clear browser data while commands are pending.

"New orders from other tills: no data" appears without a cloud connection or an available location bridge. It does not mean there are no new orders. Contact the till and restore the connection. With a working bridge the location can receive local updates through it; complete cloud order coverage cannot be promised without connectivity — If the internet goes down.

Work from a keyboard or bump-bar#

There is one layout for every kitchen screen: in the browser and in the Windows, Linux and Android apps. A compatible bump-bar must send the same keys as an ordinary keyboard; program the device buttons to the keys in the table.

Letter keys work in any keyboard layout: they are matched by the physical key. The keys do not control the rail while the cursor is in an input field or a dialog is open; Tab still moves focus between buttons. If a bump-bar does not react, first try the same actions on an ordinary keyboard and check the key codes of the device.

To speed up a particular order, press the rush button on the card or U. A ticket marked "RUSH" moves ahead of the regular ones; doing it again removes the mark.

To set the order yourselves — for example, a banquet or a VIP table first — press the ⇡ button next to the ticket number (or P): the ticket gets "P1"; further presses give "P2", "P3" and remove the priority. Rail order: "P1", "P2", "P3", then "RUSH", then the rest; with equal priority the rush ticket goes first.

Wireless bump-bars and KDS apps#

A wireless bump-bar works if, once paired, it sends ordinary keyboard keys. Pair it through the computer or tablet and test commands on a selected ticket. Pairing and battery status are managed by the device; KDS has no separate battery controls.

New-order sound on each platform#

Sound must be enabled on the screen in use. Check each workstation separately; connecting a wireless bump-bar does not itself add an audible alert to the bar.

Prepare a scheduled order on time#

An order "for 19:00" can wait in the "Upcoming" panel without taking space on the working rail: a pickup or delivery pre-order and a table order "for a time" from the POS. It moves to cooking the time of its longest dish plus a margin before the ready time. The margin is a screen setting — "Send pre-orders to the kitchen, min ahead" (0–120, default 5) — and applies to all kitchen screens of the account: ready at 19:00, a 20-minute dish and a 10-minute margin — the order comes out at 18:30. If no cooking times are set, the calculation uses 15 minutes plus the same margin.

The Cenaly KDS apps for Android, Windows and Ubuntu use the same margin. They have no "Upcoming" panel, so the pre-order stays on the rail: it is dimmed, placed last and shows "🕒 To kitchen at 18:30". Such an order is not counted in the summary. When the time comes or a cook starts an item, the ticket becomes a normal one. Releasing it early with "Start now" is only possible on the web KDS.

1. For an accurate calculation open "Menu", the dish card, and fill in "Cooking time (min)".
2. On the KDS open "Upcoming" to check the waiting orders.
3. To start earlier, press "Start now".

A held course with a fire time from the POS shows "🕒 at 21:30" next to its group: at that time an open web kitchen screen fires the course and prints its station ticket. If the floor pressed "Repeat to kitchen", the ticket shows "🔁 REPRINT 14:05" with the time of the request (for 30 minutes), and the station printed by this screen gets a copy marked "REPRINT" — once per repeat.

In the KDS apps for Android, Windows and Ubuntu a held line of such a course shows "⏸ Waits for course 3 · 🕒 To kitchen at 21:30", and the ticket shows "🔁 REPRINT 14:05" for the same 30 minutes. The apps themselves neither fire the course on time nor print the copy: the course is fired by an open web kitchen screen, a waiter or the POS. The iOS app does not show course times or repeats yet.

Fire dishes so the whole order is ready together#

If an order has a 10-minute burger and 4-minute fries, without this setting both go to the kitchen at once and the fries get cold while the burger cooks. With the setting the longest dish starts at once and the others wait "longest − own": the fries appear on the fryer station at minute 6 and the order comes together.

1. In "Menu" open the dish card and fill in "Cooking time (min)" — the plan is based on it.
2. On the KDS open "Settings" → "Behaviour" and turn on "Fire dishes so the whole order is ready together". It is off by default.
3. A waiting line is dimmed with an "in N min" label. To start earlier, press "Start now" on the line.

See the order while it is being rung up#

In fast food and at a counter the cook can start while the cashier is still entering the check: the burger goes on the grill before the guest has picked a drink. The kitchen screen has a mode for this: “Kitchen sees the order while it is rung up”.

1. On the KDS open “Settings” → “Behaviour”.
2. In “Kitchen sees the order while it is rung up” pick a mode:
   • “Each item at once” — an item appears in the kitchen as soon as the cashier rings it up;
   • “After the next item” — an item appears once the next one is rung up, so the cashier can still change or remove the last one;
   • “Off — after ‘Send’” — as before, the kitchen sees the order after it is sent. This is the default.
3. With several locations, tick where the mode is on. Nothing ticked means all locations.
4. Ring up at the till as usual. Above the kitchen rail a pale ticket with a dashed border and the “✍ Being rung up” label appears — the table, tab name or “Add-on to #…” and this station’s items.

When the cashier presses “Send” or takes payment, the pale ticket disappears and the regular order ticket arrives on the rail. If the cashier clears or cancels the check, the ticket disappears too. If the till closes or loses connection, the ticket is removed on its own after about two minutes.

In the KDS apps for Android, Windows, Ubuntu and iOS the pale ticket looks and works the same way. The till and waiter apps pass it to the kitchen both through the cloud and over the location’s local network, so if the internet drops, a kitchen on the same network keeps seeing it.

The same mode covers “the bar or the pass sees the check being rung up”: the station screen shows it read-only, with no need to join the shared check.

Cook in batches and by courses#

Press "All day": it shows the total number of each dish in the queue, so the cook can make several identical portions together. It is a summary of orders, not a production plan.

For staged service turn on "Coursing (courses of service)" → "Enable coursing" in the settings. Set the course names and the "Default course by category"; up to six courses can be configured.

In a dine-in order, courses after the first are held and shown in the "HOLD" block. Press "Fire" when the table is ready for the next course. If the waiter assigned items to guests, guest numbers are shown on the rows — Hall orders.

To have the next course go to the kitchen by itself, set "Pacing" in the same section: "Min" and "Max" in minutes for course 2 and later. A held course fires by itself "Min" minutes after all dishes of the previous courses are ready, and no later than "Max" minutes after they were fired — even if the cook forgot to press "Done". An empty "Max" means no limit; an empty "Min" means firing only with the button, as before. For example, starters are ready at 19:00 with "Min" 5 — the mains go to the kitchen at 19:05.

A held course shows "⏱ auto in N min" (or "auto when ready") on the ticket, and a course fired this way shows "fired automatically". "Fire" before the time still works.

For pickup and delivery created in the web POS, the course remains a label, but rows are not held: the whole bag is prepared together. When an order is switched from dine-in to takeaway, the till releases held rows; save the changes so the kitchen receives them.

Prep counters and “How to serve”#

To let the cook see how many prepped items are needed right now, mark them in Inventory: "Inventory" → item card (for example, "Patty" or "Bun") → "🧮 Show on the kitchen screen as a counter" → "Save". The item must be part of a dish recipe ("Menu" → item → "Inventory") or of a semi-finished product.

A strip "Patty 4 · Bun 3" appears above the tickets. The number is the total over the "queued" and "preparing" lines on this screen: portions × recipe norm, plus the recipes of the selected add-ons. For example, two burgers with one patty each and one double burger give "Patty 4"; once one burger is bumped, 3 remain. Held courses, delayed lines and lines already passed to the next station are not counted. If the marked item is inside a semi-finished product, the counter expands its composition: "Assembly → Patty" counts as a patty.

To see how to serve a dish, press and hold a ticket line (on a computer — right-click). The "How to serve" window opens: the recipe per portion (gross and net, and the total when there are several portions), the yield, cooking time, description, the dish photo and links to videos from its gallery. The window is read-only — the recipe and photos are edited in Menu. You can send a colleague a link to the window: it is kept in the address and survives a page reload.

In the KDS apps for Android, Windows and Ubuntu#

The apps show the same "🧮 Prep: Patty 4 · Bun 3" strip above the tickets and count it by the same rules as the web screen. To open the "How to serve" window:

• on an Android tablet — press and hold a ticket line;
• on Windows and Ubuntu — right-click the line, or touch and hold it on a touch screen.

The window shows the recipe per portion (gross and net, and the total when there are several portions), add-ons, yield, cooking time, description and links to plating videos. A video opens in the device browser. The app does not show the dish photo in the window — it is visible on the web screen.

A screen where a cook has signed in reads recipes and inventory itself. A station without sign-in (a screen prepared to work without sign-in) does not read the inventory: the cloud sends it ready-made dish cards. A card holds only the dish composition and the norms of items marked "Show on kitchen as a counter". Prices, cost, suppliers and stock never reach the station. The app picks up a recipe or flag change within 5 minutes, no restart needed.

Smart prep time for delivery#

In "Smart prep time" you can turn on "Auto prep-time quote": the estimate for delivery channels takes into account the number of items and active tickets. The setting names Wolt and Yandex Eda; it is off by default.

The "Cook for courier arrival (order by pickup ETA)" option moves up orders with a known courier arrival time. It is a simple load estimate, without automatically pausing order intake when the kitchen is overloaded.

Report that a dish has run out#

In the KDS header press "Stop-list", find the dish and stop it for your location. When the dish is available again, remove the local stop in the same panel.

A chain-wide stop is removed by a manager. If the kitchen cannot remove it, ask the manager: a local action must not switch a dish back on in every location at once.

Cenaly KDS app for Android#

On Android there is a separate Cenaly KDS app with the kitchen screen and a handoff (Expo) mode. The handoff mode shows ready orders and can send them back to the kitchen. Manifests and bag stickers are printed from the web Expo screen.

The app adds kiosk pinning, a brightness control, device-only settings and "Hey Cenaly" voice commands in the kitchen. Starting after a reboot depends on Android permissions; do not rely on it without testing the specific tablet.

Courses can be held on Android, but the next course is fired by the waiter, at the till or by the pacing of an open web kitchen screen. The photo setting applies to the web KDS; the hotkey table is shared by all platforms.

Limits#

• For permanent use choose a tablet or a monitor; a phone is inconvenient for a kitchen rail.

• Without the cloud and a bridge you cannot count on new orders arriving. A saved snapshot does not replace a live connection — If the internet goes down.

• The web KDS has no production-plan mode and no bumping by scanning a barcode on a paper ticket.

• Kitchen analytics in statistics is available on cenaly.com; on cenaly.ru this section is not available yet.

• Orders from connected aggregators also reach the common kitchen rail; there is no "own orders only" filter here.

• There are three priority levels ("P1"–"P3"), set only from the web KDS; the till does not set them when sending, and a VIP from the guest card is not raised automatically. The KDS apps for Android, Windows and Ubuntu show priority and pinning ("P1", an inactive "Bump") but they can only be set from the web KDS; the iOS app does not have them yet — a pinned ticket can be bumped there. A station screen without an account login cannot change rush, priority or pinning.

• Two lines, ticket transfer and the station chain work on the web KDS on a screen locked to a preset. The KDS apps for Android, Windows, Ubuntu and iOS do not yet tell claimed, transferred or waiting tickets apart — they show them by category as before. The automatic split divides orders by shares, not by the current load of a line.

• Pacing works while a web kitchen screen with this order is open; the KDS apps for Android, Windows and Ubuntu fire courses neither on a timer nor at the time set from the POS. "Upcoming" holds the entire scheduled order; in the native apps it waits on the rail, dimmed.

• Prep counters and the "How to serve" window are on the web KDS and in the KDS apps for Android, Windows and Ubuntu; the iOS KDS app does not show them yet, and the apps do not draw the dish photo in the window. A video uploaded as a file to the dish gallery is not played in the window — links to videos (YouTube, Vimeo, etc.) are shown.

• Own screen look, station schedules, station sets, order type colours and category colours are applied by the web KDS and by the KDS apps for Android, Windows, Ubuntu and iOS; on iPad the set is only shown and cannot be switched there, and the iPad does not change row density. A station screen without sign-in that runs on the location bridge alone, with no internet, gets new settings when the cloud is back. A set is switched by hand — from the kitchen screen, in “Stations”, from the web till (“Hardware”) and in the KDS and till apps for Android, Windows and Ubuntu (except a station screen without sign-in); the set itself does not change by the clock (individual stations close by the clock). Shared sets without a location are switched only in the web “Stations”. Station tickets by set and schedule are printed by the web till; the till apps do not print station tickets. Two stations are not split into halves of one monitor — open two tabs or two devices.

• The “Being rung up” draft is sent by the web till, the till apps for Android, Windows and Ubuntu and the waiter app for Android and iOS (on iOS only for a new check; add-ons are not shown there in advance), and shown by the web KDS and the KDS apps for Android, Windows, Ubuntu and iOS. The mode is turned on only on the web KDS; the apps read it themselves, and the till app picks it up with a new check. The web till and web KDS pass the draft through the cloud only. The apps use the cloud and the location’s local network, so on cenaly.ru and on a KDS station without sign-in it travels over the local network only: the till and the kitchen must be on the same LAN. The web kitchen screen does not see drafts from the local network.

• A guest check cannot be opened from the kitchen screen; the recipe opens read-only. Bump-bar key codes cannot be reassigned in KDS.

Troubleshooting#

If the problem repeats, prepare the order number, location, time, selected station, device and browser, and a screenshot. Say what you did and what you expected. The way to contact us is in the support guide. Errors of the web screen reach support automatically, so there is nothing to export. In the Cenaly KDS app for Android the problem report window opens with a gesture — hold three fingers on the screen for about a second or shake the tablet: describe what is wrong and send it with a screenshot and the app log; the support code is added automatically.

Common questions#

Can I use several screens? Yes. Open the right location on each and split the categories with station presets.

Does the screen update by itself? Yes, over a live connection; a backup refresh of the list runs about every 30 seconds.

Where do orders come from? From the till, the QR menu and other connected channels, including delivery integrations. For guest orders, operator acceptance applies.

Does "Bump" hand the order to the guest? No. Cooking and the actual handover are marked separately.

Related guides#

• Online orders at the POS and kitchen — acceptance, ready times and payment.
• POS and Orders
• Expo and Own delivery
• Kitchen printing
• QR codes and devices
• Staff and shifts