A guest database and points loyalty built into the order — not bolted on

Most restaurant loyalty runs as a bolt-on: a separate app your guests have to download, a second login for your staff to babysit, and a points system that never quite agrees with the register. Opero takes the other path. The guest database and a points-based loyalty program live on the same order spine as your POS, kiosk, and QR ordering — so a guest's history is part of the order, not a sticker on top of it. And it's included from the $99 Starter tier, not sold as a separate module.

What Opero loyalty is — and what it isn't

Opero loyalty is deliberately basic, and we'd rather be straight about that than oversell it. What you get is two things that work together: a customer database — a CRM record for every guest who identifies themselves — and a points-based rewards program tied to it. A guest earns points on what they spend, and their visit history and lifetime value accrue on one profile. That's the whole shape of it: a real guest database and a working points program, not a marketing-automation suite.

What it is not, today, is a scheduled email-and-SMS campaign platform, a multi-tier VIP-membership engine, or a gift-card system. If your growth plan depends on marketing blasts or tiered membership levels out of the box, Opero isn't that yet. What it does well is quietly build a guest record on every order and reward repeat visits on rules instead of a manager's memory.

Every guest who gives a phone number or email becomes one profile per guest, deduped so the same person isn't split across two records. The profile carries:

• ✓Name, phone, and email — however the guest chose to identify themselves
• ✓First seen and last seen — when they started coming in and when they were last through the door
• ✓Visit count and lifetime value — how often they come and what they've spent, updated on every linked order
• ✓A marketing-consent flag — captured explicitly at opt-in, so you know exactly who agreed to be contacted
• ✓One record per guest per account — a concurrent double-tap at a busy kiosk can't spawn a duplicate

One guest profile, keyed to the check

The reason any of this holds together is that a guest profile is tied to the order itself. When a guest is identified, their order is stamped with that customer record — so their history isn't a guess reassembled from a pile of receipts later, it's the orders themselves. And because the guest lives on your account rather than on a single register or a single store, that one profile spans your locations: a regular at one location is the same guest at another, on one running history.

• ✓Every identified order links to the guest — history is the orders, not an after-the-fact match
• ✓One profile per guest across all your locations under the account
• ✓Lifetime value and visit count roll up automatically as orders close
• ✓The same order-and-payment spine your POS and payments already run on — nothing to reconcile between systems

Points that earn on the order

The rewards program is points-based and simple: a guest earns one point per dollar on the order total, and their balance is shown the moment the order is placed. Every earn is written to a ledger, and the ledger is idempotent — if an order is retried or replayed, the guest is credited once, never twice. You get a clean, auditable points history per guest instead of a balance that drifts every time something reruns behind the scenes.

• ✓One point per dollar, earned on the order total
• ✓Balance shown immediately at checkout — the guest sees what they just earned
• ✓An idempotent points ledger — no double-credit on a retry or replay
• ✓Points and history live on the guest profile, per account, alongside their visit and spend record

Guests enroll themselves at the kiosk

On the self-order kiosk, enrollment is the guest's own two seconds: they add a phone number or email at checkout, the screen shows the points they just earned and their new balance, and a receipt is texted or emailed to them. There's nothing to download and no account to create — which is exactly why guests actually do it. The receipt send is transactional and tied to the payment, so the anonymous kiosk endpoint can't be turned into a spam relay; it's a receipt for a real, paid order, not a marketing message.

Because it's the same self-order kiosk that already takes the order and the payment, capturing the guest costs the operator nothing extra — no clipboard at the counter, no punch cards to reprint, no second device to buy. The guest record and the points are a byproduct of an order you were taking anyway.

Included from Starter, per location

Loyalty and the guest database are included from the $99 per-location Starter tier — the same tier that includes POS, KDS, and QR and web ordering — alongside unlimited devices and no per-device fees. You don't stack a loyalty module on top of a base price; it's part of the plan. Growth ($249), Pro ($499), and Enterprise (custom) add operations depth on top — inventory and recipe costing, labor scheduling, the AI command center, forecasting — but the guest database and points program are there from the first tier. All plans are per location, month-to-month, with no long-term contract.

How the guest data feeds the rest of the OS

Because the guest database sits on the same spine as everything else, the guest record isn't stranded in a loyalty silo. Orders carry the customer, payments are already matched to those orders, and the AI command center reads the whole picture — which guests come back, what they spend, how a location's repeat business is trending — without exporting a loyalty report and cross-referencing it against sales by hand. One menu spine, one order pipeline, one guest record: that's the point of building loyalty into the operating system instead of bolting it on.