# Set up a self-order kiosk

For the restaurant manager preparing a customer-facing device. Confirm the
location, device, menu, terminal, payment arrangement, and kitchen routing
before launch. Location settings and device settings are separate saves.

## Set the location's presentation

Open **Console → Settings → Location settings → Kiosk**.

1. Set **Items per row** to **Auto (fit the screen)** or an explicit column
   count. Verify the result on the kiosk's actual screen size.
2. Review **Collect customer details**: **Off**, **Optional**, or **Required**.
   Required prompts for details before reset; it does not prove every customer
   supplied them or require marketing consent.
3. Review **Print receipt** and **Email receipt**. Email receipt can offer
   email/QR capture even when customer-details capture is Off. Check the actual
   confirmation screen rather than assuming Off hides every details prompt.
4. Save the location settings, reopen, and verify them. A successful save does
   not launch a device, connect a reader, or test receipt delivery.

Marketing consent is a separate opt-in. Staff must not tick it on a guest's
behalf just to provide a receipt. Follow [Guest consent](/marketing/consent).

## Prepare the device and launch

In the staff app, open **Settings → Kiosk** on the intended device. The
Console's [Devices](/settings/location/devices) page also has device-level kiosk
controls.

1. Select the **Terminal** configured for kiosk orders. If absent, have the
   manager review that terminal's allowed order types and device sync.
2. Choose the supported **Card provider** where configured. If the screen says
   no provider is configured, complete [Payment setup](/payments/payment-setup)
   and the appropriate reader checks before offering card payment.
3. Set a private **Exit PIN** of 4–6 digits. Tell authorised staff how to obtain
   it through the restaurant's normal access process; keep it out of captures.
4. Review **Order types** and keep at least one enabled. Check the guest's
   available Dine in/Takeaway choices and the kiosk menu for those choices.
5. Review tip settings and idle/confirmation timing. The idle timeout is not a
   payment recovery timer; do not use it to decide a payment failed.
6. **Save** can retain partial settings without launch. Resolve any launch
   validation, then use **Launch kiosk mode → Launch** only when ready.
7. Verify the actual welcome screen and complete the safe checks below.

The current app's launch confirmation explains exit: on the welcome screen, hold
the top-left corner for four seconds, then enter the exit PIN. Check the
installed release's prompt before handing over the device; controls may differ
from local development. Do not upgrade the native app simply to match a guide.

## Verify before inviting guests

Use a test agreed with the shift leader and keep it separate from live kitchen
work and guest payments.

| Check             | Confirm                                                                                            |
| ----------------- | -------------------------------------------------------------------------------------------------- |
| Menu              | Correct location, items, availability, prices, photos, and ordering channel                        |
| Choices           | Required sizes/options and final cart quantities and total                                         |
| Guest information | Accurate allergens and translations; warnings are not allergy certification                        |
| Payment           | Intended provider and reader, confirmed outcome, correct amount, and order record                  |
| Kitchen           | One intended order reaches its station; a screen confirmation is not a physical ticket check       |
| Receipts          | Actual paper output and intended email/QR flow; the print button alone does not prove connectivity |
| Reset and privacy | Completed order leaves no guest details visible for the next guest                                 |
| Exit              | Authorised staff can return to the operator interface and review sync status                       |

Check the guest sequence: welcome, order type where offered, browsing and
choices, cart review, tip/payment where offered, then confirmation with its
order number. Receipt failure is separate from a successful payment and order.
Record any uncertain outcome and use [Kiosk recovery](/troubleshooting/kiosk).

## Hand over the kiosk

Tell the shift leader which device, terminal and provider are in use, how guests
ask for help, who controls the PIN, and which printer handles orders/receipts.
Monitor actual orders and payment recovery during service. Save layout or
receipt changes at the location level and launch/access changes at the device
level; verify both after any uncertain save.

See [Menu setup](/guides/menu-management),
[Kitchen setup](/orders/kitchen-setup), and
[Kiosk recovery](/troubleshooting/kiosk).