How Japanese Retailers Can Maximize SaaS in Thailand: Why Standard Operations Beat Custom Development

Target Audience: Site managers, store operations managers, and administrative staff at Japanese companies with retail outlets, shops, warehouses, or distribution centers in Thailand, as well as corporate planning and IT managers at headquarters who are involved in IT investment decisions for Thai operations.

“We had a system built locally, but when the person in charge quit, nobody could touch it.” “We’ve been studying how to connect it to the headquarters ERP for years and nothing has moved.” “The more we ask the vendor, the more additional costs pile up.” — These are the kinds of comments we increasingly hear from managers at Japanese companies running retail and distribution operations in Thailand.

Thailand in 2026 is not an environment where favorable economic tailwinds blow unconditionally. The World Bank has issued cautious growth projections for Thailand, and both labor costs and logistics costs continue to rise. At the same time, BOI (the Board of Investment of Thailand) has rolled out incentive measures for investments that include automation, AI, data analytics, and enterprise management IT — so there is no reason to stop investing altogether. The real issue is choosing which investments to stop and which to continue.

This article examines why Japanese retail and distribution companies operating in Thailand should choose SaaS or standard packages run in “standard mode” — rather than bespoke (custom/scratch) development — and organizes that reasoning from the perspectives of on-site challenges, cost structure, BOI utilization, and phased implementation. We will share concrete decision-making criteria covering how to connect POS, inventory, store operations, and accounting; how to protect gross margins and on-site capabilities; and how to explain the case to headquarters in Japan.

1. The “Three Structural Stresses” Facing Thai Retail Operations

Japanese companies running retail and distribution businesses in Thailand are currently confronting not isolated, one-off problems but three intertwined structural stresses.

(1) Changing Cost Structure

Thailand’s minimum wage has been raised incrementally over the past several years, and labor costs have become a fixed expense that can no longer be overlooked. On top of that, rising procurement costs for imported goods and materials, fluctuating electricity rates, and persistently high logistics costs are compounding the pressure. Even when sales remain flat, profit margins are squeezed — a situation in which simply continuing to operate as usual translates into a real deterioration of profitability.

(2) Workforce Mobility and Over-Reliance on Key Individuals

In Thailand, turnover among capable staff is high, and operational know-how tends to concentrate in specific individuals. With custom-built systems, if the local staff member who understands the system leaves, there is a real risk that operations grind to a halt or that nobody can handle system failures. Even if a manager is sent from Japan, it takes time to get up to speed on the local system specifications — and day-to-day operations cannot stop in the meantime.

(3) Information Gap with Headquarters

The difficulty of communicating the true state of Thai operations back to headquarters is a challenge common to many companies. Inventory status, sales figures, gross margins, and store-by-store performance are shared only through manually compiled daily or monthly reports, causing delays in decision-making. The less headquarters feels it understands what is happening, the more business trips and verification costs accumulate, and confidence in the local operation begins to waver.

How to alleviate these three stresses through IT investment is the core management challenge facing Japanese retail companies in Thailand right now. And whether the answer is custom development or SaaS standard operations makes a dramatic difference in cost-effectiveness and operational risk.

2. Why Custom Development Becomes a “Monster”

Custom development (bespoke or scratch development) offers an apparent “freedom” at first glance. Requirements such as “we want it tailored to our workflow,” “we don’t want to change our existing data structure,” “we need Thai-language support,” and “we need it to match headquarters’ report formats” are real and valid. However, custom development in Thailand carries significantly greater risks than in Japan.

Vendor Lock-In and Ballooning Maintenance Costs

With a custom-built system, only the vendor that built it truly understands what is inside. Development often proceeds without adequate specifications documentation, and a few years later you find yourself in a situation where “we want to add modifications, but we have no choice but to go back to the original vendor.” In such cases, the additional costs are often equal to or greater than the original development cost.

“Black Boxing” When Key Personnel Turn Over

IT companies in Thailand tend to have higher engineer turnover than those in Japan. It is not uncommon for the developer who built the system to leave the company, leaving maintenance to continue with inadequate handover. Documentation is often lacking, and investigation costs arise every time a modification is needed.

Cost of Responding to Regulatory Changes and Tax Rule Revisions

Thailand periodically revises rules governing accounting processes and tax filings (VAT, withholding tax, etc.). For SaaS or standard packages, vendors generally provide updates. With custom development, the company (or its development vendor) must request the changes and pay additional fees each time.

Barrier to Scaling

