A rewards program without the punch card

The customer who paid at the register claims their own points

This is the part that makes a loyalty program actually work in a small shop, and it is the part standalone loyalty vendors cannot solve. Someone pays at the counter with no account and no phone number on file. Under every other system, that visit earns nothing, because earning would require your staff to sign them up while a queue builds behind them.

Here the receipt carries a QR code. The customer scans it on their own phone, on their own time, and claims the points themselves. No sign-up at the counter, no staff training, no line held up, and no awkward pitch from someone who is trying to make coffee. The visit lands on a real customer record and the points land on their balance.

• Walk-in self-serve earn through a receipt QR code
• No account needed at the point of payment
• Nothing for staff to learn and nothing that slows the counter down
• The visit becomes a real customer record, not an anonymous sale

One balance, every location

If you run more than one shop, the customer earns at one and redeems at another. One balance, one customer, one brand. That sounds obvious until you try to buy it, at which point you discover that most loyalty products are built per store and quietly assume you only have one.

For a growing business this is the difference between a rewards program that encourages people to visit whichever of your locations is convenient today, and one that trains them to think of your two shops as two different businesses. See how multi-location and franchise operators run this centrally.

• Earn at one location, redeem at another, on one balance
• One customer identity across every store you run
• Per-location configuration with brand-level defaults

A real ledger, configured the way your business works

Underneath is a points ledger, not a counter someone can nudge. You set the earn rate, the welcome bonus for new members, and the catalog of rewards customers can spend points on. What you configure is what the ledger enforces.

Redemption applies as a real discount, tracked and idempotent, so a reward cannot be spent twice by refreshing a page or by two staff members processing the same thing at once. This is the same append-only approach that keeps the customer counters honest, applied to something where the accounting has to be exactly right.

• Configurable earn rate, welcome bonus, and a reward catalog you define
• Redemption applied as a real discount, tracked end to end
• Idempotent redemption, so a reward cannot be double spent

Earning happens on its own, online and at the counter

Points are earned automatically on orders placed through the platform, so anything booked or ordered in chat, on the website, or by phone earns without anybody remembering to do anything.

They are also earned on sales rung up at the point of sale, because most of your revenue still happens at the register. With Clover or Square connected, counter sales feed the same ledger as online orders. See how ordering and the POS integration work.

• Automatic earn on orders placed through the platform
• Automatic earn on sales rung up at the register, via Clover or Square
• One ledger behind both, so the balance is always the whole picture

The receptionist can answer "how many points do I have"

A customer asks that question in a WhatsApp thread at nine at night and gets a real answer, because the ledger and the receptionist are the same system. No standalone loyalty app can do that. It would have to be told, by an integration somebody maintains, and it would be out of date by one visit.

This is the quiet argument for keeping loyalty inside the platform rather than bolting on a separate vendor. The points are not a parallel universe. They are one more thing the front desk knows about the person it is talking to, alongside their last visit, their usual order, and the appointment they have on Thursday.

• Balance questions answered in chat by the AI receptionist
• The rewards wallet also lives in your own branded customer app
• One system, so the balance is never stale

Questions owners ask