I

He doesn't know. Neither does she. That's the problem.

ERP vendors in Indonesia operate in an information vacuum they helped create. Nobody publishes honest 5-year cost models. SAP partners talk about "investment" rather than cost. Odoo resellers lead with per-user-month pricing and bury implementation fees in appendices. Custom software firms quote low to win the project and scope-creep their way to the real number.

This article is the one that shows the math. Not the sales deck math. The math you need before you sign a contract for a system your factory will run for the next decade.

If you want to run the numbers for your specific headcount and situation, our Enterprise ERP TCO Calculator does the 5-year model with your inputs. The article below explains what's behind those numbers and why they land where they do.

The Three Models, Plainly Stated

Every ERP decision for an Indonesian manufacturer eventually comes down to three paths.

SAP Business One. Enterprise pedigree, high license cost, significant implementation weight, global partner ecosystem. Right for complex multi-plant operations and subsidiaries of companies that run SAP globally. Expensive for everyone else.

Odoo Enterprise. Per-user subscription, lower headline price, substantial implementation cost that tends to get underscoped. Genuinely capable when implemented well. Costs more at scale than the initial pricing implies.

Custom-built ERP on owned infrastructure. No per-user fee, no annual license, implementation cost paid once. Requires a capable engineering partner. Almost never presented as an option because nobody in the typical ERP sales process sells it.

Each has a real use case. Each has a failure mode. The failure mode almost always comes from choosing a model that doesn't match the factory's size, complexity, and operational context.

SAP: What You're Actually Paying For

SAP Business One for a 15-user factory in Indonesia: Rp 1,740,000,000 upfront. That covers the license (roughly Rp 820,000,000) and the initial implementation (roughly Rp 920,000,000).

The modules at base tier: inventory, accounting, purchasing, sales. Functional for a distributor. A manufacturing company with MRP, production planning, quality control, and shop floor visibility needs modules beyond the base—each adding to the implementation scope and the license tier.

What the quote doesn't show:

Annual maintenance runs 18–22% of the license fee. On Rp 820,000,000, that's Rp 147,600,000 to Rp 180,400,000 every year. Over five years, Rp 738,000,000 to Rp 902,000,000 in maintenance alone—on top of the initial investment.

Indonesian tax compliance (e-Faktur, PPh, PPN) is not in the base international configuration. Some SAP partners include localisation in their implementation quote. Others scope it as a separate project after go-live, when you have less leverage. Ask before you sign.

Consultant scarcity. SAP-certified consultants in Indonesia bill at Rp 3,000,000 to Rp 6,000,000 per man-day. There aren't many of them relative to market demand. When your system needs a change—regulatory update, module addition, bug in a customisation—your partner's queue determines your timeline, not your urgency.

Imagine a Yazaki subsidiary in MM2100 evaluating SAP Business One for 180 production and warehouse staff. The initial quote is Rp 1.4 billion for 12 users. Two years in, the actual spend sits at Rp 2.3 billion: e-Faktur localisation, six additional user licenses for quality and logistics supervisors, one customisation project for Japanese parent company reporting, and a partner handoff when the original implementation firm restructured. Every line item had a legitimate reason. None appeared in year one's contract.

That's not a failure. That's how SAP implementations work in practice.

Odoo: The Per-User Math Nobody Does

Odoo Enterprise is marketed as the affordable alternative. The per-user pricing—around Rp 200,000 per user per month—sounds reasonable until you model it against your actual headcount and time horizon.

A factory with 50 ERP users:

• Odoo Enterprise subscription: Rp 200,000 × 50 × 12 = Rp 120,000,000 per year
• Over 5 years: Rp 600,000,000 in subscription fees alone
• Minimum implementation for a manufacturing operation: Rp 500,000,000
• Total 5-year cost: Rp 1,100,000,000

At 100 users, the 5-year subscription doubles to Rp 1,200,000,000. Total cost: Rp 1,700,000,000. At that point, Odoo Enterprise costs roughly the same as SAP Business One's upfront quote—without the SAP ecosystem depth, and with an annual fee that continues indefinitely.

The counter-intuitive fact that Odoo partners don't publish: for factories with 80+ daily ERP users, Odoo Enterprise's 5-year total cost of ownership regularly exceeds SAP Business One's.

