Waiter pad

Goal

Take table orders on the floor, send courses to the kitchen, and print/settle the bill.

Who it is for

Wait staff with pos.restaurant.kitchen.send (nav/route) and pos.view. Table ops may also need transfer/merge/split permissions.

Preconditions

• Floor plan and tables configured; menus/modifiers ready.
• Terminal selected for the pad (bos.waiter.terminal_id).
• Open session when settlement posts through the register path.

Steps

1. Open Waiter Pad (/waiter).
2. Review floor: table statuses available, occupied, reserved, cleaning, seated (GET /v1/pos/restaurant/floor).
3. Open a table → add menu lines and modifiers → Send to kitchen (POST /v1/pos/restaurant/orders with order_type: dine_in, send: true, metadata.source: 'waiter_pad'; add-ons via …/orders/{id}/items).
4. Load bill, print (…/bill/print), then settle on payment when ready (split bill if permitted).

Result

Kitchen tickets fire; table shows occupied/open check. Stock still settles on payment — sending to kitchen alone does not issue inventory.

Hard stops

• item_already_sent when editing sent lines — void instead.
• item_sold_out / off menu.
• Void after send may require manager approval (void_approval_required).

Related

• Kitchen display
• Run a sale
• Reason codes