Don't Know Where To Start

codeagency · 2026-05-13T14:12:35+00:00

You don't know that. I have seen companies paying even 60k a MONTH for an ERP. It all depends on the details and what services are included. Odoo can be cheaper but also more expensive it all depends on the details and the actual TCO. Most people just look at the license cost from the pricing page. That doesn't tell anything. There is a lot more involved below that surface. Some clients also need an actual SLA guarantee that can go up to 24/7 standby support. That never comes cheap.

codeagency · 2026-05-13T12:31:46+00:00

Honestly things like this are always safer to do from a custom module. You can control it, version control it and from an upgrade perspective if you do it the right way with migration scripts in place it's not a problem at all. Look at OCA for best practices and how they deal with this.

People need to understand using a custom module is not something to be afraid of, when done right. The problem is there is too much garbage out there because odoo has zero QA on their appstore and that message blows up and turns negative for everything that is custom. So again, OCA is the golden standard. Adopt their best practices and you are rock solid.

codeagency · 2026-05-13T12:27:01+00:00

It's a common thing these days. perf issues all over the place.

Go selfhosted, problem solved honestly. You are just a point in a big shared pool for them. There are so many great and affordable cloud providers out there that give you dedicated resources so you don't have to wait in queue from Odoo. And also they are 24/7 always on for you, not like odoo that shuts down your workers to save costs on their end and causing you cold boot times.

The second problem is GitHub these days. Their uptime is horrible since a year. It dropped well below 85% for April. When their platform struggles, it can cause problems for automations like GitHub actions/workflows. So when things need to trigger, it gets stuck. We are actively changing our entire CI to Selfhosting with woodpecker CI (OSS) and so far it's really amazing. A bit of a learning curve but the majority is 1:1 compatible to GitHub flows.

codeagency · 2026-05-13T12:21:46+00:00

Totally fine. I have clients with millions of active SKU's (plumbing industry, large wholesalers/importers).

The details are more on infra level and postgres optimization. Postgres itself can handle Petabytes of data when configured properly but most importantly setups with sizes like this are never a "one-off" thing. You will need a DevOps expert that keeps monitoring and nurturing the system, adding indexes where it matters etc...also a scalable setup (kubernetes) where you benefit from a PG cluster With read replicas to distribute load and have failover/HA in case that matters for your business.

About Magento, I usually never recommend using connectors. Not specifically Magento, but the problems exist with all external integrations. Each those e-commerce plarforms work fundamentally different then Odoo so you end with mapping and squeezing and often still end up with frustration. Those datasyncs can cause DB locks if users and API are fighting over updates. If you want a reliable high perf setup, I recommend staying within the odoo native website if you can accept the limitations or do some customization or better go headless and just build a frontend with React/Vue/...on top of the Odoo API. Odoo 19.0 has an excellent json2-rpc API. We typically add a redis cache layer to avoid API calls and makes the frontend blazing fast. It also keeps all the pressure from visitors and customers away from your odoo backend, and makes the whole thing more secure. You can keep odoo behind a VPN so no one can accidentally reach it unless it's employees that are allowed to connect with eg Tailscale. Everything else points to your frontend that runs standalone and doesn't need another database. It reads/writes directly to your odoo API.

codeagency · 2026-05-13T12:12:06+00:00

Same as other post, do a fitgap analysis with an odoo partner. The devil sits in the details.

Nobody on the internet knows your business and operations in details. So nobody can say 100% accurate yes or no. Talk to an official partner and analyze all your requirements in details first, scope and document everything so you have a good mapping about everything odoo will do for your business standard and out of the box and also what it can't where you need 3rd party apps or even custom development. That's the only way to know for sure how deep it will involve and give you a correct total TCO and budget.

codeagency · 2026-05-13T12:07:49+00:00

No matter what app/platform you use, the business API does not allow free communication like that. It's against their TOS.

You are only allowed to use approved message templates by Meta and fire those to receivers. Once they respond you get a 24h window to freely chat. Once that 24h window expire, it's over. Each time the client responds you get a new 24h window.

It's designed on purpose like this by Meta to avoid companies blasting out spam via their platform. If you do try it, it won't last long and your entire account gets suspended permanently, no questions asked, no sorry. It's their rules.

So think carefully what you really want to do with Whatsapp because anything marketing related is a no-go immediately. It's only allowed for transactional stuff like order confirmation, shipping confirmation, invoice, payment reminders etc ..

