Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Odoo
Score 7.0 out of 10
Mid-Size Companies (51-1,000 employees)
Odoo, from the Belgium-headquartered multinational company of the same name, is a suite of business applications for managing the sales pipeline. It also comprises a PoS and inventory management modules, scaling to a warehouse or retail management solution.
$24.90
per month per user
Pricing
Drupal
Odoo
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Drupal
Odoo
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
New customers get a discount on the initial number of users purchased. ($20.00 USD instead of $24.00 USD).
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
The software is really good for managing inputs and inventory as well as maintaining traceability. The "track picking moves" functionality lets you look into a specific lot or serial numbers and view all the product moves that occurred with that lot. However, some navigation is not intuitive. For example, if I click on an item in the BoM of an assembly, then click the back button to go back to the assembly, the site goes all the way back to the home screen. Some of these quirks mean that there is a learning curve for the software, but overall the tracking is very good.
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
Community version is sometimes hard to maintain, needs some on-premise knowledge (IT) or having business with an Odoo partner that is sometimes expensive and unreliable.
Enterprise version is as expensive as other ERP in the market.
Reporting is horrible, not a lot of possibility to integrate seamlessly with a third party BI platform.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
I would give it an average rating despite being easy to use, but the user interface is very poor and not intuitive at all which makes the whole experience not that good. Also, the system is not mobile friendly at all which is annoying if you want to check something on the go.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
Easy - there is NO SUPPORT (like in ABSOLUTELY NOTHING!!!!!!!). Even for legally mandatory requirements where the system MUST work, they will gladly take a month to get back to you with a NON-answer. We couldn't even get our bank statements correctly into Odoo for 2 months - leading to no reconciliation and the company accounts were a mess (still are!!) as a result - Completely irresponsible. Have not EVEN had an apology from Odoo - they couldn't care less !!
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
Odoo talks with our other software (shipping, website, etc.) while our old software did not. It is also a web-based product so it is easily accessible from home, mobile, etc. Before, if I needed to work from home for some reason, I had to project my office computer screen to my home computer and that would cause it to lag. With Odoo, I can access our sales database without needing to do all of that.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.
