Table orders: from the first dish to the bill

This article helps waiters, cashiers and managers work with an open table order in cenaly.ge web POS: record requests, send additional dishes to the kitchen and prepare the bill. The main workflow uses Table mode in POS.

For an introduction to the screen, see the POS overview. Phone workflows are covered in the Cenaly Team waiter app; relevant differences are noted below.

What you need to get started#

• Open the correct location in POS and select a table. See the floor plan guide to set up tables.
• Make sure the location’s menu contains the dishes, variants and combos you need. Unavailable items cannot be added by a normal tile tap.
• Configure the kitchen display or kitchen printing. A saved order alone does not confirm that paper came out of the printer.
• Firing held courses requires permission to manage the hall. Voids may require a manager’s approval and PIN.

In the location’s POS appearance settings, enable the elements you need: Items by guest (bill split), item comments and Stock on tiles. Guest assignment and stock display are off by default.

Add dishes and guest requests#

1. Find the dish using search or tap its tile. If variants are available, choose the required size or version.
2. Complete the required option groups. The rule beneath a group reads for example Guest picks exactly 1, Guest picks 1 to 3, Guest picks at least 2 or Optional, up to 3 — the numbers come from the group settings.
3. Tap Add to order. If the minimum selection has not been met, complete the group first.
4. Select the order line and open ✎ Comment; on a narrow screen it may be under ⋯. Type the request or use No onions, Not spicy, To go, Serve later or Allergy.

The comment belongs to that item and is sent to the kitchen. Serve later adds a written request; use courses when you need to control when cooking starts.

To split the bill by guest later, select Shared or the relevant guest before adding an item. For an existing line, use its Guest 1, Guest 2 and so on assignment. The guest strip appears for a dine-in table order when Items by guest (bill split) is enabled.

Stock display and the stop list have different purposes. Stock on tiles shows quantities, with Off, Low and All modes. It is an indication, not an automatic sales block at zero. The stop list blocks unavailable dishes; staff with permission to manage the hall can change it.

If a tile is unavailable, ask a manager to check the stop list and the dish’s availability schedule. Do not substitute another variant without checking with the guest.

Name a table bill#

A banquet, an anniversary, a regular guest — once a table is selected, the ticket header shows the Name or tab (optional) field. Type, for example, “Smith, anniversary” and save the order. The name appears in Open orders (the 🏷️ tag next to the table), is printed on the kitchen ticket next to the table number and is shown on the kitchen display. In Bar mode the same field stays in place of the table, as before. Delivery orders do not show the field — they already have the customer name.

In the POS apps for Android, Windows and Ubuntu, the Name or tab (optional) field appears under the table picker once a table is selected. A new order takes the name with it. For an open bill, the register app saves the name on Add to bill or at payment, and the waiter app on Send.

Choose a combo#

Set up the combo on the item card#

The combo is configured on the account's item card and shares its composition across locations selling that item. POS checks each choice against the current location's menu and availability.

1. Open the item card and Build-your-combo (storefront). Despite its name, web POS uses these slots too. The fixed Combo set used for stock deduction is a separate setting.
2. Select Add slot, name it, for example “Drink”, and use Add option to choose dishes for that slot.
3. Set Surcharge for each choice. The total is the combo's own price plus the selected surcharges, not the sum of the component dishes' regular prices.
4. Enable Required if the slot cannot be skipped, and mark a choice as Default to preselect it. Before selling, check the choices in POS at the intended location.

Sell the combo in web POS#

1. Tap the combo tile and open Combo choice.
2. Choose a component for every slot marked required.
3. For optional slots, choose a component or None.
4. Check the components and surcharges, then add the combo to the order.

Each combo slot selects a component; rules such as “two to three” belong to option groups, not combo slots. The chosen components are saved with the item and shown to the kitchen.

If a required slot has no available choice, POS says Nothing available in this slot — the combo can’t be put together right now. Offer another dish or ask a manager to check component availability.

The order and receipt keep the combo as one item at the full amount, including surcharges; the selected components appear beneath it and are sent to the kitchen. A 600 ₽ combo with a 50 ₽ drink surcharge produces one 650 ₽ item.

Slot selection is available in web POS. The Android, Windows and Ubuntu POS apps preserve and display the composition of an incoming order, but do not yet offer a choice editor; they can still make a combo from items already on the ticket — see the next section.

POS suggests making a combo#

The cashier added a burger, fries and a drink separately, and the menu has a cheaper combo of them. A banner appears above the ticket lines: «Make it a combo «Business lunch» −90 ₽».