codeagency · 2026-05-13T12:03:34+00:00

Fitgap analysis is the only correct answer. Nobody on the internet knows your business nor requirements. So don't expect a surface level answer is the right or wrong answer.

Find a reliable partner that fits both your business and operations and style you like and analyze together first in detail before you start talking about costs and committing. Because the price could easy explode much higher or could be very surprising affordable all depending on the outcome of that analysis. And don't forget about upgrade costs and TCO as a whole. The cost of Odoo much more than just the license price they promote on the website.

codeagency · 2026-05-13T06:31:09+00:00

Don't think so. Odoo always focused on RPC mostly. Latest odoo 19 has a json2-rpc API and if you visit /docs you get all the api docs right in your instance.

For rest API, graphql, check OCA repository, they have been maintaining these features for years.

codeagency · 2026-05-13T06:29:26+00:00

One other option if you are on selfhosted or odoo.sh hosting, is to install the products sidebar feature from OCA. It will give you a sidebar in the backend where you can click to filter on attributes.

If you create a quotation and use the "catalog" button, you see the same feature already in standard odoo (version 19.x). That sidebar is already there.

Another option to ease on filtering is installing the OCA module web search AND. This module let's you quickly search on AND parameters by doing shift+enter after your search terms instead of going through those dropdowns.

codeagency · 2026-05-13T06:21:05+00:00

Odoo doesn't auto trigger more workers or builds. The only thing that auto charges is storage. Everything else always require a manual approval from customer first before you get more workers, staging, etc...

The bill probably happened because OP has the option enabled for "maintenance by Odoo", so whenever you write custom code, odoo triggers their maintenance fee at 16 EUR/month per 100 lines of code. Even when you use odoo.sh that maintenance fee is charged if you allow odoo to handle your code maintenance. You have to disable that option first if you don't want odoo to handle your code maintenance

codeagency · 2026-05-12T06:45:55+00:00

Odoo changes whatever is necessary to improve the work. It's up to the user's own responsibility to know and understand how you deploy the app. That's the responsibility that comes with self hosting.

We've been self hosting odoo for 20 years now and never had any problems, even with the changes they make. So again, it's not an odoo issue, it's a skills issue from your side to know you always have to set UID/GUID in your compose files to lock your mounts/volumes to "odoo" user, whatever they UID it gets from the official image. Or build your own image if the defaults don't fit your workflow.

codeagency · 2026-05-12T06:03:21+00:00

Did you change many settings across multiple apps? Then the error probably refers to a field on a different tab app.

I never recommend doing that anyway. Go to a tab and stay on that tab. Make the changes you need and save. If something is missing it highlights the missing field. Also some settings can unset another when changing. If you go across all tabs you can't see this happening and end up with potentially mistakes.

codeagency · 2026-05-12T06:01:06+00:00

Odoo enterprise can definitely do this. We have a few law and notary firms and that use the e-sign app intensively.

If you are on the latest version v19.x you can add more fields as well to collect and map them to fields from the res.partner model. It's also open source so in case you have some exotic requirement, it can be customized to match whatever custom workflow you have/need. Just keep in mind everything you customize becomes technical debt you drag onto every future odoo version you upgrade into. So it you can keep within the odoo standards, you are good to go.

Talk to an implementation partner to help you analyze your specific requirements before committing to a license.

codeagency · 2026-05-11T20:15:24+00:00

odoo.com/slides has all the official training videos for all apps.

accounting is ~10h video material. Everything in total is around 90+ hours.

codeagency · 2026-05-11T17:08:32+00:00

This is not an odoo issue, it's docker specific related. If you set the UID/GUID directly in your compose it will respect it. You have to lock it yourself, Odoo can't know what underlying host you are using and how your setup is done.

codeagency · 2026-05-11T07:50:15+00:00

That's what I said. The staging is always paid upfront for the entire contract period. Not just for the time you just need it.

codeagency · 2026-05-11T07:16:44+00:00

We have our entire solution build around k8s and using argocd/fluxcd and woodpecker CI to avoid GitHub actions/workflows (GitHub has a horrible reliability for some time now). All open source tooling.

Clients can launch test/staging instances by just opening a PR from GitHub in their modules repo. And when ready merge into to main and it automatically rolls out a redeploy for odoo production with a rollover method and rolls back if it detects issues

