Odoo vs custom software: real costs, limits and the hybrid option

Pick Odoo when your processes look like those of a typical company in your industry: sales, purchasing, inventory, invoicing, accounting. It is a broad, open and relatively affordable suite, and building the same scope from scratch would cost more and take longer. Custom software wins when your core operations do not fit Odoo's standard flows, to the point that custom modules keep piling up. In between, the most common and often the healthiest answer is hybrid: Odoo for back-office management, a dedicated application for what makes you different, connected through Odoo's API.

This is not an anti-Odoo article. We recommend Odoo ourselves in some situations. Below are its public prices recorded on 6 November 2026, the costs that show up later, its real limits, and a decision grid that does not rely on invented thresholds.

Where Odoo shines

Odoo is a modular business suite from a Belgian publisher, with an open source core (official repository). Its strengths are genuine:

• breadth: CRM, sales, purchasing, inventory, manufacturing, accounting, invoicing, HR, website and e-commerce share one database;
• a low entry price compared with traditional ERPs, including a free single-app plan;
• Odoo Studio, for adding fields, screens and simple automations without code;
• an ecosystem of implementation partners, community modules and documentation;
• an API to connect it with other systems.

For a distributor, wholesaler or services firm whose processes follow common practice, a well-configured Odoo covers most needs. Our general guide to build vs buy software applies the same reasoning beyond ERPs.

What Odoo really costs

Licences

Recorded on Odoo's pricing page on 6 November 2026, as displayed for Europe in euros, per user per month. Odoo prices vary by country and currency, so check the page for your market.

Three details on the same page change the budget:

• the page shows higher crossed-out prices and states that the discount is valid for 12 months, for the initial users ordered: budget later years, and users added later, at full price;
• Studio and the external API require the Custom plan, and installing Studio moves your subscription onto it;
• "light users", limited to self-service features such as time off and expenses, are billed EUR 7.90.

Implementation

Licences do not include business analysis, configuration, data import or training. Odoo sells Success Packs of consultant hours, recorded on 6 November 2026:

The 15% discount applies to the first pack only. These packs target companies under 50 employees; above that, Odoo points you to implementation partners, who quote case by case. The same page notes that extra monthly charges apply for maintaining additional modules or lines of code.

Costs that appear later

• Odoo.sh hosting, not included in licences, once you run modules developed for you.
• Maintenance of custom code, which the pricing page lists as not included in any plan.
• Major version upgrades: each custom module must be adapted and retested. The deeper it changes standard behaviour, the more it costs.
• Licences that scale with headcount: every internal user adds a subscription, even for occasional use.

A quick illustration on licences alone, using the monthly-billing price as a cautious figure rather than the first-year discount: 20 users on the Custom plan cost 20 × EUR 44.90 = EUR 898 per month, EUR 10,776 per year and EUR 53,880 over five years, before implementation, hosting and maintenance. Run the same sum with your own headcount and quote.

Odoo's limits, without the caricature

Odoo does not lack features. Its limits show when your business drifts away from the model it is built around.

• Unusual workflows. Businesses organised by project site, traced production batch, regulatory case file or delivery round rarely follow the quote, order, delivery, invoice path. Each gap becomes a custom module, and modules accumulate.
• Customisation debt. Past a certain volume of custom code, every upgrade becomes a project, and some companies stay stuck on an old version.
• External users. Customers, subcontractors, field technicians or resellers often need a short, focused journey. Odoo's standard portal handles common cases (quotes, invoices, orders), less so a full business workflow.
• Task-specific ergonomics. A generic screen built for every industry costs clicks for an operator repeating the same task 200 times a day.
• Partner dependency. Poorly documented configuration and modules make it hard to change implementation partner, as with any software. Our vendor lock-in exit plan lists what to secure in the contract.

When custom software is the better choice

Custom development is justified when at least one of these is true:

• your core workflow is your competitive edge, and forcing it into a standard would flatten it;
• people spend more time working around the tool than using it: side spreadsheets, double entry, repurposed fields;
• the tool must serve people outside the company with a polished experience;
• you want to turn it into a product, for example software sold to other companies in your sector, which a configured ERP cannot become.

Our comparison of custom ERP vs off-the-shelf widens the analysis to other ERPs.

The hybrid route: Odoo plus a dedicated application

In many small and mid-sized companies, the best answer is neither all Odoo nor all custom. Keep Odoo for what it does well and nobody envies you for: accounting, purchasing, invoicing, inventory. Build next to it the application that carries your actual business: a customer portal, a field app for technicians, a quote configurator, a specialised planning tool.

The two talk through Odoo's external API, over JSON-RPC or XML-RPC, which lets a third-party application query and update Odoo data. Per the pricing page, that access requires the Custom plan. Design rules: one system of record per piece of data, logged exchanges, and automatic retries when a call fails.

Studio, an Odoo module or a separate app

The separate application's advantage is that it never touches Odoo's code. Odoo upgrades do not break it as long as the API calls it relies on stay stable, and you can change ERP one day without rewriting it.

A decision grid

Common mistakes

1. Comparing a licence price with a development quote. Compare five-year total cost: full-price licences, implementation, hosting, custom code maintenance and upgrades on one side; development, hosting, maintenance and new features on the other. Our guide to custom business application costs gives the development side.
2. Customising everything inside Odoo. A heavily modified ERP carries the cost of custom software and the constraints of a package.
3. Rebuilding everything. Rewriting accounting or inventory almost never gives you an edge.
4. Forgetting who owns what. For an Odoo module as for a separate app, rights over code, data and documentation are defined case by case in the contract.
5. Deciding on a generic demo. An ERP shown on sample data says nothing about your hardest case.

Where to start

1. List your processes and mark those that follow industry practice and those that are yours alone.
2. Put a number on today's workarounds: spreadsheets, double entry, time lost.
3. Get Odoo quoted for the standard part, at full licence price.
4. See the specific part before you build it.

For that specific part, we build a free visual prototype, presented over video within 5 working days: you see the application that complements, or replaces, Odoo on your real case before committing. Our guide to prototype, MVP and proof of concept explains what that first step covers.