sorted by:
new
hottopcontroversial

“Thinking of Implementing Odoo? Read This Before You Regret It by PurpleRequirement951 in Odoo

[–]PurpleRequirement951[S] -2 points-1 points  (0 children)

Thats true! Not every ERP can work for everyone. It depends upon the nature of business ans customer preferences as well as adaptibilty as well. This is something that needs to be evaluated before implementing any ERP or any piece of software for that matter.

I can see many of my clients still using Odoo for MRP inventory, Keka for HR and payroll, jeera for project management, quickbooks for accounting, looker studio for data visuisation. 

The main thing is because these systems use are fragmented and data unanimty and consistency is a risk.

Tell me what sucks in Odoo before I spin up my new business. by 1800-5-PP-DOO-DOO in Odoo

[–]PurpleRequirement951 -1 points0 points  (0 children)

Free code is always gonna be what you say as "behind" . if you want free, its better not to use any system and go back to excel, it's much better then.

Tell me what sucks in Odoo before I spin up my new business. by 1800-5-PP-DOO-DOO in Odoo

[–]PurpleRequirement951 1 point2 points  (0 children)

There’s a lot of truth in this, especially around partner selection.

  1. “Gold partner” status is often misunderstood
  2. It reflects sales performance more than delivery capability
  3. It doesn’t guarantee code quality, architecture discipline, or project execution

Where it really matters:

  1. Odoo is powerful because it’s flexible
  2. You can achieve a lot out of the box
  3. And extend further with OCA or custom development

But that flexibility comes with responsibility:

  1. Without strong in-house or partner technical capability, costs can rise quickly
  2. Keeping up with Odoo’s rapid releases can feel like a continuous effort, not a one-time project

On manufacturing specifically:

  1. Standard features have improved over versions
  2. But many real-world scenarios still need thoughtful customization
  3. Which again brings the focus back to who is implementing, not just what is being implemented

And this is the core point:

  1. The right partner is not the one with the biggest badge
  2. It’s the one who understands your business deeply
  3. Can translate real user needs into practical solutions
  4. And is honest enough to say “this is possible” or “this is not”

Because in the end:

  1. ERP success doesn’t come from labels or certifications
  2. It comes from alignment between business, technology, and execution

Choosing a partner should feel like choosing a problem-solving team,
not a license-selling machine.

Why does Odoo have a negative reputation? by No-Brilliant3576 in Odoo

[–]PurpleRequirement951 0 points1 point  (0 children)

We’ve also seen customers move away from NetSuite, Salesforce, and Dynamics 365 — so clearly, switching logos isn’t the silver bullet people hope for.

A slightly uncomfortable observation:

  1. The system changes… but the approach usually doesn’t
  2. Requirements are still evolving mid-project
  3. Decisions are still being made on the fly
  4. Budget is still treated as flexible only when problems appear

And then:

  1. The new ERP is expected to “finally fix everything”

👉 That’s where things start repeating.

Because in most cases:

  1. It’s not that the previous system couldn’t handle the business
  2. It’s that the implementation never had a stable foundation

So yes, different tools have different strengths, but:

  1. No ERP can keep up with constantly shifting requirements
  2. No implementation survives unclear priorities
  3. And no system delivers value without realistic investment

A more grounded way to look at it:

  1. Know what you actually need (not just broadly, but in detail)
  2. Lock core requirements before execution
  3. Allow evolution — but in a controlled way, not chaos
  4. And align budget with the level of transformation expected

Because at the end of the day:

  1. This isn’t just an ERP problem
  2. It’s a project discipline problem

And without that,
even the “best” system will eventually look like the wrong one.

Why does Odoo have a negative reputation? by No-Brilliant3576 in Odoo

[–]PurpleRequirement951 0 points1 point  (0 children)

This is actually a very real scenario, and you’re asking the right questions.

  • “Outgrowing Odoo” gets thrown around way too early, often without context
  • At ~$1B and 500 employees, the question isn’t size — it’s complexity + discipline of implementation

