pos
PEKO + Haravan: how the integration works in Vietnam
Updated May 2026 — What Haravan 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 Haravan who are evaluating PEKO as an additive layer (not a replacement).
Quick facts
- Integration
- PEKO runs as a loyalty layer on top of Haravan — 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 Haravan 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 Haravan
PEKO reads Haravan's order events and customer table, then adds the AI retention layer on top — without disrupting Haravan's checkout or invoice flow.
Where the fit is strongest
Strongest for Haravan venues that already run Haravan Loyalty but want the AI/cohort layer it doesn't include.
Setup — what to expect
Connects via Haravan's public API. Setup is ~30 minutes; PEKO can coexist with Haravan Loyalty if rules don't overlap.
What to watch in month one
Don't double-issue points. Decide which system owns the points balance before activating PEKO automations.
Book a 20-minute call to map your Haravan → PEKO data flow.
Book a demo