Magento for Thailand, run from one codebase.

No, and we would rather say that here than in the first meeting. Delivery is remote. The nearest Brainvire office is Singapore, and the teams behind it work a day that overlaps Thailand hours almost end to end. What is local is the schedule: stand-ups, demos and go-live windows are booked on Thailand time, and one named owner takes your call rather than a queue.

Yes, that is exactly what websites, stores and store views exist for. Each country gets its own domain or path, currency, language, tax rules and catalogue subset while sharing one codebase and one admin. An Asia Pacific footwear brand with offices in seven countries, Thailand among them, runs that way on a setup we built. The decision worth making early is which parts are shared and which are genuinely local, because changing that answer later is what makes multi-country builds expensive.

Through configuration first and custom code second. Tax classes, rates and the price display rules that put VAT into the shelf price live in Magento settings, so they survive an upgrade. Where a full tax invoice or an electronic tax invoice format is genuinely needed, we build it as a proper module rather than as a patch on core, and your finance team signs off the printed and emailed output before we call it finished.

It means having a lawful basis for the customer data you keep and being able to show where that data lives. In practice we define retention for order and customer records, restrict and log admin access, keep consent against the customer account rather than in a spreadsheet, and write down every place order data is copied to, including marketplace, logistics and marketing integrations. The output is a data flow a reviewer can read in an afternoon.

Yes, and it is a store view decision rather than a plugin decision. One catalogue carries Thai and English content, prices in Baht, and a language switch that does not lose the basket. The part worth planning is the content operation behind it: who writes the Thai copy, and who keeps it in step when the catalogue changes. Translation that stops after launch is the most common reason a bilingual store starts to look neglected.

Yes, and most retailers we speak to here are in exactly that position. Magento holds the master catalogue, stock and orders, and the marketplace channels are integrated so listings, price and stock stay in step instead of being re-keyed by hand. We built an order tracker for the same reason: a client selling through a website and marketplaces needed both order streams in one status flow rather than in two systems that disagreed.

The ones your customers already use. Magento takes local gateways that carry bank transfer and QR payments, wallets and cards, and cash on delivery can be modelled as its own payment method with reconciliation rules attached. We integrate the gateway you hold a merchant agreement with rather than the one that installs fastest, because the settlement and refund flow matters more than the checkout button.

Rarely the platform on its own. It is normally full page cache misses, an unindexed catalogue, a third-party extension doing database work on every request, or images nobody has looked at since launch. We profile before recommending, because replatforming to fix a caching problem is an expensive way to fix a caching problem.

We work in English. Calls, documentation and support for Thailand are delivered in English by our Singapore team.