Key takeaways

• An ERP (enterprise resource planning) system runs finance, inventory, procurement, CRM and HR from one shared source of truth; a CRM covers only customers and sales.
• Odoo suits small, medium, large and enterprise businesses because it is open source and priced per user for unlimited apps, not per module.
• For an Australian mid-market business, an ERP implementation typically runs from around $40,000 to more than $200,000, depending on scope.
• Most ERP failures come from switching everything on at once. A phased rollout, one business unit at a time, keeps the project on track.
• Adapting your processes to the ERP's native flow, and customising only what sets you apart, keeps a project affordable and stable.

What is an ERP system?

An ERP (enterprise resource planning) system is a single connected platform that runs a business's core operations (finance, inventory, procurement, manufacturing, CRM, email marketing and HR) from one shared source of truth. Instead of disconnected spreadsheets and tools that don't talk to each other, an ERP gives every team the same live data, so work stops falling through the gaps between systems.

An ERP system is the operational backbone of a business: the place where every department's data and process lives together, rather than in separate apps that each hold one piece of the picture.

What's the difference between ERP and CRM?

This is the most-searched ERP question in Australia, and the distinction is simple once you see it.

A CRM (customer relationship management) system points at one slice of the picture: your customers and your sales. It's valuable, but it only ever sees that slice. An ERP is the whole picture: it includes CRM and your inventory, finance, email marketing, HR, procurement and everything else, in one place.

Here's how we frame it with clients: you might come to us wanting a CRM, but you usually have other problems too, sitting in other systems. Those problems can live in one place in an ERP, which solves the CRM need and everything around it at the same time. A CRM fixes one thing; an ERP connects everything.

If you only need to manage customer relationships, a CRM may be enough. If the same data has to flow through sales, stock, fulfilment and finance, that's ERP territory.

Odoo or SAP: which ERP fits which business?

People compare "ERP vs Odoo" and "ERP vs SAP" constantly, which is really a question about which ERP suits which business.

Traditional enterprise ERPs like SAP are powerful, but they cost a lot to implement, a lot to maintain, and carry heavy licensing. They tend to suit the big end of town.

Odoo is an ERP that fits small, medium, large and enterprise businesses for two reasons. First, it's open source, so it's flexible: if something you need isn't there out of the box, it can be extended. Second, it's priced per user for unlimited apps, rather than the per-module licensing that makes traditional ERPs expensive to grow into. For most Australian mid-market businesses, that combination of flexibility and lower cost is why Odoo is genuinely worth considering alongside the traditional names.

Who is Odoo not for? Organisations that specifically need a particular enterprise platform's ecosystem, or that would rather buy a rigid, heavily supported system than shape a flexible one to fit. For the large majority of growing Australian businesses, Odoo covers the ground.

Dapth is an official Odoo Ready Partner. See our Odoo implementation services, or read how we approach ERP implementation and integration in Perth.

What does an ERP system cost in Australia?

There's no single sticker price, because ERP cost depends on what the business actually needs: which apps, which processes, and what you expect the system to do.

As a realistic band, an ERP implementation for an Australian mid-market business runs from around $40,000 to more than $200,000. What moves a project along that range is scope: the number of applications, the complexity of the business processes involved, and how much of the work is configuration versus custom development.

One thing that quietly controls cost: how willing you are to adopt the system's native way of working. The expensive path is taking an ERP and forcing all your existing processes into it through customisation. The efficient path is looking at where your business process can shift to fit the ERP's flow, which is usually cheaper, faster, and more stable to maintain. (More on that below.)

Why do ERP implementations fail, and how do you avoid it?

Most ERP failures share one root cause: the rollout wasn't phased. Companies try to switch on everything at once (every business unit, every module, on day one) and it collapses under its own weight. They spend a lot of money and it simply doesn't work.

The safeguard is a phased rollout, one business unit at a time. Stand up a small part first (HR, for example), get it working, then roll the next area in (say, CRM) and continue. Each stage is contained, testable, and low-risk, and the business keeps running throughout.

The failure pattern, and the fix:

• Big-bang go-live → phase by business unit; prove one before starting the next.
• Forcing every legacy process into the new system → adapt processes to the ERP's native flow where you can, and reserve customisation for what genuinely differentiates you.
• Wanting everything now → sequence by priority; the system compounds in value as each unit comes online.

