Key Takeaway
Choose Odoo when your processes fit its standard apps, SAP Business One when you need multi-entity or multi-currency depth and the SAP name carries weight, and a custom ERP only when the workflow itself is your competitive advantage. For Odoo and SAP, implementation is billed separately from the licence; for a custom build it is the main cost, so budget for it on its own line.
Every business owner reaching the point where spreadsheets no longer cut it faces the same three-way fork: Odoo, SAP, or build something custom. Having spent years implementing custom ERP systems as a freelance ERP consultant and watching clients wrestle with this decision, I can tell you there's no universal right answer — but there are clear patterns for when each option wins. Gartner predicts that by 2027 more than 70% of recently implemented ERP initiatives will fail to fully meet their original business goals. In my experience, a good share of that disappointment starts with choosing the wrong platform for the wrong reasons. This post is my honest, practitioner's take on the three options.
| Criterion | Odoo | SAP Business One | Custom ERP |
|---|---|---|---|
| Licensing model | Per user/month, yearly: Rp 137,500 Standard, Rp 255,000 Custom (13 Oct 2026) | Per user type; no public price, quote from SAP or a partner | None — a one-time build cost instead |
| Implementation budget | Extra; not in the subscription | Extra; set-up by you or an SAP partner | The build itself, scaled to scope |
| Per-user fees as team grows | Yes, per user (cheaper Light User tier) | Yes, scales with headcount | None — cost stays flat |
| Customization risk | Annual upgrades can break custom modules | Customization is expensive and complex | Built to your workflow, no upgrade risk |
| Best-fit team size | 10–100 people | Small and midsize firms wanting SAP | Any size with genuinely unique processes |
| Ideal use case | Standard workflows: distribution, simple manufacturing | Multi-entity, complex compliance, investor credibility | Unique approval flows, hardware integration |
The Cost Reality: What You'll Actually Pay
Raw licensing cost comparisons are misleading because they exclude implementation, training, and ongoing maintenance. Odoo is the only one of the three with a public price list: as listed for Indonesia on 13 October 2026, the Standard plan costs Rp 137,500 and the Custom plan Rp 255,000 per user per month on yearly billing, with a first-year discount for initial users. Implementation, Odoo.sh hosting for custom code and maintenance of that code are not included. SAP does not publish a price for Business One: you request a quote from SAP or a partner, and its cloud terms exclude set-up and configuration from the subscription. Custom ERP has no licensing cost but development is expensive, and what it costs depends entirely on scope — with lower ongoing costs once built.
Odoo: Open-Source Flexibility at a Price
Odoo's promise is one subscription covering its whole integrated suite, from accounting to manufacturing to eCommerce. The Community edition is open source (LGPLv3) and free to run yourself; the Enterprise edition needs a paid subscription for every user, sold as the Standard plan (Odoo Online only) or the Custom plan, which adds Studio, multi-company, the external API and Odoo.sh or on-premise hosting. For straightforward businesses that fit Odoo's standard workflows — wholesale distribution, simple manufacturing, professional services — Odoo delivers excellent value. The problem is customization. Odoo ships one major version a year (Odoo 20 arrived in September 2026), and every upgrade can break custom modules; the subscription covers upgrades of the standard apps, not maintenance of your custom code, so that cost compounds over time. I've seen Odoo implementations end up costing several times their original budget once scope creep and upgrade work were counted.
SAP Business One: Enterprise Power, Enterprise Complexity
SAP Business One is SAP's ERP for small and midsize businesses — SAP itself says there is no minimum company size — and it suits firms with multi-entity, multi-currency or manufacturing requirements that value the SAP name with investors or enterprise customers. SAP's larger line is SAP S/4HANA Cloud, sold as Public Edition and Private Edition, which SAP describes as designed for organizations of all sizes. B1's breadth is also its weakness: in my experience, fitting an Indonesian SME with 40 employees into it often means paying for capabilities you'll never use. Pricing is by quote, the cloud edition is subscribed per user type (Professional or Limited), and set-up sits outside the subscription: you do it yourself or contract the SAP partner who sold it, before any customization.
ERP Cost Structure: What You Actually Pay For
(Odoo list prices checked 13 Oct 2026; SAP B1 is quote-only)
┌─────────────────────────────────────────────────────────────┐
│ ODOO ENTERPRISE │
│ Licence: per user / month, all apps │
│ Standard Rp 137,500 | Custom Rp 255,000 │
│ (yearly billing, Indonesian list price) │
│ Extra: implementation, Odoo.sh hosting for custom │
│ code, maintenance of custom modules │
│ Included: version upgrades of the standard apps │
├─────────────────────────────────────────────────────────────┤
│ SAP BUSINESS ONE │
│ Licence: per user type (Professional / Limited), │
│ priced by quote from SAP or a partner │
│ Extra: set-up, configuration and integration, │
│ done yourself or by an SAP partner │
├─────────────────────────────────────────────────────────────┤
│ CUSTOM ERP (NestJS + PostgreSQL + React) │
│ Licence: none │
│ One-time: development, scaled to scope │
│ Ongoing: hosting + maintenance by your team/partner │
│ (No per-user fees, cost stays flat as team grows) │
└─────────────────────────────────────────────────────────────┘
Best fit for standard processes: Odoo
Closest fit for a genuinely unique workflow: Custom ERP
When the SAP name matters to customers or investors: SAP B1From my experience in freelance ERP consulting: before comparing platforms, map your 10 most critical business processes in detail. If 8 of those 10 map cleanly to Odoo's standard modules, Odoo wins. If your processes are genuinely unique — custom approval hierarchies, industry-specific calculations, integration with non-standard hardware or local government systems — that's when custom ERP justifies its cost.
Custom ERP: When Building Makes Sense
Custom ERP is not the right choice for most businesses. It requires internal IT capability or a trusted development partner, a realistic multi-year maintenance budget, and processes complex enough that standard platforms genuinely can't serve them. But when those conditions are met, custom ERP is transformative. You get exactly the workflow your team uses, no workarounds, no unused modules, and no annual license fees that grow with your headcount. In one of my freelance ERP consulting engagements, the custom ERP I built for a client used NestJS + PostgreSQL + React — a stack that's maintainable, well-documented, and deployable on any cloud. The system covers HR leave management, multi-level AP approvals, and automated AR with payment reminders. Total development cost was a fraction of what SAP B1 would have cost, and the system does exactly what the business needs.
The Hybrid Approach
Many Indonesian SMEs benefit most from a hybrid: use Odoo for commodity functions (accounting, inventory, CRM) and build custom modules for the two or three processes that are genuinely unique to their business. This captures Odoo's breadth while preserving the precision of custom development where it matters. The key is disciplined scoping: decide upfront which processes get standard Odoo and which get custom code, and resist scope creep in both directions.
# ERP Decision Scoring Framework
# Score +1 for each condition that applies to your business
odoo_score = sum([
processes_fit_standard_workflows, # your ops are relatively standard
no_dedicated_it_staff, # lean IT team
budget_under_50k_usd, # cost-sensitive
team_under_30_people, # small organization
])
sap_b1_score = sum([
multi_entity_structure, # group of companies
complex_compliance_requirements, # regulated industry
enterprise_customers_require_sap, # client expectation
manufacturing_with_bom, # production complexity
])
custom_erp_score = sum([
unique_approval_flows, # non-standard hierarchies
hardware_integration_needed, # scanners, printers, IoT
custom_calculations_core_to_biz, # differentiating logic
trusted_dev_partner_available, # partner you already trust
team_over_50_no_per_user_budget, # per-user fees hurt at scale
])
# Highest score wins
winner = max(
("Odoo", odoo_score),
("SAP B1", sap_b1_score),
("Custom ERP", custom_erp_score),
key=lambda x: x[1]
)My Honest Recommendation for Indonesian SMEs
Start with Odoo if you're a business with straightforward operations, a team of 10–100 people, and you can fit your processes into Odoo's standard workflows with minimal customization. Budget realistically: the subscription is only part of the cost, and implementation, data migration and training are billed separately. Choose custom ERP if your processes are genuinely unique, you have a trusted development partner, and you're willing to commit to multi-year maintenance. In my experience the payback shows up after two to three years, once you're not paying per-user license fees. Consider SAP Business One when you need multi-entity or multi-currency depth and the SAP name matters to your customers or investors; if you are genuinely enterprise-scale, the SAP conversation is S/4HANA Cloud rather than B1. For most Indonesian SMEs I work with, SAP B1 is more system than they need, at a premium price.
The most dangerous ERP decision is choosing a platform and then trying to customize it to match your current processes exactly. Every customization adds upgrade cost and technical debt. The question isn't 'can we make this platform work like our current system?' — it's 'can we adapt our processes to the platform's best practices?' If you can't adapt any processes, custom ERP is probably your answer. If you're unwilling to adapt any processes, every platform will disappoint you.
Implementation Partner Quality Matters More Than Platform Choice
I've seen Odoo implementations fail catastrophically and custom ERP implementations succeed beautifully — and vice versa. The platform is less important than the implementation partner and the internal project sponsor. Before committing to any platform, evaluate: Does the partner have 3+ live references in your industry? Can they show you running production systems, not demo environments? Do they have a realistic timeline and an explicit hypercare plan? A mediocre Odoo implementation will underperform a well-executed custom ERP every time.
Decision Framework: A Simple Score
Score your situation: +1 for each: your processes fit standard workflows, you have no IT staff, budget under $50,000, team under 30 people. That's Odoo territory. Score: +1 for each: multi-entity structure, complex compliance needs, enterprise customers, manufacturing with BOM. That's SAP B1 territory. Score: +1 for each: unique approval flows, hardware integration, custom calculations, trusted dev partner, team over 50 with no per-user license budget. That's custom ERP territory. The category with the highest score wins.