Service modes and device profiles

Admin → Settings → Devices → Modes

Choose a mode profile

Review the available mode profiles and select the one intended for the POS device. Check enabled modules and the device assignment before use.

Configure table and counter behavior

Review seating, covers, service courses, kitchen sending and return-to-menu behavior in the corresponding POS settings. Save and verify on the intended device.

Keep fulfillment independent

Configure the restaurant's fulfillment methods and prompt separately from the table layout and device mode profile. The whole-check method determines its overall service; an item choice is a preparation exception and does not create a separate delivery. Review whole-check and item choices before changing a sale. A payment does not hide an order from Orders → All or automatically mark its preparation complete. Mode selection and any customer prompt precede items in a new onsite sale. The table/check is chosen only at Send/Continue; cancellation preserves the source. See whole-check fulfillment. Private guest context is staff-only, never a public checkout answer or notification variable.

Save a shared mode and recover a conflict

A mode is shared by all assigned devices. Save requires the updated API’s conflict-safe settings capability. Independent edits to different fields can merge; a competing edit to the same field is rejected and your draft remains visible. Do not repeatedly save that stale draft. Choose Reload saved settings, confirm discarding the unsaved draft, then review the latest policy and apply only the intended edit. The same recovery applies when the server cannot confirm the save. A read-only or older-API screen cannot enable the new save contract. The updated POS refreshes the shared policy in the foreground about every 30 seconds, on resume, navigation and after an action; an active payment, send or item edit defers application until its safe completion. This refresh never repeats the action. Confirm the intended device assignment and effective modules before serving.

Review and edit Modes in Admin

In Settings → Device management → Modes, search, sort by name or assigned-device count, and change the page size. Select a mode name or its options button to open its side panel without leaving the list. Review the assigned devices, then Manage opens the full-screen editor. Rename stages the new name; Save explicitly persists it. Creating a mode or deleting selected modes is also staged until Save. Closing a panel retains the list draft; leaving with changes asks whether to discard. A save error retains the draft. Only settings-edit permission can mutate profiles; read-only staff can inspect the panel. An unavailable device is reported rather than silently reassigned. Creation dates show a dash because the current API does not supply mode creation dates. Restaurant defaults remain separately accessible and are not a physical device profile.

Confirm or undo deletion from the mode editor

With settings-edit permission, open an existing mode through Manage and choose Delete mode, then confirm. This only stages the removal: the original mode name stays in the header and Deletion pending explains the next step. Save confirms the deletion and returns to the Modes list only after the server confirms the saved policy. Undo deletion restores the complete edited profile, including its unsaved changes, so you can continue editing; it does not send a request. A failed, conflicting or unconfirmed save keeps the pending deletion visible. Follow the shared-mode save recovery before retrying a stale draft; accepting Reload saved settings discards both that draft and its undo snapshot. A mode already absent when the editor loads is reported as missing, not as a pending local deletion. Do not delete a working profile to test this flow: assigned devices fall back to restaurant defaults after the removal is saved.

Return home after sending and start a fresh sale

In the effective device mode, open Open checks, enable Use on this mode and Use Open Tickets as the home screen, then Save. Refresh settings on the POS. After a confirmed Send, a table check returns to the floor plan. On a compatible iPad, a named check returns to Orders → Checks, the same view reached through Actions → Open tickets; use the view picker in portrait. Phones/compact handhelds return to their existing Open tickets workflow. Returning to Menu opens a separate empty sale; it does not reopen or erase the sent check. Reopen the saved check from its table or open-check list to add more dishes. The original customer, bill and kitchen batches remain there. Continue/Send and stay retains the current check. Failed sending or a changed restaurant, permission or editor context does not detach the source. Another unsent counter basket is not cleared. With the home setting disabled this new-sale handoff is not applied. All saved orders remain tracked on POS and Admin; payment, preparation and check closure stay independent.

Review independent confirmations

POS fulfillment methods provide separate preparation and handoff tracking. Save the method’s policy in the global catalog. It applies to new sales and remains frozen with them; later changes do not rewrite history. Shared device-mode modules remain distinct from this global policy. See tracking settings.