Commercial

Odoo pricing in Australia: Standard vs Custom, implementation, and budget traps

A practical Australian buyer guide to Odoo Standard vs Custom pricing, what is and is not included, and where implementation budgets usually expand.

Australian pricing-intent around ERP is not limited to Microsoft. Google Trends data for Australia over the last 12 months shows that “Odoo pricing” has enough live search volume to register alongside Business Central pricing and NetSuite pricing, which makes it a useful commercial topic for in-market buyers.

The easy mistake is to assume Odoo is simply the low-cost ERP option because the subscription headline looks straightforward. In practice, the real budget question is which plan is needed, whether custom modules or external API access are required, and how much implementation effort sits behind the software choice.

This guide is written for Australian buyers who want to compare Odoo against Business Central, NetSuite, or MYOB Acumatica with a cleaner commercial model before partner workshops or shortlist decisions.

What Odoo currently lists on its pricing page

• Odoo’s pricing page currently shows a Standard plan at US$16.90 per user per month on annual billing, discounted from US$21.10 for the initial 12 months.
• The same page currently shows a Custom plan at US$25.50 per user per month on annual billing, discounted from US$31.90 for the initial 12 months.
• Odoo states that both Standard and Custom include all apps for a single fee, while the free option is limited to one app with unlimited users on Odoo Online.
• Odoo also states that the Standard plan is Odoo Online only, while the Custom plan allows Odoo Online, Odoo.sh, or on-premise deployment and includes Odoo Studio, multi-company, and External API.

What is included and what is not

• Odoo says all plans include hosting, maintenance, upgrades, backups, and unlimited support by email. That is the attractive part of the commercial model and one reason the pricing headline gets attention.
• Odoo also spells out what is not included: Odoo.sh hosting for custom developments, implementation services, expert services, in-app purchase credits such as SMS and AI bill scanning, and maintenance of custom code.
• This matters because many Australian buyers compare Odoo’s subscription headline against other ERP products without separating software cost from delivery cost. That creates false confidence.
• The practical commercial question is not whether the list price looks low. It is whether the operating model can stay on Standard, or whether Custom, Odoo.sh, partner work, and support for bespoke logic will become unavoidable.

Standard vs Custom is the real budget fork

• Standard is the cleaner assumption when the business can stay close to Odoo Online, avoid custom code, and work within standard app behaviour.
• Custom becomes the realistic baseline if the business needs multi-company on one database, Odoo Studio, custom modules, partner-built extensions, or external systems making calls into Odoo through the API.
• Odoo explicitly says External API access is part of Custom, not Standard. For buyers planning ERP-to-WMS, ERP-to-eCommerce, reporting, payroll, or legacy-system integrations, that detail matters early.
• The same is true for hosting choice. If the project needs custom development and controlled deployment pipelines, Odoo.sh or on-premise design pushes the conversation beyond software subscription alone.

Implementation reality for Australian buyers

• Odoo says smaller companies under 50 employees often work directly with Odoo using Success Packs, while mid-size and large companies typically work with a partner offering local project management services.
• Odoo’s own project estimator says a successful implementation covers business analysis, configuration, training and coaching of key users, data import, and customisation of business flows. That is a good reminder that the software subscription is only one line item.
• For Australian buyers, the commercial risk usually sits in local process design, data migration, training, and customisation scope rather than in the entry-level user price itself.
• If a proposal looks inexpensive, check whether reporting, cutover support, localisation needs, integrations, warehouse mobility, and post-go-live ownership have been budgeted explicitly or quietly deferred.

The cost items buyers usually underestimate

• Plan drift. Teams often start on the assumption of Standard, then discover that integrations, multi-company structure, or modest customisation needs force a move to Custom.
• Odoo.sh and custom-code overhead. Odoo states Odoo.sh hosting is not included in the subscription price, and custom code maintenance is also outside the base plans.
• In-app usage credits. SMS, contact enrichment, lead generation, and AI bill or expense scanning are listed by Odoo as extra credits, not part of the standard subscription fee.
• Local delivery effort. Australian projects still need workshop time, training, testing, migration, and first-month support, even when the platform’s list pricing looks simple.

A practical way to budget Odoo in Australia

• Step 1: build the role and integration map before discussing plan choice. If the business expects external integrations, multi-company, or bespoke workflows, test Custom immediately instead of hoping Standard will stretch.
• Step 2: separate subscription, hosting, implementation, customisation, and support into different budget lines. This makes Odoo easier to compare fairly with Business Central and NetSuite.
• Step 3: use the first-year discount carefully. Odoo’s current pricing page shows introductory discounted pricing for initial users, so the steady-state run rate can be higher than the first quote suggests.
• Step 4: ask who owns local delivery. Odoo’s own guidance points mid-size buyers toward partners, so assess Australian partner capability, support model, and project governance before assuming the commercial model is settled.
• Step 5: pressure-test whether staying close to standard process is a real leadership choice or just a budgeting assumption. That decision usually determines whether Odoo remains commercially attractive after go-live.

When Odoo pricing changes the shortlist

• Keep Odoo high on the shortlist if the business wants broad application coverage, can stay close to standard, and the operating model does not depend on heavy external integration or bespoke logic.
• Re-test Odoo carefully if stakeholders already expect custom workflow, several third-party connections, or deeper warehouse and manufacturing tailoring. Those needs usually move the conversation from Standard pricing to Custom and partner-led delivery quickly.
• Compare against Business Central or NetSuite using the full three-year cost picture, not only the per-user subscription. Software cost, implementation risk, partner strength, and support discipline should be assessed together.

FAQ

• Is Odoo really one price for all apps? Odoo says both Standard and Custom include all apps for a single fee, but that does not mean implementation, Odoo.sh hosting, custom-code support, or in-app credits are included.
• Can Australian buyers stay on Standard long term? Some can, especially if they avoid custom code and external API requirements. Many growing businesses discover that integration or multi-company needs push them toward Custom.
• Is implementation included in the subscription? No. Odoo explicitly says implementation services and expert services are not included in the base plans.
• Is Odoo automatically cheaper than Business Central or NetSuite? Not always. The answer depends on plan choice, customisation, local partner effort, and the amount of integration and support the business really needs.