Payment terminals & status
Terminal payments and status stay attached to the correct check so staff can see what succeeded, is pending or needs recovery.
IN PILOTIntegrations
An open system. Not a dead end.
Here we show what can be used in pilot, what is being verified and what comes later. An integration is not called complete until the full flow has been tested in the receiving service.
Current statusIN PILOTTECHNICAL PILOTNEXT / LATER
Kitchen printers
Tickets and correction tickets are sent from the order flow to configured printers. A full KDS is a separate future track.
IN PILOTMews PMS
Room charge to guest folio and optional sales sync to outlet bills. Connection and mapping are set per outlet in Backoffice.
IN PILOTOpen API
Public REST API v1 (menu, Orderhanterare, checks, sales) with per-outlet keys and HMAC webhooks.
IN PILOTQuick Sale
Simplified per-device selling surface for fast checkout on iPhone, S1F2 and PAX.
IN PILOTAccounting & SIE
Account mapping, vouchers and SIE records exist. Import compatibility is being verified before general availability.
TECHNICAL PILOTOnline ordering & delivery
External orders and delivery platforms will eventually enter the same operational order flow.
LATERStaff & scheduling
Staff and scheduling platforms follow after the core service, payment and hotel flows are verified.
LATERDevelopers
Open docsOpen API docs
Auth, endpoints, rate limits and webhook signatures — the partner documentation you expect from a core API.
Pilot
Book a pilot walkthroughWhich systems need to come with you?
Tell us which connections are business-critical. They become part of the pilot's technical discovery.