I’ve been working with Odoo for about a year implementing it for a small-medium business in the UK (lots of customisations, general specing out etc, working with their partners, etc. So not all dev). Disclaimer I’ve not yet touched v13.
The good; The OCA (community association), the people (both community and Odoo), the basic framework gets you up and running fast. You can tell it’s grown over time, and it’s got sharp edges, but you can get what you need done. Not necessarily in the prettiest way. The backwards compatibility and desire to not break the core APIs is generally good from what I’ve seen so far. Individual modules depends how much Odoo themselves lean on it afaict. GitHub access for partners and direct source access to both enterprise and community editions has been extremely helpful.
The bad; imho testing is a pain. The ORM uses Polish notation to build filters, which if you’re used to SQL is frankly irritating to work with. The ORM itself is quite clever, but it’s also not like any ORM I’ve worked with. The dev docs aren’t great, beyond the basics. The quality of modules in the “App Store” is extremely hit or miss. Odoo official “support” as a partner is questionable. I feel like they’re under pressure to get you to pay up to be a partner and then some period of time you might get help later. Anecdotally I’m led to believe our partner account manager has been pushing us hard to host a local event at our own cost (I’m not that involved with that side). The last few versions have seen more accounting features drop out of community edition. Some of the official apps are basic.
Is it better than SAP, Dynamics, etc.? Probably not. Is it good enough given the price point and flexibility, for smaller businesses? Probably, especially if the business has been tying together lots of apps adhoc.
You should also checkout ERPNext (https://github.com/frappe/erpnext). Its another free and open source ERP (GNU GPL v3) which is not open core. ERPNext is also built as a monolith, so you get maximum features out of the box instead of relying on 100s of extensions to fulfill your requirements. All since there is no "enterprise" version, there is no chance of features dropping out like accounting and payroll.
ERPNext has reasonable traction too (~5k+ stars on GitHub, 12k+ forum members) and is used by some very large enterprises.
Disclaimer: I am the founder of ERPNext
You guys should definitely dial down on the marketing hyperbole. A good technical getting started documentation would be much better than forcing potential users to dig through GitHub and stumble their way in.
Posted GitHub since it’s HN. Docs available at https://erpnext.com/docs/user/manual/en
Tried to get into it. Docs are poor, not many tutorials about Frappe in real life situations.
Lots of marketing hyperbole which puts me off.
Gotta say I don't understand why you're going against PEP 8 and using tabs for indenting.
> The last few versions have seen more accounting features drop out of community edition.
Does this mean they are removing features from the open-source edition and limiting those features to enterprise users?
V12 saw accounting reports, and iirc budgets and assets moved to enterprise. I saw a tweet I can’t lay my hands on right now from an OCA member about additional modules being moved in V14 (for context V13 was only released a few weeks ago, so things may change)
If they move components to enterprise in a new version, how hard is it for the community to fork the last open source version of those components and port them to work with the newer version?
That has happened several times already. The best known fork is probably Tryton, which forked during the OpenERP transition. It has seen a lot of independent development since then, also with some sort of company backing. (I evaluated it many years ago so my experience is probably no longer relevant.)
It would take an experienced odoo Dev to fork and maintain it. And they would also have to take the huge amount of business requests and support questions.
No, Odoo is not going into that direction. We invest more and more in the community version.
Here is a blog that explains the right balance between Odoo Community and Odoo Enterprise: https://www.odoo.com/blog/odoo-news-5/post/odoo-community-en...
I worked on developing a module last year. I see a number of issues, most are shared with many "platform" applications.
Somehow you see especially "enterprise" software being written as a kind of proprietary platform, often like a kind of jvm or .net clone, with some half-baked ORM and lots of moderately documented (at best) infrastructure ("framework" ugh, usually feels like a straightjacket), on top of which one can develop "modules" that are all intertwined and create a dependency hell and a huge dependency on the proprietary platform.
I don't see the point. There are enough open platforms that are at least as good to create "enterprise" functionality, including database frameworks etc. Why would one use a proprietary framework that you have to adapt to, instead of a general purpose platform with some libraries that you can pick and choose from?
I had my fingers in SAP, a lot, some Odoo and tried out Dynamics 365 for my startup. SAP is great for larger companies or even smaller ones if they resist the urge to customize the ship out of SAP. Can't say too much about Dynamics, only that without manufacturing there are more specialised WMS and TMS solutions out there.
Odoo on the other was just a big pain. None of the workflows was automated. The consultant had no idea how goods receipt works. Not sure how much of it was the fault of Odoo and how much was due to a bad installation and bad custumizing. Regardless, this experience kicked Odoo of my list potential ERPs right away.
this. i jumped from 10 to 12 and ton of features from accounting is missing.
they really push you towards enterprise.