What Makes Odoo Different#
Odoo isn't like traditional ERP vendors. Started in Belgium in 2005, it took an entirely different approach: build a modular, open-source platform where customers choose only the applications they need. This philosophy has attracted over 12 million users globally and created an ecosystem of 14,000+ applications.
If you're evaluating Odoo, you're likely a small to mid-market organisation (10-200 users) attracted by the promise of paying only for what you need, accessing source code, and avoiding vendor lock-in. Odoo's strength lies in modularity, pricing transparency, and flexibility. Its weakness is fragmentation—implementation quality varies enormously depending on your partner.
The ANZ reality: Odoo has a growing presence in New Zealand and Australia, but the partner ecosystem is less mature than for SAP, Oracle, or Microsoft. Implementation success depends heavily on partner selection—more so than with major vendors where methodologies are more standardised.
This guide provides an honest assessment of Odoo specifically for New Zealand and Australian organisations—covering the platform, editions, implementation realities, and when Odoo is the right choice.
---
The Odoo Philosophy#
Modular Architecture#
Odoo is built as a collection of integrated applications:
Core Applications: - Accounting - Inventory - Sales - Purchasing - CRM
Business Applications: - Project Management - Manufacturing - Warehouse Management - E-commerce - Point of Sale - Human Resources - Marketing - And 30+ more
Key principle: Install only what you need. Start with accounting, add inventory later, add manufacturing when required. Each application integrates seamlessly with others.
Open Source Foundation#
Odoo Community Edition is open source (LGPL licence). This means:
- Source code access: You can modify the code
- No vendor lock-in: You're not trapped with a single vendor
- Community contributions: 14,000+ third-party modules
- Self-hosting option: Run on your own infrastructure
The Enterprise Trade-off#
Odoo Enterprise Edition adds proprietary features:
- Full accounting functionality
- Advanced inventory management
- Studio (customisation tool)
- Mobile app access
- Email gateway
- Hosting included
Reality check: Most serious business implementations require Enterprise Edition. Community Edition is more suitable for evaluation and simple deployments.
---
Odoo Editions Comparison#
Community Edition#
Free to use, open source.
Included: - Basic CRM - Sales orders - Purchasing - Basic inventory - Project management - Website builder
Limitations: - No full accounting (only basic journal entries) - No bank integration - Limited reporting - No mobile apps - No Studio customisation tool
Enterprise Edition#
Subscription-based, per user pricing.
Adds to Community: - Full accounting (multi-currency, multi-company) - Bank integration - Advanced inventory - Manufacturing - Warehouse management - E-commerce - Point of Sale - HR management - Studio customisation - Mobile apps - Hosting included
Pricing (2024)#
| Users | Enterprise (Annual) | Notes |
|---|---|---|
| 1 | ~$560 | |
| 5 | ~$2,800 | |
| 10 | ~$5,600 | |
| 20 | ~$11,200 | |
| 50 | ~$28,000 |
Custom apps: Additional cost for custom modules.
Implementation: Typically $30-150K depending on scope.
---
The Module Ecosystem#
Core Business Modules#
Accounting: - Chart of accounts - Journal entries - Invoicing - Bank reconciliation - Multi-currency - Multi-company
Sales: - Quotations - Sales orders - Invoicing - Customer portal
Inventory: - Stock management - Warehouses - Moves and transfers - Valuation methods
Purchasing: - Purchase orders - Vendor management - Receptions
CRM: - Lead management - Pipeline - Activities
Advanced Modules#
Manufacturing: - Bills of materials - Work orders - Routing - Quality control
Warehouse Management: - Advanced picking - Barcode scanning - Put-away strategies
E-commerce: - Online store - Payment integration - Inventory sync
Point of Sale: - Retail POS - Restaurant POS - Hardware support
Project Management: - Tasks - Timesheets - Billing
Human Resources: - Employee management - Recruitment - Expenses - Time off
Third-Party Modules#
Through the Odoo Apps store: - Industry-specific modules - Integration modules - Enhanced functionality - Localisations
Caution: Third-party module quality varies significantly. Verify module maintenance and compatibility before relying on critical functionality.
---
NZ/AU-Specific Considerations#
Localisation#
GST/BAS: - NZ GST (15%) supported - AU GST (10%) supported - BAS reporting capability
Banking: - Bank statement import (major NZ/AU banks) - Direct credit file generation - Payment file formats
Payroll: - No native AU/NZ payroll - Integration with local payroll providers required - Common integrations: Xero Payroll, PayGlobal, FlexiTime
Partner Ecosystem#
Australia: - Growing partner network - Several certified partners - Implementation options available
New Zealand: - Limited partner presence - Most implementations from Australian partners - Self-implementation more common
Reality check: Partner quality varies more than with major vendors. Due diligence is essential.
Data Residency#
Odoo.sh (Odoo's cloud): - Servers in Europe - May not meet NZ/AU data residency requirements
Self-hosting: - Full control over data location - Requires technical capability - Can host on AWS/Azure in Australia
---
Implementation Approach#
Methodology#
Odoo implementations typically follow a phased approach:
Phase 1: Foundation (1-2 months) - Install core modules - Configure company data - Basic accounting setup - Chart of accounts
Phase 2: Operations (1-2 months) - Sales and purchasing - Inventory setup - Basic workflows
Phase 3: Enhancement (ongoing) - Additional modules - Customisations - Integrations - Reporting
Customisation Options#
Configuration: Built-in options for standard requirements.
Studio: Enterprise tool for creating custom fields, views, and workflows without coding.
Custom Modules: Python development for unique requirements.
Third-Party Modules: Pre-built solutions from the ecosystem.
Principle: Configure first, Studio second, custom development last.
Data Migration#
Approach: - Start clean when possible - Import essential master data - Historical data in separate system
Tools: - Built-in import functionality - CSV import - API-based import for complex scenarios
---
When Odoo Is the Right Choice#
Strong Fit#
- Small to mid-market (10-200 users)
- Budget-conscious organisations
- Companies wanting source code access
- Businesses with technical capability
- Modular requirements (need specific modules, not full ERP)
- Start-ups and growing businesses
Poor Fit#
- Complex manufacturing (consider SAP)
- Large enterprises (>500 users)
- Organisations needing robust ANZ payroll
- Companies without technical resources
- Businesses requiring extensive compliance reporting
Compared to Alternatives#
| Factor | Odoo | SAP B1 | NetSuite | MYOB |
|---|---|---|---|---|
| Price | Low | Medium | High | Low |
| Flexibility | High | Low | Medium | Low |
| ANZ support | Limited | Strong | Strong | Excellent |
| Technical requirement | High | Low | Low | Low |
| Scale ceiling | ~200 users | ~100 users | ~500 users | ~50 users |
---
Implementation Realities#
What Goes Wrong#
Partner quality: Implementation quality depends entirely on partner capability.
Customisation debt: Excessive customisations create upgrade challenges.
Module compatibility: Third-party modules may conflict or break during upgrades.
Payroll gap: No native AU/NZ payroll requires workarounds.
Support responsiveness: Community support is free; Enterprise support varies.
What Goes Right#
Rapid deployment: Core functionality live in weeks, not months.
Cost control: Pay only for what you need; no forced bundling.
Transparency: Know exactly what you're paying for.
Flexibility: Modify the system as your business evolves.
---
Monday Morning Action Plan#
This week:
- Evaluate Edition Needs: Do you need Enterprise features (accounting, bank integration)? Most businesses do—budget accordingly.
- Assess Technical Capability: Do you have Python/PostgreSQL skills in-house? If not, partner selection is critical.
- Check Payroll Requirements: Odoo doesn't have native AU/NZ payroll. Plan for integration or alternative.
- Research Partners: For ANZ, partner options are limited. Check Odoo's partner directory, get references, verify local experience.
- Start Small: Don't implement everything at once. Start with accounting, add modules as needed.
---
Conclusion: Odoo for Flexible, Budget-Conscious Businesses#
Odoo isn't for everyone. It requires more technical involvement than traditional ERP, the partner ecosystem is less mature in ANZ, and you'll need to solve payroll separately.
But for budget-conscious organisations that value flexibility, source code access, and modular pricing, Odoo offers a compelling alternative to traditional ERP. The key to success is: - Honest assessment of your technical capability - Careful partner selection - Phased implementation - Disciplined customisation - Realistic expectations about ANZ-specific requirements