Restaurants
Campaigns that fill the evening service, points per spend and birthday automation.
In a restaurant guests come less often than in a café, but they leave far more behind each time. That makes the loyalty problem a different one: you know the table, not the person. There is a name in the booking book, but nowhere does it say how many times that name has been in, what they liked, or when they were last seen. A restaurant loyalty system does exactly that job — it ties every bill to a person, separates the regular from the one-time visitor, and fills quiet evenings with a targeted campaign instead of a blanket discount.
Points make sense when the bill varies
One bill is lunch for two, the next is dinner for eight. A fixed stamp ignores that difference; points per spend do not — the guest earns in proportion to what they left, and partial points are recorded too. Points can be given an expiry date, so a balance earned years ago never turns into a surprise cost on a busy evening. If you prefer, you can run a stamp card on a single group of items, such as the lunch menu, and leave the rest on points.
The campaign that fills a quiet evening
Friday is already full; Tuesday is the real question. In the campaign builder you choose the audience — for example guests who have not been in for sixty days — the day and hour, the reward and an end date. A coupon can be single-use, valid at one branch only, or capped at a daily volume. The campaign lands in the notification inbox of guests who use the app, and the coupon is validated by QR at the till, so nobody types codes or decides eligibility by hand.
Tiers: tell the regular apart
Bronze, silver and gold tiers move up on their own as guests pass each threshold, and every tier has its own earn rate and rewards. When the QR is scanned at the till, the guest's tier appears on screen, so the floor team does not have to rely on memory to know who eats here every week. It is the simplest way to create privilege without handing out discounts: the regular feels the difference, and that difference is the reason to keep the habit.
Birthdays, and the guest who disappeared
A birthday gift is issued automatically three days ahead, with a reminder if it goes unused — nobody has to watch a calendar. The same automation works in reverse: guests who have not been seen for a set period become an audience you can invite back. In the panel you follow return rate, revenue per guest and reward cost with a per-branch breakdown, and the cohort report shows which campaign genuinely produced new visits.
Two seconds at the till, nothing else changes
Nothing matters more here than a loyalty program that stays out of the service flow. The QR is scanned as the bill is settled, and points, tier and any available reward appear on one screen. The cashier types no codes and judges no eligibility. If the connection drops, the transaction queues offline and syncs when it returns, so the till never locks up mid-service.
How it works
Set the earn rate
How many points per hundred lira, which item groups are excluded, how long points stay valid. Start from a template and adjust.
Define the tiers
Bronze, silver and gold thresholds and the reward at each level. Promotion is automatic and the guest is notified in the app.
Connect the till
A tablet or your existing screen is enough. If you want data to flow to your POS, we connect over the REST API and webhooks.
Publish a campaign
Pick your emptiest evening, choose the audience and the reward. The campaign closes itself when the window ends.
Frequently asked questions
No, your booking book stays as it is. The loyalty program starts when the bill is settled: who came in, what they earned, and when they are likely to return.
Every scan is made with a cashier PIN and the transaction log records who processed it. Because reports break down by cashier, unusual activity does not go unnoticed.
Yes. Guests can spend points at a branch other than the one where they earned them, and both sides of that movement are recorded separately in reports.
The system calculates points; nobody keys anything in. Kitchen flow is untouched, and the only change is a QR scan at the till.