When trying to roll out a system built for one store to three or five stores, custom development almost always generates “unanticipated man-hours.” With SaaS, in most cases the solution is simply adding accounts or licenses.

Custom development is not inherently a “bad choice.” It has merit when there are business requirements that a standard package simply cannot accommodate. However, in the majority of cases at Japanese retail and distribution companies in Thailand, the business workflow is not particularly unique — the chief driver of choosing custom development is often the psychological barrier of not wanting to change familiar ways of working.

3. Practical Reasons SaaS “Standard Operations” Are Chosen

Choosing to use SaaS or a standard package in “standard mode” — meaning adapting the business workflow to the system rather than the reverse — can meet resistance from Japanese companies. “It doesn’t fit the way we do things” is still a common objection. Yet in the Thai business environment, there are multiple reasons why this choice is rational over the long term.

Compressed Initial Costs and Implementation Lead Times

Because SaaS is available on a monthly or annual subscription, the initial development investment is kept down. Implementation timelines can be compressed as well: whereas custom development may take months to over a year, a standard package can often go live within a few weeks to two months. The ability to start quickly and validate results quickly is a genuine advantage in a high-uncertainty operating environment.

Automated Updates and Security

SaaS vendors regularly update their systems, delivering regulatory compliance updates, security patches, and new features. User companies can essentially receive these at no additional cost. When Thailand’s tax rules change — such as e-invoice compliance requirements — major SaaS vendors tend to respond promptly.

Ease of Multi-Site Expansion

When rolling out a system established in Bangkok to warehouses and stores in Chiang Mai, Rayong, or Chon Buri, SaaS often requires only license additions and configuration changes. Custom development tends to generate additional modification work for each new site, causing costs to grow super-linearly.

Absorbing Turnover Risk

Standard packages come with well-prepared operation manuals, YouTube videos, online help, and vendor support. Even when a key staff member leaves, new employees can learn to operate the system in a relatively short time. With custom development, there are no such generic learning resources, and if handover fails, there is a real risk that operations stop.

The Mental Shift: “Adapting Business Processes to the System”

Using SaaS in standard mode means setting aside “our unique way of doing things” and aligning business workflows with “the industry-standard best practice.” This can create short-term pressure on the team on the ground, but over the medium to long term it leads to process standardization, elimination of over-reliance on individuals, and lower onboarding costs for new employees. This is a particularly significant benefit for companies planning to hand operations over to local Thai staff.

4. The “Four Data Streams” That Must Be Connected in Retail Operations

For Japanese retail and distribution companies in Thailand leveraging SaaS or standard packages, the single most important principle is “connecting data.” Even if individual tools are implemented, isolated data cannot be used for decision-making. To link the data generated on the floor every day to management decisions, it is essential to keep the following four data connections in mind.

① POS Data (Sales Results)

Which product was sold, when, at which store, and in what quantity — this is the starting point for everything. If POS data is managed through manual tabulation or Excel, delays and errors are inevitable, and reorder decisions are delayed as well. With cloud-based POS, data from multiple stores can be aggregated in real time and viewed from headquarters or the back office.

② Inventory Data (Physical Counts and Stock Movements)

Both excess inventory and stockouts hurt gross margins. Excess inventory strains cash flow and generates disposal and storage costs. Stockouts are lost sales. When POS data and inventory data are linked, real-time inventory management becomes possible — stock decreases automatically as items are sold. The labor required for physical inventory counts is also dramatically reduced.

③ Purchase Order and Procurement Data (Suppliers and Purchasing)

Purchase order management linked to inventory data directly enables inventory optimization. Automated order proposals based on demand forecasting (historical sales data and seasonal patterns) reduce the judgment burden on purchasing staff and lower the risk of over-ordering or under-ordering. Digitizing communications with Thai suppliers reduces the labor involved in purchase orders, receipts, and reconciliations.

④ Accounting and Financial Data (Revenue, Cost of Goods, Gross Margin)

When sales, inventory, and purchasing data are connected to the accounting system, revenue, cost of goods, and gross margin can be tracked in real time. Month-end close work is reduced, and reporting to headquarters becomes faster. Thailand’s accounting processes (VAT filing, withholding tax, e-invoice compliance) are complex, making the use of a Thailand-compliant accounting SaaS a practical choice.

Creating a state in which these four data streams are connected is the “true goal” of digitalization. Implementing any one tool in isolation leaves data silos intact.

5. Decision Criteria: Which Investments to Stop and Which to Continue

