Contact Info
Odoo in New Zealand
Is Odoo a good fit for a New Zealand business?
Odoo suits New Zealand wholesalers, food and beverage producers and light manufacturers that need stock, purchasing, production and accounting in one database. Before committing, check what the New Zealand localization covers in your version, how Peppol invoices would be exchanged, whether Community or Enterprise fits, and how an Australian company would sit beside the local one. As a freelance Odoo consultant I check each point remotely with your accountant.
Last reviewed by Vikas Saroj
The New Zealand businesses that look hardest at Odoo are usually the ones where stock moves fast and margins are thin: importers and wholesalers, food and drink producers, and small manufacturers. Their Xero or MYOB file is fine, but batch tracking, landed costs on imported goods, production runs and warehouse picking live in other tools that do not agree with each other.
Odoo can bring those together, but the New Zealand details still need proof. GST coding, Peppol exchange, payroll outside the system and, for many firms, an Australian entity all have to work in the version and edition you actually license. I test them with your accountant and your own transactions before a contract is signed.
My Odoo work is freelance and remote, with no reseller margin or implementer tie behind the recommendation.
What I Do
Focused on what a New Zealand producer or distributor needs proven before Odoo runs the business.
I confirm what the New Zealand localization contains in your version, then run local, export and import transactions through to the GST report for your accountant to compare.
Whether your Odoo version and edition can exchange Peppol invoices for New Zealand directly, or needs an external access point, and what has to be captured on customer and supplier records.
Lots, expiry dates, recall reporting and first-expiry-first-out stock rotation designed for food, beverage and other producers who must trace product from supplier through to customer.
Freight, customs and other landed costs on imported goods allocated to stock in Odoo, so product margins reflect the real cost of getting goods to New Zealand rather than supplier price alone.
One database holding both a New Zealand company and an Australian company, each keeping its own localization, plus intercompany rules, shared products and reporting in NZD and AUD.
Community or Enterprise, and Odoo's own hosting or a cloud server you manage, weighed against the modules you need, custom work, upgrade effort and privacy expectations.
How I Work
Test New Zealand fit early
GST cases with accountant
Peppol route confirmed
Edition decision made
Australian needs listed
Build stock, production and finance
Warehouses and routes
Lot and expiry rules
Landed cost method
Payroll journal import
Migrate and go live
Stock counted and loaded
Open items reconciled
Old apps switched off
First GST return reviewed
Odoo ships country localizations as modules, and New Zealand has one. What it contains, typically a chart of accounts template and GST taxes, and how complete its reporting is, varies with the version and edition. Treat the localization as a starting point that your accountant reviews, not a finished compliance product.
The test cases I run with your accountant before go-live:
The resulting GST report is compared with figures your accountant prepares separately. Any difference is traced to a tax setting, fiscal position or account and fixed in configuration rather than with manual journals. Tax treatment itself remains your accountant's decision. More on the ledger side is covered on my Odoo Accounting page, while the general platform guide is on Odoo consulting.
New Zealand uses Peppol for e-invoicing, and government agencies and some larger buyers may ask suppliers to invoice through it. Peppol support has been growing inside Odoo, but whether New Zealand is covered for your version, and on which edition, needs confirming. If not, an external access point can connect to Odoo instead. I test sending, receiving and matching inbound bills to purchase orders in a staging database, and make sure NZBN and other identifiers are held on partner records.
Keeping payroll in dedicated local software, which already deals with payday filing, KiwiSaver and leave entitlements, is usually the safer choice. Odoo then receives a pay run journal split by department, site or production line, so labor cost appears in product and job margins. I design that mapping and test it with a real pay run.
Other connections to plan for include ecommerce stores, EDI or portal ordering from supermarket and trade customers, freight carriers and bank feeds. Each one is listed with its owner, data direction and failure alert in an integration register. The ERP integration page explains how I specify and test these links without building a fragile web of scripts.
Odoo's multi-company features make a trans-Tasman setup possible in one database: two companies, one per country, each carrying its own localization, chart, taxes and currency, sharing products, customers and warehouses where that makes sense. It works well when both sides run similar processes. It gets awkward when one side has very different needs, for example Australian payroll or reporting requirements that push heavy configuration into a database the New Zealand team also depends on.
The questions I settle with group finance:
Australian GST and BAS settings are tested separately from New Zealand GST, with no shared tax codes. If the Australian company is the larger or more complex part of the group, my Odoo consultant in Australia page covers that side. Stock-heavy groups should also look at Odoo Inventory, and producers at Odoo Manufacturing.
Community is open source with no subscription; Enterprise adds features and Odoo's hosting options under a paid subscription. For a New Zealand business, check which accounting, Peppol and localization pieces depend on Enterprise before assuming Community is cheaper. Hosting can be Odoo Online for standard setups, Odoo.sh where custom modules are needed, or your own cloud server, for example in an Australian region. New Zealand privacy law applies to personal data wherever it is hosted; review the provider's terms with your advisor.
Migration usually comes from Xero or MYOB plus inventory and job apps. I move customers, suppliers, products, open invoices, balances and counted stock by location, keep older transaction history in a read-only archive, and agree the reconciliation with your accountant before cutover. The ERP data migration method describes each step.
If you hire a New Zealand or Australian Odoo implementer, I complement them rather than compete: the requirements stay with me, I check their configuration against those requirements, and I lead acceptance testing for you. Live calls are booked for the New Zealand afternoon, and progress between calls is shared in writing so nobody waits on a meeting. Beyond Odoo, my general New Zealand ERP advice is on the ERP consultant in New Zealand page.
Odoo is a good fit for many New Zealand producers and distributors, but not all of them:
In those cases I say so and help you compare alternatives on the same scripts. Choosing the platform that fits is the whole point of independent advice, and that sometimes means recommending a lighter or heavier system than the one you came asking about. The New Zealand hub summarizes how I support companies there.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
FAQ
Yes, Odoo provides a New Zealand localization module, typically with a chart of accounts template and GST taxes, though what it holds shifts between versions and editions. I run your actual import and export invoices through it and have your accountant compare the GST report before you rely on it.
Peppol features have been arriving in Odoo Accounting over recent releases, yet New Zealand coverage and edition requirements should be confirmed for your version. An external access point is the fallback. I test sending, receiving and purchase order matching in staging before customers depend on it.
Often yes, with each company keeping its own localization, taxes and currency. It works best when both run similar processes. I design shared records, intercompany trading and group reporting, and flag where separate databases would be simpler to run and support.
No. I can guide your own team directly or sit next to an implementer on your behalf, owning the requirements, questioning their design and running acceptance tests. Configuration, local support and any custom modules stay with the people who will maintain them.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Insights
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.
