Skip to Content

Case files

Movo: Build a Malaysian multi-merchant e-commerce platform from scratch

Phase 1 launched. Malaysia-local payment rails (FPX and credit cards) and logistics (EasyParcel) were integrated. The bilingual English/Simplified Chinese site lets third-party merchants list products and order shipping labels themselves.

Movo (movo.com.my) is a multi-vendor e-commerce platform operating in Malaysia. This project was not about translating a Taiwan website into English; it was about adapting the full transaction flow to how local buyers buy and local merchants operate.

Why can’t we copy Taiwan’s approach?

Almost every item of Taiwan’s e-commerce defaults has to be changed when it comes to Malaysia:

  • Payment: Local buyers make heavy use of FPX (instant bank transfer), not only credit cards. Without FPX, an entire customer segment is blocked at checkout.
  • logistics: The local model uses aggregators such as EasyParcel, not Taiwan-style convenience-store pickup. Merchants must be able to order AWBs themselves and choose door-to-door pickup or self-drop-off.
  • language: The primary language is English and the second language is Simplified Chinese, not Traditional Chinese. That is an audience decision, not a font conversion.
  • Currency and tax: Single MYR pricing, completely separate from Taiwan’s cash flow and accounting.

These are not things you learn by searching. You have to run the process once to see where it gets stuck.

What we did

Platform construction — WordPress + WooCommerce + Dokan multi-vendor architecture running on a Hetzner VPS. Blocksy, LiteSpeed Cache, and Rank Math provide the theme, caching, and SEO structure.

Local payment rails — Stripe integration for both credit cards and FPX; both payment paths were verified in the live environment.

Local logistics — EasyParcel integration: merchants order their own labels from paid sub-orders, with door-to-door pickup and self-drop-off options. Shipping is pass-through; the full difference between the buyer-paid and actual shipping costs goes to the merchant, with no platform markup or subsidy.

bilingual structure — WPML directory mode, English is in the root path, Simplified Chinese is in /zh-hans/. It's not a plug-in translation, it's two sets of content that can be edited independently.

Merchant self-service process — After merchants register, they will be reviewed by the platform once; after passing the review, products will no longer be reviewed one by one. Merchants can see orders, logistics, and settlement themselves.

Buyer-side delivery visibility — Give each package a five-stage timeline (order confirmed → prepared → shipped → delivered → complete), tracking each merchant order independently instead of collapsing the whole order into one status.

boundary

This case is marketing and platform execution. Company registration, taxation, and local legal compliance are outside the scope; local service providers are responsible for those items, consistent with our approach to all cross-border cases.

What does this case prove?

It proves more than our ability to build WooCommerce. It shows that we know what a market’s checkout should look like, who should handle logistics, and which language buyers need. That is what the channel-map and compliance-threshold sections of a market-entry diagnostic deliver; the difference is that we took Movo all the way to launch ourselves.

This case is named with the client’s written authorization dated 2026-07-31.