Send, hold, and fire a service round
For front-of-house and kitchen staff working a dine-in order. Check the table,
order, items, and round before Send. A round's preparation timing and the
order's payment state are separate.
| State/control | Meaning in the current app |
|---|
| Pendings | Items still being composed |
| Kitchen starts on send | The round starts when sent |
| Held until you fire it | Sending records the later round but holds preparation |
| Fire while pending | Chooses that this later round starts when sent; it does not itself print |
| Fire on a sent held round | Releases it on station displays and sends the fire ticket |
| Fired | Preparation was released; not proof it is served or paid |
The first round starts on send. Later rounds are held by default unless their
pending Fire control is selected. Read the round's displayed status rather than
assuming every sent item starts cooking immediately.
Together is offered for dine-in when both supported serving styles are
configured. It expresses pacing, not another order or payment. Sent-round pacing
can become information-only. Moving a pending round earlier changes its
sequence; verify its items and resulting round number before sending.
Before firing a held course, confirm with the kitchen and floor team that the
guest is ready. Firing is not a second sale and does not create another stock
deduction for the same accepted items. Do not resend the items to make a fire
ticket appear after a printer failure.
After an uncertain Send or Fire, inspect that same order, round, kitchen state,
and print queue before retrying. A local optimistic change can still await sync.
Use Connection and sync and
Printer recovery while preserving pending work.