Claude Code Appears in Odoo.sh, €650M on the Board, and a Module I Shipped in Two Days

• 19.2 is live on Odoo.com: Ray Carnes confirmed Odoo.com itself flipped to 19.2 on 4/14. New customers got it 3/9, the release notes landed 3/12. Odoo 20 is dated: September 24–26 in Brussels.
• Partena + Deloitte + Lyon: Fabien announced a Partena Professional partnership sized at "several hundred thousand payslips a month", Deloitte Digital Austria picked up Odoo, and Odoo is opening a Lyon office June 1 with 80 hires to meet France's Sep 2026 e-invoicing mandate.
• Numbers drop: €650M billing revenue, 42% ARR growth, nearly 7,000 employees, per Odoo's own Sep 2025 results post. Stated target: €1B by 2027, 10,000 employees in 2026. Fabien's other flex: 2% of all open-source Python code is Odoo. LLMs are training on it whether Odoo charges for it or not.
• Claude Code inside Odoo.sh shipped. I tested it. Three sessions, three meltdowns. The verdict post and blog writeup.
• I shipped a module: Mail to Blog, one click turns a sent Odoo mailing into a draft blog post. Built it because every newsletter I sent was aging out of inboxes with zero SEO residue. Running Odoo 18 with Email Marketing and the Blog module? Go grab it.

Hey there,

