One guest record — visits, spend, and last-seen — built into every order

Most restaurants know almost nothing about the people who eat there. The regular who comes in every Thursday, the big party that dropped $400 once and never came back, the guest who used to be weekly and hasn't been in for two months — they're all invisible, scattered across receipts nobody reads. Opero fixes that quietly, without a clipboard or a punch card. Every guest who adds a phone number or email at the kiosk or over QR ordering becomes one profile, and that profile fills itself in on every order: how often they come, what they've spent, what their average check is, and when you last saw them.

One guest record, filled in by the order

A guest identifies themselves once — a phone number or an email at checkout — and Opero finds or creates a single record for them, deduped per account so the same person isn't split across two profiles. From then on, every order they place attaches to that record and keeps it current. There's no manual data entry and no after-the-fact matching: the history is the orders themselves. Each profile carries a live, always-current view of the guest:

• ✓Name, phone, and email — however the guest chose to identify themselves
• ✓Visit count — incremented on every linked order
• ✓Lifetime value — total spend, rolled up as orders close
• ✓Average ticket — spend per visit, recomputed on every order so it's always current
• ✓First seen and last seen — when they started coming in and when they were last through the door
• ✓Loyalty points earned — one point per dollar, on an idempotent ledger that never double-credits a retried order
• ✓One record per guest per account — a concurrent double-tap at a busy kiosk can't spawn a duplicate

Behavioral segments, drawn from real columns

Because visits, spend, average ticket, and last-seen are live columns on the record — not a report you assemble by hand — Opero can group your guests the way an operator actually thinks about them. Every segment is a plain rule over those columns, so a guest moves in and out of a segment on their own as their behavior changes:

• ✓New / one-time — a single visit so far, ripe for a nudge back for a second
• ✓Regulars — five or more visits, your frequent guests
• ✓Active — seen in the last 30 days
• ✓Slipping away — quiet for 30 to 60 days, the window to win them back before they lapse
• ✓Lapsed — 60+ days since their last visit, or never seen since capture
• ✓Top spenders (VIP) — $250 or more in lifetime spend
• ✓Big checks — a $75-or-more average ticket per visit

Where these segments are used for campaigns, they come from one place — the audience picker and the server-side validation read the same source of truth, so what you preview is exactly who a campaign reaches. Targeting a segment with an email marketing campaign is a Growth-plan feature (SMS campaigns are on the way). The guest database, the profiles, loyalty points, and consent tracking are on every plan from Starter up, and the Customers browse carries its own quick filters — top spenders, recently active, SMS-marketable, emailable — on Starter too.

Consent and opt-out, tracked on the record

A guest database is only useful if you can trust who's in it and who agreed to be contacted. Opero tracks consent per guest and per channel, and treats SMS and email by their real legal rules rather than one blunt flag:

• ✓SMS is opt-in — a guest is textable only with a phone number, an explicit marketing-consent opt-in, a recorded consent-evidence timestamp, and no opt-out on file
• ✓Email is opt-out — a known guest with an email can be emailed until they opt out, per CAN-SPAM
• ✓Opt-outs are honored per channel, and a guest can be opted out of texts without losing the record or their history
• ✓Consent is checked one final time per recipient at send, so an opt-out that lands mid-send is respected — a non-consented guest can never be reached even if a segment resolved a moment earlier

That last point matters: the consent check isn't only a filter on the audience list, it's a hard gate the send loop re-runs for every single recipient right before dispatch. It's the one enforcement point, so a bug upstream can't leak a message to someone who opted out.

Where the data comes from, and how you browse it

The guests come from the ordering paths you already run: the self-order kiosk and QR ordering. A guest adds their contact info to get a receipt and earn points, and that's the enrollment — nothing to download, no account to create, which is exactly why guests actually do it. In your Customers screen you can search by name, email, or phone, filter to SMS-marketable guests, emailable guests, top spenders, or recently-active guests, and see each guest's points, lifetime value, and last visit at a glance, with a running total of how many match. It's the operator's window into the whole guest base — and the jumping-off point to the campaign composer when you're on Growth or above.

Included from Starter, per location

The guest database and loyalty points are included from the $99 per-location Starter tier — the same tier that runs your POS, kiosk, KDS, and QR and web ordering — with unlimited devices and no per-device fees. You don't buy a CRM module on top of a base price; capturing guests and building profiles is part of the platform from the first tier. Growth ($249), Pro ($499), and Enterprise (custom) add depth on top — including turning the behavioral segments into email marketing campaigns (SMS campaigns coming) — but the profiles, the visit and spend history, the consent tracking, and loyalty points are there from Starter. All plans are per location, month-to-month, with no long-term contract.