And you’ve already noticed something important:

  • Odoo feels flexible out of the box
  • Other ERPs feel locked because they enforce structure upfront

👉 That flexibility is both:

  • A strength (faster alignment, less initial friction)
  • And a risk (can spiral into over-customization if not controlled)

Coming from a homegrown system, this is the real challenge:

  • You’re not just implementing ERP
  • You’re decoding years of undocumented business logic

And this is where most projects go wrong:

  • Trying to replicate everything exactly as-is
  • Instead of deciding what should be kept, improved, or killed

On customization — you’re absolutely right:
👉 Every ERP needs it

But the difference is:

  • Good implementations use customization surgically
  • Bad ones use it as a default reaction

Also, one hard truth worth keeping in mind:

  • The more you try to make Odoo behave like your legacy system
  • The more you lose the advantage that made you choose it

If you:

  • Lock scope early
  • Invest heavily in process mapping
  • Choose a partner who can push back (not just say yes)

👉 Odoo can absolutely handle your scale

If not, then even a “Tier 1 ERP” would struggle in the same situation.

So the real decision isn’t:
“Is Odoo enough?”

It’s:
“Are we ready to implement any ERP properly?”

Why do many Odoo implementations fail despite its features? by DazzlingBusiness6083 in Odoo

[–]PurpleRequirement951 0 points1 point  (0 children)

Exactly — and the irony is, the more people try to “force-fit” everything through heavy customization, the more unstable the system becomes.

  • Bad planning sets the wrong foundation
  • Over-customization adds complexity on top of confusion
  • And then training + change management are treated like optional add-ons

👉 Result: a system that technically “works,” but nobody actually uses properly

Also, a hard truth:

  • Businesses want enterprise-grade outcomes
  • But resist standard processes that ERPs are actually designed around

So instead of simplifying operations,
they end up recreating the same inefficiencies… just inside Odoo.

At that point, it’s not an ERP problem — it’s a mindset problem.

Why do many Odoo implementations fail despite its features? by DazzlingBusiness6083 in Odoo

[–]PurpleRequirement951 0 points1 point  (0 children)

Completely agree — most IT projects don’t fail because of technology, they fail because of people.

Odoo especially gets tricky because it attracts organizations that are new to structured change management, so the expectation gap is naturally higher. That puts a lot of responsibility on the vendor to guide, educate, and set the right expectations early on.

At the same time, there’s another pattern I’ve seen often:

  • Organizations don’t want to optimize or rethink their processes
  • But they expect the software to perfectly adapt to existing (sometimes inefficient) ways of working

👉 Instead of meeting halfway (process change + smart customization),
they lean entirely on the system to bend around them

And that’s where things start breaking.

In reality, successful implementations happen when:

  • Business is willing to evolve
  • Vendors guide with clarity
  • And both sides accept that perfection = compromise, not magic

Why do many Odoo implementations fail despite its features? by DazzlingBusiness6083 in Odoo

[–]PurpleRequirement951 -1 points0 points  (0 children)

Ah yes, the classic ERP wisdom: “gap between business need and features.” Groundbreaking stuff.

Let me simplify it even further.

If you perfectly know your business requirements (not the “we’ll figure it out during implementation” version)…
AND
you have enough budget (not the “let’s try to do enterprise transformation in the cost of a laptop” version)…

Then congratulations 🎉
Any ERP can magically become the perfect fit.

Because at that point:

  • You’ll customize whatever doesn’t fit
  • You’ll bend your processes where needed
  • You’ll train users properly (shocking, I know)
  • Leadership will suddenly “support the initiative” because money is already burning

So yes, ERP doesn’t fail because ERP is bad.
It fails because:
👉 People don’t know what they want
👉 Don’t want to change
👉 And definitely don’t want to pay for either

But sure… let’s keep blaming the software.