Jet Sarmartkoon - MD
The developer says the site is working. Marketing says the traffic is there. But conversion stays flat. This article explains why the gap between Marketing and IT is the real reason most E-Commerce sites in Thailand underperform — and what a consultant who understands both technology and Thai buyer behavior actually does to close it.
"A website built primarily by a developer tends to produce a system that works — but not a system that sells. E-Commerce requires both technical strength and an understanding of buyer behavior at the same time."
You have a website. It works. Orders come in — slowly, inconsistently, never quite at the level anyone expected. The developer says the system is running fine. Marketing says the traffic is there. But somewhere between landing on the page and pressing pay, something isn't connecting.
The explanation that usually surfaces: "Thai consumers prefer Marketplace." It sounds plausible. It lets everyone move on. And it's wrong — or at least, it's only half right.
The real reason most E-Commerce sites in Thailand underperform isn't Thai consumer preference. It's that the site was never built for the way Thai consumers actually buy. That's a different problem — and it starts with a question most organizations never fully answer: who actually owns this?
Marketing is often the natural answer. And that makes sense — Marketing understands the customer, the brand, the market, and the revenue targets. Nobody is better placed to own the brand voice, the content direction, and the commercial goals of an online store.
But when the actual work starts, the questions that come up aren't purely Marketing questions anymore.
Which platform should we use? How do we architect this for growth? Can our existing systems connect to a new E-Commerce setup? Where does the data flow? Who handles security when a campaign drives a hundred thousand visitors in a single day?
These questions don't have answers in a Marketing plan — because they're a different set of problems entirely. They need someone who understands technology, system architecture, and how to manage a complex implementation.
On the other side, some organizations look at E-Commerce and decide it's a technology problem — so they hand it to IT. That logic is understandable too. But what I've seen repeatedly, working in this market, is that websites where IT takes the lead tend to produce a system that works but doesn't sell.
IT thinks from a technical requirement perspective — the system needs to be stable, security needs to be solid, integrations need to be complete. All of that is right. All of it is necessary. But what tends to disappear is the dimension that makes people actually want to buy: the UX that flows naturally, the content that answers the question in the buyer's head at the right moment, the checkout that doesn't give people a reason to leave halfway through.
The result is a technically sound website with sales numbers that never quite meet expectations.
And this needs to be said clearly: "making people want to buy" doesn't mean making the website look beautiful and adding nice product photos. It means understanding what a buyer is feeling at each point in their journey — what they're looking for when they arrive, what's making them hesitate on the product page, what stops them at checkout. It means designing the entire experience deliberately, from the first headline to the final confirmation screen. It means selling with content, not just displaying products.
This skill — conversion through content and experience design — sits at the intersection of buyer psychology, UX, and the technology to make it real. Teams with genuine depth in this area are rare in Thailand. Those who have it tend to get absorbed by large brands quickly.
The project stalls. Not because Marketing isn't doing their job. Not because the developer isn't capable. But because there's a gap in the middle — and whichever side leads the project, the other half of the problem doesn't get solved.
This isn't anyone's fault. It's structural. Enterprise-level E-Commerce isn't a Marketing project or an IT project. It's a cross-functional undertaking that needs someone to connect the pieces.
E-Commerce at any serious scale isn't like running a small online shop. The complexity is different across several dimensions — and in Thailand specifically, each of these has local nuance that global experience alone won't prepare you for.
Volume and pressure. During major campaigns, your system needs to handle hundreds of thousands of visitors without going down. A site that crashes on campaign day doesn't just lose that day's revenue — it damages customer trust in the brand in a way that takes time to recover from.
Legacy system integration. Most organizations operating in Thailand have existing ERP, WMS, or POS systems that pre-date any E-Commerce ambition. Connecting a new storefront to these systems has to be done carefully — it's not a matter of plugging in an API and moving on. The dependencies run deep, and the consequences of getting it wrong show up in places you don't expect.
Security that requires ongoing calibration. E-Commerce security isn't a set-and-forget installation. It has to be tuned continuously between the technology and the campaign calendar. Protect too aggressively and your own campaign traffic gets blocked — tens of thousands of real customers locked out at the worst possible moment. Protect too loosely and bots clear your inventory before genuine buyers can reach it. There's no universal formula. It requires experience tuned to each specific environment.
Multiple stakeholders with different languages. A serious E-Commerce project involves Business, IT, Marketing, and often senior leadership — each with different KPIs, different priorities, and different ways of describing the same problems. A consultant has to be able to translate across all of them. Getting everyone aligned and moving in the same direction is often more than half the work.
Thai-specific implementation requirements. This is the layer that catches most foreign brands by surprise. Global platforms — Shopify Plus, commercetools, BigCommerce, Adobe Commerce, SAP Commerce Cloud — are built for international markets. They don't arrive pre-configured for Thailand.
Payment behavior here is different. PromptPay (Thailand's instant QR transfer system), direct bank transfer, and Cash on Delivery are primary payment methods for Thai shoppers — not edge cases. Each requires custom integration. Cash on Delivery in particular functions partly as a trust signal: a shopper choosing COD isn't necessarily unable to pay digitally, they may simply not yet trust an unfamiliar brand enough to pay before delivery.
Pre-purchase behavior is different. LINE Official Account is a primary channel Thai shoppers use to ask questions before committing to a purchase. A brand without a responsive LINE presence is missing a trust signal that matters here in a way it wouldn't in most Western markets.
UX expectations are different. Mobile-first in Thailand means speed and zero friction above everything else. A checkout flow that converts well in Europe can lose buyers in Thailand if it has one extra step, one unfamiliar payment option, or loads a half-second too slowly.
None of this can be handled by someone who understands the platform but doesn't understand the buyer. All of it requires both dimensions at once.
Before getting into what a consultant actually does, it's worth being clear about what's at stake in this market.
Thailand's E-Commerce market has reached approximately 1 trillion THB in value, according to Priceza. The infrastructure is mature. Consumer spending online is significant and growing.
But D2C — brands selling directly through their own websites — accounts for only around 4% of that market. The rest flows through Marketplace platforms: Lazada, Shopee, and TikTok Shop.
For comparison, Direct-to-Consumer E-Commerce represents approximately 15–19% of US online retail, according to eMarketer. The gap between 4% and 15–19% isn't inevitable. It reflects where brands have invested, not a ceiling on what's possible.
"A trillion-baht market where D2C is 4% isn't a sign of saturation. It's a sign of opportunity most brands haven't touched yet."
The brands that are quietly investing in D2C now are compounding a data advantage every day. The window is still open — but it won't stay that way indefinitely.
Customer behavioral data from your own website — what products they browse, what goes in the cart without converting, where they come from, when they buy — takes time to accumulate. A brand that starts collecting this data today will have an asset in two years that a competitor with more budget can't simply purchase.
Technology today is meaningfully more accessible than it was five years ago. What previously required a budget of tens of millions of THB to build properly can now be approached at a fraction of that cost, with platforms that are more flexible, more mature, and better supported. The constraint is no longer the technology. The constraint is finding people who can implement that technology correctly for the Thai market.
And there's a longer-term dimension worth naming. Organizations with clean, well-structured customer data collected consistently over time will be positioned to use AI in ways that those without it simply can't — product recommendations calibrated to individual behavior, dynamic pricing, personalization at scale. AI is only as useful as the data behind it. The organizations that start building that data asset now will have an advantage that compounds in ways competitors won't be able to catch up to simply by spending more later.
Setting aside the brands that have been quietly investing in D2C for years and building up their data advantage in the background — most brands, Thai and foreign alike, haven't committed to E-Commerce fully. Not because they don't want to. Because they perceive the risk as too high.
Risk of choosing the wrong technology and having to start over. Risk of investing significantly and not seeing a return. Risk of building a system that nobody can maintain once it's built.
The underlying cause, in most cases, is a lack of a partner who genuinely understands the problem.
Most Thai agencies grew from a Marketing background — strong in advertising, content, social media, campaign planning. These are real and valuable skills. But when a client asks about E-Commerce technology — platform architecture, system integration, data infrastructure — it's not their primary expertise. That's not a criticism; it reflects how the Thai market developed, where demand for Digital Marketing has always been high.
Global technology firms know the platforms. They don't understand Thai consumer behavior, how Thai buyers make decisions, or what an experience needs to feel like for a Thai user to trust it enough to complete a purchase.
The gap between these two — between technology capability and local market understanding — is wide. And it's this gap that leaves most organizations without a partner they can genuinely rely on.
This gap shows up differently depending on where an organization is starting from.
An organization has an E-Commerce site — built properly, invested in significantly. The system functions. But it slows under campaign traffic. Back-end systems connect imperfectly; orders that come through the website have to be manually re-entered into the ERP. Customer data sits in separate systems that don't talk to each other. Sales haven't grown the way they should, but nobody can pinpoint whether the problem is the UX, the product presentation, or the checkout.
The organization knows a Replatform is needed. But the project stalls every time it comes up — fear of disrupting sales during migration, fear of data loss, fear that the team won't adapt. So the existing system continues, while the cost of maintaining an ageing architecture quietly rises. Systems past a certain age reach a point where annual maintenance costs exceed what it would take to rebuild entirely. But nobody pulls the trigger because the risk of the transition feels greater than the cost of staying still.
When a consultant enters this situation, the first step is never recommending a new platform. It's a full audit of what's working and what isn't — followed by a phased migration plan designed to minimize disruption: start with the least-risky components, run old and new in parallel during the transition, and have a clear rollback plan at every stage.
The result is that the team gains confidence, the path becomes visible, and a project that had been stuck for years begins moving.
The budget has been approved. The team is ready. But the more they research, the more options there seem to be, and the harder it is to choose. Vendors are presenting their own platforms as the obvious answer. IT recommends one thing. Marketing wants something else. Leadership isn't sure who to listen to.
The decision ends up being made by committee — a vote in a meeting room, without anyone in the room having a complete view of the full system requirements.
The consequences of choosing the wrong platform don't always show up immediately. A year in, growth demands features the platform can't support. The team starts building workarounds. The system becomes something nobody wants to touch. And eventually the organization faces a Replatform — having spent significant budget and time to arrive back at the beginning, with less organizational confidence in E-Commerce than when they started.
The analysis that tends to follow is predictable: "Thai consumers prefer Marketplace." This conclusion is half-true at best. Thai consumers are accustomed to Marketplace. But the reason they don't buy on a brand's own site is often not preference — it's that the site hasn't been built to make them want to buy. Friction in the UX, incomplete product information, an unfamiliar checkout flow, a missing payment method: fix these things, and the results change.
If a consultant had been involved before the platform decision, the process would have looked different: requirements defined not just for today, but for where the business will be in two to three years. That investment in planning typically costs a fraction of what a Replatform costs later.
In my experience, the planning phase almost always takes longer than anyone expects. We spend more time on it than seems reasonable — sometimes more time planning than building. But it's the planning that determines whether the build succeeds. Projects that are planned properly encounter far fewer problems during implementation and tend to hit their targets. "Wasting time" on planning is, in practice, how you save time across the whole project.
A consultant doesn't replace Marketing. Doesn't replace IT. Doesn't replace an agency. But in practice, a good consultant is often the person holding the complete picture — working from behind the scenes, not in front of the internal team.
The role is to see Business, Technology, and People at the same time — and to connect every stakeholder toward the same goal. Simply put: the consultant is the person who makes sure everyone is speaking the same language, from the boardroom to the server room.
And critically — a good E-Commerce consultant doesn't just produce a strategy and hand it over. They need a team that executes. From strategy through platform selection, architecture design, implementation, and post-launch optimization. Because if they only plan and then step back, who ensures that what was designed gets built the way it was intended?
Not a generic E-Commerce framework applied to Thailand. A roadmap built on actual analysis of the Thai market, local consumer behavior, organizational constraints, and real business objectives — then translated into phases with clear timelines and budget requirements that leadership can make decisions against.
A roadmap that looks good on paper but can't be executed has the same value as no roadmap at all.
Not a vote. A multi-dimensional evaluation that accounts for long-term business direction, the constraints of existing systems, team capability, and where the technology is heading. The right platform decision, made correctly the first time, changes the entire economics of the project.
A good consultant explains why — not just which platform to choose, but what the trajectory of that technology looks like, how it aligns with business direction, and where the risks are that need to be managed.
Strategy without execution is a document. A full-service E-Commerce consultant brings a team that builds — storefront development, payment and logistics integration, back-end connections, performance optimization — and remains accountable through launch and beyond.
The phase where most E-Commerce projects go wrong is implementation: the moment when strategy has to become a working system. Without someone who holds the complete picture present throughout that process, what was designed carefully can be built incorrectly without anyone catching it in time.
The E-Commerce storefront doesn't exist in isolation. It connects to ERP, CRM, WMS, POS, and whatever else already exists. IT knows those existing systems best — their constraints, their history, their fragility.
The consultant's job is to design integrations that work without destabilizing what's already there, and to define clear boundaries: what belongs to internal IT, what belongs to external partners, and what needs to be done together. Without those boundaries established clearly from the start, IT gets overloaded — because anything that looks technical gets pushed to them, regardless of whether it should.
If data isn't planned from the beginning, every decision that follows is based on intuition rather than evidence.
Define from the start: what data to collect, where to collect it, how to analyze it, and what decisions it will drive. Don't build the website first and think about data afterward.
The right consultant helps Marketing see data as a tool, not a burden. When teams understand how customer behavior data enables campaign segmentation, how conversion rates by channel tell you where to invest, how purchase patterns reveal what to recommend next — the team starts asking better questions, making faster decisions, and measuring outcomes with more clarity.
And beyond Marketing: organizations with clean, well-structured customer data are positioned to apply AI in ways that create lasting competitive advantage. Product recommendations, dynamic pricing, personalization at scale — none of this works without good data underneath it. The organizations that build that data asset now will have an advantage in two to three years that no amount of spending can replicate quickly.
The market for E-Commerce consultants in Thailand is varied — from individual freelancers to global consulting firms. But not everyone who describes themselves as an E-Commerce consultant has genuine depth in Enterprise-level work. In practice, the field is smaller than it appears, and much of what's available is oriented toward SME marketing rather than complex system implementation.
The simplest test: a consultant should be stronger than the team you already have. There's no reason to pay significant fees for someone who knows less than the people already inside your organization.
What "stronger" looks like, concretely — at minimum, three things:
Deep knowledge of E-Commerce technology. Not just awareness of which platforms exist, but genuine understanding of architecture, integration patterns, performance requirements, and where the technology is heading. The ability to make a platform recommendation and defend it against scrutiny.
Understanding of how Thai buyers actually behave. Not Western best practice applied to Thailand. Genuine understanding of how Thai shoppers make decisions, what they need to feel before trusting a brand enough to buy, where they drop out of a checkout flow and why, what the presence of COD or a LINE contact does to conversion. This cannot be borrowed from experience in other markets.
The ability to work across all stakeholders. Marketing, IT, and leadership all have different priorities, different vocabularies, and different definitions of success. A consultant who can only speak to one of them isn't solving the whole problem. The role requires being able to hold the full picture and translate across every stakeholder simultaneously.
At Deeboon, we focus specifically on Headless Commerce for organizations in Thailand — because we believe it's the architecture that best serves long-term flexibility and growth. But if a client's situation doesn't fit that model, we say so. The right answer is the one that fits the client's actual constraints and goals, not the one we're most comfortable building.
The gap in Thailand is wide. Thai agencies are strong in Marketing. International firms are strong in technology. Neither typically has both — and both are necessary.
The Thailand E-Commerce market is heading toward 2 trillion THB. D2C is currently 4% of that. The brands that are building their own channels now are quietly accumulating a data and relationship advantage that compounds every day. The window is still open.
That 4% isn't a ceiling. It's a starting point — for the brands willing to build something they actually own.
At the core, a consultant closes the gap between Marketing and Technology — the two sides that every E-Commerce project needs, and that rarely exist in the same team. In practice this means building strategy and roadmaps grounded in Thai market reality, selecting and configuring platforms with Thai-specific requirements from the start, leading implementation so strategy doesn't get lost in execution, designing data architecture from day one, and aligning all stakeholders — marketing, IT, operations, leadership — around a shared understanding of what the project needs to achieve.
Global platforms and global best practices don't arrive pre-configured for Thai buyers. Payment behavior is different — PromptPay, bank transfer, and Cash on Delivery are primary methods, not edge cases. Trust signals work differently — LINE Official Account plays a role in pre-purchase decisions that has no equivalent in most Western markets. Mobile expectations focus on speed and zero friction in ways that require specific optimization. A consultant with strong technology knowledge but no Thai market experience will build something that works technically and underperforms commercially.
The most common causes in Thailand: payment options that don't match what Thai buyers expect, product pages missing information that Thai buyers need before deciding, absence of trust signals that matter here (LINE contact, familiar payment methods), and mobile performance issues. The right starting point is a structured audit of where in the journey buyers are dropping out — and why — before making any changes. Changing the wrong thing first costs time and rarely solves the underlying problem.
A marketing agency drives traffic and manages channels — the right partner for building awareness and running campaigns. An E-Commerce consultant works on the system those campaigns send traffic to: the platform, the checkout, the integrations, the data architecture, the experience design that determines whether a visitor becomes a buyer. At serious scale, both are needed. The mistake is asking one to do the other's job.
A developer builds to a specification. If the specification is right, the result can be excellent. If the specification is missing key Thai-market requirements, or doesn't account for how the system will need to evolve in two years, a technically perfect build can still produce a commercial disappointment. A consultant is involved in defining the specification — what to build, why, in what order, with what architecture — before the building starts. Engage a consultant when you're making decisions about platform, system architecture, or why your current setup isn't converting. Engage a developer once those decisions have been made well.
For a serious build from scratch or a Replatform, a realistic timeline from strategy to a properly functioning and optimized live site is typically 6–12 months, depending on integration complexity and the state of existing systems. The planning phase takes longer than most organizations expect — and that time is where the outcome is determined. Projects that rush through planning consistently encounter more problems during build and require more correction after launch. Time spent in planning is time saved across the whole project.
Assuming that what worked in another market will work in Thailand with minor adjustments. This shows up most clearly in payment flow design (treating COD and PromptPay as secondary options), trust signal strategy (no LINE presence, relying on on-site reviews that Thai buyers weight less heavily), and mobile experience (optimized for general standards rather than Thai user expectations). The technology can be correctly implemented and the approach still miss the market.
Yes. Marketplace is still the primary discovery channel for Thai online shoppers and remains an important revenue source. The goal isn't to abandon it — it's to stop building your entire Thai business on channels you don't own. The right approach is to use Marketplace for what it does well (volume, discovery) while building the channel that creates customer relationships, data ownership, and margin control over time. Both can run simultaneously. What matters is that the D2C investment is treated seriously, with realistic timelines and the right partners — not as a secondary project that gets the budget Marketplace doesn't need.
Three things that matter most: genuine depth in E-Commerce technology (not just awareness of platforms, but real understanding of architecture and implementation), specific knowledge of Thai consumer behavior (not borrowed from other markets), and the ability to work across Marketing, IT, and leadership simultaneously. Beyond that: ask to see what they've actually built, not just what they've planned. Ask what went wrong during implementation on past projects and how it was resolved. A consultant who can answer that question clearly has been present through the hard part. One who can't may not have been.
Because the planning phase is where you discover all the things that would have gone wrong during build. Every question answered in planning is a problem avoided in implementation — and implementation problems are significantly more expensive to fix than planning questions are to answer. Organizations that treat the planning phase as a delay consistently encounter more surprises during build, more corrections after launch, and worse outcomes overall. The planning phase isn't the preamble to the project. It is the project.
