What Odoo costs in baht over three years
We ran three typical Thai companies through the same calculator that powers our Odoo cost tool. Year one uses Odoo's first year discount, years two and three the list price, plus the Success Pack that matches the scope, plus 7% VAT. Odoo prices its plans in euro, so the baht figures use our planning rate of 1 EUR to 38 THB. Odoo sets prices by country, so a quote in Thailand can differ.
| Company | Pack | Year one | Years two and three, each | Three years incl. VAT |
|---|---|---|---|---|
| Shop with 5 users | Starter (4 hours) | THB 45,400 | THB 56,800 | THB 190,300 |
| Distributor with 15 users | Standard (50 hours) | THB 136,100 | THB 170,300 | THB 700,200 |
| Group with 30 users | Custom (100 hours) | THB 491,100 | THB 614,200 | THB 2,182,100 |
Change the users, apps and pack to match your company in the Odoo ERP cost estimator. It runs in your browser and asks for no contact details.
Worked example: the 30 user group
The group needs multi company and two integrations to other systems. That forces Odoo's Custom plan and the Custom Success Pack, so its three year total is THB 2,182,100 including VAT before integration work. Adding our published ERP integration starting point of THB 570,000 gives THB 2,609,300 before VAT on the integration. That is the number a custom build has to beat for the same modules.
A custom build can beat it, but only if the build plus three years of care stays below that figure and still delivers accounting, stock, sales and Thai tax reports. In our view that is rare below roughly this size when the processes are standard, and it is realistic when the licence cost scales to hundreds of users or when the workflow is unusual. We would rather tell you that now than after a discovery call.
Per user, the 15 user distributor pays about THB 11,400 per user per year from year two. That is the figure to compare against the cost of building and maintaining the same features once.
Thai tax: check this before you decide
Odoo's documentation for version 20.0 lists Thai features including VAT 7%, VAT 0% and VAT exempted taxes, withholding taxes with income tax types under section 40, sales and purchase tax reports as XLSX, P.P. 30 VAT report as CSV for RD Prep. The documentation for the previous version 19.0 states: "Odoo cannot generate the PND or PDF report or withholding tax certificate directly." That means a company on the older version still files its PND returns and withholding tax certificates outside the system.
Ask any Odoo partner which version they will install, which tax reports are native in that version and which need a workaround. A custom ERP has the opposite risk: every report works exactly as specified on day one, and someone must update it when the Revenue Department changes a form.
When Odoo wins
Odoo is the better first answer when most of these are true.
- Your sales, purchasing, stock and accounting follow common patterns for your trade.
- You have 5 to a few hundred users and the licence cost stays below the cost of building the same features.
- You want Thai VAT and withholding reports on a supported route, and you are on a version that provides them.
- You need to be live in weeks, with an implementation pack that has a fixed number of hours.
- Your team can adopt a standard screen and change the process where Odoo is better.
When custom wins
A custom ERP, or custom software next to a packaged one, earns its cost in these cases.
- One workflow is your competitive edge, for example a bespoke production or booking process that no module models.
- You need Odoo's Custom plan features (Studio, multi company, external API, or Odoo.sh or on premise hosting) so heavily that the subscription and customisation bill approaches a build.
- You must own the source and host the data yourself for contract or compliance reasons.
- Licence cost per user will dominate at your size for years.
- You plan to sell the software, so it cannot sit on someone else's platform.
If your answer is mixed, our ERP integration work connects Odoo to the custom part. See ERP integration for Thai companies.
Honest tradeoffs, including against our own interest
We build custom software and ERP integrations, so a custom recommendation would pay us more. Our view is that rebuilding stock, accounting and Thai tax reporting from nothing is rarely worth it for a company with standard processes. The most useful custom work is usually the narrow piece that differs, connected to a standard core. The cost of Odoo grows with every user and every customisation, and heavy customisation makes upgrades harder. The cost of custom grows with every year of maintenance. Neither is free.
Checklist before you sign anything
- List your ten most frequent processes and mark each as standard or different.
- Count users by role, and decide who needs a full licence.
- Ask the Odoo partner for a fixed scope and hours, or use a Success Pack, and ask which version they install.
- Ask which Thai tax reports are native in that version and which are workarounds.
- Ask for the three year cost, with VAT, in baht, in one table.
- For custom: ask for phases, a first usable release, the hosting plan and a named maintenance owner.
- Put code and data ownership, a source handover and an exit plan in the contract.
- Pick a decision date. Run the cost estimator and compare against the first two quotes.
Questions buyers ask
Is Odoo enough for a Thai company?
For standard sales, purchasing, stock and accounting, usually yes. Check the Thai localisation of the version you will run, because the documentation for older versions says the system cannot produce PND PDF reports or withholding tax certificates directly.
Which Odoo features need the more expensive plan?
Odoo's pricing page lists Odoo Studio, Multi Company, External API, Odoo.sh or on premise hosting as Custom plan features. Hosting, implementation services and in app credits are not included in the subscription.
Who owns software I commission in Thailand?
Section 10 of the Thai Copyright Act deals with ownership of commissioned work, and how it applies to software depends on the facts. Do not rely on the default. Write the ownership, source handover and licence of any third party code into the contract. This is general information, not legal advice.
Can we start on Odoo and replace parts later?
Yes, and for many companies it is the cheapest route. Keep customisation in separate modules, keep your data exportable and replace only the part that proves unusual.
Who wrote this, how and why
Who: Written by the DLVX team. We sell ERP integration and custom software in Thailand, so we gain from custom work. We do not resell Odoo licences on this page.
How: Baht figures come from the same code as our Odoo cost tool and our price list, with Odoo's public prices checked 30 October 2026 and converted at a fixed planning rate. The legal text was read on 8 November 2026.
Why: Buyers ask us this question before every ERP project, and most pages that rank for it use dollars and vendor claims. We wanted one honest comparison in baht.
Sources and checked dates
- Odoo pricing, plans and per user prices (checked 30 October 2026)
- Odoo Success Pack prices and hours (checked 30 October 2026)
- Odoo 20.0 Thailand fiscal localization (checked 30 October 2026)
- Odoo 19.0 Thailand fiscal localization (checked 30 October 2026)
- Copyright Act B.E. 2537 (1994), sections 9 and 10, WIPO Lex (checked 8 November 2026)