> ## Documentation Index
> Fetch the complete documentation index at: https://docs.now-os.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Order actions

> Add a kitchen note, set covers, print the bill, reprint a kitchen ticket, and void an order from the Actions tab on the NowOS register.

The **Actions** tab gathers everything you can do on an order besides adding items: the kitchen note, covers, printing the bill, reprinting kitchen tickets, and voiding the order.

<Note>
  This page applies to **restaurant mode**. In **retail mode**, *before* payment
  the right-hand panel is a simple cart with no **Actions** tab: you go straight
  to payment (see [Taking payments](/en/pos/payments)). *After* payment, a paid
  order offers an **Actions** sheet (reprint receipt, issue invoice, refund) —
  see [Receipts and printing](/en/pos/receipts-printing).
</Note>

## Open the Actions tab

Open an order, then tap the **Actions** tab at the top of the right-hand panel (between **Check** and **Guest**). You can also swipe the panel left from the **Check** tab. The **Split**, **Pay**, and **Send** buttons stay visible at the bottom while you use the tab.

A badge appears on the **Actions** tab when the order carries a kitchen note: everyone can see at a glance that there is something to know about this order.

## Add a kitchen note

The kitchen note is free text attached to the whole order. It prints at the top of every kitchen ticket for this order, starting with the next round you send.

<Steps>
  <Step title="Tap Order note">The **Order note** window opens.</Step>

  <Step title="Write the note">
    Type your text in the **Note** field, or tap a quick chip — **Allergy**,
    **No ice**, **Rush**, **Serve together**. Each chip is added after what is
    already written; it does not replace it.
  </Step>

  <Step title="Tap Save note">
    The note is saved. The **Order note** row icon turns blue and the badge
    appears on the **Actions** tab.
  </Step>
</Steps>

To edit the note, reopen **Order note**: the field is pre-filled. To remove it, clear the field and tap **Save note**.

<Note>
  The note goes to the kitchen with the **next** round. Kitchen tickets already
  printed do not change — if the dish has already gone out, tell the kitchen in
  person or reprint the ticket (see below).
</Note>

<Note>
  **Order seated from a reservation:** the internal note written in your
  reservation provider is already there when you open the order — nothing to
  copy over. What you write here travels back to the provider, and what changes
  there comes back here. Last edit wins.
</Note>

## Set covers

Covers are the number of guests at the table. The **Covers** row shows a **− / +** stepper:

* tap **+** to increase the cover count (the first tap goes from "—" to 1);
* tap **−** to decrease it, down to a minimum of 1.

The cover count shows at the top of the order panel (for example "4 covers") and prints on the bill. It is also requested if you issue a single invoice for the whole table.

<Note>
  When the table was opened from a **reservation**, the correction is sent back
  to your reservations provider: the booking there moves to the new cover count.
  You never have to change it in two places — and the old number cannot come
  back onto the order at the reservation's next update.
</Note>

## Discard items not yet sent

When the order contains items that have not been sent to the kitchen yet, the **Discard new items** row appears, with the number of items concerned. Tap it to remove all pending items at once — for example when the customer changes their mind before you send.

<Warning>
  The removal is immediate, with no confirmation. Items already sent to the
  kitchen are not affected: for those, void the line from the **Check** tab.
</Warning>

## Print the bill

**Print bill** prints the bill to present to the customer before payment.

<Steps>
  <Step title="Send the items first">
    The bill can only be printed after at least one round has been sent to the
    kitchen. Until something has gone out, the row shows **Nothing sent yet**.
  </Step>

  <Step title="Tap Print bill">
    The row shows **Printing…** then **Queued**: the bill goes to the receipt
    printer.
  </Step>
</Steps>

If you split the check, **Print bill** prints one slip per check still open, each labelled "Check 1 of 2", "Check 2 of 2", and so on. See [splitting the check](/en/pos/payments).

<Note>
  Printing always runs through the main register — it is the one driving the
  printers. From a secondary device (another iPad, or the handheld), the print
  rows send the request to the register over your local network, and the
  document comes out of the same printers. If no receipt printer is configured,
  the register tells you. See [Receipts and
  printing](/en/pos/receipts-printing).
