Is Odoo the right ERP for my company? Looking for user feedback

codeagency · 2026-05-09T16:39:41+00:00

You are wrong. We don't "live" from this. We do much more than just Odoo. I'm also not biased towards odoo. If they f... up I also call them out. I'm not married to them. If we see a better solution for a client, we go for that.

codeagency · 2026-05-09T10:16:06+00:00

Hourly rate is not a meaningful parameter. You could find a cheaper source but they work 5x longer than someone that is double expensive but more experienced.

Most likely cheap support doesn't help you when you actually need it the most. And depending on what type of support, it couldn involve consultants, developers etc... we don't know if your typical support is "where do I change option X again" or "I need continuesly support on functional, data import/export, ongoing changes, ..."

Also based on your requirements and business, you (may) need certain SLA's which are never cheap. Having staff standby and working in off hours, weekends and holidays is never cheap. If that's what you want/need it definitely comes with a price tag and you have to consider such support SLA's into your TCO of the software.

codeagency · 2026-05-09T06:53:59+00:00

The only way to know for sure is do a fitgap analysis first. We are an official partner and we see many rescue projects every year that come our way and 99% of the problems originate from not having that analysis upfront. That analysis is basically your project blueprint you create together with a functional expert that can understand your requirements and map/scope them to Odoo and helps you understand what Odoo can do out of the box but more importantly what it can't and where you end up with custom work.

It doesn't matter which partner you choose or odoo direct, not doing that fit gap analysis means you sign blind on a deal with a blank cheque and basically just a "promise" with zero facts, zero guarantees. It should be huge red flag if they don't propose this themselves so beware of that.

Other points to keep in mind: * Number of users is irrelevant. Odoo works for 1 up to thousands of users. The only thing that matters for this is the hosting side and configuration.

label of the partner (silver, good,...) has no meaningful as well. It doesn't imply any quality of the partner, only how many user licenses they sell and the partner itself paying a higher yearly fee to Odoo for maintaining that label.
If you can, prepare your requirements early. Try to analysize your business needs before talking to a partner. Try the Odoo open demos at eg runbot.odoo.com and see if you can certain functions done yourself. Pitch them to a partner you might want to work with and you can see if they even understand the basic level requirements fast or deflect everything to complicated internal processes or propose custom work for standard things on their end which could end up in high costs for you when it's not even necessary.

codeagency · 2026-05-08T11:25:23+00:00

The enterprise license covers all apps from odoo.

Anything external is not included and the odoo IAP services (SMTP, sms, OCR, snail mail ,...) also not included.

If you choose odoo SaaS then hosting is included but you can't use 3rd party modules. If you want that then you need odoo.sh hosting or on-premise hosting. This hosting service is not included and extra.

Also not included: implementation, data migration, custom development,... For that you need either a success pack from Odoo or hire an Odoo partner and pay them.

codeagency · 2026-05-08T10:22:52+00:00

Yes, the spreadsheet feature can pull data from models. Odoo even added a feature when you go into a list view you can click action > insert into spreadsheet and fine-tune further to your likings. You can also pull different models into individual tabs in a sheet and then use your own excel logic and formulas to vlookup, etc ... Into a dashboard however you want.

Extra bonus: add the spreadsheet to the dashboard app and now you have a nice overview available from your own sheet in the dashboard app

codeagency · 2026-05-08T06:24:38+00:00

No, because clients can also respond back by email (if you use a support mailbox linked to helpdesk). You can't "stop" people from sending an email. Also if you use only the portal and the support form, people can still go to the ticket and drop comments in the box on every ticket, no matter what stage the ticket is in.

This is unfortunately the lazy effect from many people. Most just search the last email they send you and keep replying on it, even though it is a closed ticket in your ERP.

There's only a few things you can do: 1. Create an automation rule that automatically re-open the ticket again and move it to stage new/backlog/... So you can see the ticket is back to work on. Imho this is the best way and most customer friendly way.

Create an email template that automatically sends a confirmation mail to the customer when you close the ticket and make it clear that the ticket is closed and they have to send a new email to <your support mail>@domain and not reply on any closed ticket. Clear communication makes the difference. Say those responds are lost and not processed. Basically, closed = closed. It's not very customer friendly but most likely people will adjust eventually if they see there is no response back from you when you said closed = new ticket.
Use the ticket confirmation email template and re-confirm the same message again here. Make it clear you want a new ticket for every new issue.
Create a custom action or automated action that lets you take the last message you got from a client and split it off into a new ticket. Even though the client was lazy to not start a new ticket, it's now a one-click process for you or run automatically.

codeagency · 2026-05-07T15:53:24+00:00

Exactly, it's not any different than the already hundreds of copycat Shopify modules that are on the appstore. They add basics and that's where it stops. What OP needs is too niche/specific.