Another installment of my semi-regular Odoo ramblings. This email is sent via Odoo, so feel free to opt-out (I won't be offended).

Quarter's been loud. Louder than any since I've been paying attention. €650M billing revenue and 42% ARR growth on the scoreboard, a Deloitte partnership, a new Belgian payroll beachhead, 19.2 flipped live, Claude Code quietly landing in Odoo.sh, and Fabien on LinkedIn at least once a week flexing the AI numbers.

The question I keep coming back to, and the one that organizes this issue, is simple: who is all of this actually for?

Because the numbers point one way. My last month using the product points another.

The News

19.2 is the real thing, and Odoo 20 has a date. Release notes dropped 3/12. New customers got it 3/9. Odoo.com itself cut over on 4/14. That's the tell — Odoo eats its own cooking before it pushes upgrades to paying customers. Odoo Experience 2026 is locked for September 24–26 in Brussels, which means Odoo 20 lands then and the GA patch follows a few weeks later. The pre-released briefing language emphasizes agentic AI and native financial forecasting. Translation: the chatbot-style copilots shipping today are scaffolding for something that actually executes work in 20.

Partena is the quietly huge deal. Fabien said the quiet part loud: Odoo's biggest current customers run 5,000–10,000 users, and the Partena partnership is sized at "hundreds of thousands of payslips a month." This is not a logo grab. It's Odoo reaching for a segment — Belgian HR outsourcing — where the incumbent is SD Worx and where payroll compliance alone is a moat. If this works, the Odoo go-upmarket thesis gets a real reference customer.

Deloitte Digital Austria adding Odoo to its portfolio is the other tell. Deloitte does not take on ERPs for fun. An Austrian practice betting billable hours on Odoo is a bet that mid-market Europe is flipping. Combine it with Lyon, Odoo's new French HQ, led by Joséphine Vander Linden, 80 hires year one and several hundred within three years, positioned squarely for France's September 2026 e-invoicing mandate, and Odoo's European quarter has more signal than any single product drop. France is reportedly Odoo's #2 market behind the US.

The AI highlight reel. Fabien and Fabrice Henrion turned March and April into a rolling AI demo. In no particular order: create a purchase order from a customer quotation, generate a project and tasks from a spec doc, enhance and generate product images for ecommerce, pick up WhatsApp conversations from CRM, translate Odoo in-app and in-context, and dynamic lists in Odoo Sheet. Each one separately is a nice demo. Together they are a thesis: Odoo is going to out-ship every AI-for-ERP vendor by putting the AI inside the model you already paid for.

Fabien's unfair-advantage post put the whole case in one line: "2% of all open-source code in Python is Odoo. LLMs are already well-trained on Odoo." That is the bet. That is also, not coincidentally, the same bet that makes Claude Code plugged into Odoo's codebase the next obvious move.

Which brings me to the thing that actually happened to me this month.

On 4/2 I noticed a new Claude Code message in my Odoo.sh dashboard. Zero documentation. No announcement I could find. Just a new surface in the UI and an invitation to figure it out.

So I spent three sessions figuring it out. Here's the verdict, and it is not flattering.

Session one: skipped the /init step, watched the environment's CSS collapse, had to abandon. Session two: got it to generate new pages, which Odoo then 404'd on because the URLs were wrong. Session three: tried three separate times to commit changes to staging, all failed. In VS Code with Claude Code, that same commit action is a single keystroke.

The wins were narrow and real: Claude cleanly updated missing title tags and meta descriptions, and modified an H1 with the right fonts. Everything else was friction. Terminal-only interface means no image paste, no markdown file reference, no screenshot handoff. Session state evaporates on restart. And most damning, you don't have a local copy of your site to test against.

That is not a deal-breaker for a developer. A developer is already working in VS Code, already has a branching workflow, already has local environments. They don't need Claude Code in the Odoo.sh terminal.

The person who does need it — the non-developer Odoo operator who has a business problem and wants to describe it in English and watch it get solved — hits the terminal wall in the first thirty seconds.

That is the gap. And it is the same gap that shows up in every other Odoo AI demo if you squint.

The Bottom Line

The technology is capable. The product isn't ready for the person who most needs it. Stick with VS Code + Claude Code + the odoo-theme-fix skill. That is the workflow that redesigned my homepage in under 20 minutes. The Odoo.sh version will get there. It isn't there yet.

Three quick road stories make the point.

Miami, 3/12. Ten minutes with a business owner who could not figure out how to update a PO sequence. Fix took two minutes. She had been stuck for days and was already working with a partner. Dallas, before that: someone stuck on accounting for employer retirement contributions. Philly, 3/24, my sixth roadshow — about 50 at the Tuesday demo, 40 at the Wednesday accounting academy. Most had never touched Claude anything. They wanted to stop leaving leads on the table and stop re-keying data across eight disconnected platforms.

These are the people the AI story needs to serve. They are also the people who will not try a terminal-only beta hidden in an Odoo.sh dashboard.

The in-product AI demos (generating POs, projects, images) move in the right direction — they land where the functional user already works. The Claude Code integration moves in the wrong direction: a developer tool with a developer UX dropped into a system whose users are functional.

What's not being said in any Fabien highlight reel: which of these AI features a non-developer can actually use today, without a partner. That's the number I'd like to see on the next Odoo financial slide.

The Bottom Line

Odoo has the distribution, the dataset, and the momentum to win AI in mid-market ERP. It will win it by translating the tech for the functional user, not by handing them a terminal.

I built a module. Mail to Blog, shipped 4/13. One click turns a sent Odoo mailing into a draft blog post on your Odoo website. Pick the blog, click the button, review the draft, publish. I built it because every newsletter I sent — including the one you're reading — was dying in inboxes with zero SEO residue. The hole was obvious. Nobody was filling it. Odoo 18 + Email Marketing + Blog module required. The point here is not the module. The point is: I am not a developer, I used Claude Code + VS Code, and the whole build fit around a normal work week. That is the AI-for-Odoo story that actually scales.

The AI rubric. If you are evaluating AI tools for Odoo, and by my count there are already 12 of them chasing this market, stop asking "is it a module or a GitHub repo?" That question answers how to install. It does not answer whether you should. Five dimensions that do: Outcome Type, Primary Beneficiary, Deployment Method, Data Scope, Trust Model. The rubric is on the blog. Use it before the next partner pitches you something AI-flavored.

Plain-English Odoo primer. For the people in your network still asking "okay but what even is Odoo", here is the answer I wish I'd had on day one. Community vs Enterprise, hosting options, the $60–70/mo Odoo.sh floor, why monthly billing is a 30–40% premium over annual, how the partner ecosystem actually works. Send it to the person who should read it.

OCA crowdfunding. The Odoo Community Association is running its funding challenge. Three options: join the group, volunteer, pledge. I did all three. If you run a business on Odoo Community, the OCA is the reason your modules still work next year. Kick in.

Next stop: the next roadshow. I've done Phoenix, Tucson, Dallas, Austin, Miami, Philly. Next stop is Boston! The pattern holds. Every city, I walk away with one person whose business changed because they learned something that took two minutes to explain. Come find me at the next one. I'll buy the beer.

Cheers!

Darren from 19 Prince

PS. Random music recommendation. Checkout the Ratboys new album, Singing To An Empty Chair