By Dissai Pindatisha, Founder, Simply & Fine Solutions · Published 10 Oct 2026 · Updated 10 Oct 2026

The more useful lesson is what we did not build

We've built 19 custom modules to close the gap between Odoo Community Edition and Enterprise Edition.

Every gap looks worth closing when a client asks. But a custom module is not a one-time cost — it's a commitment to maintain that code through every Odoo version upgrade, forever. Build the wrong one and you've bought yourself a permanent tax on every future upgrade.

The three questions

  1. Does this gap block a legal or accounting requirement, or is it a convenience? Compliance gaps get built. Convenience gaps usually don't.
  2. Will more than one client need it? A module built for exactly one client is a consulting deliverable, not a product — price it that way.
  3. Is upstream Odoo likely to ship this within two versions? If yes, wait. Nothing ages worse than a custom module competing with core.

What passed the filter

Thai withholding tax, cheque register, TFRS 16 lease schedules, consolidated reporting. Compliance, repeatable, and not on anyone else's roadmap. More on the editions in Odoo Community vs Enterprise (Thai).

Simply & Fine Solutions — Odoo implementor, Bangkok. ISO/IEC 29110 certified. More insights

Planning an Odoo project in Thailand?

A free 30-minute call. We will tell you plainly whether Odoo fits your business.

Book a free consultationChat on LINE

Related: Odoo ERP implementation in Thailand · SF Thai Accounting Cloud · Pricing · Odoo Thai accounting