Here is what each connection does, what is live and what is still introduced with a pilot. An integration is not called complete until the full flow has been tested in the receiving service.
Card, QR payments and split checks stay on the same receipt. Staff see what went through, what is waiting and what needs recovery.
What is ordered on the floor should print in the kitchen without a second system.
Kitchen display with order queue and stations — alongside printer tickets.
Hotel guests pay to the room from the POS. The folio lives in Mews — not as an extra line in the books.
Tickets sell in the same register as food and drink. No extra iPad for box office.
The day’s sales become a voucher in Fortnox. You connect the company once per outlet, then send Z — automatically or by hand.
Partners read menu, checks and sales without entering the POS.
A simpler register when it has to be fast — the same numbers as the full POS.
SIE4 is built from the same Z as Fortnox — for agencies and other ERPs.
External orders should land in the same order flow as the floor — not a parallel system.
Staff and scheduling platforms follow once service, payments and hotel flows are verified.
Auth, endpoints, rate limits and webhook signatures — the partner documentation you expect from a core API.
A hotel using Mews, or an arena and event venue? We review your integration needs and propose a focused, paid pilot at favourable pricing. Scope and pricing are provided in a quote.