Odoo vs custom ERP: an honest comparison for Indonesian businesses
By Apex Horizon Digital
When an Indonesian business starts shopping for an ERP, Odoo is usually the first name on the list (open source, modular, with local implementation partners. We recommend it ourselves in some audits. But "Odoo vs custom" is rarely compared honestly, because the people comparing are usually selling one of the two. We build custom systems, so read our bias accordingly) and then read the checklist at the end, which does not care what you pick.
Key takeaways
- Odoo is usually faster when your processes fit standard module patterns.
- Custom ERP earns its cost when the workflow itself creates your operational advantage.
- Compare adaptation, ownership, and lifetime operating cost, not license price alone.
What Odoo genuinely does well
Odoo ships dozens of modules that already work together: accounting, inventory, sales, purchasing, HR. If your processes are close to standard (buy, stock, sell, invoice) a competent partner can get you live in weeks. For a trading company with conventional workflows, that speed is hard to argue with, and we have told audit clients exactly that.
Where the friction starts
The trouble begins when your workflow is not standard, because then you customize. Odoo customization is real software development (Python, ORM, upgrade scripts) usually billed by the same partners who quoted the cheap implementation. Each version upgrade has to carry your customizations with it, and heavily customized Odoo instances have a way of getting frozen on old versions because upgrading became too expensive.
The second friction is pricing structure: Odoo Enterprise charges per user per month. A 40-person operation pays for 40 seats forever, whether a user lives in the system all day or approves one document a week. For workflow-heavy teams (the exact teams that need everyone in the system) per-seat pricing punishes adoption.
The real comparison is total cost of fit
The fair comparison is not license price vs build price. It is: what does it cost for the system to actually match how you operate, over three years?
- Odoo with standard processes: low cost, fast: the honest winner when your workflow is conventional.
- Odoo with heavy customization: implementation + custom development + per-seat licenses + upgrade tax on every customization, indefinitely.
- Custom build: higher first invoice, but scoped to only the modules you need, no per-seat fees, and the source code is yours.
When Odoo is the right answer
Your processes are close to industry-standard and you are willing to adapt the remaining 20% to the tool. You have (or will hire) a partner relationship you trust for maintenance. Your team size makes per-seat pricing tolerable. In that case: pick Odoo, pick a good partner, resist customization requests for the first year.
When custom is the right answer
Your workflow is the business (a catering kitchen schedule, a reseller pricing structure, a program-and-donor model no template anticipates. You would customize Odoo so heavily that you are paying for custom development anyway, plus licenses, minus ownership. Or the team that must use the system daily will only adopt something that mirrors how they already work. In those cases a scoped custom build) one high-friction module first, 6-12 weeks: usually costs less over three years and fits on day one.
How to decide without trusting either sales pitch
Map your five highest-volume workflows before talking to any vendor. For each, ask: does the template handle this as-is? If four of five are standard, Odoo deserves the shortlist. If three of five need custom work, you are buying custom development either way: the only question is whether you also want to rent the platform underneath it. A workflow audit produces exactly this map, and ours is free whether or not you build with us.