How to Plan an Odoo ERP Implementation for Australian Manufacturers and Distributors
Buying ERP (Enterprise Resource Planning) software is the easy part. The hard part is turning it into a system your purchasing officer, warehouse team, production supervisor and bookkeeper all trust enough to stop keeping their own spreadsheets on the side. That only happens when the project is planned properly from the start.
This guide is written for Australian manufacturers and wholesale distributors considering Odoo. It follows the order most successful projects take, from scoping through to the months after go-live, and points out the local details that are easy to overlook.
Start With the Problems, Not the Modules
It is tempting to open a demo, see dozens of apps and start ticking boxes. Resist that. A good scope starts with a plain description of how work flows through your business today and where it breaks.
Sit down with the people who do the work. Ask the warehouse lead how a customer order turns into a picked and packed delivery. Ask production how they know what to make next and how they find out a component is short. Ask accounts how long month-end takes and which numbers they never quite believe. Write it all down, including the workarounds nobody is proud of.
From those conversations, pull out a short set of outcomes the project must deliver. For example: accurate stock by location, real job costs for manufactured products, faster invoicing after dispatch, and one set of books for two trading entities. These outcomes become the yardstick for every later decision, including what to leave out of the first phase.
Be honest about what can wait. Many projects run late because they try to deliver everything at once. A first phase that covers the core of sales, purchasing, inventory, manufacturing and accounting, with extras added later, is usually faster and cheaper overall than one large launch.
Choosing Modules for Manufacturing and Distribution
Odoo is built from apps that share one database, so the choice is less about features in isolation and more about which processes you want joined together.
For distributors, the core tends to be Sales, Purchase, Inventory and Accounting. Inventory decisions carry the most weight: how many warehouses and locations you hold, whether you track lots or serial numbers, how you handle expiry dates, and which replenishment rules suit your range. A food wholesaler with short shelf-life lines needs very different settings from a hardware distributor with slow-moving stock.
For manufacturers, add Manufacturing and often Quality and Maintenance. The Manufacturing app relies on bills of materials, work centres and routings. Getting bills of materials right for your main products is worth more than modelling every variation on day one. Quality checks and control points can sit inside work orders so inspections happen as part of production rather than on paper afterwards.
Optional apps such as a customer portal, eCommerce, field service or a barcode app for the warehouse floor can make a big difference, but each one adds testing and training. Add them when the core is stable, unless one of them is central to your business case.
Finding the Right Implementation Partner
Odoo is mostly implemented through partners, and the partner you choose will shape the result as much as the software. Look for experience in your industry, a clear method, and people you can actually reach once the system is live.
Questions worth asking include how many similar projects they have delivered, who will be on your project team, where support staff are based, and where your data will be hosted. Ask to speak with an existing client in a similar line of business.
As one reference point, Australian Odoo partner WilldooIT says it has completed more than 100 projects since becoming an Odoo partner in 2009, works across timber, food distribution, manufacturing and renewables distribution, and typically delivers a standard implementation in three to six months. More complex multi-location or heavily customised projects take longer, so treat any timeline as a range until scoping is finished.
Whoever you choose, agree in writing on the scope, the deliverables for each phase, how changes are priced, and what support looks like after go-live. A short, clear statement of work prevents most of the disputes that sink ERP projects.
Data Migration and Integrations
Data migration needs its own plan and its own owner inside your business. Start by listing every source: your accounting system, stock spreadsheets, a separate CRM, supplier price lists and any job costing tool. Then decide what moves. Most businesses bring across customers, suppliers, products, bills of materials, opening stock and open orders, plus opening balances for the ledger. Detailed transaction history can stay in the old system for reference.
Clean the data before you load it. Merge duplicate customers, retire products you no longer sell, standardise units of measure and check that every stocked item has a cost. Bad data in an ERP spreads quickly, because every sale, receipt and production run uses it.
Run at least two trial migrations into a test environment. After each one, compare stock quantities and values, debtor and creditor balances and the trial balance against your old records. Only sign off when the numbers match or the differences are explained.
Give each data set a named owner inside the business. The person who manages purchasing should check supplier records and price lists, while someone from production confirms bills of materials and routings. Your partner can build the import tools, but only your own team knows whether a product cost or a reorder point actually looks right.
Integrations come next. Common ones for Australian manufacturers and distributors include eCommerce platforms, freight and courier services, EDI with major retail customers, bank feeds and payment gateways. For each integration, be clear about which system is the master for each piece of data and what happens when a sync fails. Fewer, well-chosen connections are easier to maintain than many fragile ones, a point that also comes up in this guide to choosing your business tech stack.
Getting Australian Tax and Payroll Right
Local compliance is where generic configurations fall short, so build it into the scope from the first workshop.
GST settings need to reflect how you actually trade, including taxable, GST-free and input-taxed items, imports and any export sales. Your tax codes in Odoo should line up with the labels you report on your business activity statement, so that preparing the BAS becomes a review rather than a rebuild. Ask your accountant to check the tax mapping before go-live and to review the first BAS produced from the new system.
Payroll needs the same care. Under Single Touch Payroll, employers report payroll information to the ATO through STP-enabled software, and the report is due on or before pay day. If you plan to run payroll in Odoo, confirm that the payroll setup is STP-ready, that your awards and pay rules are configured correctly, and that year-to-date figures carry over cleanly if you switch mid-year. The Australian Taxation Office publishes the current STP reporting guidelines and BAS instructions, and those should always be the final reference over any summary, including this one.
Record keeping is part of compliance too. Decide how long the old system will stay accessible and how you will export and store its records once licences lapse, and ask your accountant how long each type of record must be kept. It is also worth checking the government’s business.gov.au website, which brings together business information and lists government assistance, grants and events that may be relevant when you are investing in new systems.
Training, Go-Live and the First Ninety Days
Training should be role-based and hands-on. Warehouse staff need to practise receipts, picks and stocktakes on a scanner. Production needs to run work orders. Accounts need to reconcile, run reports and prepare a BAS in the test system. Generic overview sessions rarely stick, while short sessions using your own products and customers usually do.
It also helps to name one or two internal champions in each area. These are the people others ask first when something looks odd on screen. Give them extra time in the test system before go-live and involve them in testing, so they understand why the system is set up the way it is, not just which buttons to press.
Use the test environment for user acceptance testing. Give each team a set of real scenarios, such as a backorder, a supplier return, a rework job or a credit note, and have them sign off once each scenario works from start to finish.
Pick a go-live date with care. Avoid your busiest season and the last weeks of the financial year. Many businesses choose the start of a month so opening balances line up with a clean accounting period. Plan a stocktake close to the cutover so opening stock is accurate, and agree on a short freeze on new products and price changes during the switch.
Write a simple cutover plan that lists each task, who owns it and when it happens. It should cover the final data load, the last invoices and receipts in the old system, user access, printer and label setup, and a clear point at which everyone stops using the old system. Walk through it with your partner a week before go-live so nobody is surprised on the day.
Expect the first few weeks to be bumpy. People will hit screens they have not used before, and some processes will need small adjustments. Have your partner on call, keep a shared log of issues, and meet briefly each day at first to work through them. Most problems in this period are about habits and settings rather than bugs.
After about ninety days, step back and review the outcomes you set during scoping. Are stock levels accurate? Are job costs believable? Is month-end faster? The answers will show where the system is working, where more training is needed, and what belongs in the next phase. An ERP is never really finished, but with a careful plan and steady follow-through it becomes the place where the whole business finally works from the same numbers.
***
PW











