Set your tiers and their conditions
You decide how many tiers, how many points or visits each requires, and what perks come with each one.
Features
Tiers only work when guests can see them. On PEKO, every guest opens WhatsApp to find their current tier, its perks, and exactly how far they are from the next one.

Updated August 2026 — Membership tiers only motivate guests when they can see where they stand. On PEKO, opening WhatsApp shows the current tier, its perks, and how far to the next one. Moving up triggers an automatic congratulations message; slipping down triggers a warning first.
Updated: 2026-08-09
You decide how many tiers, how many points or visits each requires, and what perks come with each one.
The membership card on WhatsApp shows the current tier and a progress bar toward the next, updating after every point earned.
Moving up sends a congratulations message with the new perks. About to drop a tier sends a reminder of exactly what's missing and how many days are left.
In their membership card on WhatsApp. Opening it shows the tier, its perks, and a progress bar to the next tier — no asking staff, no standing at the counter.
Whichever fits your venue. You can base tiers on total spend, accumulated points, or visit frequency within a period. You choose at setup.
Yes if you want that. You can set a review cycle. Before a drop, guests get a reminder of exactly what's missing and how many days are left — that's usually enough to bring them back.
Yes. Each guest is a single profile across your whole system, so the tier stays consistent at every branch instead of a separate record per location.
Yes. When a guest checks in or scans a receipt, their tier shows on your venue's dashboard, so staff know who deserves extra attention.
PEKO and LOOP are two products from the same company. PEKO is the AI retention layer and runs alongside the POS you already use. LOOP is the AI-native POS that covers operations: recipe-level inventory, staff shifts, table plans and the kitchen display. Each works on its own, and run together they share one dataset, so nothing has to be entered twice. See PEKO + LOOP in one ecosystem