SpicyChef.io
Log in

POS service sessions

POS service sessions

What this feature is for

A service session is the operational center of the POS. Run it from /pos/service: it groups the orders, table moves, and service context for one booking or walk-in from the moment guests sit down until settlement.

Who can use it

Owners, Admins, and Staff can open sessions and orders. Seating a booking opens its session automatically as a best-effort side effect, so most sessions start without a manual action.

Availability and required module/permission

Service sessions require the POS module plus the session and order permissions. Floor-plan status stays booking-owned; the POS session enriches the table panel but does not replace availability derivation.

Prerequisites

At least one orderable product with complete financial metadata (price, currency, tax, accounting category) must exist before you can add items to a session.

Common tasks

  • Open a session: seat a booking or create a walk-in; both open a get-or-fetch session with no duplicates.
  • Work the session: add orders, move the table, and follow the service from a single view.

Buttons and statuses

Active sessions hold their tables in the POS service view until closed. An expected departure can warn as ending soon but never auto-releases the table.

Warnings and important constraints

Orders and table assignments belong to the session, not to the table. Moving a table updates assignment history without moving or recreating the order.

Troubleshooting guidance

If a session did not open on seating, confirm the POS module is active and that you hold the session-open permission; you can then open it manually from the service view.

Related articles

  • Take or record a payment

Related articles

Reviewed 2026-07-13Source: official SpicyChef documentation