Odoo vs custom ERP: an honest comparison

We build custom software, so it would be easy to write a page that concludes custom always wins. It does not, and pretending otherwise would be useless to you. This comparison uses Odoo's own published pricing and our own published bands, and it names the situations where Odoo is the better buy as plainly as the ones where it is not.

Comparison table

Odoo figures are the values shown on odoo.com/pricing at the time of checking and vary by country. KodDelta bands are published on our pricing page. Implementation, migration and localisation costs are separate in every option here.

The Standard-versus-Custom line

Most Odoo comparisons on the internet quote the Standard price and stop. That understates the real cost for a large share of buyers, because Odoo's own page puts three specific capabilities in the Custom plan and nowhere else: Odoo Studio, Multi-Company and External API.

Read that list again against your requirements. If you will connect Odoo to a machine, a warehouse scanner, an e-invoicing provider, a dealer portal or an existing accounting system, you need the External API — so you need Custom. If you run two legal entities, you need Custom. If you will reshape screens and add fields yourself, Studio is in Custom. In practice, most companies with a real integration requirement are buying the €17.90 plan, not the €11.90 one, and any comparison built on the lower number is comparing a product they would not buy.

Where configuration becomes debt

Configuration is not free just because it is not a licence line. Every field added, every screen reshaped and every automation written is something that has to survive the next version. That is true of any packaged platform, Odoo included, and it is the single most underestimated cost in ERP projects.

A rough working rule from real projects: up to about five significant deviations from standard behaviour, configuration is clearly the cheaper path. Between five and fifteen, it becomes a judgement call that depends on how central those deviations are to how you make money. Beyond fifteen, you are effectively building a bespoke system inside someone else's framework — with all the constraints of the framework and few of the benefits of ownership.

The honest test is not "can Odoo do this?" — with Studio and a partner, the answer is usually yes. The test is "how much of what makes us competitive lives outside the standard model, and what will it cost us at every upgrade?"

Which one, in which situation

The hybrid answer most companies end up with

In practice the interesting question is rarely "Odoo or custom". It is "where should the line be drawn?" The pattern that works most often looks like this:

• Packaged core. Accounting, statutory reporting, standard purchasing and inventory stay in the packaged product, where a vendor tracks legislation for you and does it far more cheaply than you could.
• Custom edge. The layer that touches your differentiator gets built: the shop-floor terminal screen, the dealer ordering portal, the maintenance scheduler, the pricing rule engine. These are the places where general-purpose software costs you every day in small frictions.
• A clean interface between them. This is why the API line in the plan comparison matters so much. On Odoo, that means the Custom plan; budget accordingly from the start rather than discovering it mid-project.

KodDelta's published bands for the custom edge: $3,000-6,000 for a single-process solution (2-4 weeks), $8,000-15,000 for a multi-module system (4-8 weeks), $20,000+ for an end-to-end platform, and $5,000-12,000 for a retrieval-augmented AI assistant over your documents. Maintenance is optional at 12-25% per year, there is no per-user fee, and source code is delivered under contract.

Test your own situation in three questions

1. How many deviations from standard do you actually have? Write them down as a list, not as a feeling. Under five, configure. Over fifteen, build. In between, weigh how central each one is to how you win business — that is the tie-breaker.
2. How many users in three years, and on which plan? Multiply your three-year headcount by €17.90 rather than €11.90 if you need API or multi-company, then by sixty months. Compare that single figure with a one-time band plus optional maintenance.
3. What would you refuse to give up? If the answer is a specific screen, rule or workflow that no vendor ships, that is your custom scope — and usually it is much smaller than a whole ERP. Building only that, on top of a packaged core, is normally the cheapest correct answer.

Bring those three answers and a decision that usually takes months takes about half an hour. If they point to Odoo, we will say so — we would rather be useful than win a project that should not exist.

Sources

• Odoo Pricing — plans, per-user rates, and what the Custom plan adds (odoo.com)
• Dynamics 365 Business Central Pricing (for context on per-user models) (microsoft.com)
• Acumatica Pricing (for context on non-seat-based models) (acumatica.com)
• KodDelta pricing and delivery bands
• KodDelta package vs custom comparison

Sources checked in August 2026. Vendors change prices without notice and regional rates differ; verify the linked page before deciding. Product names belong to their respective owners; KodDelta is not an Odoo partner or reseller.

Frequently asked questions

What does Odoo actually cost?

Odoo publishes three plans on its own pricing page: One App Free at €0, Standard at €11.90 per user per month billed yearly (€14.80 billed monthly), and Custom at €17.90 per user per month billed yearly (€22.40 monthly). Both paid plans include all apps. Implementation, data migration and localisation are separate and are not published as fixed prices.

What is the difference between Odoo Standard and Custom?

Odoo's own pricing page lists three additions in Custom: Odoo Studio, Multi-Company and External API. That makes Custom effectively mandatory for anyone integrating with another system or running more than one legal entity — and it raises the per-user price by roughly 50%. Compare at the plan you would actually buy.

Is Odoo open source, and does that mean I own it?

Odoo publishes a Community edition that is open source, alongside the paid Standard and Custom cloud plans. Running Community means you hold the code but also the operational burden: hosting, upgrades and maintenance are yours. The paid plans are subscriptions and do not transfer ownership of the platform to you.

When does a custom ERP beat Odoo on cost?

Usually at scale and at complexity. Per-user pricing compounds every year, so a large headcount changes the arithmetic; and heavy configuration creates work at every upgrade. KodDelta publishes one-time bands of $3,000-6,000, $8,000-15,000 and $20,000+ with no per-user fee and optional maintenance at 12-25%. Whether that wins depends entirely on your headcount and your five-year horizon.

When is Odoo clearly the better choice?

When you need many modules at once, your processes are close to standard, your headcount is modest, and you want to be live in weeks rather than months. All apps are included in one per-user price, which no bespoke build can match on breadth. We say so when that is the honest answer.

Can the two be combined?

Often the best answer is exactly that. Keep the packaged system for accounting, statutory reporting and standard inventory, and build only the layer that is genuinely specific to your business — the shop-floor screen, the dealer portal, the maintenance scheduler. This keeps compliance with a vendor who tracks legislation while the differentiating part is truly yours.