Ways to Order
One system. Every way they order.
Dine-in, kiosk, takeaway, delivery, an online store — they all run off the same Quivi. Each is just a channel you switch on, not another product to buy. One backend runs them all.
One menu · one payment layer
The stack
Four vendors, none of them agree.
A kiosk from one supplier, delivery from another, an online store from a third, and your POS in the middle trying to keep up. Each keeps its own menu, its own orders, its own idea of what was sold. At the end of the night you reconcile four systems by hand — or you don't, and you guess. You bought a POS and ended up an integrator.
its own menu
its own orders
its own totals
trying to keep up
Four systems. One reconciliation, done by hand.
Same system
Same system. Different service.
Every mode below is one Quivi channel with a different profile switched on — a set of feature flags on one menu and one payment layer. Switch the mode and the guest flow reconfigures. The backend behind it does not change.
Tap a mode to see what the guest sees.
Guest sees
Dine-in QR
Channels & profiles
A channel is a QR. A profile is the job it does.
A channel is a single point of sale — one table, one room, one kiosk, one storefront — each with its own QR code and URL. A channel profile is the template stapled to it: the feature flags for sessions, pre-paid or post-paid ordering, tipping, splits, scheduling. Point twenty tables at the same profile and they all behave the same. Change the profile once, and all twenty update at once.
Channel profile
On SiteChange the profile once — all of them update.
Every service style
Five ways in. One way out.
Dine-in QR
Each table is a channel with its own QR; guests open a session, keep ordering, and pay by QR when they're done. Switch on the split and tipping flags and they can settle evenly, by item, or a free amount.
Kiosk
A terminal that takes the order and the payment before it hits the kitchen; the shared-kiosk flag resets it between guests so nobody inherits a half-built order.
Takeaway / click & collect
Guests pay up front, leave an email, and pick ASAP or a future slot — then track the order from paid to ready, in the same kitchen queue as the room.
Delivery
A pre-paid channel that carries courier name, phone, location, estimated time and a tracking link on the order, so the guest can follow it out the door.
Online store
A pre-paid store on its own URL — email required, scheduling and live order tracking, running off the exact menu your floor uses.
Delivery
We track the courier, not run the fleet.
Quivi's delivery layer routes orders out and follows them back — courier name, phone, location, estimated time and a live tracking link, right on the order the guest already sees. Uber Eats and Glovo are connected too, so marketplace orders land in the same POS and kitchen queue as the dining room.
Live in production. Quivi connects to Uber Eats, Glovo and an on-demand rider integration and routes every order through one system — it just doesn't run the couriers itself.
One backend
However they order, it all lands in one place.
Whichever modes you switch on, every order comes off one menu, through one payment layer, into the same POS and kitchen flow, synced in real time. A kiosk sale, a QR tab and an online order are the same kind of record, read the same way. The count is the count, whichever door it came through.
- All three apps — Backoffice, POS & Guests
- Native Paybyrd payments
- Real-time sync across every device
- Sales-tax-ready receipts & invoicing
Run every service style off one system.
See how one Quivi handles the table, the kiosk, the collection counter and the storefront — without four vendors, four reconciliations, or a second product bolted to the side of the first.
- All three apps — Backoffice, POS & Guests
- Native Paybyrd payments
- Real-time sync across every device
- Sales-tax-ready receipts & invoicing