pos
PEKO + KiotViet: how the integration works in Vietnam
Updated May 2026 — What KiotViet owners in Vietnam get from running PEKO as a loyalty layer on top — data flow, setup, and what to watch. This page is for operators already running KiotViet who are evaluating PEKO as an additive layer (not a replacement).
Quick facts
- Integration
- PEKO runs as a loyalty layer on top of KiotViet — it does not replace the existing system.
- Category
- pos
- Ecosystem
- PEKO (AI customer retention) + LOOP (AI POS for operations) — same company, use either on its own or both together.
This page is for operators already running KiotViet who are evaluating PEKO as an additive layer (not a replacement). It covers exactly what data crosses between the two systems, how long setup takes, and the common mistakes we see in the first 30 days.
What PEKO does on top of KiotViet
PEKO listens to KiotViet's transaction webhooks and builds a customer-level retention picture KiotViet doesn't ship: cohorts, win-back lists, AI churn scores, and Zalo OA campaigns triggered by visit gaps.
Where the fit is strongest
Strongest for KiotViet venues with 600+ unique customers/month and a Zalo OA already verified. Smaller venues can start, but ROI lands faster at scale.
Setup — what to expect
API connection takes ~30 minutes with a KiotViet admin account. PEKO begins importing historical orders the same day; cohorts are usable after ~72 hours of fresh signal.
What to watch in month one
Watch refund handling — KiotViet refunds need to roll back loyalty points cleanly. PEKO does this automatically but spot-check the first 10 refunds.
Book a 20-minute call to map your KiotViet → PEKO data flow.
Book a demo