Does an ERP work for my industry?

A common assumption is "ERP isn't built for my industry." In practice, a platform like Odoo is industry-agnostic, because businesses share more patterns than they think. Whatever you do, you need somewhere to manage employees (HR), somewhere to manage customer relationships (CRM), and usually somewhere to run email marketing, and so on across the core functions.

Different industries don't share workflows 100%, but Odoo is granular enough that it doesn't need to care what industry you're in: the modules exist out of the box, and each is shaped to fit how your industry actually works. Manufacturing leans on production and inventory; a services business leans on projects and time; food or retail leans on point of sale and stock. Same platform, configured to the shape of the work.

Explore ERP for your sector: manufacturing, construction, retail, health, professional services

Should you host your ERP in the cloud or on-premise?

For most Australian organisations, this question is largely settled. On-premise ERP hosting is the traditional model, and it's far less relevant now. Cloud hosting is ISO-certified, data is held in Australia, and it typically runs on Microsoft or AWS infrastructure, so the old objections about control and security no longer really apply. Cloud is also significantly cheaper to run than on-premise today. For the large majority of businesses, on-premise shouldn't be the default consideration it once was.

What should an ERP own, and what should it integrate?

A platform like Odoo has accounting built in, so in principle the ERP can own your financials. Whether it should comes down to the individual business and its policies.

Some organisations prefer to keep their financials in Xero or MYOB, separate from an ERP that might have hundreds or thousands of users, often for a sense of security in keeping finance ring-fenced. That's a legitimate choice, and it's not a technical barrier: Odoo integrates with Xero and MYOB out of the box, and the systems talk to each other cleanly. So the principle is less "the ERP must own everything" and more: let the ERP own the operational core, and integrate the systems your governance or comfort says should stay separate.

What should a Head of IT check on data governance and integration risk?

Two things de-risk an ERP project before a line of code is written.

Certified developers. Implementing through a certified partner means the delivery risk sits with specialists, not your internal team. (Dapth, for example, works with certified Odoo developers.)

A shared risk matrix. Before we consider a project, we build a risk matrix with the client: they add the risks they see, we add the risks we see, and each is scored: how serious is it, and how do we circumvent it? We agree on that together before implementation starts, so everyone knows the risks and the mitigations up front. It turns "hope it goes well" into a documented plan.

What is the one principle that saves ERP projects?

If there's a single rule worth taking from this: look hard at what the ERP already does before you change it.

Odoo is open source and can be customised to your liking, but the most valuable question isn't "how do we make it match what we do today?" It's "can our business process be improved to fit the ERP?" Much of the time, the way a business does something has built up over years (repeated steps, traditional habits) without anyone asking whether it could be better. A good implementation partner runs a service-design step first: understand the business completely, then improve the workflow and see how it should look in the ERP. Customise for genuine differentiation; adopt the native flow everywhere else. That single discipline is what keeps a project affordable, stable and successful.

Ready to see where an ERP fits your business?

Before you shortlist a platform, it's worth understanding where your biggest operational gaps actually are.

Take the Digital Advantage Assessment: 10 questions, about 3 minutes, for a free read on where connected systems would create the most value. Or, if you're weighing Odoo specifically, see our Odoo implementation services.

About Dapth

Dapth is your Perth digital consultancy, building connected digital systems from websites and intranets to applications, software, ERP and AI tools. For more than 15 years we have helped WA businesses, government agencies and organisations unlock advantages like streamlined workflows, increased efficiency, cost savings, new revenue and more powerful marketing.

We start with your organisation, not the technology: your users, your operations and your objectives. Then we connect everything across four areas:

• Digital Consultancy: Digital strategy, service design and UI and UX design that map how your customers, people and systems should work together, before anything is built.
• Customer Experience: Websites and digital experience platforms on Xperience by Kentico (Kentico Gold Partner), Sitefinity, Umbraco and Payload CMS, plus ecommerce.
• Employee Experience: Intranets and employee portals on Microsoft SharePoint, and workflow automation that takes the double handling out of everyday work.
• Operational Systems: ERP with Odoo as our primary platform (we are an Odoo partner), plus custom software, apps and the integrations that connect them.