Odoo Community exists as a free alternative. The catch: Community lacks proper HPP (Harga Pokok Produksi) costing functionality, has known MRP accuracy limitations, and runs into real constraints around multi-warehouse management. These aren't edge cases in manufacturing. They're core requirements. The factories that start on Community and later migrate to Enterprise pay the implementation cost twice—once for Community setup, once for the Enterprise migration.

Imagine a Sumitomo Electric wiring harness plant in Delta Silicon evaluating Odoo for 200 warehouse and production staff, of whom 70 need daily ERP access. The Odoo reseller's proposal leads with "Rp 200,000 per user per month." The 5-year model—done after the fact, not during the evaluation—shows Rp 1,840,000,000. The SAP quote they had declined as "too expensive" was Rp 1,740,000,000.

The decision was made on year-one pricing. The 5-year comparison was never built.

The Ownership Model: What Nobody Pitches

The third option doesn't have a branded name or a slick demo environment because the companies that build it don't have reseller networks distributing their sales materials to your inbox.

The model: pay for implementation once, own the system, run it on infrastructure you control—either a cloud server at a flat monthly cost or on-premise hardware at a lump sum. No per-user fee. No annual license that compounds with headcount growth. No vendor relationship that gives someone else leverage over your operating costs.

This works when:

Proven Workflows: The ERP module architecture is designed around proven manufacturing logic—the same workflows SAP spent decades refining: production orders, BOM management, shop floor control, cost accounting, multi-warehouse inventory. The difference is that instead of buying SAP's implementation of those workflows, you're building them to fit your factory's actual processes. The module concepts are proven. The implementation is yours.

Domain Expertise: The engineering partner has done this in Indonesian manufacturing before—knows e-Faktur, BPJS payroll, multi-currency IDR/JPY/USD, and has built production modules that factory staff will actually use, not modules that look correct in a demo.

Operational Buffer: The factory has enough operational stability to survive a 6–9 month implementation without the ERP being live. A factory in genuine operational crisis needs something faster, which usually means a packaged solution.

The 5-year math for this model, at 50 users in a Karawang manufacturing operation:

• Implementation (one-time): Rp 600,000,000
• Cloud infrastructure (~USD 1,000/month): Rp 900,000,000 over 5 years
• Annual support retainer: Security patches, regulatory updates (e-Faktur, BPJS), priority support: Rp 120,000,000/year = Rp 600,000,000 over 5 years
• Per-user fee: Rp 0
• Major version upgrade project: Not applicable — the retainer covers ongoing evolution; a ground-up re-platform only happens at year 7–10 if the business has fundamentally changed

5-Year Total: Rp 2,100,000,000

At 100 users, the total is the same. At 200 users, it's still the same. That's where the model changes — not at the headline number, but at the crossover point where Odoo's per-user subscription compounds past custom's flat cost. At 80–100 users, the 5-year totals are roughly equal. Beyond 100 users, custom wins by a growing margin every year.

The 5-Year TCO Comparison

All figures based on a 50-user Indonesian manufacturing factory, single plant, one legal entity. Amounts in IDR.

At 100 users:

The custom model's cost doesn't change with headcount. That's the structural difference. You can run your exact configurations on our Enterprise ERP TCO Calculator.

The Gotcha That Shows Up in Year 2

The number on the contract is not the number you'll spend. Every ERP path has a version of this problem.

SAP's version: annual maintenance compounds, consultant scarcity drives up change request costs, and the implementation scope always expands once the factory is actually using the system and realises what's missing.

Odoo's version: the per-user subscription grows with your headcount, Community-to-Enterprise migrations are expensive, and Indonesian regulatory compliance often requires ongoing paid customisation rather than native system updates.

The custom model's version: it requires an engineering relationship rather than a vendor relationship. If the firm that built your system is unavailable, you need someone who can read and maintain code they didn't write. That's manageable with good documentation and a well-structured codebase. It's a serious problem with poor ones.

The honest question to ask in every ERP evaluation: "What does year 3 cost look like?" Not the contract. Not the implementation. What are you realistically paying in year 3 for maintenance, regulatory updates, and the inevitable customisations that emerge once people are actually using the system every day?

Vendors who give you a specific, defensible answer to that question have done this before. Vendors who pivot back to the benefits of the platform probably haven't.

Choosing Based on What Your Factory Actually Is

The framework isn't complicated once the numbers are visible.