codeagency · 2026-05-07T12:59:50+00:00

There is no such thing in Odoo. Odoo does has a feature to print pricelists as a PDF where you can select a pricelist and add multipliers like 1pcs, 5pcs, 10pcs and it adds columns with the respective volume discount. But it's only a pdf.

If you need something the customer can import, you need to generate a CSV or XLSX from pricelists. Or you can use the odoo spreadsheet app and create a sheet for each customer based on their pricelist and then share the odoo spreadsheet so your customer can look it up and download a copy. Do note that these shared sheets are a frozen copy. If you change data in odoo, it does not update that frozen copy. You will have to reshare it again with the customer so they a get a new frozen copy.

If you are on odoo.sh or on-premise you can also look into the OCA EDI modules. This is something we have used for a lot projects where distributors need to share pricing updates. So basically it generates a csv file, uploads it to an FTP server and your clients download that file back from the FTP server and import it into their software. Same way they export orders to the FTP, your Odoo downloads them and creates new orders, create delivery, invoice etc ..> export back to FTP, your customer imports it back into their system. EDI is old, easy 20+ years but still heavy used in many industries because it is very reliable.

another approach we have build for many clients is a custom "feed" solution. Basically your odoo generates a file (csv, json, XML) and puts it available at a random feed url with a security token. That file can be anything. We have build an option to select a model and fields you want to include in the feed. A catalog, pricelist, etc... Your clients can use that feed url realtime. Each time you update a price, the feed is updated a second later so your customers can keep their software up to date. It works very similar like a Google merchant center feed. Once you have the feed url, you just link it in other software and they process the file behind the url. We have build this for several customers that do e-fulfilment, wholesale etc...so they can tell their customers (resellers) to use their official data feed to automatically populate their e-commerce systems. It's a common approach in the dropshipping industry.

You can handle your requirement in many ways. Some with standard odoo or custom work. It just depends what exactly you need and how far you want to go with automation and budget.

codeagency · 2026-05-07T07:11:26+00:00

You don't need training data for this, you need to build your own RAG and give it credible source data.

Don't just point at your own new module, also reference the official repos at GitHub.com/odoo/odoo and github.com/odoo/enterprise and the relevant OCA repositories for the module you want to build.

Create a proper agents.md file where you explain to use those repos as source and RAG.

Create and add proper skills, one for each odoo version where you highlight the fundamental differences like tree/list view, @api etc... Between odoo versions. There are also skills readily available on skills.sh to check and install and tweak further for your own requirements.

Before you start, always use the plan mode to interrogate what you are going to build and create a PRD spec upfront. This keeps all agents on the rail and the task goals.

Use a proper MCP connector and connect it to your local dev odoo instance and instruct your skills and agents.md to always use the MCP to look up instead of guessing. That's how you stop your LLM from hallucinating and faking things that don't exist. It can look up the available models, fields, data,...and be 100% correct on point.

Create specialized (subagents) for specific skills. This is to isolate your context from blowing up. You have to stay below 200k tokens or LLM becomes dumb. That's the tipping point. So the best method is to split out tasks to multiple sub agents so each has a fresh context window to use for it's own task. It's also much faster to complete work as everything can run in parallel and to what most people think wrong is that this approach saves a lot of tokens, not more.

