pos
PEKO + iPOS: how the integration works in Vietnam
This page is for operators already running iPOS 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 iPOS
iPOS pushes ticket data to PEKO; PEKO returns retention scoring and triggers Zalo OA / SMS / email outreach based on AI churn signals.
Where the fit is strongest
Best fit for restaurant chains on iPOS that need a layer above iPOS's reporting — operator-grade retention dashboards instead of raw exports.
Setup — what to expect
iPOS provides a partner API. Plan ~1 hour with iPOS support to enable webhook scope; PEKO does the rest.
What to watch in month one
iPOS's data lag can be ~5–10 minutes on busy nights. PEKO accounts for this in its trigger windows.
Book a 20-minute call to map your iPOS → PEKO data flow.
Book a demo