1. Tap «Make combo» — the burger, fries and drink lines leave the ticket and one combo with the same items takes their place.
2. The guest wants them separately — tap «No thanks»: POS will not suggest it again for this set.

Result: the ticket has one combo item at the combo price plus surcharges of the chosen choices; the kitchen sees the composition, as with a manual choice.

POS suggests only a combo that saves money and only from not yet sent lines without options, extras, variants, discount, weight or marking codes. A required slot without a matching line means no suggestion; an optional slot is filled when possible. From a «×2» line one unit goes into the combo. POS never rewrites the ticket on its own.

The suggestion is in web POS and in the POS and waiter apps: on Android the banner sits above the bottom bar with the ticket total; in the Windows and Ubuntu POS apps it sits above the ticket lines in a wide window and above the bottom bar in a narrow one. Same buttons, same rule.

Manage serving courses#

A course groups dishes that should start cooking together. When courses are enabled, POS takes the default course from the category setting; the number appears on the order line. Use the individual line’s course badge to change it.

1. Assign courses before sending the order. Courses above the first are created on hold.
2. Save the order: held items remain in it but do not enter preparation until their course is fired.
3. When guests are ready for the next course, a staff member with hall-management permission taps Fire course 2 (the number of the next course) or Fire next course.

The selected course’s items are released for preparation. Fire course does not mean that the waiter has already brought the dishes to the table.

If Pacing is set on the kitchen screen (KDS settings → Coursing), the next course goes to the kitchen by itself: “Min” minutes after the previous courses are ready and no later than “Max” minutes after they were fired. The timer runs on an open web kitchen screen; firing from the POS before that time still works — Kitchen display.

Send a course to the kitchen at a set time#

The guest wants dessert at 9:30 pm — you do not have to keep it in mind. Next to Fire course N tap 🕒, pick a time (quick options “in 30 min”, “in 1 h” or your own) and tap Set time. The button then shows “🕒 at 21:30”.

At that time an open web kitchen screen fires the course by itself — the same as Fire course — and the station gets its ticket. You can still fire the course by hand earlier; Remove time in the same window returns to manual firing. The course time is also shown on the kitchen screen next to the held group (“🕒 at 21:30”).

If the button is missing, check that courses are enabled, that there are held items and that the staff member has the required permission. Bulk course assignment to selected lines and a separate “cook everything now” mode are not yet available; single items of a course can be sent early with ⏩ Prep ahead (below).

Prep a dish ahead of its course#

A long-cooking steak or baked fish can be started early while the guests are still choosing or eating starters. Open ⋯ on a saved held item and tap ⏩ Prep ahead: only that item goes to the kitchen now, the rest of the course stays held. Repeat for a second item if needed.

The kitchen screen shows ⏩ prep ahead on the item, and the station ticket is printed marked PREP AHEAD. When the course is due, Fire course N sends and prints only the remaining items — prepped ones are not printed again. On the ticket line such an item shows ⏩ instead of 🔒.

In the waiter app (Android) and Cenaly Team for Windows, prep ahead is a ⏩ Prep ahead button right under the held item in the order card. It is shown to whoever can fire that order's course: a waiter on their own and unassigned orders, a manager on any. Kitchen screens on Android, Windows and Ubuntu also show ⏩ prep ahead on the item; a kitchen screen connected to the bridge on the local network needs an up-to-date bridge for this.

Reminder about a course held too long#

The POS counts how long a course has been waiting since it was held. The 🔥 Fire course 2 button shows the wait (“⏳ 25 min”), and Open orders shows a ⏳ course 2 waiting 25 min badge on the order. When a course waits longer than the threshold, the badge turns red and on the floor plan (Hall panel → Floor plan or Now, and the table picker) the table gets a red frame with “⏳ 2 · 35′”.

To find such checks quickly, tap the ⏳ With held courses chip in Open orders — only orders with waiting courses remain, overdue ones first.

The threshold is set in the kitchen screen settings → Coursing → Remind about a held course after, min: 30 minutes by default, 0 — no reminder. The setting is account-wide.

The same reminder is available in the apps:

• POS on Android, Windows and Ubuntu — Hall panel → Floor plan: a table whose course has waited longer than the threshold gets a red frame with “⏳ 2 · 35′”, and the table card shows “⏳ course 2 waiting 25 min”. The POS uses the same coursing setting for the threshold.
• Waiter app (Android) — a “⏳ course 2 waiting 25 min” badge on the table tile (over the threshold the tile gets a red frame), in the order list and in the table's order picker; in the order card, “⏳ 25 min” under the course title.
• Cenaly Team for Windows — the same badges on table tiles, in the order list and on the floor plan, and “⏳ 25 min” next to the course in the order card. Here the threshold is always 30 minutes: Cenaly Team does not read the threshold setting yet.

Courses, their names and category defaults are account-wide and apply to all locations in the account. The Table/Bar/Counter service mode is set for the location; permission to fire courses belongs to the role.

When entering payment in Table mode, the POS checks for held courses. If any remain, Still on hold: … explains that the kitchen has not started these items. Choose Back to the order, then fire the course or remove items the guest no longer wants. Continue to payment lets you proceed with payment; it does not start preparation. This warning is not shown in training mode.

Printed kitchen tickets list items in course order, preserving item order within each course. Items without a course belong to the first course.

Save and send the order to the kitchen#

1. Check the table, guests, items and comments.
2. Enable Rush if the order needs priority in the kitchen queue.
3. Tap Save to save and send the order. Wait for a successful result.

When kitchen printing is configured, the kitchen ticket prints after the order is saved successfully. Additional orders send changes; held courses are not printed as preparation tasks until fired. Rush moves the ticket to the top of the kitchen screen.

Serve a table order at a set time#

A banquet “for 7 pm” or a guest who ordered ahead — tap the 🕒 ASAP chip in the ticket header (enabled by the POS view setting “Order for a time”) and set the ready time. The kitchen screen keeps such an order in Upcoming and puts it on the rail “longest dish + kitchen margin” before the time; stations printed by the kitchen screen get their ticket at that moment. A ticket of a station printed by the POS comes out at once, with the time on top. The margin is set on the kitchen screen — see Kitchen display.

Repeat a ticket to the kitchen#

The kitchen ticket got lost or wet — open the saved order and choose 🔁 Repeat to kitchen (a POS screen library command; the owner places it in design mode). The POS prints a copy of the ticket with a large REPRINT mark on the stations it prints, and kitchen screens show “🔁 REPRINT 14:05” on the ticket. The web kitchen screen prints the copy on its own stations; the Android and Windows KDS apps only show the mark.

The copy holds what has already gone to the kitchen: held courses and cancelled items are not printed. The order, the sale and add-on tracking do not change. If the role needs a manager PIN to reprint a receipt (the “Receipt reprint needs a manager PIN” role permission), the POS asks for it here too. While the ticket has unsaved changes the command is unavailable — save the order first.

In Table mode, the order stays open for additions. In Bar and Counter modes, saving also sends the order, then POS moves to the next ticket; in Bar mode the button may read Open tab. Adding a tile alone does not replace sending the order.

If saving fails, do not assume the kitchen received the order. If saving succeeds but there is no paper ticket, check the queue and printer connection using the kitchen printing guide.

Check readiness and record service#

POS shows item and open-order statuses; a ready order stays open until payment. In the Hall panel, Ready, not served helps identify tables waiting for a waiter. The hall monitor shows readiness, including All items ready.

With Time at table enabled, the timer shows Seated … · … since the last order or the time since the last dish was served. This helps identify a table that has not received attention recently.

In Cenaly Team, open the order and tap Served for a dish you have delivered. If you delivered all the displayed ready items, tap All ready served · 3 (the number of ready items). Record service after handing over the dishes; kitchen readiness and service are separate events.

If an item is missing from the list, first check whether the kitchen marked it ready. See the waiter app guide for details.

Remove an item already sent#

1. In the open order, reduce the quantity or remove the required line.
2. If the location asks for a reason, select one, such as a guest refusal or a defective dish.
3. If approval is required, ask a manager to enter their PIN.
4. When asked what happens to the products, select Write off as waste if they need to be written off, or Do not write off.
5. Save the order changes so that the cancellation reaches the kitchen.

The location settings are Ask for a reason when a sent item is voided, Manager PIN to void a sent item and Ask what happens to the products. They are off by default. The PIN request also depends on the staff member’s permission to void items.

Select the location in the POS, open settings using the gear and enable Ask what happens to the products. This setting applies to that location; removing a sent item opens the Void an item already sent to the kitchen dialog. Write off as waste creates a write-off document for the order’s sales warehouse, with waste as the reason. It deducts the recipe ingredients for the removed quantity, including variants and combos. If there is no stock composition to deduct, for example a dish has no recipe, no document is created. Do not write off creates no such deduction; check the result in Inventory.

