Odoo 19's AI is a genuinely good piece of engineering — Ask AI on every screen, agents that learn from your documents, fields that fill themselves. If you are on Odoo Online 19, switch it on today.
OdooBridge Agent solves a different set of problems. What happens when AI changes real data. Who can see what it did, and prove it. How any of this works on Odoo 16, 17 and 18. And the two-thirds of an employee's day that happens outside the ERP entirely.
Not a replacement for Odoo AI. Most companies run both.
None of these are things Odoo's AI set out to do. All of them are shipped and in use today.
It drafts the change, shows exactly what will happen, and waits for a person. Odoo's own docs say their AI tools execute unconditionally.
Who asked what, when, and the values before and after — per employee, scoped by role, ready for an auditor.
Start hosted in minutes. If and when you need it, move to your own infrastructure — then credentials and audit log never leave it, and it works air-gapped with any model, including one on your own hardware.
Odoo's AI exists only in version 19. No migration project needed to start using this one.
Build the board deck from live figures, read a scanned delivery note, generate images and video, pull statements off a supplier portal.
WhatsApp on your own number, Claude, Cursor, our desktop app, or a scheduled digest nobody has to ask for.
Adding fifty employees costs nothing. Odoo's AI is priced per user, plus usage credits their pricing page lists as not included.
This is the single biggest difference between the two products — and it is the step Odoo's framework does not have.
In plain language
Nothing saved yet
Preview, with warnings
Or you don't
Before & after values
With Odoo's AI server actions, a tool “will execute unconditionally, unless the code itself prevents it” — there is no stop.
Honest about the overlap: on asking questions inside Odoo, Odoo's own AI is at least our equal and better integrated.
| Capability | Odoo 19 AI | OdooBridge Agent |
|---|---|---|
| Ask questions of your records | ✓ Yes | ✓ Yes |
| Totals, comparisons, graphs | ✓ Yes | ✓ Yes |
| Draft text inline in Odoo fields | ✓ Yes | ✗ Use Odoo's |
| Document sort, voice transcription | ✓ Yes | ✗ Use Odoo's |
| Approval before a change is saved | ✗ Executes unconditionally | ✓ Drafts, previews, waits |
| Audit trail of AI activity | ✗ Not documented | ✓ Every call, per employee |
| Restore what was changed | ✗ No | ✓ From recorded values |
| Runs fully private / air-gapped | ✗ Always calls out | ✓ Your infrastructure |
| Choice of AI model | ~ ChatGPT or Gemini | ✓ Any, incl. local |
| Odoo versions supported | ~ 19 only | ✓ 16 – 19 |
| Work beyond Odoo — decks, images, video, web | ✗ Odoo only | ✓ Included |
| Channels — WhatsApp, Claude, Cursor, scheduled | ✗ Odoo's UI | ✓ All of them |
| Adding a business action | ~ Write Python | ✓ Allow-list, no code |
| Pricing axis | ~ Per user + credits | ✓ Per instance |
Odoo's agent is an assistant inside Odoo. Ours is a full AI assistant that happens to be fluent in your Odoo — so the request doesn't stop at the ERP boundary.
The moment employees can ask an AI about company data, Finance, IT and Legal each arrive with a question. These are the answers — and they are the reason enterprise buyers choose this over a chat box.
Reads are logged too, so “what is my team actually asking the AI about our data?” has an answer — per person, per day.
Resolved from each user's own Odoo security groups. Staff see their own activity; managers and admins see wider. Enforced in the query layer, not the client.
Before and after values on every committed change†, a web view, CSV export, and conversational queries over the trail itself.
Scoped keys cap what a team or integration may do and how much it may use. Deletes off, business actions allow-listed.
The connected Odoo user's rights are the ceiling. Restricted data returns an explicit refusal with the reason, never a quiet workaround.
Because the previous values were recorded, a wrong change can be restored from the trail rather than reconstructed from memory.
† Value capture runs where the log stays on your own infrastructure — private and desktop deployments. On our hosted service the trail records who, what and when, but not your field values, because we would rather not hold them.
The point isn't that one is cheaper today — it's that one bill grows with every person you hire and the other doesn't.
Illustrative shape, not a quotation — the vertical axis is deliberately unlabelled because your Odoo list price and AI usage vary. What is fixed is the shape: theirs is a slope, ours is a line.
$49/month per Odoo connection. Fastest way to start.
$149/month per production instance. Staging free.
From $499/month. Scoped and deployed with you.
The long tables and the sourcing, folded away so they don't get in the way.
“If a tool is called by the AI server action, it will execute unconditionally, unless the code itself prevents it.”
“The server action does not enforce business rules, modify records directly, or guarantee the correctness of the operation.”
Odoo 19 documentation — Productivity → AI → AI server actions
With Odoo's agents, safety is something a developer builds per tool, in Python. Miss a check in one server action and the AI can act on it. With OdooBridge Agent the controls sit in the bridge, once, and cover every tool your team will ever use.
| Control | Odoo 19 AI | OdooBridge Agent |
|---|---|---|
| Default posture | Acts if a tool is attached | Read-only until writes are deliberately enabled |
| Before a change is saved | Executes unconditionally | Drafts, previews, waits |
| Business actions | Any server action you expose | Allow-list only, never arbitrary code |
| Deletions | Possible via a tool | Off by default; dry-run first |
| Duplicate protection | Your code's job | Built in |
| Odoo user permissions | Apply | Apply — the user's rights cap the AI |
Shipped capabilities, not a roadmap. Each becomes a business operation once it can read and write your ERP in the same breath.
| Family | What it does | What that means at work |
|---|---|---|
| Documents & files | Read, write, patch, search | The deck, the spreadsheet, the PDF — from live Odoo figures |
| Code execution | Runs code in a sandbox | Reconciliations and reports Odoo has no screen for |
| Images | Generate and analyse | Product visuals; read a scanned invoice or delivery note |
| Video | Generate, edit, extend | Product and training clips without a production cycle |
| Browser automation | Navigate, click, type, extract | Supplier portals and filings with no API |
| Web research | Search and extract | Enrich a lead, check a supplier, price the market |
| Scheduling | Its own scheduler | Digests that run whether or not anyone opens Odoo |
| Work tracking | Kanban, to-dos, memory | Keeps multi-step work straight across days |
| Delegation | Spawns sub-agents | Long jobs split and run in parallel |
| Computer & terminal | Desktop control, processes | The legacy tool with no integration at all |
| Skills | 14 Odoo skill packs | Your procedures become things it knows how to do |
WhatsApp on your own number: link it once by scanning a QR code, the way WhatsApp Web works, then ask your Odoo from the chat with yourself. Anything that changes Odoo needs a typed confirmation first. For a public company number, that is the Enterprise offering on the official WhatsApp Business API with an allow-list of who may talk to it. Also Discord, Feishu documents and drive, any MCP client, and scheduled delivery.
The WhatsApp channel attaches as a linked device, the same way WhatsApp Web does. It is not an official WhatsApp product, and one channel may be active per account at a time.
Once employees can ask an AI about company data, three questions arrive from Finance, IT and Legal. Odoo's documentation answers none of them for agent activity.
| The question | Odoo 19 AI | OdooBridge Agent |
|---|---|---|
| “Who asked what, and when?” | Not documented | Every tool call recorded, reads included, against the authenticated Odoo user |
| “What changed, exactly?” | Not documented | Before and after values on every committed write† |
| “Can we put it right?” | No | Restore from the recorded values |
| “Can a junior see everyone?” | — | No — scoped by role from Odoo security groups, server-side |
| “A report for the auditor.” | No | Web view, CSV export, conversational queries |
| “Cap what a team can do.” | Credits, per database | Scoped keys with action and usage limits |
† Value capture runs where the log stays on your own infrastructure — private and desktop deployments. On our hosted service the trail records who, what and when, but not your field values, because we would rather not hold them.
A comparison that concedes nothing is a brochure. Use Odoo's AI when:
Most companies end up running both. Anyone telling you to rip one out for the other is selling, not advising.
You bring your own provider key and pay the provider directly, at cost, with no margin from us — Claude, ChatGPT, Gemini, OpenRouter, or a local model.
Odoo supports ChatGPT and Gemini only. On Odoo Online, Odoo supplies the service through in-app-purchase credits, which their pricing page lists as not included in the plan. On Odoo.sh and on-premise you must supply your own OpenAI or Gemini key — the same arrangement as ours, minus the choice of model.
We do not train on your data, and on the private and desktop deployments we never receive it. Beyond that your data is governed by your chosen provider's terms — itself an argument for picking your own provider, or running a local model where the question does not arise.
Tap a question to open the answer.
For asking questions inside Odoo, you may not — Odoo's is right there and well built. This earns its place when one of four things becomes true: the AI will change data and that needs approving and proving; the data cannot leave your infrastructure; you are on Odoo 16, 17 or 18, where Odoo's AI does not exist; or the job doesn't stop at Odoo — a deck, a document, a portal, WhatsApp.
Neither. They run side by side and never touch each other — we install nothing inside Odoo and connect over Odoo's standard external API, the same way any integration does. Keep Odoo's AI for drafting in fields, sorting documents and transcribing meetings; use this for work with consequences or work beyond Odoo.
The design assumes it will. Writes are off until you switch them on; business actions run from an allow-list rather than arbitrary code; deletes are off by default and preview first; a change is drafted and shown before it saves; and once committed it is in the trail with the values as they were. A wrong change is visible, attributable and restorable.
Odoo's documentation describes the other posture: a tool “will execute unconditionally, unless the code itself prevents it”.
No. Approval before writes, the allow-list, deletes-off, Odoo permission enforcement and the audit trail are the same on every deployment, including hosted. Self-hosting changes where the data lives, not how governed it is — and it adds before/after value capture, which we deliberately do not do on our hosted service.
Most customers start hosted in minutes and move later, if ever.
Any — Claude, ChatGPT, Gemini, OpenRouter, or a model running on your own hardware. You bring your own provider key and pay the provider directly at cost; we take no margin on tokens.
Odoo supports ChatGPT and Gemini only. On Odoo Online the AI service comes from Odoo through in-app-purchase credits, which their pricing page lists as not included in the plan; on Odoo.sh and on-premise you supply your own OpenAI or Gemini key.
Not by us. We do not train on your data, and on private and desktop deployments we never receive it at all. Beyond that, your data is governed by the terms of whichever provider you choose — which is an argument for choosing your own, or running a local model where the question does not arise.
Hosted: minutes. You get a token, paste one line of configuration into your AI client, and point it at your Odoo — nothing is installed inside Odoo and no module is deployed.
Private, on your own infrastructure: one container and an environment file, so an afternoon at most for someone comfortable with Docker.
Yes. It reads your live schema rather than assuming a stock Odoo, so custom fields and custom models are visible to it and answers reflect how your Odoo is arranged. That is also why it works across Odoo 16 to 19 without a version-specific build.
Quite a lot, and all of it centrally. Writes on or off; which business actions exist at all; deletes off; which models may be touched; per-key limits on actions and usage. Above all of it sits the connected Odoo user's own permissions — give that user read-only rights to Sales and Invoicing and nothing else is reachable, whatever anyone types.
No. Pricing is per Odoo instance rather than per user, which tends to suit smaller teams best — a ten-person company pays what a two-hundred-person company pays. The governance features are what larger and regulated buyers come for, but they are on by default for everyone.
A token and a live demo Odoo, or attach your own. Nothing is installed inside Odoo, and it works on 16 through 19.
Odoo capabilities described here are drawn from Odoo’s own published documentation — Productivity → AI (overview, agents, server actions, API keys), the Odoo 19 release notes and the Odoo pricing page, August 2026. Where that documentation is silent on a control, this page says “not documented” rather than asserting absence. OdooBridge Agent capabilities are as shipped and verified in the product.