Does PosIQ fit your service?
PosIQ fits where orders, tickets, payment and day-end should share one flow across iPhone and iPad.
12 situations
Split one bill across several guests
Split bills come out of the open transaction, so service does not have to capture anything twice.
See a concrete example
Starting pointSix guests at table 12 want to pay separately, two of them together.
PosIQ in useThe bill is split by guest or by item without leaving the transaction. Cash and card can be combined in the same close, and tips are accounted for within the total.
Get a special request safely into the kitchen
Special requests stay attached to the position and travel with the ticket to the right station.
See a concrete example
Starting pointA guest orders the main course without onions; the order is taken on the iPhone at the table.
PosIQ in useThe request stays connected to the position and appears on the kitchen ticket. Shouting across the pass is no longer needed.
Two team members on the same table
A soft table lock prevents duplicate entries when two devices open the same order.
See a concrete example
Starting pointWhile a colleague is still ordering, someone opens the same table on the iPad.
PosIQ in usePosIQ reports the already open transaction instead of creating two separate states. Whoever takes over sees straight away what is running at the table.
Keep working when the connection drops briefly
Core steps continue locally and reconcile again afterwards.
See a concrete example
Starting pointWi-Fi is weak on the terrace and the connection drops for a moment in the middle of service.
PosIQ in useThe table plan stays usable locally, the print queue buffers open tickets and releases them afterwards. Service does not have to capture anything twice.
Quick counter sales without a table
Short sales close directly, without opening a table first.
See a concrete example
Starting pointIn the morning, coffee and rolls go over the counter minute by minute.
PosIQ in useThe quick sale runs without a table assignment and still lands completely in the day-end close.
Take card payment and close the table on the spot
The card payment is recorded in the open order; amount, tip and receipt stay together.
See a concrete example
Starting pointThe guest wants to pay by card, the terminal is at the counter and the table is on the terrace.
PosIQ in useToday the payment runs through the payment provider's terminal and is booked into the order at the table. Integrated payment directly on the iPhone via GP tom is prepared.
Issue a receipt without handing out paper
The fiscalized receipt can be issued digitally by QR code or printed.
See a concrete example
Starting pointThe guest does not want a paper receipt, but the receipt obligation still applies.
PosIQ in usePosIQ issues the receipt as a QR code or a printout. At close, it stays visible which transactions are fully fiscalized.
Route food and drinks to different stations
The category of a position decides whether it goes to the kitchen, the bar or the counter.
See a concrete example
Starting pointOne order contains food for the kitchen and drinks for the counter.
PosIQ in useRouting happens through the category, without capturing twice or assigning manually. Courses can be fired separately.
Close the day cleanly at two in the morning
Cash count and Z-report come out of the trading day instead of later rework.
See a concrete example
Starting pointAfter the last payment, the day should be closed quickly and traceably.
PosIQ in useThe cash count shows the difference against the expected balance. The closed day produces the Z-report as a PDF.
Trace how a day's revenue came together
Closed days stay documented, broken down by payment method and VAT rate.
See a concrete example
Starting pointSomeone asks how revenue and tax rates for a particular day are composed.
PosIQ in useThe closed day is available already broken down and does not have to be reconstructed from several systems.
Onboard a weekend stand-in
Roles and permissions define what is possible. Login runs by PIN or QR code.
See a concrete example
Starting pointA stand-in works with the system for the first time and should not be allowed to do everything.
PosIQ in useLogging in takes seconds, permissions are stored per role, and every sale stays assigned to the employee who served it.
Sell at a market with very little setup
The device setup stays limited to iPhone and iPad, without fixed infrastructure.
See a concrete example
Starting pointA food truck works from changing locations with two devices.
PosIQ in useOne to ten devices belong to the same business without a monthly device surcharge. During short outages, selling continues locally.
Run through a real service flow.
A table, special request, kitchen ticket, split bill and day-end quickly show whether PosIQ fits.
Request advice