In Thailand’s 2026 economic environment, sustaining every investment is not feasible, and prioritization is necessary. Use the comparison table below as a reference for organizing investment decisions in the retail and distribution space.

What the “investments to stop” in this table have in common is that information stays on-site and never flows outward, operations depend on specific individuals, and hidden additional costs accumulate. Conversely, the “investments to continue” share the characteristics that data accumulates and can be reused, the vendor handles maintenance, and results can be measured in numbers.

6. BOI Utilization: The IT Investment Incentives That Retail and Distribution Companies Are Missing

The incentive targets of Thailand’s Board of Investment (BOI) are not limited to manufacturing. Since 2023, BOI has expanded its incentives to cover investments that include digitalization, automation, AI, data analytics, and enterprise management IT. For Japanese companies operating retail and distribution businesses in Thailand, planning IT investments in conjunction with BOI applications is worth considering from a cost-reduction standpoint.

Investment Areas Potentially Eligible for BOI Incentives (Retail / Distribution)

• Warehouse and logistics automation (automated sorters, AGV, racking systems, etc.)
• Deployment of smart warehouse management systems (WMS)
• AI/machine learning-based demand forecasting and inventory optimization
• Building or strengthening e-commerce (EC) platforms
• Investment in data centers and cloud infrastructure
• IoT sensor-based refrigeration and temperature management systems

Representative BOI incentives include corporate income tax exemptions, import duty exemptions, and facilitated work permits for foreign nationals. However, applications must in principle be filed before the investment is executed — waiting until after the investment decision is made often means it is too late. Checking BOI eligibility at the early stages of IT investment planning is essential.

BOI applications may also require documentation demonstrating the investment’s impact in quantitative terms. This documentation can also serve as the basis for explanations to headquarters in Japan. Framing the proposal as “plan Thai IT investment together with a BOI application” is a key point for making it easier to obtain approval.

7. Failure Patterns and How to Avoid Them: Common Pitfalls in IT Implementation for Japanese Companies in Thailand

The same failure patterns repeat themselves when implementing systems for retail and distribution in Thailand. Below is a summary of the most representative patterns and how to avoid them.

Failure Pattern ①: Requirements Are “Just a Translation of the Japanese Way”

This is the case where attempting to transplant the systems, forms, and workflows used at headquarters in Japan directly into Thailand causes custom development costs to balloon. Thailand’s accounting processes, tax rules, language, and the operating habits of local Thai staff are different from Japan’s. Adopting the mindset of “aligning with Thailand’s standard approach” leads simultaneously to lower costs and better adoption on the ground.

Failure Pattern ②: “Cheap for Now” Tools That Cannot Integrate

This is the situation where POS, inventory management, accounting, and purchasing are each implemented with separate low-cost tools, resulting in data that cannot be integrated — and Excel transcription work that never goes away. Even if the individual tool costs are low, when integration costs, human labor, and error risk are added together, the total can be surprisingly high. Before implementation, it is essential to confirm “what does this tool integrate with?”

Failure Pattern ③: Insufficient Explanation to On-Site Staff Prevents Adoption

This is the case where a system is implemented but on-site staff never learn to use it — resulting in a state where “it ends up unused.” Before implementation, it is necessary to confirm whether there are Thai-language manuals and instructional videos and whether the vendor can provide support in Thai. Building a management dashboard and then neglecting to roll it out to the floor means data is never entered, and the system cannot function.

Failure Pattern ④: Slow Headquarters Approval Process Causes Missed Opportunities

This is the case where a system implementation study is advanced at the Thailand site but headquarters approval takes six months or more, during which the local project lead transfers or resigns and the project resets. When presenting to headquarters, number-based explanations such as “recoverable in three years, reduces risk, reduces management labor” are more effective than “it seems convenient.” Proposing phased investment (starting with one store or one process) can also lower the approval hurdle.

Failure Pattern ⑤: Trying to Implement AI Before Data Has Accumulated

Demand for “AI demand forecasting” is growing, but AI models cannot function when less than one year of historical sales and inventory data has been accumulated. Building the mechanism to accumulate baseline data must come first. AI is a tool that “only works when data exists.”

8. How to Execute Phased Implementation: Start With “One Store, One Process, One Form”

As an approach to successful system implementation in Thailand, what TOMAS TECH has found effective in the field is phased implementation: “start small, measure the results, then expand horizontally.”

Step 1: Make “Hidden Costs” in Current Operations Visible