KDS receives a cancellation alert, and kitchen printing shows a cancellation with the removed quantity (ОТМЕНА −N on a Russian ticket). This allows the kitchen to stop preparation or account for an already prepared dish.

Cancel the entire order#

Open Cancel order, enter a Reason (optional) if needed and confirm. A staff member without void permission needs a manager’s PIN. After a successful cancellation, the order becomes cancelled and the current ticket closes.

If confirmation fails, ask a manager to complete the action. In the waiter app, a waiter can cancel only while every item is still new; handle other cases in POS with the required permissions.

Move guests and items#

To move the whole party, open Merge / move, select a free table under Move to table, tap Move and confirm. The order moves to the new table.

To merge bills, select another open bill in the same window and choose Take onto this bill or Move to that bill. Check the destination table and amount before confirming.

To transfer part of an order, use Move items: save the source bill, select the lines and quantities, then choose the destination. Kitchen status is preserved, so ready dishes do not need to be cooked again. Moving items already in progress may require a manager’s approval.

Merging is unavailable if there are partial payments, prepayments, a corporate-account charge, loyalty redemption or an online payment in progress. Closed orders and family-cart orders cannot be merged either; handle aggregator orders in the Orders section.

Money moves by one rule when you merge:

• An item discount travels with its item.
• A check discount is recalculated so that each table keeps its own discount and does not get the other one’s. Only the source bill had it — it moves as an amount equal to that discount (the percentage does not spread to the destination table’s dishes). Only the destination had it — it stays and is recalculated for the new contents. Both had one — the same percentage stays a percentage, otherwise the two are added up into one amount.
• A coupon on the source bill moves with its amount.
• The guest count is added up.
• The service fee follows the destination table’s rules and is calculated on the merged bill after discounts. If the destination table’s fee is waived or absent, there is no fee; the source table’s fee does not move. A large-party fee counts the combined number of guests.

If the location enforces discount limits on the server, a moved discount above the merging employee’s limit is not applied — let an employee with the right permissions merge. If the destination bill’s guest bill has already been printed, print it again.

In the POS apps for Android, Windows and Ubuntu, merging means Move items with all items into another open bill: money moves by the same rule. If you move only some items, the check discount and service fee are not recalculated — the same as in web POS.

Cenaly Team supports moving an entire order to another table. Use web POS or a POS app for merging or moving individual items.

Split the bill#

Open Split bill and choose By items, By guest or Equally. The By guest tab depends on Items by guest (bill split) being enabled.

For a shared dish, use Split this item to make 2–6 shares. Select a part and tap Pay part. Check Paid and Left to pay so that you do not collect the same amount twice.

See the orders guide for the full allocation and payment workflow. The waiter app does not offer this bill-splitting workflow; hand payment over to the cashier.

One guest's bill#

When items are assigned to guests (Items by guest (bill split)), you can view, print and take payment for one guest at a time without splitting or closing the table bill.

1. In the guest strip above the bill, choose a guest, for example 👤3, and tap 🔍 Guest bill. The bill shows only guest 3's items, with a Guest 3 bill bar and their amount above them. Tap another guest chip to switch; ✕ Whole bill or Shared brings the whole table back.
2. 🧾 Guest pre-check prints a memo for this guest only: their unpaid items and their share of the service charge, add-on tax and tip. The table bill is not split or closed, the order is not marked as pre-checked, and no payment QR is printed, because it would pay for the whole table.
3. 💳 Pay for guest opens Split bill on the By guest tab with only this guest. The amount matches their pre-check; choose the method and tap Pay part. The other guests stay on the bill; All guests in the window shows them again.

Lines hidden by the filter stay on the bill and go to the kitchen as usual. Shared items (with no guest) are not part of a guest's bill; they are paid as a separate Shared items part. A reservation deposit is not deducted on a guest pre-check; the payment window shows its share.

In the POS apps for Android, Windows and Linux, choose a guest in the guest strip and tap “🔍 Guest bill”: a window lists that guest's items — both new and already sent to the kitchen — with their amount. “Whole bill” closes the window. Once the order has been sent, the same window has:

