Answers / Loyalty programs

What is a loyalty layer, and why pick one over the loyalty module bundled with your POS?

Written by PEKO Team.Last updated: 05/24/2026.

A loyalty layer is a POS-agnostic system that sits on top of whatever point-of-sale you already run and owns the customer relationship (identity, segmentation, win-back, reporting). It beats a POS-bundled loyalty module because the POS vendor's roadmap optimises for transactions, not for retention.

Published: 05/24/2026

A loyalty layer is the system that owns your customer relationship — identity, segmentation, AI churn prediction, automated win-back, multi-channel messaging, and reporting — separate from the point-of-sale system that owns your transactions. The POS rings up orders; the loyalty layer decides which guest deserves the next message and when.

Most POS vendors ship a bundled loyalty module because customers ask for one. Those modules are almost always a thin points-and-vouchers shell stitched onto a transaction product. They were not architected as a CRM, they have no AI surface, and the vendor's roadmap will always prioritise transaction features (kitchen display, e-invoice, COGS, recipe management) over retention features. That is fine — POS vendors should be great at POS. It also means the bundled module will plateau exactly when your retention programme starts to matter.

A dedicated loyalty layer like PEKO is built the other way around. The POS is treated as a data source, alongside Zalo OA, booking systems, miniapps, and CSV imports. The product surface is the customer — every dashboard, every report, every workflow starts from a unified guest profile rather than from a receipt. The trade-off is that you run two systems instead of one. The win is that neither system pulls the other down: your POS keeps getting better at transactions, your loyalty layer keeps getting better at retention.

POS-agnostic also means portable. If you switch from KiotViet to LOOP next year because LOOP fits a new bar concept better, your loyalty programme, customer profiles, tier mappings, and messaging cadence all stay intact. The customer never notices the swap. With a bundled loyalty module, the migration is a hostage situation — leaving the POS means rebuilding the loyalty programme from scratch.

Identity unification across every channel

A real loyalty layer matches a guest's POS receipt, Zalo ID, phone number, miniapp session, and email into one profile. POS-bundled modules typically index by phone number only, so the same guest signs up three times across three branches and shows as three different customers.

AI churn prediction, not just stamp counting

Bundled modules count stamps and trigger anniversary emails. A loyalty layer scores each guest's churn risk daily against their personal visit cadence and fires a win-back the moment cadence breaks. The single highest-leverage retention move in F&B.

Multi-channel messaging from one workflow

Zalo OA, ZNS, SMS, email, in-app push. A loyalty layer orchestrates the channel mix per guest (ZNS for high-intent, free OA broadcast for the rest); bundled modules usually pin you to whichever channel the POS vendor partnered with first.

Operator reporting that compounds

CLV, RFM, cohort retention, redemption funnel, point liability, tier upgrade rate, AOV uplift, visit heatmap. Bundled modules rarely ship more than 3–4 of these. PEKO ships 15.

Works alongside your POS, never instead of it

PEKO connects to LOOP, KiotViet, iPOS, MISA CukCuk, Sapo, Toast, Square, Loyverse, Haravan, and PosApp via native connector or CSV. Payment processing stays where it is. You do not replace the POS.

FAQ

Why not just use the loyalty module bundled with my POS?

If the bundled module covers your need today, use it. The moment you want AI churn prediction, multi-POS or multi-branch identity unification, ZNS at scale, or reports beyond stamps and vouchers, the bundled module hits its ceiling. A loyalty layer is what you graduate to.

Will I need to replace my POS to use PEKO?

No. PEKO works alongside any POS via native integration (LOOP, KiotViet, iPOS, MISA, Sapo, Toast, Square, Loyverse, Haravan, PosApp), CSV import, or API. It never touches payment processing.

What if my POS already syncs to a CDP?

Even better. PEKO consumes CDP feeds via API and adds the F&B-specific layer most general CDPs lack: receipt OCR, Zalo-native channels, F&B-specific RFM thresholds, and AI-written win-back copy.

How is this different from a CRM?

A CRM is a contact database with workflows; a loyalty layer adds the loyalty mechanics (points, tiers, stamps, redemptions), the AI churn surface, and the F&B-specific reports. Most F&B operators do not need a horizontal CRM — they need a loyalty layer that already speaks their vertical.

What about LOOP — isn't that PEKO's POS?

LOOP is a sister POS product. PEKO is POS-agnostic and works with every major POS in Vietnam and SEA, including LOOP. If you are choosing both, ask about the LOOP × PEKO bundle (50% off LOOP on any paid PEKO plan).

How long does setup take?

10–15 minutes for a single-location café connecting via CSV or LOOP. Multi-branch chains with KiotViet, iPOS or MISA usually take an afternoon for connector setup and identity reconciliation.

Calculate your PEKO ROI →