First, identify where losses are occurring within current operations. Inventory disposal, stockouts, excess inventory, manual tabulation labor, form transcription errors, missed billing, time spent aggregating daily reports — converting these into monetary terms provides the justification for the implementation investment.

Step 2: Choose the Single “Breakthrough Point” With the Greatest Impact

Rather than trying to solve everything at once, focus on the single point of greatest impact. If inventory losses are large, start with inventory management. If form transcription labor is large, start with form digitalization. By starting within a defined, limited scope — “one store,” “one warehouse,” “one type of form” — you can validate results while keeping risk low.

Step 3: Verify Results in Numbers at the Three- to Six-Month Mark

At three to six months post-implementation, compare figures such as “the change in inventory disposal cost before and after implementation,” “the change in physical count labor time,” and “the reduction in form transcription labor hours.” These numbers become the “justification for the next investment approval” when reporting to headquarters.

Step 4: Expand Horizontally After Results Are Confirmed

Once success at one store or one process is confirmed, roll out to other stores, warehouses, and departments. By this point, on-site staff also have a shared sense that “this is a system that works,” and adoption rates are higher.

The advantages of phased implementation are three: you can move forward without taking on major failure risk; you can explain results to headquarters in numbers; and staff on the ground are genuinely convinced.

9. Explaining to Headquarters in Japan: Lead With “3-Year Payback, Risk Reduction, and Reduced Management Labor” — Not “Convenience”

Even when the need for a system investment is clearly felt at the Thailand site, there are many cases where approval from headquarters in Japan cannot be obtained. To make a headquarters presentation more likely to succeed, it is necessary to change the “language” of the proposal.

Explanations That Tend Not to Get Approved

• “It will make operations easier.”
• “It will improve work efficiency.”
• “It’s the latest DX tool.”
• “Other companies in Thailand are adopting it.”

Explanations That Tend to Get Approved (Numbers- and Risk-Based)

• “We are currently losing approximately XX million baht per year to inventory disposal and excess stock. The inventory management system is projected to reduce this by XX%. The investment pays back within three years.”
• “Physical inventory counts currently consume XX hours per month. Systemization will reduce this by XX hours — equivalent to approximately XX million yen per year in labor cost savings.”
• “One person currently handles all tasks in this area, creating high turnover risk. Systemization will eliminate the over-reliance on that individual and reduce handover costs.”
• “To comply with Thailand’s mandatory e-invoicing requirements, an accounting system update is necessary. With a SaaS solution, compliance is covered at no additional cost.”
• “By applying as a BOI incentive project, there is a potential for corporate income tax relief.”

What headquarters approves is “problem resolution,” “risk reduction,” and “cost savings.” “Convenience” alone is not grounds for approval. The fastest route to approval is for the Thailand site staff to communicate the local reality in numbers.

10. Pre-Implementation Checklist for SaaS Standard Operations in Retail and Distribution

Use the checklist below to assess your company’s current status and implementation readiness.

The more items on this checklist where you answered “No,” “Partially,” or “Some risk,” the higher the investment priority for that area. There is no need to solve everything at once — the most practical approach is to start with the area of highest risk.

11. Accounting DX and Paperless Operations: The “Quiet but High-Impact” Improvements in Thai Retail

While large-scale system investments get most of the attention, one area with quietly significant improvement potential at Japanese retail and distribution companies in Thailand is accounting processes and going paperless.

Why Is Thailand’s Accounting Process So Complex?

Thailand’s accounting and tax rules differ from Japan’s in many ways, and if VAT (value-added tax), withholding tax, e-invoicing, and other areas are not managed properly, tax risks arise. In recent years, Thailand’s Revenue Department has been pushing harder to promote electronic bookkeeping and e-invoicing, and more situations requiring digital compliance are expected going forward. Using a Thailand-compliant accounting SaaS reduces the cost of adapting each time regulations change.

What Paperless Operations Mean for Retail Floor Operations

Daily reports, purchase orders, receiving documents, inventory sheets, and claim records generated in day-to-day store operations each carry a fourfold cost: recording, storage, transcription, and submission. Digitizing these via tablets or smartphones achieves a reduction in transcription errors, a reduction in storage costs, and instant transmission of information to managers. At Thai on-site operations, it is important that the interface be available in Thai so that staff who cannot read Japanese can use the system.

The impact of going paperless can be measured in “how many hours per month are saved.” Even if one store saves 10 hours per month, five stores save 50 hours per month — 600 hours per year. Converted to labor cost, that builds a solid case for the investment’s payback.