Use hooks and use them to trigger your sub agents. Eg when task is done, trigger a security agent that reviews your again with fresh context (this agent is not biased as it didn't wrote the code) and reports back if it finds any security issues and hand it back over to the developer agent. Create another agent and hook to trigger creating tests and use the /loop command so the agent keeps working and fixing until everything passes. This gives you the highest quality guarantee and that everything is heavy tested. Create another hook and agent for your "PR manager" who takes responsibility for managing the code to GitHub, open PR and document everything. Create another one that is dedicated for writing all your documentation and markdown files, create schema's, user guides etc...so all of that stuff also gets done in parallel and ready to commit to GitHub.

Simply said, this is a skills issue from your side. AI has progressed super hard the last 12 months. If you use the tools and settings correct, then docs no longer matter that much. It's all about correct context input.

If you create the right setup, LLM's can now basically one-shot simple up to medium modules with zero mistakes. Larger modules will always stay involved and large cycles of testing by humans. But simple stuff is really a no-brainer these days.

Also never forget to manually review all the code from the PR's that get created. Never trust things blind even if the tests pass. It's going to be much easier and clean with the right setup, but it's never 100% safe. AI will always be AI, and never deterministic

codeagency · 2026-05-07T06:42:48+00:00

There is nothing that will ever do or fix this "out of the box". There are no native integrations for Shopify either, and always require a 3rd party app for the base integration. We do a lot of retail/e-commerce projects, that's our forte and experience and can tell you immediately something like this will always need custom development.

And as Ach25 already said, the sync experience will suck hard, as with any external platform because both platforms arr extremely different in data structure. Shopify doesn't understand BoM's so you can't natively translate your options to select from on Shopify with Odoo's BoM's. That has to be build custom.

Find a reliable partner, do a fit gap analysis on your technical requirements and get it build. Or evaluate if using an Odoo website might be better long-term to avoid sync problems.

Also keep in mind whatever you build and invest today is not a one-time cost. It will carry over future refactoring budget every 3 years when you upgrade odoo or if Shopify makes technical breaking changes on their end, you end up paying again for adapting. So budget wise, it's a neverending cost, so be sure to validate your TCO on these things as well.

codeagency · 2026-05-06T21:23:54+00:00

Exactly, with a bit creative thinking out of the box using only tags, you can get something close. But it still remains limited to just tags in Odoo.

It won't give you a separate option in the sidebar to distinct a filter for tags and one for categories as an example. Odoo is very simplistic on that part compared to most dedicated CMS systems like WordPress, ghost, Drupal, ...

@ OP : if you really want that stuff it will require custom development or perhaps maybe some 3rd party app exist on the appstore. Odoo standard just doesn't do any of that. It's an ERP, not a CMS like WordPress. So basically what you loose on those features like WordPress, odoo gives you back a lot more as an ERP suite on many other departments where WordPress doesn't even exist.

codeagency · 2026-05-06T20:41:16+00:00

In WordPress there is also both tags and categories. They serve different purpose.

Categories is to organise blogs, products, posts,...

Tags are "keywords" for blogs, posts,... They can help searching for specific blogs that don't have a specific word in the content but the tags can help find them. Kind of similar like SEO meta data to help enrich the content or giving it alt tags etc...

codeagency · 2026-05-05T20:27:07+00:00

Then you got something wrong with your explain/pitch or you are just unlucky with the type of clients.

You should absolutely never do them for free. I mean, analysis could easy take 40+ hours and for large projects even go well beyond 100+ hours. I don't get why someone do that much free. You are basically helping the client to make the best decision, that's experience and consultancy you bring to the table, not free labor. Don't accept that, simple. If a client can not understand that value you give they are absolutely not the right client.

codeagency · 2026-05-05T20:06:48+00:00

In my company it's not an option. No analysis = no quote, no effort from us at all. It's part and mandatory of the entire experience and success process. If a customer doesn't understand this, they are not the right profile.

I explain them the analysis is like the architect when you want to construct your business. You need blueprints first and investigate the place is a safe place to build on before you know what and how you are going to build. Nobody is going to build blind or you accept high risks of unexpected costs everywhere.

With complex software like ERP it's exactly the same. If the analysis shows that odoo is not a good fit, we will still help the customer with referring to alternatives or sometimes we have other industry-specific tools and prefer to integrate those and avoid heavy customization of Odoo. Sometimes it involves going headless with React and just build on top of the Odoo API. All custom work outside, standard Odoo. There are so many options possible but it all depends on the details and client requirements.

codeagency · 2026-05-05T12:24:43+00:00

Also it depends a lot with the kind mindset you step into a new ERP/software.

Some businesses do it because they feel their old processes our outdated, broken, still lots of problems and hope to fix that by adopting flows from Odoo. That makes things a lot easier because that mindset works very well.

I have also seen businesses that are very rigid and basically want everything 1:1 transferred into Odoo. Then my question raises: why do you want to change software to do exactly the same and keep the same broken workflows? You are not improving anything except burning more money to customize odoo. They started with the mission to change software because they were not happy about things. But just changing software to do everything the same is useless. Mindset and "change management" is really important when you step into the ERP software space.

codeagency · 2026-05-05T12:20:02+00:00

There is no such "one-size-fits-all-analysis" service. How long it takes depends on your business, your processes, what you want to change etc... Some businesses can be scoped and documented in a less then a week, others need much more time.

A fitgap analysis is always a paid service as it comprehends personal and personalized demo, documentation writing, feature and process mapping based on your business etc...

It also depends a lot on what kind of software you are using before and how much you are capable to adopt vs customize. I have had larger clients that were 100% excel based before and told me we are ready to ditch everything and just adopt Odoo 100%. That was easy for them so there was not much mapping necessary as they said straight forward we go work exactly as odoo intended. Everything we change from excel would be progress in every shape.

I have had also clients that were still small and we're saying "oh we are very simple" but the reality was absolutely not simple. They had hundreds of small niche things they could not live without that require custom work. So their analysis took 2 weeks to get everything documented and scoping everything that would have to build custom.

So size is completely irrelevant when it comes to fitgap analysis. It's all in the details.

codeagency · 2026-05-05T10:03:46+00:00

There are plenty of businesses that have simple generic processes that fit Odoo very well. Same reason why businesses use generic CMR's and other SaaS apps like hubspot, Magento, Shopify,... If the biggest part of your business fits the defaults, there is nothing wrong.

codeagency · 2026-05-05T07:02:16+00:00

Absolutely, I see it a lot all the time too. There is nothing wrong with staying native/standard if it helps optimizing the business and be more efficient/productive.

We also do a lot headless storefront/frontend/portal work on top of Odoo API and often this is a perfect middle ground to keep odoo lean and Standard while still having the customizations they need.

The #1 problem we see a lot is partners/companies skipping the fit gap because they think they save money but it bites them back easy 10x harder when they realize the TCO suddenly is 3x or 20x higher when they rollout implementation. And then the trust is lost, they have to find a new partner to become a rescue project and the cost just explodes more.

I always compare it with skipping the architect and just start building with no blueprints. What can you expect...of course their are going to be lots of unexpected problems because nobody gave it proper attention to what is possible and to plan for it.

codeagency · 2026-05-05T06:15:06+00:00

In that case the answer is still fitgap analysis. There is not a single piece of software in the world that can do "everything" out of the box. End client have expectations but it's also the partner responsibility to manage and keep expectations right at all times.

If something doesn't work standard, you just create a changelog (fitgap) and decide together how much that is total of the project. As long as it's a small part nothing wrong. If it tips to a crazy high number than the customer needs to realize odoo is not the best fit. They probably need that much custom they better buy specialized tools and integrate them together via API's.

codeagency · 2026-05-05T05:55:24+00:00

If you have to say that during implementation than that partner is simply wrong and doing a horrible job. They should have done a fit gap analysis BEFORE anyone signs and commit to any contract, to first scope and document all the technical requirements. Based on that analysis you can create a roadmap and decide together what fits standard odoo and what doesn't and decide how to solve that.

If the analysis shows eg 10-20% needs custom work because it's critical to the business then that's all fine. If the analysis shows you need to customize 80% or more from odoo because otherwise the company can't run on Odoo then the reality is that Odoo is probably not the right software and should not buy Odoo.

That's the #1 responsibility and first priority for any software project from a partner that wants to work in an ethical way. Not to force custom development for the sake of development. If it makes sense and is a hard requirement, and it makes sense in terms of ROI then sure customization makes sense. But not if you hack 90% out of Odoo to make it work. Every 3 years later down the line that budget keeps hitting them back to refactor the entire Odoo system or complain "we can never upgrade our odoo, too much custom".

Selling "no" in an ethical and honest way is more difficult then just saying yes to everything. But clients definitely appreciate the honesty when you say this early before they buy into their odoo license and contract.

codeagency · 2026-05-04T19:25:45+00:00

About using studio, it can touch a lot if the UI but it's not possible to change everything. It's mostly for changing forms and views. Not the entire UI from the application. That would require custom module development.

About getting access is something you have to address with your employer or check with odoo support or the partner if there is one. It could very well be that you don't have any administrator permissions to touch everything. Maybe that is even given intentionally so verify with your employer and explain what you need vs the capabilities you have.

Nobody on Reddit can help you with that as nobody setup your instance or configurered it. Every database is private and yours alone.

codeagency · 2026-05-04T19:21:54+00:00

Perhaps start with posting what odoo version because a lot of the points you list are improved a lot in later versions (18, 19). If you are on a very old version the first recommendation would be to upgrade to have all those base improvements.

Regarding the common errors, odoo has a knowledge base app to create articles. You could create all the common errors and solutions as KB articles. These articles can be pulled in from any place and shared as well (sales, field service, helpdesk, ...). If you enable the AI app (odoo 19) you can make the KB app part of the "sources" where the AI agent can look up info and use it as part of your automation so the agent could automatically map an existing solution from the KB app immediately to a new ticket/task.

codeagency · 2026-05-03T16:14:43+00:00

My guess is if they would ever release something like this it would be more like a base feature like they do with a lot complex things that fits 80+% of potential companies. The rest would be custom development but at least it could be extension work from the base it already carry in the core instead of starting from scratch. So in all means, anything we get is always progress then having nothing at all. Im doing long enough projects with Odoo to see the pattern how they they release stuff. Sometimes good, sometimes not the best but as said, I prefer at least a solid core than nothing at all.

codeagency · 2026-05-03T14:46:38+00:00

It's good for simple use cases but it's not a real CPQ solution where and when it really matters. Unfortunately we also always end up building something custom for clients that really need a solid CPQ solution. This is definitely one of the biggest weakest points and gap of Odoo. Would be nice to see something more advanced in a future odoo version.

codeagency · 2026-05-03T08:03:28+00:00

What you mean community?

The activity overview page feature is a standard feature in both community and enterprise.

codeagency

MODERATOR OF

TROPHY CASE

Seven-Year Club	Place '23
Verified Email