Commercial
Odoo pricing in Australia: Standard vs Custom, implementation, and budget traps
At a glance
- Type
- Commercial
- Use case
- Growing business ERP decision support
- Recommended action
- Use before vendor demos or partner final selection
Compare verified Australian-dollar Odoo subscription prices, Standard vs Custom scope, hosting and implementation with a three-year quote checklist.
Odoo pricing in Australia starts with the subscription, but the approval decision needs a complete delivery budget. Establish which users, entities, interfaces and workflows must work in phase one before comparing Standard with Custom.
Short answer: how much does Odoo cost in Australia?
On 6 November 2026, Odoo’s Australian-dollar pricing page displayed the following per-user monthly equivalents. Its introductory discount applies for 12 months to initial users ordered. The undiscounted display is a budgeting reference, not a guaranteed future renewal price.
| Plan and billing option | Introductory AUD / user / month | Undiscounted AUD / user / month displayed |
|---|---|---|
| Standard — yearly | 34.40 | 43.00 |
| Standard — monthly | 43.20 | 54.00 |
| Custom — yearly | 64.00 | 80.00 |
| Custom — monthly | 80.00 | 100.00 |
Check the live pricing link below and obtain a dated offer stating currency, billing commitment, invoice timing, discount eligibility and GST treatment. Do not assume a monthly equivalent means monthly payment. Subscription figures do not establish the cost of implementation.
What changes between Standard and Custom?
Both paid plans advertise all apps. Standard uses Odoo Online; Custom adds Studio, multi-company and external API access, with additional hosting choices. Odoo.sh hosting, implementation, in-app purchase credits and custom-code maintenance are excluded from the base subscription.
Plan entitlement and deployment are separate decisions. Odoo’s version 19 documentation says Odoo Online does not accept custom modules or Apps Store modules. Buying Custom while remaining on Online does not remove that hosting constraint. Require the proposed module list and hosting design before approving any development estimate.
Check which system initiates each integration
Odoo distinguishes external software calling into its API from Odoo calling an external service. Its pricing FAQ says supported calls initiated from Odoo, such as payment-provider or carrier connections, can be part of Standard. This does not establish that a particular third-party connector is supported or included.
The version 19 external API documentation reserves API data access for Custom plans. For each proposed interface, ask which system initiates the call, which connector or module is used, the target Odoo version, required entitlement, hosting compatibility and who supports failures. A label such as “Shopify integration” is not enough to price the design.
Choose a plan from the workflow evidence
Use this buyer decision table to test a proposed scope, rather than treating a lower subscription as the starting architecture.
| Proposed operating model | Evaluation path | Proof before approval |
|---|---|---|
| Standard workflows on managed Online hosting | Test Standard against the complete phase-one script | No essential requirement depends on an unavailable extension or interface |
| Several companies or Studio-led tailoring | Evaluate Custom and retain a separate hosting decision | Entity boundaries, permissions and the exact tailoring demonstrated |
| External application reading or updating Odoo records | Scope API entitlement and integration delivery together | Call direction, access rights, failed-message recovery and reconciliation |
| Essential custom or third-party module | Assess a compatible deployment and code-maintenance owner | Installation, upgrade testing, support responsibility and an exit path |
Re-scope before signing if the design depends on an untested connector or an unnamed developer. Compare another platform when the mandatory workflows require more ongoing development or administration than your team can own.
Build a three-year Odoo budget
Ask every delivery bidder to fill the same schedule. A blank or “to be confirmed” line is an unresolved estimate, not a zero cost.
| Budget line | Year-one quote evidence | Years two and three assumptions |
|---|---|---|
| Subscription and users | Plan, user roles, start dates, term, currency and discount scope | Undiscounted baseline, expansion rules and renewal terms |
| Hosting and environments | Deployment, capacity, test environments and accountable provider | Capacity growth, recovery arrangements and ongoing charges |
| Implementation | Named deliverables, delivery roles, milestones and exclusions | Optimisation work or deferred scope priced separately |
| Data migration | Datasets, cleansing owner, trial loads and reconciliation acceptance | Archive access and additional migration obligations |
| Interfaces and custom work | Connector licences, build scope, acceptance tests and code ownership | Monitoring, incident support, regression testing and maintenance |
| Training and internal effort | Process-owner time, testing, training and cutover cover | New-starter training, administration and business ownership |
| Usage and support | Consumption assumptions, support coverage and escalation | Usage growth, service changes and support renewal |
For a fixed user group, calculate each year’s software subtotal as quoted monthly-equivalent rate × eligible users × covered months. Split periods when users, plans or discounts change. Add the separately quoted delivery and operating lines; show GST consistently so the proposals remain comparable.
Model a base case and a change case using your own assumptions, such as another entity, a new warehouse interface or extra users. Keep uncertain work visible as a scoped allowance with an owner rather than relying on a generic implementation-cost range.
Australian delivery checks to put in the quote
- Ask your finance lead to sign off the target-version GST/BAS workflow, banking files and reconciliation evidence. Price any local configuration or external services explicitly.
- Identify where payroll, superannuation processing and eInvoicing exchange happen in the proposed design. Ask for a demonstration of the production service path and its costs rather than treating an app name as proof of readiness.
- Name the party responsible for Australian business-hours support, cutover assistance, urgent fixes and escalation to Odoo. Separate vendor support from partner work and internal administration.
- Record where data is hosted, who administers access, what can be exported and how you would recover or transition the service. Put the agreed responsibilities in the proposal.
These are scoping questions, not a certification of Australian localisation. Use the linked localisation guide to prepare the workshop, then verify the current target version and provider arrangements directly.
Questions for Odoo or your implementation partner
- Which named requirement determines the plan and hosting choice, and can you prove it with our end-to-end demo script?
- Which roles need full users, and are any restricted user types suitable? Document allowed actions and entitlement instead of assuming every employee has the same licence requirement.
- What happens to the price after the introductory period, when users are added, or when our scope changes? Put each assumption in the offer.
- What exactly does the implementation package deliver, who performs our data cleanup and testing, and how are extra services approved?
- Who maintains each module and connector after an upgrade, and which recurring tasks remain our responsibility?
Odoo’s Success Packs page describes consultant-led implementation services. Treat any pack as a proposal to match to your acceptance criteria, not evidence that every migration, interface or local workflow is covered. The version 19 upgrade documentation also makes custom-module compatibility a prerequisite for upgrading a customised database.
Use the linked implementation-cost worksheet and product comparisons to give Odoo, Business Central and NetSuite bidders the same scope. For help defining that scope before introductions, use the guidance enquiry below.
FAQ
- Are these prices in Australian dollars? Yes. The table records the AUD amounts served by Odoo’s pricing page on the review date. Check your own current offer for tax treatment, billing commitment and eligibility.
- Does Custom mean custom modules will run on Odoo Online? No. Plan entitlement does not remove the documented hosting restriction. Confirm a compatible deployment before buying or commissioning a module.
- Does every integration force a move to Custom? Identify the actual interface first. External API data access and supported calls initiated by Odoo are treated differently; a specific connector may also have separate requirements.
- How much is Odoo implementation in Australia? A defensible estimate needs agreed processes, data, interfaces, reports, training and acceptance criteria. Use a scoped proposal rather than extrapolating from user count.
- Is Odoo cheaper than Business Central or NetSuite? Compare the same three-year operating scope and delivery obligations. The subscription alone cannot answer that question.
Sources and review note
Reviewed by ERP Search editorial on 6 November 2026. Australian-dollar prices and plan boundaries were checked against Odoo’s live pricing page. Technical references are the version 19 Online, external API and upgrade documentation; confirm behaviour in your proposed version. Implementation scope was checked against the Success Packs page. Direct references are linked below.
The decision and budget tables are original buyer frameworks. Prices can change; no implementation-rate benchmark, guaranteed discount or automatic Australian compliance claim is implied.