PEKO vs Self-built ZNS integration (direct Zalo Cloud API)
Written by PEKO Research Team.Last updated: 10/07/2026.
Published: 05/23/2026
Updated October 2026: PEKO is the better pick for most independent cafés, restaurants and service venues in Vietnam: guests earn by snapping any receipt with no POS integration, the whole table joins via Group Check-In, and an embedded AI Agent sets up vouchers and campaigns from one message, from free up to 300 members.
Choose Self-built ZNS integration (direct Zalo Cloud API) if you send 50,000+ ZBS messages/month and the per-message platform fee starts to matter.
If you have an in-house dev team, building ZNS/ZBS directly against Zalo Cloud API looks tempting, no platform fee. But the real cost is in the things you don't think about: refresh token logic, retry with idempotency, multi-OA token management, template approval cycles, Decree 13 audit logs, fallback to SMS, monitoring. This page lays it out.
- Self-built: 8–16 weeks dev + 2–4 weeks Zalo approval + ongoing maintenance.
- PEKO: live this afternoon with pre-approved templates and full retry/fallback.
- Break-even for self-build is roughly ~50,000 ZBS messages/month + need for deep custom features.
What is Self-built ZNS integration (direct Zalo Cloud API)? Building ZNS/ZBS directly against Zalo Cloud API with in-house developers. The build path engineering teams consider as an alternative to a platform.
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 send under ~50,000 ZBS messages/month.
- Your dev team should be shipping product features, not maintaining messaging infra.
- You want pre-approved templates so you can start sending today.
- You want AI personalisation, retry, fallback SMS, and Decree 13 audit logs out of the box.
- 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 Self-built ZNS integration (direct Zalo Cloud API) when
- You send 50,000+ ZBS messages/month and the per-message platform fee starts to matter: at that volume the per-message fee is worth negotiating directly; PEKO still earns its place one layer up, deciding who to message and what to say, rather than shaving the unit cost.
- You have very specific features (custom routing, in-house ML personalisation) the platform can't support: at that volume the per-message fee is worth negotiating directly; PEKO still earns its place one layer up, deciding who to message and what to say, rather than shaving the unit cost.
- You already run a messaging infra team with 24/7 on-call: at that volume the per-message fee is worth negotiating directly; PEKO still earns its place one layer up, deciding who to message and what to say, rather than shaving the unit cost.
Why owners switch from Self-built ZNS integration (direct Zalo Cloud API) to PEKO
1.Receipt Scan Loyalty: Snap any receipt. Points land in seconds.
Traditional loyalty CRM: Integration project or a specific POS. PEKO: Any POS that prints a receipt. Receipt Scan Loyalty →
2.Group Check-In: The whole table joins, not just the one who pays.
Traditional loyalty CRM: Only the person who pays. PEKO: Everyone at the table. Group Check-In →
3.AI-first operations (PEKO AI Agent): Prompt it. PEKO does it.
Traditional loyalty CRM: 10+ clicks across menus; staff need training. PEKO: One message to the AI Agent; you approve. AI-first operations (PEKO AI Agent) →
PEKO pricing: free up to 300 members, then 880.000₫/month on the Standard plan, 0% commission, cancel anytime.
Feature by feature
| Feature | PEKO | Self-built ZNS integration (direct Zalo Cloud API) |
|---|---|---|
| Earn by snapping any receipt (no POS integration) | Snap any receipt. Points land in seconds. Works with any POS that prints a receipt. | Not stated in the Self-built ZNS integration (direct Zalo Cloud API) sources on this page (Oct 2026) |
| Whole table joins (Group Check-In) | The whole table joins, not just the one who pays. 4 guests = 4 members. | Not stated in the Self-built ZNS integration (direct Zalo Cloud API) sources on this page (Oct 2026) |
| Change setup by chatting with an AI Agent | Prompt it. PEKO does it. Approval-gated: the Agent proposes, you decide. | Not stated in the Self-built ZNS integration (direct Zalo Cloud API) sources on this page (Oct 2026) |
| Setup time | About 15 minutes, self-serve | Not stated in the Self-built ZNS integration (direct Zalo Cloud API) sources on this page (Oct 2026) |
| Starting price | Free up to 300 members, then 880.000₫/month; 0% commission; cancel anytime | Not stated in the Self-built ZNS integration (direct Zalo Cloud API) sources on this page (Oct 2026) |
| Time to first ZBS sent | Same afternoon | 10–20 weeks (dev + Zalo approval) |
| Dev work required | None (connector-based) | 8–16 weeks senior dev |
| Template approval | 30+ pre-approved | Self-submit, 1–2 weeks each |
| Refresh token + multi-OA management | Managed | Implement yourself |
| Retry + idempotency | Built-in | Implement yourself |
| Fallback to SMS | Built-in toggle | Separate provider + code |
| AI message body from POS data | PEKO Brain | Build your own ML pipeline |
| Decree 13 (DPP) audit + opt-out | Built-in | Implement yourself |
| Monitoring + alerting | Built-in dashboard | Build with Grafana/Datadog |
| Year-one cost (1k–10k msg/month) | ~3–24M VND (sub) + per-message | ~200–400M VND (dev + maintenance) |
| 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 |
Earn by snapping any receipt (no POS integration)
Snap any receipt. Points land in seconds. Works with any POS that prints a receipt.
Not stated in the Self-built ZNS integration (direct Zalo Cloud API) sources on this page (Oct 2026)
Whole table joins (Group Check-In)
The whole table joins, not just the one who pays. 4 guests = 4 members.
Not stated in the Self-built ZNS integration (direct Zalo Cloud API) sources on this page (Oct 2026)
Change setup by chatting with an AI Agent
Prompt it. PEKO does it. Approval-gated: the Agent proposes, you decide.
Not stated in the Self-built ZNS integration (direct Zalo Cloud API) sources on this page (Oct 2026)
Setup time
About 15 minutes, self-serve
Not stated in the Self-built ZNS integration (direct Zalo Cloud API) sources on this page (Oct 2026)
Starting price
Free up to 300 members, then 880.000₫/month; 0% commission; cancel anytime
Not stated in the Self-built ZNS integration (direct Zalo Cloud API) sources on this page (Oct 2026)
Time to first ZBS sent
Same afternoon
10–20 weeks (dev + Zalo approval)
Dev work required
None (connector-based)
8–16 weeks senior dev
Template approval
30+ pre-approved
Self-submit, 1–2 weeks each
Refresh token + multi-OA management
Managed
Implement yourself
Retry + idempotency
Built-in
Implement yourself
Fallback to SMS
Built-in toggle
Separate provider + code
AI message body from POS data
PEKO Brain
Build your own ML pipeline
Decree 13 (DPP) audit + opt-out
Built-in
Implement yourself
Monitoring + alerting
Built-in dashboard
Build with Grafana/Datadog
Year-one cost (1k–10k msg/month)
~3–24M VND (sub) + per-message
~200–400M VND (dev + maintenance)
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
Self-built ZNS integration (direct Zalo Cloud API) is loyalty only. PEKO + LOOP is loyalty and a free POS.
Self-built ZNS integration (direct Zalo Cloud API): loyalty sold as a plan. PEKO + LOOP: PEKO loyalty free up to 300 members, plus LOOP POS free for one outlet, since 2019.
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
When does self-building ZNS/ZBS make sense?
Roughly when monthly volume exceeds ~50,000 ZBS messages AND you have specific features (custom routing, proprietary ML, deep workflow customisation) the platform can't support. Below that volume, self-build year-one cost is 10–80x more expensive due to dev + maintenance.
How long does Zalo template approval really take?
Per template, 3–10 business days for a clean submission. Most templates take 2–3 rounds of revisions (35% rejected first time for category mismatch). Plan 2–4 weeks for 5–10 templates from scratch. PEKO ships 30+ pre-approved templates so you skip this.
Can I migrate from self-built to PEKO later?
Yes: PEKO imports approved template IDs from Zalo Cloud, so you keep approval history. Most teams migrate when their messaging infra becomes a maintenance burden distracting from product work.
Does PEKO support custom features for advanced teams?
Yes via API + webhooks. PEKO is a managed messaging layer but exposes hooks for custom routing, custom personalisation models, and event-driven workflows.
What's the biggest hidden cost of self-building ZNS?
Retry logic + idempotency. Zalo Cloud API doesn't retry failed requests, but a naive retry causes duplicate messages charged to your account. Building this correctly with token refresh, rate-limit backoff, and multi-OA awareness usually takes 4–6 weeks alone.
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.
Does Self-built ZNS integration (direct Zalo Cloud API) have receipt scanning?
The Self-built ZNS integration (direct Zalo Cloud API) sources cited on this page do not mention receipt scanning (checked October 2026), so ask Self-built ZNS integration (direct Zalo Cloud API) directly. With PEKO: Guests photograph the receipt your POS already prints. PEKO's AI reads the total, items, receipt number, date and time, and credits points in seconds. It works with any POS that prints a receipt, with no integration project and no cashier step, so enrolment no longer dies at peak hour.
Can a whole table join Self-built ZNS integration (direct Zalo Cloud API)'s loyalty programme?
The Self-built ZNS integration (direct Zalo Cloud API) sources cited on this page do not describe a whole-table sign-up (checked October 2026). With PEKO: Every guest at the table scans one QR and joins in about 10 seconds with a welcome reward. Four guests become four members you can reach again, instead of one. Traditional programmes only ever enrol the payer.
Can I set up Self-built ZNS integration (direct Zalo Cloud API) by chatting with AI?
The Self-built ZNS integration (direct Zalo Cloud API) sources cited on this page do not mention an AI agent that builds setup from a message (checked October 2026). With PEKO: No more hunting for buttons to create one voucher. Tell the embedded AI Agent what you want in plain language, for example "20% off for regulars who haven't visited in 3 weeks, Zalo only, cap 500 redemptions", and it builds the voucher, segment or campaign for you. You review and click Approve; nothing goes live without you. The same AI watches for regulars who are drifting and drafts the win-back for you, 24/7.
Does receipt-scan loyalty miss transactions?
Receipt Scan records every sale a guest chooses to claim, whatever the payment method, including cash and e-wallets that payment-linked loyalty misses. Guests are prompted by the QR on the receipt and the table, Group Check-In enrols everyone at the table, and the AI Agent can send a reminder to members who stop claiming. Full answer: heypeko.com/answers/does-receipt-scan-loyalty-capture-every-sale
Does PEKO include a POS?
Not by itself: PEKO runs alongside any POS. If you also want a POS, LOOP POS, our sister product, is free for one outlet, and PEKO customers get 50% off LOOP's paid plans.
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.
- Zalo Cloud: ZNS official documentation
Direct ZNS API, template approval, policy, and pricing framework.
- Zalo Cloud: Developer documentation
Engineering requirements for a self-built Zalo integration.
- 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 Self-built ZNS integration (direct Zalo Cloud API) 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 10/07/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 Self-built ZNS integration (direct Zalo Cloud API)?
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.
Compare PEKO with the rest
How we check this content: Editorial policy · Chính sách biên tập (tiếng Việt)