• “🧾 Guest pre-bill” — the same slip as in the web POS: the guest's unpaid items and their share of the service charge, add-on tax and tip, with no pre-check mark on the order and no payment QR. Send the guest's new items to the order first.
• “💳 Pay for guest” — a window with the guest's amount: “Cash” or “Card” (card only on the bridge terminal, for the guest's amount). The register issues a receipt for the guest's items only, and the table bill stays open for the others. If the payment did not reach the bill, tap again — the retry reuses the same receipt, no second one is issued.

If the guest pays the whole remainder, the app asks you to pay the whole bill with the regular “Pay” button. If the bill already has a gift card, deposit, corporate account, packaging, delivery or online payment, pay the guest in the web POS or pay the whole bill. A cash shift must be open.

Repeat an item#

Select an order line and tap ↻ Repeat selected item. POS adds one item with the selected options; without an explicit selection, it repeats the last non-cancelled line. If the button is missing, check Repeat button in POS appearance settings.

For combos, POS checks the current choices: if the combo can no longer be assembled, the selection window opens. If repetition is blocked, read the reason and add the dish normally with the required selection or scan.

Repeat round#

“Another round for the table” — the 🔂 Repeat round command adds every item of the last kitchen send to the bill in one tap: four beers for guests 1–4 become four more lines with the same options, guests, course and comment.

1. Open the saved table order or bar tab.
2. Choose 🔂 Repeat round — the command shows how many items the last send had.
3. Check the list in the Repeat the last round? window and tap Add to bill.
4. Tap Save — only then do the new lines go to the kitchen.

A round is the items sent to the kitchen by the last save; cancelled items are not included. The price is the current catalogue price (the location’s own price, happy hours); item discounts are not copied. Not repeated, and listed in the window with a reason: weighed items (weigh again), marked items and items with an EGAIS stamp (each unit has its own mark), items with a serial number, a product variant added by scan, time-billed items and anything not on sale right now (stop list, schedule). If nothing has been sent to the kitchen yet, POS says so.

The command is an option of the POS screen library: in the Restaurant and Hotel restaurant starting layouts it is in the ticket’s ⋯ menu, in the Bar layout — in the action row next to ↻; the owner adds it to their own layout in design mode.

In the POS apps for Android, Windows and Ubuntu the same command sits wherever the location’s layout puts it and opens the same window with the list. One difference: in the POS app the table order updates straight away, so the new lines go to the kitchen when you tap Add to bill — there is no separate Save. In the waiter app they wait for Send, like items added by hand.

Find an unpaid order#

Open Open orders, enter a number or name in Find: number or name, then select the bill. Save changes to the current order before switching: POS warns about losing unsaved changes.

When there are more than six open bills, ordering chips appear next to the search: Oldest and Newest sort by opening time, Table by table number (table 2 before table 10), Total from the largest. Tap the active chip again to return to the usual order. 💡 At the end of a shift, tap Oldest: bills forgotten since the morning come to the top.

Order type. When the list holds bills of different types, chips Dine-in, Takeaway, Delivery and Online appear above it with the number of bills of each type. A tap leaves only that type in the list, a second tap brings everything back. The choice stays while the POS is open: close the window and open it again — the filter is still there. “Online” means orders the guest placed on their own through the website, widget or a delivery aggregator, even for pickup; an order a cashier took by phone stays “Delivery” or “Takeaway”.

Open a bill by scanning the pre-check#

Turn on Bill code on the guest bill in POS → ⚙ POS appearance → Bill features — a small QR captioned “Bill code for the register” is printed at the bottom of every pre-check. Scan it on any register of the location — with a barcode scanner or the camera (the table QR scan button):

