Odoo 20 AI in Saudi Arabia: Agents, MCP and Practical Automation

If your finance team already issues Phase 2 e-invoices from Odoo, integrated with ZATCA's Fatoora platform and carrying 15% VAT, you have the right starting point. Odoo 20, released in September 2026, places AI on top of that setup rather than inside it. The same release sends invoices to ZATCA from the Send wizard, with submission history and batch sending, and ZATCA timeouts or outages no longer block invoicing. Compliance stays with the Saudi localization, not an agent.

An AI agent in Odoo 20 has three ingredients: a prompt describing its role, skills, and sources. Skills are the new name for what Odoo used to call topics: sets of instructions and tools for a given context. Odoo's documentation is clear that an agent with no skills can only provide information; it cannot complete tasks or change the database. Add the Create Records or Update Records skill and it can act on your data.

What this release adds:

• Agents create records, including from an uploaded file of instructions such as a PDF, and update existing records.
• Automated and scheduled actions can call an agent, agents can adjust themselves to their use case, and automation chats show how each run went so you can ask for changes.
• Agents report specific live progress instead of a generic "AI is thinking" message.
• Questions, permission requests and suggestions arrive with buttons you click to answer.

All of it comes with one condition: every AI feature consumes credits bought through Odoo's IAP service.

Here is what is new in Odoo 20, grouped by where you meet it.

• Agents: ask about a file while previewing it, upload files and link documents in a chat, dictate requests by voice, add options from the + menu, write default prompts with dynamic values, and manually ask an agent to reprocess its sources so it uses their latest version. Sources themselves (PDFs, web links, Documents files, Knowledge articles) and Restrict to Sources were already available before this release.
• Automatic model selection: you choose an AI provider and Odoo picks the best model for each task.
• Website: the AI Website Assistant builds pages, forms and menus through chat, and the editor marks every block it generated or changed. AI can also help improve a page's SEO.
• eCommerce: from the Shop page, generate product images or change a product's name, price or description.
• Marketing: agent-generated images and enriched buttons for websites and mailings, AI-written social posts and AI-assisted campaign setup.
• Helpdesk, Documents and ESG: similar-ticket detection with suggested answers, AI file renaming and AI-assigned emission factors.
• Live Chat: supported records an agent mentions can appear as clickable cards.

MCP needs a plain explanation. An external AI tool connects to your database at its address followed by /mcp, using a user's API key, and works with that user's permissions, no more.

On bilingual Arabic and English sites, the AI-content marker shows reviewers which blocks need a human check in both languages.

The useful question is not what the AI can do, but which step a person still signs off. Examples that fit Saudi teams:

• Sales: a live chat agent answers routine website questions; for custom pricing, contracts, implementation work, demo requests or low confidence, it collects contact details and creates a lead for your team. Managers can also get agent-built pipeline views filtered by quarter. Checkpoint: a salesperson owns every lead the agent creates.
• Customer service: Helpdesk suggests answers from similar tickets, and an agent restricted to your Knowledge articles answers from approved content. Checkpoint: support staff choose, edit and send each reply.
• Finance and admin: an agent creates customers and draft invoices from a PDF of instructions. Checkpoint: an accountant reviews before posting, including the identification type (national ID, Iqama or GCC ID) and the Building and Secondary Numbers, which Odoo 20 limits to four digits. E-invoices go to ZATCA from the Send wizard; AI does not handle that compliance. Bill line prediction, which pre-fills lines from your bill history, is a separate Accounting feature, not an agent task.
• HR: GOSI integration and the updated end-of-service rules stay with Saudi payroll, not with an agent.
• Management: read-only reporting over MCP with the five tools exposed by default.
• Marketing and web: Arabic and English pages, product edits, images, social posts and campaigns. Checkpoint: a reviewer fluent in each language approves anything public.
• Back office: AI renaming of uploaded files in Documents, or an AI server action whose tools hold your business rules.

Odoo 20 gives you real controls. Set them on purpose.

• Grant skills on a least-privilege basis. An agent that only answers questions needs no skill that writes.
• Turn on Restrict to Sources, and remember that files uploaded in a chat affect only that conversation unless they are added as sources.
• Approve actions through the permission buttons, and use the tool-call limit confirmation to check the work so far.
• Agent conversations are stored for up to 30 days after the last message. Review them within that window.
• For MCP, use a dedicated user with limited access rights, give its API key the MCP scope and a short expiry, and store the key safely, because it is shown only once.
• Expose extra MCP tools deliberately. By default only five tools for reading models, fields and data are available; anything else must be ticked Available in MCP. The Readonly Tool tick only lets the client run a tool without asking, so reserve it for tools that truly do not write.
• Put business rules in tool code. Odoo's documentation warns that the AI step does not enforce them and a tool runs unconditionally unless its code prevents it.
• Use the simplified access rights and the user-group change log in each user's chatter for audit.

On language, the release notes make no claim about Arabic output quality. Test with your own Arabic documents and have a person review anything a customer will read. Finally, check these settings against your local data-protection obligations.

AI in Odoo 20 is a usage cost on top of your subscription. Odoo's pricing page lists IAP credits among what plans exclude, and places agentic AI and External API under the Custom plan; confirm with us what applies to you.

Odoo's AI service in the IAP store sells credits in packs of 10, 100, 500 or 1,000, all listed at the same rate per credit at the time of writing, and starts you with 20 free credits. Check the current rate from your database before you budget in riyals. Enterprise subscribers also get free credits to test IAP features. Usage varies by feature, task complexity and request size, so there is no fixed price per action. Credits belong to one service and one database, do not expire and can be refunded on request within 30 days if unused. Auto-refill is optional, an Email Alert Threshold emails the users you choose when the balance falls below the amount you set, and if credits run out, AI features stop until you top up.

Budget credits as an operating cost and run a 30-day pilot:

• Pick one use case.
• Set up one agent with narrow skills and restricted sources.
• Set the alert threshold.
• Check usage weekly under Settings > Contacts > Odoo IAP > View My Services, or on the My Subscription page.
• Review the stored conversations, then expand.

Upgrading too? AI fits our usual path: assessment, a test copy, then training. METCH's Riyadh team offers a free consultation to plan it with you.