Hey there,
In the same nineteen days, Odoo's website builder learned to take orders in plain English, and Odoo cut your staging branch lifetime in half without sending an email. One makes the demos better. One makes the implementations harder.
Odoo Rewrote the Docs at 6am
On a Tuesday morning in early May, Odoo cut Odoo.sh staging lifetime from 90 days to 30. The policy did not arrive in your inbox. There was no blog post. No release note. No heads-up from your account manager.
Commit 69625b5 by Sam Degueldre, titled "adapt documentation to new staging lifetime," rewrote the single sentence that defined the policy.
The old line: "Databases created for staging branches are intended to last up to three months. After that, they can be automatically blocked without prior notice."
The new line: "Databases created for staging branches are automatically deleted after one month. To use the branch again, you must rebuild it."
The word "intended" is gone. "Blocked" became "deleted." The doc was updated the same morning the policy went into effect, with no runway, no opt-in, and no explanation.
It took seven hours before any partner noticed.
Fabrice Henrion replied on two threads on behalf of Odoo. His defense, in full:
(1) "1 build represents 1 code change. It never happens that you need 30 days to test a code change."
(2) "There are 30 product owners (and hundreds of developers) at Odoo SA that use runbot builds all day every day without problem and those expire within a couple hours."
(3) "If partner-specific configuration is so time-consuming, the correct practice is to put it in the demo data of your module."
Each quote argues partners are testing wrong. None of them engages with what partners actually do.
What the defense does not say: why the policy changed. The candidates are all conjecture: infrastructure cost, ISO 27001 data retention posture, license discipline against staging running as a second production instance. Nobody at Odoo has said which one it is. Fabrice defended the new rule without explaining where it came from.
The community filled in what the defense left out.
If you run an Odoo.sh staging branch: treat the May 31 banner as real, plan the rebuild, and put that timeline in front of your client now.
The Bottom Line
Odoo runs the infrastructure and gets to set the rules. But when the rules change overnight with no explanation, the silence is itself a policy statement. Partners who treat this as a true partnership will keep being surprised. Partners who treat it as a vendor relationship, with the constraints that implies, will be less so.
Odoo 19.3 Can Vibe Code a Website. Dynamics Has Autonomous Agents.
Odoo 19.3 shipped in May. No specific day on the release notes page.
AI record management. You can now tell Odoo in plain language to create or update a record. The system interprets the instruction and makes the change. It is the database responding to a sentence, not a smarter autocomplete.
Website design via chat. The website builder now accepts plain-text prompts: "make me a modern drone website with a green theme," "create a clean service-focused homepage." Odoo calls this "vibe coding." Fabien reposted a demo to 199 reactions, his highest amplification of the period.
Offline mode. All apps work without a connection and auto-sync on reconnect.
Payments. Mollie, ACH, and Redsys tokenization (cards on file, mandates, subscriptions).
Localizations. Saudi Arabia ZATCA, Hong Kong, Egypt, Dominican Republic, and 27+ more.
Industry packages. Pet Groomer. Agri-Equipment Rental. (More vertical entry points, more reasons for a first conversation.)
Fabien also reposted William McMahon's post about Claude integration on Odoo.sh (281 reactions on the original). In a period where Fabrice posted only one R&D peek compared to 11 in the prior 15 days, Fabien is doing the signal work with two AI-forward reposts. The message being amplified: AI is baked in now, not bolted on.
Now to other news:
Microsoft shipped Dynamics 365 Business Central 2026 Wave 1 in April. The headliners are autonomous agents: a Payables Agent, a Sales Order Agent. These replace tasks, not assist them. Microsoft also released an "AL MCP" server, meaning coding agents can now develop BC extensions autonomously. The deepened Shopify integration is a bonus.
Salesforce confirmed support for Google's Universal Commerce Protocol via Agentforce Commerce. Salesforce merchants will get native UCP checkout across Google AI surfaces. Odoo still has no confirmed UCP integration.
Here is my read: Odoo is building AI into the data model and the interface. Microsoft is building AI into the workflow and the decision layer. Interface AI wins demos. Workflow AI wins renewals. Odoo 20 ships in October at Odoo Experience Brussels (Sept 24–26). That is when we find out which bet paid off.
The Bottom Line
Odoo 19.3 ships features your clients will notice and non-developers can actually use. But autonomous agents in Business Central mean Odoo's AI story needs to be more than interface polish by October. I'm watching the Odoo 20 roadmap for workflow automation, not just prettier prompts.
