Odoo Support in Australia: What Odoo Includes, What a Partner Adds, and What It Costs

The first support question we hear from Australian businesses evaluating Odoo is who they will call when something breaks. It is the wrong question. The useful one is what the call is allowed to be about, because an Odoo Enterprise subscription includes more than most buyers expect and excludes the exact things most businesses end up needing help with. This post sets out how Odoo support in Australia works: what the subscription covers, what a partner adds, and where the costs sit, using Odoo’s own subscription agreement as the reference.

What your Odoo Enterprise subscription already includes

Every Odoo Enterprise subscription is governed by the Odoo Enterprise Subscription Agreement, and the current version (12, dated December 2025) spells out the support services in plain terms.

• Unlimited support tickets at no charge. You can raise as many tickets as you like for bugs and for guidance on using standard features. There is no ticket cap and no per-incident fee.
• Bug fixing with a response commitment. Odoo SA commits to start handling a reported bug within two business days, and to fix it in every more recent covered version once it is resolved. A bug means a complete stop, an error traceback or a security breach that is not caused by your own installation or configuration.
• Coverage for the three most recent major versions. Odoo releases one major version a year, so a database usually has about three years of cover before an upgrade becomes a condition of support. Our Odoo version support guide has the dates.
• Security updates. On Odoo’s cloud platforms, security fixes are applied for you. Self-hosted customers receive a security advisory at least two weeks before public disclosure.
• The upgrade service. Converting your database to a newer covered version through Odoo’s upgrade platform is included for every Enterprise subscriber, partner or not.

Two things people get wrong. First, all of this applies whether you work with Odoo SA directly or through a partner; section 4.6 of the agreement gives you the choice. Second, Odoo is closer than it sounds. Tickets go through the web form and phone numbers on odoo.com/help, and the same page lists Odoo’s Australian office at Varsity Lakes on the Gold Coast for sales and services.

What Odoo support does not cover

The scope of Odoo support is bugs and standard features, and the boundary is firm.

• Customisations. Any custom code, and any change made in Odoo Studio, is an Extra Module. Odoo SA supports and upgrades an Extra Module only if you pay a maintenance fee to make it a Covered Extra Module, charged monthly per 100 lines of code. Uncovered modules are yours to maintain.
• Development questions. Guidance on how to build or change something sits outside the ticket scope and may need a separate service agreement.
• Configuration mistakes. A failure caused by how the system was installed or set up is not a bug by definition. A wrong tax mapping that produces a wrong Business Activity Statement (BAS) figure is a configuration issue, not a defect.
• Compliance. Section 7.2 states that Odoo SA does not warrant the software complies with any local law. Odoo does treat a country feature that no longer meets legal accounting requirements as a bug, so the Australian localisation gets maintained, but the accuracy of what you lodge with the Australian Taxation Office is on you.
• Extra modules off Odoo’s cloud. If you work with Odoo SA directly, services for Covered Extra Modules are only provided when your database is hosted on Odoo Online or Odoo.sh. Self-hosted with customisations means a partner is your only route to that coverage, which is one reason the hosting decision matters more than people expect.

Most Australian businesses running Odoo carry at least some customisation and have a finance team lodging BAS and Single Touch Payroll (STP) reports every cycle. That is the gap partner support exists to fill.

What an Odoo support partner adds

Under the agreement, a partner can be your main point of contact for bug fixes, support and upgrades. Odoo SA then subcontracts the Covered Extra Module work to the partner, and the partner can escalate standard-feature issues to Odoo SA for second-level assistance on your behalf. Partners also have a dedicated account manager at Odoo and can report bugs directly for their clients, and you can check any partner’s tier on Odoo’s partner directory.

What that means in practice:

• Someone who knows your setup. A partner ticket starts from your configuration, your modules and your history, rather than from a blank description of the problem.
• Local hours and local context. Odoo’s ticket availability is subject to local opening hours. A Brisbane partner answers in Australian Eastern time and knows what the last week of a BAS quarter feels like.
• One channel for standard and custom. You raise it with the partner. The partner works out whether it is a standard bug for Odoo SA, a fault in custom code, or a configuration issue, and handles all three.
• Freedom to change. The agreement lets you switch partners, or go direct, with 30 days’ written notice, so a partner has to keep earning the role.

A partner is not compulsory. A business on Odoo Online with standard apps and a capable in-house administrator can work with Odoo SA directly and do fine. Our post on consultants versus certified partners goes deeper on when the difference matters.

Odoo support in Australia: what it costs and who you pay

The Odoo SA side is simple. Support, bug fixing, security updates and upgrades are included in the per-user subscription. The extras are the Covered Extra Module fee per 100 lines of code, set in writing in your contract, and a 25% annual surcharge if you stay on a version older than the three covered ones.

Partner support is priced by the partner, and in Australia it usually takes one of three shapes: a prepaid bank of hours drawn down as needed, a monthly retainer with defined response times, or pay-as-you-go at an hourly rate. Our implementation packages page sets out how we structure ours.

It is worth budgeting for. Capterra’s Australian research found fewer than one in three Australian businesses successfully adopt new software, and in our experience the failures happen in the months after go-live, when questions go unanswered and workarounds set in. With 36% of Australian mid-sized businesses looking to upgrade their ERP, a lot of teams are about to find out how much post-go-live support matters.

Direct, partner, or both: which Odoo support setup fits

Go direct if you are on Odoo Online, run standard apps with no custom modules, and have someone in-house who is comfortable reading the documentation and raising tickets. Go partner-led if you carry customisations, host on Odoo.sh or your own servers, or want your finance team to have one number to ring in BAS week. Most Australian businesses we support land on the combination: partner as the main contact, Odoo SA behind them for platform bugs. Our Odoo services page explains how we run it.

“The subscription buys you Odoo’s engineers for bugs in standard Odoo. It does not buy you anyone who knows why your BAS moved by the amount of last week’s stock adjustment. That gap is what a support partner is for, and it’s why we ask about support before we ask about modules.”

Josh Craig, Director, Auboros

Working out Odoo support for your Australian business?

We are a Brisbane-based Odoo Silver Partner supporting businesses across Queensland and Australia, and support arrangements are something we scope before implementation rather than after. If you want to know whether you need a partner at all, book a free consultation. The conversation is free, and the retainer decision can wait until you have seen what your go-live actually needs.