12. TOMAS TECH’s Perspective: Connecting On-Site Challenges to Solutions

TOMAS TECH supports IT implementation for Japanese manufacturing, logistics, and retail companies in Thailand and across ASEAN, starting from on-site challenges as the point of origin. Below is a brief overview of how the challenges covered in this article connect to the solutions TOMAS TECH provides.

Inventory Management Digitalization: Achieving “Inventory Visibility” With PEGASUS

The inventory management system PEGASUS, provided by TOMAS TECH, is a system that manages inventory at warehouses, stores, and logistics sites in real time. It supports barcode- and QR code-based inbound/outbound management, streamlined physical inventory counts, stock movement recording, and visibility of inventory status for headquarters. It is a system well-suited to companies with challenges such as “we manage inventory in Excel but errors are frequent,” “physical inventory counts take too long,” or “we lose track of where inventory is.”

PEGASUS has been developed and improved based on practical experience at Japanese manufacturing, warehouse, and logistics sites in Thailand. It offers an operation screen available in both Thai and Japanese and support from Thailand-based staff. Implementation is possible starting from a single small warehouse, and it supports the phased implementation approach of expanding after results are confirmed.

Going Paperless: Digitizing Daily Reports and Forms With i-Reporter

As a tool for digitizing paper daily reports, inspection forms, receiving documents, and claim records at stores, warehouses, and logistics sites, TOMAS TECH supports the deployment of i-Reporter. i-Reporter is a tool that digitizes paper forms exactly as they are using tablets or smartphones, with the distinguishing feature that existing form formats can be maintained as the transition to digital is made. Thai-language form design is also available, making it easier for on-site staff to adopt.

Operations Management: Making “Downtime” Visible on the Floor

At retail and logistics sites, work backlogs, waiting time, and line stoppages occur — but in many cases this time is not recorded as data. By leveraging the operations management system provided by TOMAS TECH, work time, stoppage time, and cause classifications can be recorded and visualized in real time, accumulating the data needed to drive improvement PDCA cycles.

Smartwatch System: Real-Time Communication on the Floor

At Thai warehouses and stores, information transfer between on-site staff is sometimes handled through informal channels such as verbal communication, paper notes, or LINE. By leveraging the smartwatch system, work instructions, alerts, and task completion reports can be exchanged in real time via watch devices, reducing communication loss on the floor.

The hallmark of TOMAS TECH’s approach is not “implementing a large-scale complete system all at once” but rather “starting from the single point most likely to generate results, embedding it on the floor, and then expanding horizontally.” Japan- and Thai-language-capable staff based in Thailand handle everything from implementation to ongoing operational support, enabling assistance that minimizes friction related to language and culture.

For inquiries and consultations, please feel free to reach out at https://tomastc.com/contact.

Summary

This article organized the reasons why Japanese retail and distribution companies based in Thailand should choose SaaS standard operations over custom development, from the following perspectives.

• Addressing structural stresses: Rising costs, workforce mobility, and the information gap with headquarters can all be mitigated by connecting data.
• Risks of custom development: Escalating maintenance costs, black boxing, regulatory compliance costs, and scaling barriers tend to be more acute in Thailand.
• The rationale for SaaS standard operations: Four advantages — compressed initial costs, automated updates, ease of multi-site expansion, and absorption of turnover risk.
• The four data streams that must be connected: POS, inventory, purchasing, and accounting must all be linked before the data becomes useful for management decisions.
• Investment decision criteria: Distinguish between investments to stop and investments to continue; present to headquarters based on three-year payback, risk reduction, and reduced management labor.
• BOI utilization: Planning IT investment in combination with BOI incentives improves cost efficiency.
• Phased implementation: Starting with one store, one process, or one form — measuring results before expanding — increases adoption rates.

Thailand in 2026 is not a time to stop all investment — it is a time to “invest selectively.” What Japanese retail and distribution companies in Thailand need right now is not DX as a buzzword, but DX that actually moves the numbers on the ground.

If you are unsure where to start, please consult TOMAS TECH. We will propose the most impactful entry point for investment, starting from the on-site challenges specific to your company.

References

• World Bank Thailand — Thailand Economic Conditions and Growth Outlook
• Thailand BOI — Board of Investment of Thailand (Incentives for Automation, AI, and Enterprise Management IT)
• JETRO Thailand — Business Environment and Market Entry Information for Thailand
• S&P Global PMI — Thailand Manufacturing and Business Sentiment Data
• Ministry of Economy, Trade and Industry — Manufacturing White Paper 2025