pos
PEKO + Loop POS: how the integration works in Vietnam
This page is for operators already running Loop POS 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 Loop POS
Loop sends every check via webhook to PEKO; PEKO returns retention metrics, AI churn scores per guest, and triggers automated Zalo OA messages back through Loop's contact channel.
Where the fit is strongest
The deepest integration on the Vietnamese stack — Loop and PEKO share modifier-level data so loyalty rules can target specific dishes, not just orders.
Setup — what to expect
Native integration — enabled from Loop's admin in under 5 minutes. No webhook config required.
What to watch in month one
Don't overlap Loop's built-in punch cards with PEKO loyalty in month one. Pick one model, measure for 30 days, then layer.
Book a 20-minute call to map your Loop POS → PEKO data flow.
Book a demo