41–50 of 76 posts
Interesting to see them on HN! They are running a massive out-of-home media campaign in my city, they billboard even busstops in home-districts with lowered traffic speed in the suburbs :-))
We have been using Odoo for some specific processes in the company in the past. There are some bright ideas based on strong fundamentals. Regarding the strong fundamentals: - A clever, extremely flexible, roles/permissions system. It is based on giving CRUD permissions to user roles, allowing to define access rules based on the fields (for instance a READ access with a record rule [('user_id', '=', user.id)] would al…
I tried to get Odoo adopted at my company for about a year but eventually gave up in favor of a paid solution. The thing is that what you really need to get something like this working is support (by phone, screen sharing etc.), and it came down to two options: either I permanently become Odoo support for everyone else, or we pay someone else to do it. All the companies offering Odoo support are very expensive, so an…
I am the founder of Odoo: ask me anything. Happy to see Odoo on HN.
Last time I worked with Odoo (v15/v16, enterprise, self hosted) we had to send a dump of the production database over to you to be migrated to the new version and then it was sent back. The upgrade path for third-party and custom addons was not defined. And since it is Odoo, everything is in that database: from employee's time tracking to customer support chats, from stock info to accounting data, from e-mail address…
See `./odoo-bin obfuscate --help` to check how to crypt your custom data and uncrypt after upgrade.
It's not perfect (crypt specific columns rather than full DB) but, unfortunatelly, to operate our upgrade service, we need access to the database. Upgrades are complex and requires testing, fine tuning scripts to your specific use cases, etc.
The other alternative is to not use our services, but do it yourself using upgrade scripts from the community: https://github.com/OCA/OpenUpgrade
Earlier quoted context omitted.
By having every services inside one tool, what are the new possibilities that Odoo can do easily that is hard to do with others suite of tools (where you’d need to connect together multiple independent services) ?
Just an example: when I send an email marketing campaign with Odoo, I have all the stats attached: the usual # clicks, open rate, ... but also # Leads, # Orders, Revenues. Because Odoo as it all: - You send an email with link tracker (Email Marketing App) - The visitor goes on website (Website App) - He fills a form that creates an opportunity (CRM App) - 4 weeks later a sales make a quotation (Sales App) - After Del…
I noticed this on your site recently whilst evaluating Odoo for a use case, and I’m glad I get the opportunity to ask…why? That seems an astronomical amount for this product. This isn’t a criticism, I am just genuinely curious about the business.
I've built a couple of Odoo integrations for clients. For the longest time, they only offered XML-RPC as an external API. At some point they also added JSON-RPC, which is the same kind of suckage. But now they're suddenly planning to remove both in the next major version (to replace them with something different) with very little advance notice. Their API documentation is virtually nonexistent. You have to basically…
Damn. Just finished an integration with their XML-RPC. It was quite bad experience, the API documentation is horrible as you mentioned.
Earlier quoted context omitted.
Just an example: when I send an email marketing campaign with Odoo, I have all the stats attached: the usual # clicks, open rate, ... but also # Leads, # Orders, Revenues. Because Odoo as it all: - You send an email with link tracker (Email Marketing App) - The visitor goes on website (Website App) - He fills a form that creates an opportunity (CRM App) - 4 weeks later a sales make a quotation (Sales App) - After Del…
> has 6700 employees I noticed this on your site recently whilst evaluating Odoo for a use case, and I’m glad I get the opportunity to ask…why? That seems an astronomical amount for this product. This isn’t a criticism, I am just genuinely curious about the business.
On the service side, we onboard 14.000 new clients per month. (need a lot of sales too for that). Projects varies from a 5 users company (4 hours of service), to 5000 users. (1 year implementation for a team of 5)
The spread in people is more or less: 30% developers, 30% consultants, 30% sales.
In addition to our 6700 employees, we also have a large partner network: 200k FTE working on Odoo (selling, developing, doing services). They developed 50k apps, and onboard tens of thousands of companies per month.
Earlier quoted context omitted.
Last time I worked with Odoo (v15/v16, enterprise, self hosted) we had to send a dump of the production database over to you to be migrated to the new version and then it was sent back. The upgrade path for third-party and custom addons was not defined. And since it is Odoo, everything is in that database: from employee's time tracking to customer support chats, from stock info to accounting data, from e-mail address…
You can crypt the data before sending to the upgrade platform. Before it was an external script, and since Odoo 16 you can use the `oboo-bin obfuscate` command, before running the upgrade script. See `./odoo-bin obfuscate --help` to check how to crypt your custom data and uncrypt after upgrade. It's not perfect (crypt specific columns rather than full DB) but, unfortunatelly, to operate our upgrade service, we need a…
But - I can't wrap my head around why an on-prem customer cannot be allowed to run the upgrade scripts on-prem.
I have almost lost customers to it, and it's a super big headache delaying the upgrade process for both political and technical reasons.
Having tried to discuss the options and reasons with both Odoo support and employees at OXP has been an almost Kafkaesque experience.
Please explain to me like I am 5 years old.
Earlier quoted context omitted.
You can crypt the data before sending to the upgrade platform. Before it was an external script, and since Odoo 16 you can use the `oboo-bin obfuscate` command, before running the upgrade script. See `./odoo-bin obfuscate --help` to check how to crypt your custom data and uncrypt after upgrade. It's not perfect (crypt specific columns rather than full DB) but, unfortunatelly, to operate our upgrade service, we need a…
Small partner here who absolutely love Odoo for what it is and you can make it to be. But - I can't wrap my head around why an on-prem customer cannot be allowed to run the upgrade scripts on-prem. I have almost lost customers to it, and it's a super big headache delaying the upgrade process for both political and technical reasons. Having tried to discuss the options and reasons with both Odoo support and employees…
1/ Upgrade are super complex: requires a service, not just a script
2/ We used it to monetize Odoo Enterprise
Upgrade: Even after 1000+ upgrades, we still run into issues regularly as every environment is different (set of modules, customizations, community apps, ...). So we need to test the database, and fix scripts when necessary. If we would just provide scripts, it would cost us a lot in support for issues... and a bad customer experience. At least, by having the control we can ensure a smooth customer experience; it just works - and you don't see everything we do behind. (most of the time)
Monetization: The open core business model is hard, when your goal is to do a maximum open source. Our main competitor being Odoo Community, we charge 5x less than competitors for a better software. (25€ vs 180€)
So, we had to pick a few apps and services to monetize Odoo Enterprise, like the accounting app, or the upgrade service.
Fortunetally, there is OpenUpgrade (scripts from the community) so that there is no lock-in on the upgrade. (you spend time with open-upgrade or go to Enterprise and we do it)
Earlier quoted context omitted.
Small partner here who absolutely love Odoo for what it is and you can make it to be. But - I can't wrap my head around why an on-prem customer cannot be allowed to run the upgrade scripts on-prem. I have almost lost customers to it, and it's a super big headache delaying the upgrade process for both political and technical reasons. Having tried to discuss the options and reasons with both Odoo support and employees…
2 reasons: 1/ Upgrade are super complex: requires a service, not just a script 2/ We used it to monetize Odoo Enterprise Upgrade: Even after 1000+ upgrades, we still run into issues regularly as every environment is different (set of modules, customizations, community apps, ...). So we need to test the database, and fix scripts when necessary. If we would just provide scripts, it would cost us a lot in support for is…
Make it an encrypted binary for all I care, just allow us to run it on-prem.
Edit-due-to-pinky07-reply-edit:) 1+2 - I get all that. Perhaps provide enterprise customers with a GitHub repo to the upgrade scripts? Require the same subscription key like for Enterprise proper. Then you can continue to iterate on the scripts while still giving customers who wants (and pays extra!) for it as a white glove service to run it on their own servers.
Might be that me and some of my customers are old-school "server huggers", but I think it is holy to be able to decide on which CPU and disk my DB is processed on.
Why not Dolibarr?
Because no one knows it. Are you using it?
Similar to Odoo in a lot of point but full opensource, more affordable than Odoo and easier to use and customize. Has less external addons (1200 vs 40000) than Odoo but external addons are rarely required. Odoo would be a better choice if you have a very large company with an internal team of developper, Dolibarr will be easier and cheaper if you have less than 5000 employees.
Disclaimer: i'm on old Odoo integrator, now Dolibarr developer.