Bring guests back.

Tiers sit on top of the same automatic point tracking. Guests move through Bronze, Silver and Gold as they meet the thresholds you set, and the unlocked status badge appears on the guest profile so both your team and the guest can see where they stand. Tiers are a way to structure whatever benefits you choose to attach at each level — the levels, the thresholds and the benefits are all yours to configure. Vertex does not impose a standard programme, and no tier structure can predict how a particular guest will respond to it.

Redemption happens inside the normal checkout flow: the balance is shown on screen and points can be swapped for a free item or a discount with a single tap, so there is no separate redemption journey to run. What a point is worth is set entirely by you when you configure the programme — Vertex does not define a fixed cash value, and a points balance is a promotional balance within your own programme rather than stored value or a means of payment. Any rules around expiry, transferability, or how balances are treated if the programme changes are yours to decide and to publish in your programme terms.

A guest profile brings together the details your programme is configured to collect — contact information such as phone number and email linked back to order history, preference mapping for modifier choices like dairy-free or extra spicy, visit counts and spend patterns — so a regular can be recognised rather than served cold every time. Which fields are captured, which are optional and how long records are kept are configuration decisions you make and control as the operator. Collecting and using guest data still requires the notice and consent your jurisdiction and your own privacy policy call for; enrolling someone in a loyalty programme does not remove that obligation.

Order history feeds a recent-orders list the guest can reorder from with a single tap, so a daily regular is not rebuilding the same basket every visit. Alongside it, payment cards can be saved as tokens in PCI-compliant storage for one-click payment, delivery addresses can be stored under labels like Home, Work or Gym, and social login through Google or Facebook is supported for account entry. Each of these is optional and enabled per venue when configured — saved cards and saved addresses exist only for the guests who choose to store them.

Both patterns are supported, and they use the same building blocks configured differently. A café built on high-volume, frequent visits can run a "10th Coffee Free" digital stamp card with frequent-visit multipliers, and use push notifications to reach guests during quieter mid-afternoon hours. A casual-dining room can lean on dine-in history instead — personalised suggestions such as wine pairings, automated "We Miss You" and birthday rewards, and dine-in table reservations. These are configuration patterns rather than fixed packages, and which ones fit depends on how your venues actually trade.