Implementing Odoo: The ANZ Reality#
Odoo implementations in New Zealand and Australia face unique challenges. The partner ecosystem is less mature than for major vendors, local support options are limited, and specific requirements like AU/NZ payroll require workarounds.
This guide provides practical implementation guidance specifically for ANZ organisations.
---
Implementation Methodology#
Phased Approach#
Unlike traditional ERP implementations that try to do everything at once, Odoo implementations work best with a phased approach:
Phase 1: Foundation (4-8 weeks) - Odoo installation and configuration - Company and user setup - Chart of accounts configuration - Basic master data import - Core accounting setup
Phase 2: Operations (4-8 weeks) - Sales and CRM configuration - Purchasing setup - Basic inventory - Integration testing - User training
Phase 3: Enhancement (4-12 weeks) - Advanced modules (manufacturing, warehouse) - Integrations (payroll, banking) - Reporting and dashboards - Mobile setup - Go-live support
Why Phased Works Better#
- Lower risk: Problems are contained to each phase
- Faster value: Start using core functionality quickly
- Learning curve: Users adapt gradually
- Budget control: Pause between phases if needed
---
Module Selection#
Core Modules (Most Businesses)#
Accounting: - Required for any business - Foundation for all other modules
Sales: - Customer management - Quotations and orders - Invoicing
Purchasing: - Vendor management - Purchase orders - Receiving
Inventory: - Stock management - Warehouses - Valuation
Optional Modules (Based on Need)#
CRM: If you need lead management and pipeline tracking.
Project Management: If you bill by project or track tasks.
Manufacturing: If you produce goods.
Warehouse Management: If you have complex warehousing needs.
E-commerce: If you sell online.
Point of Sale: If you have retail operations.
HR: If you need employee management (note: not full payroll for AU/NZ).
Module Selection Principles#
- Start minimal: Implement only essential modules first
- Add progressively: Add modules when you're ready to use them
- Avoid complexity: Don't enable features you won't use
- Integration check: Verify new modules work with existing setup
---
Configuration vs Customisation#
Configuration#
Using built-in options to match your requirements:
Examples: - Chart of accounts structure - Payment terms - Product categories - User permissions - Email templates - Report layouts
Principle: Always prefer configuration over customisation.
Studio Customisation#
Odoo Enterprise's Studio tool for no-code customisation:
What you can do: - Add custom fields - Create custom views - Modify menus - Build custom reports - Create automated actions
When to use: When configuration isn't enough, but development isn't justified.
Custom Development#
Python module development for unique requirements:
When needed: - Unique business processes - Complex integrations - Industry-specific functionality
Risks: - Upgrade compatibility - Maintenance burden - Partner dependency
Principle: Minimise custom development. It creates technical debt.
---
Data Migration#
What to Migrate#
Always migrate: - Chart of accounts - Customers - Vendors - Products - Opening balances
Consider carefully: - Historical transactions - Old orders and invoices - Historical stock movements
Generally don't migrate: - More than 2 years of history - Inactive customers/products - Deleted records
Migration Approach#
Manual entry: For small data volumes (<500 records per type)
CSV import: For medium volumes (500-5000 records)
API import: For large volumes or complex data
Data Cleansing#
Before migration: 1. Deduplicate: Remove duplicate customers, vendors, products 2. Standardise: Consistent naming conventions 3. Validate: Check for missing required fields 4. Archive: Move inactive data to archive
---
Integration Requirements#
Payroll (Critical for AU/NZ)#
Challenge: Odoo doesn't have native AU/NZ payroll.
Solutions: - Xero Payroll integration: Export timesheets to Xero, import payroll entries - PayGlobal integration: For larger organisations - Manual journal entries: For simple scenarios - Third-party connectors: Check Odoo Apps store
Recommendation: Evaluate payroll integration early in the project.
Banking#
Bank feeds: Import statements from major banks.
Payment files: Generate direct credit files for NZ/AU banks.
Setup: - Configure bank accounts in Odoo - Set up bank journal - Test statement import - Configure payment file format
Other Integrations#
E-commerce: If using Shopify, WooCommerce, or similar.
CRM: If using separate CRM system.
Shipping: For carrier integration.
Document management: For automated document storage.
---
Partner Selection#
Why Partner Matters More for Odoo#
Unlike SAP or Oracle where implementation methodology is standardised, Odoo implementations vary enormously based on partner capability. The open nature of the platform means partners can—and do—implement very differently.
Partner Evaluation Criteria#
Odoo certification: - Official partner status - Certification level (Ready, Silver, Gold)
ANZ presence: - Local office or team - ANZ client references - Time zone coverage
Technical capability: - Python development skills - Integration experience - Module development track record
Industry experience: - Clients in your industry - Understanding of your requirements
References: - At least 3 ANZ references - Similar size and complexity - Ask about problems encountered
Red Flags#
- No ANZ references
- Vague about team members
- Unrealistic timeline or cost estimates
- Reluctance to discuss challenges
- Pushing excessive customisation
---
ANZ-Specific Implementation Checklist#
Before Starting#
- [ ] Verify partner has ANZ experience
- [ ] Confirm payroll integration approach
- [ ] Check banking format support
- [ ] Understand data residency requirements
- [ ] Confirm post-go-live support arrangements
During Implementation#
- [ ] Test GST calculations early
- [ ] Verify bank statement import works
- [ ] Test payment file generation
- [ ] Validate reporting meets requirements
- [ ] Train users in time zones that work for you
Go-Live#
- [ ] Ensure support coverage during business hours
- [ ] Have escalation path documented
- [ ] Confirm partner availability for first 2-4 weeks
- [ ] Plan for parallel running if needed
---
Timeline Expectations#
Realistic Timelines (ANZ)#
Simple implementation (Accounting + Sales + Purchasing): - Timeline: 2-3 months - Cost: $30-60K
Medium implementation (Add Inventory, CRM): - Timeline: 4-6 months - Cost: $60-120K
Complex implementation (Manufacturing, Warehouse, integrations): - Timeline: 6-12 months - Cost: $120-250K
Timeline Accelerators#
- Clean master data ready before starting
- Clear requirements documented
- Committed internal team
- Minimal customisation
- Experienced partner
Timeline Risks#
- Poor data quality in legacy systems
- Unclear or changing requirements
- Payroll integration complexity
- Partner resource constraints
- User adoption resistance
---
Common Implementation Failures#
Over-Customisation#
Building too many custom modules creates upgrade challenges and maintenance burden.
Prevention: Challenge every customisation request. Can it be done with configuration?
Poor Data Migration#
Dirty data from legacy systems causes ongoing problems.
Prevention: Invest in data cleansing before migration.
Inadequate Training#
Users don't adopt the system properly.
Prevention: Plan comprehensive training, not just a half-day session.
Ignoring Payroll#
Leaving payroll integration to the last minute.
Prevention: Address payroll early in the project.
Wrong Partner#
Partner lacks capability or availability.
Prevention: Thorough partner evaluation with reference checks.
---
Monday Morning Action Plan#
- Document Requirements: List the functionality you actually need. Not everything—what's essential?
- Research Partners: Check Odoo's partner directory for ANZ partners. Get their client references.
- Address Payroll: Decide how you'll handle AU/NZ payroll before starting the project.
- Assess Data Quality: How clean is your master data? Plan for cleansing.
- Plan Phased Approach: Don't try to implement everything at once. Start with foundation, add modules progressively.
---
Conclusion: Success Requires Partner Rigor#
Odoo implementation in ANZ is more dependent on partner quality than implementations with major vendors. The platform's flexibility is both a strength and a risk—without experienced guidance, it's easy to over-customise, under-train, and create problems that will surface later.
Success requires: - Careful partner selection with ANZ references - Phased implementation approach - Early attention to payroll integration - Discipline around customisation - Investment in data quality and training - Realistic timeline and budget expectations