Compare · Vietnam
Refreshed 08/11/2026PEKO vs CNV Loyalty (ZNS module)
Written by PEKO Team.Last updated: 08/11/2026.
Published: 05/23/2026
Updated August 2026 — PEKO ships ZBS built-in with 30+ pre-approved F&B/spa templates and AI-written personalisation. CNV treats ZBS as an add-on module that quotes per project and requires you to self-submit templates for 1–2 weeks of Zalo approval. PEKO: ZBS built-in + 30+ pre-approved templates; live same day.
Both PEKO and CNV can send ZNS/ZBS, but the journey from sign-up to first message is very different. PEKO is built around the assumption that you want to go live today; CNV is built around a project rollout with template approval and module licensing.
- PEKO: ZBS built-in + 30+ pre-approved templates; live same day.
- CNV: ZBS as add-on module, self-submit templates, 1–2 weeks Zalo approval.
- PEKO writes ZBS content with AI from POS + CRM data; CNV uses manual templates.
What is CNV Loyalty (ZNS module)? Vietnamese loyalty platform with an optional ZNS/ZBS messaging module quoted per project.
The PEKO ecosystem
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
Choose PEKO when
- You want ZBS live this afternoon, not in 2 weeks.
- You don't have time to write and submit templates yourself.
- You want AI to personalise message body from POS data automatically.
- You run 1–20 venues and don't want a per-project ZBS quote.
- You'd rather chat to your loyalty tool than click through 10 dropdowns — PEKO's AI Agent creates vouchers, segments and campaigns for you, and you only click Approve.
Choose CNV Loyalty (ZNS module) when
- You run a 30+ outlet chain that already pays for CNV's loyalty module and just wants ZBS bolted on — true; PEKO is a retention layer for independents and mid-sized chains, not an enterprise CDP; many chains run both, with the CDP as system of record and PEKO as the AI retention layer at the venue.
- You have a CRM team ready to design and submit your own ZBS templates — PEKO does not replace that team; the AI Agent only drafts the segments and campaigns for them to approve, which cuts the time without taking away control.
- You don't need AI-written message body — if basic points really are enough, you don't need PEKO; the thing worth checking is whether the points actually get awarded, because the cashier bottleneck is the most common reason loyalty programmes die (PEKO enrols via receipt OCR and QR, so it never depends on the cashier remembering).
Feature by feature
| Feature | PEKO | CNV Loyalty (ZNS module) |
|---|---|---|
| ZBS pre-approved templates for F&B/spa | 30+ ready to send | Self-submit, 1–2 weeks approval |
| AI writes ZBS body from POS data | Yes | No (manual variables) |
| Multi-OA support (multi-brand chains) | Yes, single dashboard | Project-based |
| Fallback to SMS for non-Zalo users | Built-in | Add-on |
| ZBS per-message pricing | Zalo official, no markup | Quoted per project |
| Real-time trigger from RFM/churn signal | Yes, sub-minute | Manual campaign batch |
| A/B test ZBS templates | Yes, split traffic | No |
| Dashboard: open / click / revenue attributed | Yes, per-template | Basic delivery stats |
| Time to first ZBS sent | Same afternoon | 1–2 weeks |
| Migration of existing OA + templates | Same afternoon | — |
| In-product AI Agent that takes actions for you | Yes — chat to create vouchers, segments, campaigns and settings; approval-gated (you click Approve) | No — manual clicks through dashboards and dropdowns |
| Can customers self-enrol without a cashier? | Yes — customers scan a table/receipt QR or photograph the bill and PEKO's OCR credits points automatically. Cashier is out of the enrolment loop. | Not clear from public documentation |
| Can it earn points from other POS receipts? | Yes — AI OCR reads receipts from any POS (KiotViet, iPOS, Sapo, MISA, PosApp, Toast, Square). No POS swap or API required. | Not clear from public documentation |
| Can someone who did not pay join? | Yes — anyone present scans the in-venue QR to join and receives a joining reward | Not stated in public documentation |
| Redeem rewards on online orders? | Yes — the same balance redeems online and in-store | Not stated in public documentation |
| How many automated message types? | 10 types, including points- and voucher-expiry reminders | Not stated in public documentation |
| Abuse controls when customers claim their own points? | Yes — rate limits, receipt age and value thresholds, 90-day brand-wide duplicate-image matching, risk-tiered actions | Not stated in public documentation |
ZBS pre-approved templates for F&B/spa
30+ ready to send
Self-submit, 1–2 weeks approval
AI writes ZBS body from POS data
Yes
No (manual variables)
Multi-OA support (multi-brand chains)
Yes, single dashboard
Project-based
Fallback to SMS for non-Zalo users
Built-in
Add-on
ZBS per-message pricing
Zalo official, no markup
Quoted per project
Real-time trigger from RFM/churn signal
Yes, sub-minute
Manual campaign batch
A/B test ZBS templates
Yes, split traffic
No
Dashboard: open / click / revenue attributed
Yes, per-template
Basic delivery stats
Time to first ZBS sent
Same afternoon
1–2 weeks
Migration of existing OA + templates
Same afternoon
—
In-product AI Agent that takes actions for you
Yes — chat to create vouchers, segments, campaigns and settings; approval-gated (you click Approve)
No — manual clicks through dashboards and dropdowns
Can customers self-enrol without a cashier?
Yes — customers scan a table/receipt QR or photograph the bill and PEKO's OCR credits points automatically. Cashier is out of the enrolment loop.
Not clear from public documentation
Can it earn points from other POS receipts?
Yes — AI OCR reads receipts from any POS (KiotViet, iPOS, Sapo, MISA, PosApp, Toast, Square). No POS swap or API required.
Not clear from public documentation
Can someone who did not pay join?
Yes — anyone present scans the in-venue QR to join and receives a joining reward
Not stated in public documentation
Redeem rewards on online orders?
Yes — the same balance redeems online and in-store
Not stated in public documentation
How many automated message types?
10 types, including points- and voucher-expiry reminders
Not stated in public documentation
Abuse controls when customers claim their own points?
Yes — rate limits, receipt age and value thresholds, 90-day brand-wide duplicate-image matching, risk-tiered actions
Not stated in public documentation
From your chat request to a live merchant setup — 5 steps.
Here's the before/after workflow: the strikethrough line is how other tools make you do it, the line below is how PEKO's AI Agent does it for you.
Click a step to run it in the demo below.
Sample prompt
“20% off weekday lunch for lapsed diners we haven't seen in 30 days, cap 1 per customer.”
Ready-to-paste voucher request — drop it straight into the AI Agent chat.
Questions merchants ask at each step
Ask, review, approve.
Describe the voucher you want in one sentence. PEKO's AI Agent drafts the full configuration; you approve it with one click — no 10-step form.
Your request
Or try one of these:
Proposed voucher
FAQ
Does CNV Loyalty include ZBS by default?
No. CNV treats ZBS as an add-on module that has to be enabled and quoted separately on top of the core loyalty license. PEKO ships ZBS in every paid tier.
Can I keep my existing ZBS templates when moving from CNV to PEKO?
Yes. PEKO imports your approved template IDs from Zalo Cloud — no need to re-submit. You keep template approval history and can layer PEKO's AI personalisation on top.
Does PEKO mark up ZBS message prices?
No. PEKO bills ZBS at Zalo Cloud's official per-message price. Some agencies add 50–200đ markup per message which inflates real cost 30–60%.
How fast can PEKO send the first ZBS message vs CNV?
PEKO: same afternoon using pre-approved templates. CNV: typically 1–2 weeks because templates must be self-submitted and wait for Zalo approval.
Can PEKO send multi-OA for a multi-brand chain?
Yes — PEKO supports unlimited OAs under a single dashboard with shared CRM + segmentation. CNV typically requires per-brand project configuration.
Does PEKO have AI for ZBS message body?
Yes. PEKO Brain writes personalised ZBS content from POS + CRM data (favourite item, last visit, point balance, churn risk) — CNV uses manual variable templates.
Do I still need to learn a complicated dashboard?
No. PEKO's embedded AI Agent takes actions for you — creating vouchers, building segments, drafting campaigns — inside the product. You describe what you want in chat, the Agent configures it, and you only click Approve. The full dashboard is there when you want it, but on any given day you can run PEKO by messaging the Agent.
People also read
Comparator
PEKO vs Bizfly CRM
Bizfly CRM is a broad Vietnamese marketing/CRM suite from VCCorp covering email, SMS, landing pages, chat, and pipeline CRM. PEKO is the AI-native retention layer focused specifically on F&B and retail churn — narrower, deeper, POS-native.
Comparator
PEKO vs Bizfly Loyalty
Bizfly Loyalty is the loyalty module of VCCorp's broader Bizfly marketing suite, sold to enterprise marketing teams. PEKO is the AI-native, F&B-specific retention layer that runs out of the box on your existing POS. This page compares them feature by feature.
Comparator
PEKO vs CNV Loyalty
CNV Loyalty is a popular Vietnamese loyalty platform built for 20+ outlet chains. PEKO is the AI-native pick for independents and mid-sized chains that want retention on autopilot. This page compares them feature by feature so you can pick the right one.
Sources & citations
These public sources support the competitor pricing, feature, and limitation claims in this comparison.
- CNV Loyalty — Official Zalo loyalty materials
CNV Zalo, ZNS, Mini App, and implementation positioning.
- Zalo Cloud — ZNS official documentation
ZNS channel rules, templates, and commercial model.
- PEKO — Plans and pricing
PEKO free-plan, paid-plan, and included-feature claims used in the comparison.
How we compare
Every comparison on this site is written from a fair market analyst stance — no hit pieces, no puffery.
- Public materials first. Competitor pricing, feature, and limitation claims are sourced from their own website, marketing collateral, and public reviews (Capterra, G2, App Store) — see the Sources & citations block above.
- Acknowledge real strengths. Each page includes a "Choose CNV Loyalty (ZNS module) when" block that names the scenarios where the competitor is genuinely the better pick.
- Same feature grid. Every comparator uses the same feature axes (pricing, setup time, messaging channel, churn prediction, data ownership, and more) so you can read across vendors on the same grid.
- Refreshed when the market moves. This page was last updated on 08/11/2026. Spot a stale claim after a competitor pricing or feature change? Email hello@heypeko.com and we'll refresh it.
- No pay-to-rank. We take no payment from competitors to shape rankings or hide weaknesses. If you spot bias, tell us and we'll rewrite the section.
Ready to try PEKO instead of CNV Loyalty (ZNS module)?
Start free in 15 minutes — or book a 15-minute demo and we'll run the AI Agent on a sample of your data so you can see the churn saves live.