AI Agents in Odoo: What You Can Wire Up Today, and What v20 Changes

Odoo now ships real AI agent features, Odoo 20 is about to promise bigger ones, and most of what’s written about either comes from people who haven’t opened the source code. We implement Odoo for Australian businesses and run AI agents against it in production, so this is the practitioner’s version: what you can switch on in Odoo today, what you can wire up alongside it, and what to leave alone until it ships.

First, a working definition. An AI agent in Odoo is software that uses a large language model to do useful work in your database: answering questions about your records, drafting content, sorting documents and, within strict limits, acting through tools an administrator has approved. In practice that covers two different things: the agent features built into the product, and external agents you connect through Odoo’s APIs. The capability is different and so is the risk, so it pays to be precise about both.

The demand side isn’t speculative. MYOB’s research found 78% of wholesale distribution businesses plan to use AI inside their ERP, and wholesale is exactly the kind of business Odoo wins in Australia. The question we hear in discovery calls has shifted from “should we?” to “what’s actually real?”

What ships in Odoo 19 for AI agents today

Odoo 19, the current production release, includes a dedicated AI app, covered in the official Odoo AI documentation. We’ve checked what follows against the v19 Enterprise source code, because vendor marketing and shipped software aren’t always the same thing.

Ask AI is the headline: an assistant available across the database that answers questions in plain language, finds records and opens the right views. Its most important property is what it can’t do. The standard Ask AI agent cannot change your data. It will show you the report; it won’t post the journal entry.

Custom AI agents sit one level up. You create an agent, give it a system prompt and a response style, choose which large language model runs it, and attach knowledge sources it can search, like your product documentation or internal procedures. Then you give it topics: instruction sets with tools attached.

The tool design is the detail worth understanding, because it’s where Odoo quietly got the governance right. An agent’s tools are Odoo server actions, and only the ones an administrator has explicitly flagged as available to AI. The agent can’t grant itself new abilities. If nobody hands it a “schedule a follow-up activity” action, it can’t schedule one. That’s an allowlist, which is how agent permissions should work, and it’s the same principle we apply to every agent we build regardless of platform.

The same app also brings the assistive features: AI fields that fill themselves from context, AI server actions for automations, document sorting and data extraction, livechat agents for the website, AI drafting in email templates, and voice transcription. Our guide to AI in Odoo for Australian businesses walks through those feature by feature.

Two caveats. The AI apps are part of Odoo Enterprise, so Community sites don’t include them, though the API route below works for both editions. And what ships today is assistive: it answers, drafts, sorts and suggests. A native agent that runs a multi-step process across modules end to end isn’t in v19. That’s the v20 conversation.

The Odoo AI agents you can wire up from outside

Most of the practical agent value in 2026 comes from the second layer: an agent that runs outside Odoo, powered by whichever model you choose, working through Odoo’s API under a normal user account. The Model Context Protocol has become the standard way to make that connection, donated by Anthropic to the Linux Foundation’s Agentic AI Foundation in December 2025 and backed by the major AI vendors. MCP connectors for Odoo already exist from the community and the Odoo app store, and we build ours against the API directly.

Here’s the worked example we’re asked about most. A wholesale business receives purchase orders as PDF attachments, in a different layout for every customer. The agent watches the inbox, reads each PDF, matches the customer record, checks products and pricing against the price list, checks stock, and creates a draft quotation in Sales tagged for review. A salesperson opens the draft, corrects anything odd and confirms it. The agent never confirms an order itself. When it misreads a smudged quantity, and eventually it will, the mistake dies at the review step instead of shipping.

Two properties make this safe enough for a sceptical CFO to sign off:

• The agent has its own user account. Odoo enforces access rights on API sessions, so the agent sees exactly what that user role sees. No administrator login, ever.
• Writes arrive as drafts. Anything touching the ledger, tax codes, pricing or stock is proposed by the agent and posted by a person. The approval gate is the design, not a training-wheels phase.

This is the architecture from our broader guide to AI agents for Australian businesses, and Odoo is a good host for it: the API is mature, permissions are granular, and everything the agent does is inspectable.

What Odoo 20 changes, and what’s still roadmap

Odoo 20 gets unveiled at Odoo Experience in Brussels, 24 to 26 September 2026, with general availability expected after the event. Agentic AI is the expected headline: agents that execute multi-step work across modules natively rather than assisting inside one screen. We track what’s confirmed versus expected in our Odoo v20 roadmap breakdown.

Until it ships, it’s a roadmap. Nothing announced at a keynote should drive a 2026 implementation decision, and anyone selling you native “Odoo agents” as a present-tense product is describing slideware.

“The mistake we keep seeing is businesses pausing everything to wait for Odoo 20’s agents. The API is the agent surface today. Wire the workflow up now, run it drafts-first, and when v20’s native agents mature you’ll already have the data discipline and the approval habits they’ll need.”

Josh Craig, Director, Auboros

Our advice hasn’t changed: implement on the current version now, treat v20 as an upgrade decision once it’s real and stable, and let external agents cover the gap in the meantime. The work transfers. Clean data and approval workflows are exactly what v20’s agents will need too.

Running Odoo AI agents safely in Australia

Adoption is accelerating. The Australian Bureau of Statistics reports 12% of Australian businesses used AI in 2024-25, up from 1% two years earlier, and most of them have no written rules about what the AI can touch. That gap is what turns a useful agent into an incident.

The Australian framework is workable. The National AI Centre’s Guidance for AI Adoption sets out six voluntary practices, including human oversight and accountability. The Privacy Act is not voluntary: customer records in your CRM are personal information, and the OAIC publishes guidance on using commercial AI products. From 10 December 2026, privacy policies must also disclose the kinds of substantially automated decisions that significantly affect people. If an agent helps decide credit terms, that needs documenting before the deadline, not after.

For an Odoo database specifically, safe operation comes down to five controls:

• Role-scoped access. The agent runs as its own user with the narrowest access rights that still let it work. Odoo’s permission model does the enforcement if you let it.
• Approval gates on writes. Ledger, tax, pricing and stock changes are drafted by agents and posted by people.
• An audit trail. Log what the agent read, what it proposed, who approved it and when. Odoo’s chatter and server logs make most of this cheap.
• Sandbox first. Prove the agent on a staging copy of your database before it sees production.
• A named owner per agent. Someone reviews its permissions and output quality on a schedule, so access never quietly grows.

Where to start if you run Odoo

Start with the workflow that burns the most hours and has an obvious human checkpoint: inbound order entry, reconciliation exceptions and supplier chasing are the proven first picks. Fix the data the agent depends on, run it against a staging copy until its drafts are consistently right, then go live with the approval gate permanent. Add a second agent only once the first has an owner, a budget and a clean month behind it.

None of this needs to wait for a keynote in Brussels.

---

Thinking about AI agents for your Odoo database?

Auboros is a Brisbane-based Odoo Silver Partner that designs and runs AI agents over Odoo, drafts-first with human approval, for businesses across Queensland, NSW and Victoria. If you want to know what an agent could safely take off your team’s plate, book a free consultation. If the honest answer is “fix the data first”, you’ll hear that instead.