The Philippines looks like Indonesia on a map — islands, dense youth phone use, malls as public living rooms — and like Vietnam on a payment call: if GCash is not in the rent flow, conversion dies at the QR. English ops manuals actually get read. The trap is a “nationwide” first PO that dumps 20 cabinets in Manila, 15 in Cebu, and 10 in Davao. That is three refill teams and one unreadable pilot.
Where a first cluster should sit
- Metro Manila malls — food courts, cinema levels, BPO-adjacent retail. Landlord onboarding is slower than the hardware.
- F&B counters — 4-slot stations; same pack family as the mall so spares mix.
- Cebu / Davao — after you have a pin/PSU/screen kit in Manila and a technician who can travel. Typhoon weeks are when dead slots become public.
We do not publish a named Philippines slot-count case yet. Hardware path matches the Vietnam F&B (6-slot + local wallets) and Bangkok mall (4-slot stack + CMF) patterns — wallets change, cabinet family should not.
Hardware path
- 4-slot cabinet for counters and first mall sites.
- 6-slot stackable when a food court already proved 4-slot GMV.
- 8-slot LCD station for lobby QR guidance — not the first 40-unit batch unless the landlord demands a screen.
Keep one module family per cluster. Mixing native-8 and stacked-from-4 in the same Metro Manila PO creates two spare lists before you have a warehouse.
GCash, Maya, and docs
GCash and Maya (PayMaya) should be named at OEM kickoff, next to the BOM. White-label SaaS plus QR is enough for a 6–8 week pilot. Card-only checkout still fails in many mall kiosks. Docking examples: OEM payment matrix.
Export pack: CE/FCC/RoHS on the program, UN38.3 + MSDS matched to the cells on the invoice. Any extra importer or bureau request belongs on the RFQ — we will not invent a local mark we do not hold. Ask on the quote form (country = Philippines).
Playbook: How to start in 2026. Filipino: bersyong Filipino. Cluster map: SEA country notes.