Malaysia is the market where English ops manuals actually get used, and where importers ask for a document list earlier than Vietnam. Repeat orders we see are not “nationwide coverage.” They are Kuala Lumpur / Petaling Jaya / Shah Alam clusters that learned on 4- and 6-slot stations, then stacked when a mall site cleared internal ROI. Penang and Johor Bahru come second. Sabah and Sarawak come after a spare-parts plan exists.
Venue mix that shows numbers in weeks
- Shopping malls — food courts and cinema levels; landlord onboarding is the long pole, not the cabinet.
- F&B and campus-adjacent retail — 4-slot on the counter; 6-slot when dwell and theft risk both rise.
- Transit retail — only with uptime SLAs and a local technician, not a Shenzhen WhatsApp group.
We do not publish a named Malaysia case with slot counts yet. If your RFQ looks like the Bangkok mall pattern (CMF packs + 4-slot stack), we can reuse that hardware path and change wallets.
Hardware path
- 4-slot cabinet for first-wave mall and F&B sites.
- 6-slot stackable when a site already proved 4-slot GMV.
- Native 8-slot only if you already know the corridor will grow to 16-slot stacks.
Keep one module family per cluster. Mixing stacked-from-4 and native-8 in the same 40-unit batch creates two spare lists and two firmware habits.
Touch ’n Go, GrabPay, and importer files
Local wallets should be scoped at kickoff. White-label SaaS is enough for a 6–8 week pilot; a public App Store listing can wait. On paperwork: we ship CE/FCC/RoHS program files and UN38.3 + MSDS matched to the cells. Any extra importer or SIRIM-related request belongs on the RFQ so we do not invent a certificate we do not hold. Start the list on OEM delivery and the quote form.
Ops checklist for field teams: daily operations. Bahasa Melayu: versi Melayu. Neighbors: Thailand, Vietnam, Indonesia.