For
Multi-location F&B chains
Updated May 2026 — PEKO gives a multi-branch F&B chain one customer profile across every location, sitting on top of whichever POS each branch already runs — KiotViet, iPOS, Sapo or MISA CukCuk. Identities merge by phone, Zalo or email, so tier, points and visit history follow the customer between branches, and every staff dashboard sees the same VIP status in real time.
Most chains run one POS per location and discover, too late, that they're running five customer databases — and treating top spenders like first-timers.Quick facts
- For
- Multi-location F&B chains
- The problem
- Per-location POSes were designed for transactions, not customers. Without an identity-resolution layer on top, chains can't tell that 'Linh from D1', 'Linh phone …482', and 'Zalo user lh_nguyen' are the same person.
- How PEKO fixes it
- Most chains run one POS per location and discover, too late, that they're running five customer databases — and treating top spenders like first-timers.
- Ecosystem
- PEKO (AI customer retention) + LOOP (AI POS for operations) — same company, use either on its own or both together.
Symptoms you're seeing
- 01.A customer joins the loyalty programme three times — once per location.
- 02.VIPs get treated as walk-ins at the branch they don't usually visit.
- 03.Each manager runs their own promos, often cannibalising each other.
- 04.Group-level reporting is a Sunday-night spreadsheet exercise.
Root cause
Per-location POSes were designed for transactions, not customers. Without an identity-resolution layer on top, chains can't tell that 'Linh from D1', 'Linh phone …482', and 'Zalo user lh_nguyen' are the same person.
How PEKO fixes it
1.Connect every location's POS
Native connectors for LOOP, KiotViet, iPOS, MISA, Sapo, Toast, Square, Loyverse. Mix-and-match across locations is fine.
2.Identity-resolve in one pass
PEKO matches transactions across POSes using phone, Zalo ID, and email; produces one customer profile per real human.
3.Expose VIP tier at every counter
Staff dashboards show 'returning VIP — top 5% spender, last visit Đông Du' the moment a customer is identified at any branch.
What you get
Every location treats every customer correctly. The unification problem most chains hire a consultancy to solve ships out-of-the-box — and feeds the AI churn + win-back loop with one clean profile per person.
Common questions
How many locations can PEKO handle?
Tested through ~20 locations on the Professional plan; bigger groups should talk to us about Pro Max + a dedicated CSM.
What if my locations run different POS brands?
Fine. PEKO normalises across POSes and stores one canonical schema.
Can each location see only its own customers?
Yes. Location-scoped roles let staff see only the branch they work at, while HQ sees the group.
See the full product spec: /product · Related vertical
Talk to us about your chain →