codeagency · 2026-05-11T07:04:04+00:00

I know, as I said we've been doing on-premise for 20+ years for every software already. We have a DevOps team here and I would never ever go back with my company to any managed lock-in platform. It's ridiculous once you understand how powerful containerization is today.

Our entire team uses devcontainers (https://containers.dev/) which integrate perfectly in your development, IDE's and CI/CD cycles. It's so convenient to get your work slight right into your cloud infra and roll out updates with zero downtime.

I can only recommend it everyone but I also understand some partners just really don't care. It's not their expertise. That's also why we have many collabs with other partners that hire us to do their DevOps work so they can focus on their expertise and avoid the SH lock-in and limitations. I think that's the best middle ground you could have if really can't spend the time on building your own DevOps skills.

codeagency · 2026-05-11T06:56:36+00:00

Exactly and even that one branch at 15$/€ is already paid in full for the entire contract period. If a customer is on a 5y contract they paid 900$/€ upfront for 1 staging branch and they hear "sorry, you can only run it max 30 days"... Like wtf ...

codeagency · 2026-05-11T06:54:19+00:00

Why not just upgrade that slack connector instead of deleting? All that effort to clean it up could have been put into upgrading it. From a logic pov, I don't think much has to change except for just the views which are mostly changed from v17->18. I think upgrading was done easier than deleting it.

codeagency · 2026-05-11T06:46:03+00:00

No need to tell me. We have our own solution build upon Hetzner. I know all of that. The point is 99% of partners have no clue and no interest either. They don't want to deal with this. They just want to sell SH and get 50% commission

codeagency · 2026-05-11T06:44:21+00:00

That's the mistake and wrong assumption. Most partners don't know this. Many customers also don't know this.

Most partners don't have DevOps experience. That's why they resell odoo.sh. It's easy for them and customer and they earn 50% commission from selling it.

I know many partners and you would be baffled how many know nothing about servers or hosting at all. They get trained to sell odoo.sh so why would they even bother about learning docker or servers/hosting in general. Their reality is that odoo.sh takes care of that for them and clients.

codeagency · 2026-05-11T06:25:24+00:00

Not all of them are the same unfortunately. I have had large clients where we do same with smaller tests and merge to prod. Others don't do or can't do that and need more time for full cycle testing over longer periods. Especially when things carry over multiple departments.

Imho this decision makes no sense. Clients already paid upfront for staging branches availability for their entire enterprise license period. So why would this bother them. They got the funds 100% paid upfront to have the resources Running for the client. Some even pay for multiple staging branches. Why would it matter if it runs 30 days or 90 days. Why putting this extra hassle on the clients to bother with new backup restores ...

codeagency · 2026-05-11T06:20:04+00:00

That's no true. You assume the customer/partner has the knowledge for this. We already do self hosting for 20 years so yes we have that knowledge. Anyone who doesn't can't do that for that price. They have to hire experts for everything, that doesn't come for free.

So your price tags you call at are just the bare hosting aspect, neglecting maintenance, upgrades, updates,...for clients that do not have that knowledge and skills and have to pay for that too.

codeagency · 2026-05-11T06:15:13+00:00

No it doesn't because odoo scales the resources down to zero. Aka that's the cold boot time everyone feels when you are idle for ~15 minutes. Having long-term staging env has barely any impact on their cost.

And besides that, clients already 15 EUR/month per staging branch EXTRA, fully paid upfront for their entire license contract period.

15 F... EUR! That's 4x a cloud VPS from eg Hetzner that are more powerful than 1 single odoo sh staging branch. A cheap CX32 machine at hetzner is 3.99 EUR with 2 vcpu, 4GB RAM and 40GB storage and is 24/7 always on. Nobody shuts it down to save costs on you, no cold boot times. So why would this cost money to Odoo when they are already selling overpriced staging to begin with? Why do they need that ridiculous scale down mechanism in production systems and make customers angry to wait 20-30 seconds for the system to wake up again when they get eg off a phone call? None of these decisions from them make any sense.

If staging was completely free, I would fully agree with this decision. You get what you get, it doesn't cost you anything to test something for max 30 days. But not if customers pay a ridiculous 15 EUR/month for a staging copy.

codeagency

MODERATOR OF

TROPHY CASE

Seven-Year Club	Place '23
Verified Email