</Note>

## Discount or comp

**Discount** lets you reduce the price of an order — or offer items on the house — before payment. The screen opens for anyone; **manager approval is decided at Apply**: a free discount, a comp, and a preset with a lock need a manager (PIN, or nothing if a manager is already signed in); a preset configured without a lock applies in one tap.

<Steps>
  <Step title="Tap Discount">
    The discount screen opens with every item selected — ready for a discount on
    the whole check. To target specific items, tap **Clear** and select them one
    by one; the **− / +** stepper picks how many units of a line are concerned
    (1 of 2 coffees, for example).
  </Step>

  <Step title="Choose the type">
    * **Percent** — a percentage off, with **5 % / 10 % / 20 %** shortcuts or
      the keypad; - **Amount** — an amount of your choice, typed on the keypad; -
      **Comp** — the selected items are offered: they stay on the bill at zero; -
      **Presets** — named discounts prepared ahead of time ("Loyalty club",
      "Staff"…); one tap applies them with their value, their name serving as the
      reason. See [Discounts](/en/backoffice/discounts).
  </Step>

  <Step title="Give the reason">
    For a free discount or a comp, the reason is required: pick it from the list
    your venue has set up (managed in the backoffice). You can add a short
    free-text **note**. A preset already carries its name as the reason.
  </Step>

  <Step title="Confirm">
    Tap **Apply** (or **Comp**). If the action needs a manager and none is
    signed in, a manager enters their PIN. The discount shows on the check with
    its reason, and the new total applies to the bill and the payment.
  </Step>
</Steps>

A comped item stays visible on the order and the receipt at **0.00** with its original price struck through — that is the difference with a void: the dish was made and served, it is simply not charged.

To remove a discount before payment, tap the **✕** next to its line in the check totals. The full price comes back immediately.

<Note>
  One percent or amount discount at a time per check — remove it before applying
  a different one. Comps can be added freely as long as units remain. Once a
  payment has been taken on the check, the discount is locked: refund the sale
  instead if needed.
</Note>

## Reprint a kitchen ticket

On the main register, once at least one round has gone to the kitchen, the **KITCHEN** section lists each round: **Reprint round 1**, **Reprint round 2**… with the time it was sent and the item count. Tap a row to reprint the kitchen ticket for that round — handy if the ticket got lost or the printer had an issue.

A round whose items have all been voided disappears from the list: there is nothing left to reprint.

## Void the order

**Void order**, in red at the bottom of the tab, cancels the whole order: it disappears from the floor and does not count in your sales.

<Steps>
  <Step title="Tap Void order">
    If items have already gone to the kitchen and you are not a manager, the
    **Manager approval** window opens first: a manager enters their PIN to
    authorise the void. On a draft order (nothing sent yet), this step does not
    exist.
  </Step>

  <Step title="Check the summary">
    The **Void this order?** window opens, with the order summary (item count,
    total).
  </Step>

  <Step title="Give a reason">
    The **Reason** field is optional — for example "Customer left" or "Test
    order". If items have already gone to the kitchen, take the time to fill it
    in: it prints on the void ticket the team receives.
  </Step>

  <Step title="Confirm with Void order">
    The order is voided and the register returns to the orders list. If items
    had already gone to the kitchen, each station involved receives a void
    ticket so they know what to discard.
  </Step>
</Steps>

<Warning>
  Voiding is final: it cannot be undone. And as soon as a payment has been taken
  on the order — even a partial one — it can no longer be voided: the **Can't
  void this order** window points you to [the refund](/en/pos/refunds) instead.
</Warning>

## On a paid order

The **Actions** tab stays useful once the order is paid. On the main register, as soon as a check is paid, the **RECEIPTS** section appears with, for each sale:

* **Reprint receipt** — reprint the sale's receipt, see [Receipts and printing](/en/pos/receipts-printing);
* **Issue invoice** — issue an invoice for this customer.

When every check is paid, the **Refund** button appears at the bottom of the tab. Refunds are reserved for managers and run from the main register, with internet — see [Refunding a sale](/en/pos/refunds).
