No integration project. Ever.
Perkaria runs on its own tablet, beside the register you already have. Nothing gets installed in your POS, nothing plugs into it, and nothing we do can break it. Your till rings sales the way it always has — Perkaria handles the loyalty right next to it.
Every plan works this way. There's no integration tier, because there's no integration.
Compatibility
If you can ring a sale, you can run Perkaria.
The setup is identical no matter what sits on your counter: a tablet beside the register. That's why this list is short on fine print — there's no connector to build, so there's nothing to be incompatible with.
Square
Perkaria sits beside it on its own tablet. Your Square terminal keeps taking the money.
Clover
Nothing added to the device, nothing from an app market. The two run side by side.
Lightspeed
Restaurant or retail, same setup: your screen rings the sales, ours handles the loyalty.
Toast
No module to enable, no permissions to grant. Perkaria never touches it.
TouchBistro
Two tablets on the counter, each doing its own job. That's the whole architecture.
Maitre'D
A Québec staple. Works alongside it like everything else on this list.
Veloce
Another Québec regular. Same answer: nothing to connect, nothing to configure.
Legacy & no-API systems
No API? Perfect — we weren't going to call one anyway.
Cash register only
A standalone register — or just a cash drawer — is all the counter flow needs from your side.
Square, Clover, Lightspeed, Toast, TouchBistro, Maitre'D and Veloce are trademarks of their respective owners, named here only to say that Perkaria works alongside them. No partnership or endorsement is implied — that's rather the point.
What “alongside” means
Two moments a day. That's the whole overlap.
Your POS and Perkaria meet exactly twice: for two taps during service, and for one file after close. Here's each one, concretely.
Separate by design
Your POS can't even tell Perkaria exists.
There's no code in your register, no middleware box under the counter, no update from us that can take your till down on a Saturday night. If the tablet loses Wi-Fi, your POS keeps ringing sales like nothing happened — because as far as it knows, nothing did.
- Runs on its own tablet, with its own connection
- Nothing installed in the POS — no module, no plugin, no script
- A Perkaria hiccup can't stop a sale; a POS change can't break your program
- The counter app is PIN-gated, so only your team records visits
During service
Two taps, while the card machine does its thing.
A visit is recorded on the Perkaria tablet in two taps: find the member, tap to stamp or add points. It's built for the rush — big buttons, and every action is safe to retry if the connection hiccups. Joining happens once, at the counter, in about ten seconds: phone number in, text message out, card on their phone. No app to download, no password to invent.
- Two taps per visit — find the member, stamp
- New members join in about 10 seconds with a phone number
- Magic-link sign-in for members: no app, no passwords
- The sale itself doesn't change — the register does that part, as always
After close
The sales export keeps everyone honest.
The only thing Perkaria ever reads from your POS is the daily sales export it already produces. Overnight, the day's stamps and points are reconciled against it: entries land as pending during service and are verified against your sales before they count. One file a day — that's the entire bridge between the two systems.
- Stamps and points stay pending until they're reconciled against your sales
- Reads the daily sales export your POS already produces — no API required
- Works with any system that can export its sales
- Gift-card balances go through the same nightly reconciliation
Fair questions
Before you ask
Will it slow down my line?
It's two taps during service — find the member, tap to stamp — on a screen designed for rush hour. Signing someone up happens once and takes about ten seconds: phone number, done, the card arrives by text. Nobody stands in your line downloading an app or resetting a password, because there's no app and there are no passwords.
My POS has no API. Is that a problem?
No — it's the exact situation Perkaria was designed for. We never call a POS API; the only thing we read is the daily sales export your system already produces, for the nightly reconciliation. If your register can export the day's sales, you have everything the setup requires. Nothing is ever installed on the register itself.
What happens if I switch POS?
Your program doesn't notice. Members, stamps, points, rewards and gift-card balances all live in Perkaria, not in your POS — so there's nothing to export, migrate or rebuild. On our side, switching means one adjustment: the nightly reconciliation starts reading the new system's sales export instead of the old one's.
Keep reading
The rest of the picture
Ready to meet your regulars?
Book a 20-minute demo — we'll set up a sample program with your brand on it, live, while we talk.