Odoo ships in two editions. Community is the free, open-source core — the modules that run sales, inventory, manufacturing and projects. Enterprise is the paid subscription that adds Studio, the modern web client, mobile apps, advanced accounting, country-specific localisations, official upgrades and support. For most Australian businesses, the choice comes down to what the localised modules — Single Touch Payroll, Peppol e-invoicing and the AU accounting reports — live behind. They sit behind the Enterprise licence.
What each edition actually is
Odoo is one codebase distributed in two versions. The split isn’t about features at the surface — most Community users would not notice a missing CRM or stock module — it’s about the parts of the system that touch money, payroll and compliance.
Community: the open-source core
Community is free under LGPL v3. You can download it, host it anywhere, modify the source. It includes Sales, CRM, Inventory, Purchase, Manufacturing, Project, Timesheets, basic Accounting (entries and invoices, not full reporting), Website builder and eCommerce. It does not include Studio, the iOS/Android apps, the consolidated financial reports, document management, or any of the country-specific localisation modules that Odoo publishes.
Enterprise: the paid subscription
Enterprise is currently around $34 AUD per user per month for the full suite, billed annually, with discounts at higher user counts. The price includes the modern Owl-based web interface, the mobile apps, Studio (no-code customisation), advanced accounting reports, the IoT box for shop-floor and POS hardware, and — most relevant for us — the Australian payroll, Peppol and BAS-aligned reporting modules. Bug fixes and version upgrades are part of the subscription.
Hosting is a separate decision
Odoo Online (SaaS), Odoo.sh (managed cloud) and self-hosted are deployment choices that sit on top of the edition choice. Online is Enterprise-only. Odoo.sh is Enterprise-only. Community must be self-hosted — either on your own infrastructure or with a hosting partner. We see most Australian SMEs land on Odoo.sh in a Sydney region for the combination of managed backups, staging environments and proximity to local data.
Australian compliance: GST, BAS, STP and Peppol coverage by edition
This is the section that decides the call for almost every Australian business. The Australian localisation in Odoo isn’t a single module — it’s a stack — and the pieces are split across editions in ways that aren’t obvious until you go looking.
GST calculation, the AU chart of accounts, and ABN handling exist in Community via the l10n_au localisation module. BAS report generation in the format the ATO expects (Type A, C, D fields with the right GST clearing accounts) is Enterprise. Single Touch Payroll Phase 2 reporting — the actual submission to the ATO — is Enterprise. Peppol BIS Billing 3.0 e-invoicing through the Australian Peppol network is Enterprise. The Fair Work-aligned leave management and award rate handling sits in the Enterprise payroll module.
You can run a workable Community install for a business that lodges BAS quarterly through a bookkeeper exporting to Xero or a spreadsheet — we’ve seen this pattern in trades businesses with a single bookkeeper. The moment you want Odoo to be the system of record for payroll or to send e-invoices to government and large-enterprise customers, Enterprise becomes the answer. The Australian compliance picture we configure from day one is built around the Enterprise modules.
Pricing and total cost of ownership in AUD
Headline pricing is easy. Real total cost of ownership takes a minute longer.
Enterprise licence costs
Enterprise list pricing in AUD as of mid-2026: roughly $34 per user per month for the full app suite, billed annually. A 15-user business pays around $6,100 per year in licences. A 50-user business pays around $20,400. Volume and partner discounts apply at higher tiers. There are no per-module charges — one user gets every Enterprise app.
Community licence costs
Zero. You pay nothing to Odoo for the software. You will pay for hosting, backups, monitoring, security patching and any developer time spent integrating modules or maintaining the install. For a Sydney-hosted Community deployment, expect $200 to $600 a month in infrastructure and managed-hosting costs alone before any internal or partner labour.
Total cost over three years
A realistic three-year TCO for a 20-user Australian business on Enterprise (licences, Odoo.sh hosting, implementation, two minor upgrades): $90,000 to $130,000. The same 20-user business on Community (self-hosted, with a partner handling upgrades, custom STP integration via a third-party payroll, Peppol via an external service): $70,000 to $110,000. The Community saving is real but smaller than people expect once you price in the work it pushes back onto you. We cover the full breakdown in our Odoo licence costs in Australia article.
Feature differences between Community and Enterprise
The feature list is long; the ones that matter for Australian SMEs are short.
Enterprise-only features that Australian businesses ask about most: Studio (no-code form, report and workflow editing), the iOS and Android mobile apps (field service crews live in these), Documents (OCR-driven document workflow), Sign (electronic signatures), Marketing Automation, Subscriptions (recurring billing — crucial for service businesses), Helpdesk, Planning (resource scheduling), the consolidated financial reports, Peppol, and the full STP Phase 2 payroll module.
Community covers the operational core — selling, purchasing, making, shipping, invoicing — and that’s it. For a single-warehouse trading business that uses Xero or MYOB for accounting and a third-party tool for payroll, Community can carry the operational load. For a business that wants Odoo to be the single source of truth, Enterprise is the answer.
Hidden risks of running Community in Australia
This is the conversation we have most often with prospects who arrive already running Community. The risks are not catastrophic — they are slow, compounding and expensive to unwind.
The first risk is payroll. Community has no STP Phase 2 submission. Businesses on Community run payroll on Employment Hero, KeyPay or external bookkeepers and then journal the result back to Odoo. That works, but it creates a reconciliation surface and a second source of truth for employee data. When Fair Work award rates change or super rates step up — as they did to 12% on 1 July 2025 — you are updating two systems and hoping they stay in sync.
The second risk is Peppol. The ATO’s push for Peppol adoption across the public sector and large enterprise procurement means more of your invoices to government departments and tier-1 customers will be expected via Peppol within the next two to three years. Community cannot send or receive Peppol natively. You need a third-party gateway and a developer to wire it up — or you swap to Enterprise. We cover the Peppol e-invoicing in Odoo detail separately.
The third risk is the audit trail. Community lacks some of the period-locking, approval and IRN-style invoice numbering controls that auditors and the ATO expect on a system of record. For an audited business or one heading toward investor due diligence, that gap is visible in the data room.
Australian integrations: what each edition supports
Australian SMEs don’t just need GST and STP — they need the system to talk to the rest of the local stack. The integration story differs meaningfully between editions.
Enterprise ships with — or has officially maintained connectors for — ANZ, NAB, CBA and Westpac bank feeds via Plaid and Yodlee, ABA file generation for batch payment uploads, the Employment Hero and KeyPay connectors for payroll handoff, Australia Post and StarTrack shipping labels, and the Starshipit multi-carrier integration that most omnichannel Australian retailers use. The Peppol integration plugs straight into the ATO Peppol directory lookup.
Community has the Odoo Community App Store with hundreds of third-party modules, some of which cover the same ground — community-maintained bank statement importers, ABA generators, Australia Post connectors. The quality is mixed. Some are excellent and free; some are abandoned. None come with a service-level guarantee. We worked with a Perth wholesaler last year running 14 users on Community who had pieced together five separate third-party modules for AU localisation; the upgrade from Odoo 16 to 17 broke three of them and ate six weeks of developer time. The moment they swapped to Enterprise the maintenance overhead collapsed.
Self-hosted Community vs Odoo.sh Enterprise: the operating reality
The hosting and operations picture is where the editions diverge most in daily life.
Community route
You run PostgreSQL, Python and the Odoo application on a server you control — typically AWS Sydney, Vultr, DigitalOcean or an on-premise box. You’re responsible for daily backups, point-in-time recovery, OS patching, Python and PostgreSQL upgrades, SSL certificates, security hardening and monitoring. Version upgrades — Odoo releases yearly — require migrating the database with the open-source upgrade scripts and remediating any custom modules. None of this is hard; all of it is yours.
Enterprise route
Odoo.sh gives you managed PostgreSQL, automatic daily backups with 14-day retention, staging environments per Git branch, one-click promotion to production, an upgrade pipeline, monitoring dashboards and Odoo’s own infrastructure team behind it. You provide a GitHub repository for any custom modules; Odoo.sh runs everything else. For most 10-to-100-user Australian businesses, the Odoo.sh cost — typically $150 to $600 AUD a month depending on workers — is the cheapest way to get production-grade ERP hosting in this country.
What we recommend
Unless you have an in-house DevOps capability and a strong reason to self-host (data sovereignty requirements, very high transaction volumes, integration into existing infrastructure), Enterprise on Odoo.sh is the default. Community self-hosted is for businesses with the technical depth to own the operating burden — and the willingness to keep owning it.
Upgrading from Community to Enterprise
The mechanical upgrade is straightforward. The cleanup work around it isn’t.
The licence side is simple: buy an Enterprise subscription, activate the licence key against your existing database. Odoo’s Enterprise modules install on top of the Community install; your data stays in place. The web interface flips from the older client to the Owl-based Enterprise one, and Studio, Peppol, STP and the Enterprise accounting reports become available.
The cleanup is where most projects spend the time. Any custom modules built against the Community APIs need to be reviewed — most work, some need adjustments where Enterprise has overlapping models. Any third-party Community apps that have Enterprise equivalents should be retired before they fight the official module. Custom reports built against the older reporting engine are usually rewritten against the Enterprise accounting reports.
A typical Community-to-Enterprise upgrade for a 20-user Australian business takes us four to eight weeks: a fortnight of audit and module review, two to four weeks of remediation and testing, then a weekend cutover. We sequence it so BAS lodgement and payroll cycles aren’t disrupted, which usually means a cutover the weekend after a BAS quarter closes. The full picture sits in our Odoo implementation timeline in Australia breakdown.
When each edition makes sense in Australia
Community makes sense when
You are a small operational business — under 10 users — running Xero or MYOB for accounting and Employment Hero or KeyPay for payroll, and you want Odoo for the operational side only (sales, inventory, manufacturing). You have technical staff comfortable managing PostgreSQL and Python. You don’t sell to government or tier-1 customers who will demand Peppol soon. You’re comfortable owning the upgrade cycle.
Enterprise makes sense when
You want Odoo to be the single source of truth — accounting, payroll, operations. You sell to government, large enterprise or healthcare and need Peppol. You need Studio to model your business processes without writing Python. You have more than 15 users and the per-user cost is dwarfed by the operational overhead Community would push back onto you. You want Odoo’s official upgrade pipeline and support behind the platform. This is the call we recommend for the majority of the SMEs and mid-market businesses we work with.
The right answer is rarely binary, but the gravity for Australian businesses pulls toward Enterprise once compliance and payroll enter the picture. If you’d like a straight read on which edition fits your business — and what the AUD numbers look like across three years — start a conversation with us and we’ll map it out against our implementation method.
Frequently asked.
What is the difference between Odoo Community and Odoo enterprise?
Community is the free, open-source edition with the core ERP modules. Enterprise is the paid edition that adds Studio, the modern web client, mobile apps, accounting reports, Peppol e-invoicing, Single Touch Payroll for Australia, official upgrades and Odoo support. In Australia, Enterprise is what most businesses need because the localised payroll and Peppol modules ship with it.
Can I use Odoo in Australia?
Yes. Odoo runs in Australia with full GST, BAS, STP Phase 2 and Peppol e-invoicing support on the Enterprise edition. Community can be used too, but the Australian payroll and Peppol modules sit behind the Enterprise licence. Most Australian SMEs we work with run Enterprise hosted on Odoo.sh or a Sydney AWS region.
What are the two types of Odoo?
Odoo ships in two editions: Community and Enterprise. Community is open-source and free to self-host. Enterprise is a paid subscription that adds Studio, official mobile apps, advanced accounting and country-specific modules including Australian payroll and Peppol. Hosting options are separate: Odoo Online, Odoo.sh, or self-hosted on your own infrastructure.
Why are businesses switching to Odoo ERP?
Australian businesses move to Odoo to replace a stack of disconnected tools — Xero plus a CRM plus a warehouse system plus spreadsheets — with one integrated platform. The economics are the second driver: a 30-user mid-market business pays less in Odoo Enterprise licences than the same business pays for NetSuite or Business Central.
What is the difference between community edition and enterprise edition?
Community gives you the open-source core: CRM, Sales, Inventory, Manufacturing, Purchase, Project and basic accounting. Enterprise adds Studio for no-code customisation, the modern web interface, mobile apps, advanced reporting, country-specific localisations including Australian payroll and Peppol e-invoicing, plus official upgrades and Odoo's own support.
How to upgrade Odoo community to enterprise?
Buy an Enterprise subscription from Odoo, then activate the licence key against your existing database. The upgrade installs the Enterprise modules on top of your Community install — your data stays in place. Custom modules need to be reviewed for compatibility, and any third-party Community apps that have Enterprise equivalents should be swapped before go-live.