pos
PEKO + POS365: how the integration works in Vietnam
Updated May 2026 — What POS365 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 POS365 who are evaluating PEKO as an additive layer (not a replacement).
Quick facts
- Integration
- PEKO runs as a loyalty layer on top of POS365 — 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 POS365 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 POS365
PEKO ingests POS365 transactions and surfaces what POS365's own dashboards don't: cohort retention, segmented win-back lists, and AI churn alerts.
Where the fit is strongest
Best for spa, salon, and F&B venues on POS365 with at least 400 unique customers/month.
Setup — what to expect
Setup via POS365 API takes ~45 minutes. Historical import depends on POS365's data retention plan.
What to watch in month one
POS365's customer attribute schema is limited — PEKO compensates with its own enrichment but plan for ~2 weeks of signal cleaning.
Book a 20-minute call to map your POS365 → PEKO data flow.
Book a demo