Questions a multi-location operator asks first
Short answers, including the ones where we come off worse. Every claim here is something you can check in your own account.
Who owns the guest data and the payments?
You do. Each payment is charged directly on your own account, so you are the merchant of record and the money is yours before any fee comes out. Guest records belong to the location that collected them, and you can export or delete them whenever you want.
Can two unrelated brands sit in one group without mixing?
Yes, and they stay properly separate. A group is owned by a business rather than by a person, so one operator running two unrelated brands gets two independent groups with their own payouts, menus and guest records. Switch between them from the business chip in the top bar.
Can we bring our existing customer list across?
No, and that one is deliberate. We stopped accepting imported contact lists because we cannot tell whose consent came with them, and one bad list burns the sending reputation every other merchant on the platform shares. Guests join when they scan, book or ask for a receipt. Menus and items do import.
- None today, and that is the honest answer. QRDERS is the ordering and payment layer itself, so orders land in your order feed, on the kitchen display and on a kitchen printer without a till in between. If your group runs on a POS you intend to keep, this is the row where a competitor beats us.
- We have never run a ten-location rollout, so any number here would be invented. What we can tell you is the shape of the work: each location signs up for payments in its own name, and the menu is built once and pushed to the rest from this page.