Single plant, under 200 employees, one legal entity, domestic focus: SAP is almost certainly oversized. Odoo Enterprise is worth evaluating on a 5-year model. A custom system on owned infrastructure is worth a serious conversation, particularly if headcount is expected to grow.

Single plant, 200–500 employees, subsidiary of a Japanese or Korean parent company: The parent company reporting requirement is the deciding factor. If HQ uses SAP and mandates integration, the cost premium of SAP may be justified by integration savings. If HQ reporting can be served by management summaries rather than system-level consolidation, the mandate and the fit question are separate conversations worth having.

Multi-plant, multi-entity, regional operations: SAP's strength is genuine here. Multi-plant MRP, intercompany transactions, consolidated group reporting—these work better within an integrated enterprise platform than across separately built systems. The premium reflects real capability.

Manufacturing subsidiary whose current ERP is a spreadsheet: Don't implement enterprise ERP first. Get the core operational layer working first—inventory, production, purchasing—on a system your team will actually use. Complexity added before trust is built creates a system that technically functions and practically gets bypassed.

A Note on Indonesian Market Context

The ERP market in Indonesia follows dynamics that differ from Singapore, Australia, or Japan.

SAP-certified partner density is lower relative to the implementation demand. Quality variance between partners is significant. The factory in KIIC that had a successful SAP implementation and the factory in Delta Silicon that spent 18 months past their go-live date may have used different partners running the same software.

Odoo has a larger local partner ecosystem, which means more options and more variance. The Odoo partner who specialises in trading companies and the Odoo partner who has done five manufacturing implementations in Cikarang are not equivalent, even though both will tell you they can handle your factory.

Indonesian regulatory change is ongoing. e-Faktur format has changed. BPJS contribution structures have changed. Minimum wage calculations change annually by province. Whatever ERP you implement needs a maintenance model that keeps pace with regulation, not just with software versions.

The factories that make ERP work—where the system is actually the source of operational truth rather than a parallel data entry system running alongside the real spreadsheets—share one characteristic: they chose a vendor based on evidence of prior manufacturing implementations in Indonesia, not on feature demos.

Feature demos are optimised for demo conditions. Reference visits to live factories with similar profiles are evidence of what the system actually does in production.

FAQ

Q: What is the total cost of ownership (TCO) ERP manufaktur Indonesia untuk 5 tahun?

A: Depends on the platform and user count. Based on the figures in this article: SAP Business One runs Rp 3,000,000,000–Rp 3,800,000,000 over five years for a 50-user factory. Odoo Enterprise runs Rp 1,400,000,000–Rp 1,700,000,000. A custom system on owned infrastructure runs Rp 870,000,000–Rp 1,500,000,000, with costs that don't scale with headcount.

Q: Is Odoo really cheaper than SAP for Indonesian factories?

A: In year one, almost always yes. Over five years, it depends on your user count. At 80+ users, Odoo Enterprise's 5-year subscription cost closes the gap with SAP significantly. At 100+ users with implementation included, the 5-year totals are often comparable. The per-user pricing that makes Odoo look affordable in the demo becomes its cost driver at manufacturing scale.

Q: What does ERP implementation typically cost in Indonesia, separate from the software license?

A: For a manufacturing operation with proper production module configuration, data migration, and user training: Rp 400,000,000 to Rp 900,000,000 is a realistic range depending on complexity and vendor. Quotes below Rp 300,000,000 for a manufacturing implementation deserve scrutiny—either the scope is minimal or the vendor is underestimating to win the contract.

Q: How long does ERP implementation take for a factory with 200 employees?

A: Six to twelve months for a phased implementation done well. Per Horváth & Partners 2025 data, implementations average 30% longer than initial estimates. A quote promising full go-live in three months for a factory of this size is either scoping a very limited initial phase or hasn't accounted for the real work. Plan for nine months. Budget for twelve.

Q: Can we implement ERP without disrupting production?

A: Yes, with a phased approach. The safest sequence: start with inventory and purchasing (no disruption to production floor), stabilise that layer, then add production planning and shop floor modules. Running old and new systems in parallel for 4–8 weeks during each phase adds cost but protects operations. Vendors who push for a single big-bang cutover on a manufacturing operation are optimised for their timeline, not your risk.

The cheapest ERP to buy is often the most expensive ERP to own. That sentence sounds like a truism until you're looking at a 5-year total that's three times the number on the contract you signed.

The math exists. It just requires someone to show it to you before you sign rather than after.