• no bill is open on the register — the bill from the pre-check opens;
• another bill is open — the POS asks: Merge into current (the pre-check bill's items move into the open one and that bill closes — as in the Merge window) or Just open #… (switch to the pre-check bill);
• the pre-check bill is already paid or closed — the POS says so.

Handy when a guest brings the pre-check to the bar counter or a party moves to another table. The POS also understands the payment QR on the pre-check (the “QR to pay” option). Only a saved bill without unsaved edits can be merged — save the ticket first. The code is digits only, so any scanner reads it with any keyboard layout.

In the apps. The apps print the bill-code QR too: the Android waiter app on the table pre-check, Cenaly Team for Windows on the bill, and the Android, Windows and Ubuntu POS apps on the “🧾 Guest pre-bill” (the code of the whole table, not of one guest). It is switched on by the same location option in “POS appearance”. Scanning in the POS apps works as in the web POS: with the camera (the scan button), a barcode scanner, or by typing the digits in “🔢 Code entry”. One difference: if a new ticket that has not been sent yet is on the register, the app does not open the scanned bill over it — it asks you to send or clear the current ticket first, so nothing you rang up is lost. The “🧾 Open bills · N” list with the same order-type chips is in the POS menu (☰): the oldest bills on top, a tap opens the bill in the ticket. The waiter app does not open a bill by scan — the POS does.

If you cannot find the order, check the selected location and use the general Orders section. A ready dish does not mean the bill has been paid.

Stale open bill banner#

To keep a bill forgotten yesterday from hanging until the shift closes, turn on ⏰ Bill open longer than in the location’s POS appearance and pick a threshold: 4, 8, 12 or 24 hours (default Off). When the location has open bills older than the threshold, a yellow banner appears above the ticket lines — in the hall, at the bar and at the counter:

• one bill — Bill #123 · Table 5 has been open for 26 h and an Open button;
• several — their number, the oldest one and the Open (oldest) and All open bills buttons.

Hide removes the banner until a new stale bill appears. The bill currently open on the till is not included. The banner blocks nothing: new bills open as usual — it only reminds you to close or pay the old one so the shift report adds up.

In the POS apps for Android, Windows and Ubuntu the same banner sits above the menu of the order screen; the threshold is the same location setting from the admin. Open opens the oldest bill; there is no separate All open bills button there.

Suggest an addition#

With Upsell hints enabled, adding a dish can show Suggest with this: recommendations above the ticket. Offer the addition to the guest first; after they agree, tap its chip and select options if needed.

Dish relationships are configured in the dish card; suggestions can also use combinations frequently ordered together. If no suggestion appears, check the setting and whether related dishes are available.

Apply a promo code before payment#

In web POS, enter the code in Promo code, tap Apply and check the total. Tap Remove coupon to remove it. The field is available when the discounts and coupons block is shown.

When a known reason is available, POS shows it: for example, No such promo code at this location — check the spelling., This promo code is switched off. or This promo code has been used the maximum number of times. Date, amount and item conditions share a message naming those conditions; an unknown reason falls back to Invalid or not applicable. Follow the hint and ask a manager to review the terms if needed. Cenaly Team has no promo-code input.

EGAIS alcohol sales (cenaly.ru)#

For a bottle requiring an excise stamp, add the item and scan its PDF417 stamp at Scan the excise stamp. POS checks the scan format and prevents attaching the same stamp to two lines of the ticket. A valid format alone does not confirm that the bottle belongs to your location: UTM may still reject it.

A rejection shows EGAIS rejected the sale, the UTM message and The operation was NOT completed — do not take the money and do not hand over the goods. If equipment or the catalogue is unavailable, the message is EGAIS fixation is impossible right now — the register/UTM or the product catalogue is unavailable.

POS blocks the alcohol sale until registration succeeds. The rejection dialog has no “skip” or “take a prepayment” bypass: prepayment does not replace registering the sale. Resolve the cause and retry.

Pay for alcohol items in a single receipt: bill splitting and moving to a tab have additional restrictions. See marking errors, EGAIS and beer and inventory.

Limitations#

• POS does not automatically turn individually added dishes into a combo: add the combo item itself and choose its components.
• Courses are assigned to individual lines; bulk assignment and a “cook everything now” command are unavailable.
• On Android, Windows and Ubuntu POS, courses are fired and prepped ahead from the waiter app, Cenaly Team or web POS: the native POS ticket has no Fire course or ⏩ Prep ahead buttons yet. The iOS waiter app has no courses.
• You can repeat the selected item or the whole last round, but not the entire order. Weighed, marked, serial-numbered, time-billed items and variants added by scan are not copied — add them the usual way.
• The stale bill banner is only a reminder: it does not block opening new bills.
• Stock on a tile is informational; the stop list blocks adding unavailable items.
• The waiter app does not include web POS bill splitting or promo-code entry. Transfer and cancellation capabilities also differ.

Troubleshooting#

Frequently asked questions#

Do I need a new order for an additional dish? No. Open the table’s bill, add the items and save the changes.

Does firing a course mean the food is on the table? No. It releases a held course for preparation; actual service is recorded separately in the waiter app.

Can I remove a paid item with the delete button? Use a refund through receipt history for a paid sale.

Related sections#

POS · Floor plan · Hall panel · Waiter app · Orders and bill splitting · Kitchen display · Kitchen printing · Receipts and refunds · Option groups · POS discounts and promo codes · Service charge · Shift manager tasks · Roles and permissions · Tech cards · Several POS devices per location