Odoo 20 AI in Jordan: Agents, MCP, IAP Credits and Safe Automation

If your finance team already sends invoices to JoFotara from Odoo, the first thing to know about Odoo 20, released in September 2026, is that its AI stays out of that flow. Your invoices, the 16% general sales tax on them and their submission to the Income and Sales Tax Department remain in the Jordanian localization, which runs on fixed rules. Odoo 20 improves that localization separately, for example by checking supplier details before sending and letting you fix errors in the Send wizard. None of that is AI. AI is an extra layer you switch on for specific jobs.

So what is an AI agent in Odoo 20? Picture three parts: instructions, skills, and the sources it reads from. Skills, called topics in earlier versions, are bundles of instructions and tools. Odoo's documentation says an agent without skills can only provide information; give it skills such as Create Records or Update Records and it can act on your database.

That is the real change in this release:

• Agents create records, including from an uploaded file of instructions such as a PDF, and update existing ones.
• Automated and scheduled actions can call an agent, and the automation chat shows how it handled each run.
• Agents show live, specific updates on what they are doing instead of a generic thinking message.
• Their questions, permission requests and suggestions reach the user as buttons.

One condition covers all of it: every AI feature in Odoo 20 consumes credits bought through Odoo's In-App Purchase (IAP) service.

Odoo 20 spreads AI across several apps. Here is where each piece lives:

• Agents: chat with an agent, send it files, ask about a file while previewing it, dictate requests by voice, and have it build views filtered by week or quarter.
• Connect Odoo to anything (MCP): external AI tools that support the Model Context Protocol connect to your database.
• AI Website Assistant (Website): build pages, forms and menus by chatting, add Unsplash or generated images, and point at a block with Select Elements.
• AI-assisted product editing (eCommerce): generate product images or change a product's name, price or description from the Shop page.
• Helpdesk: AI detects similar tickets and offers your team suggested answers.
• Documents: rename uploaded files with AI.
• Marketing: help setting up Marketing Automation campaigns, AI-written social posts, image generation for websites and mailings, and using AI to improve a page's SEO.
• Live Chat: when an AI agent answers website visitors, the records it mentions can appear as clickable cards.

MCP deserves a plain explanation. The Odoo user whose identity the tool will use creates an API key with the MCP scope and an expiry date, and the external tool connects to your database address followed by /mcp. From then on it works with that user's permissions and nothing more.

If your website runs in Arabic and English, the Website editor marks every block the assistant generated or changed. Use that marker to make sure a person reviews both language versions before they go live.

The safest way to use AI in Odoo 20 is to give it narrow jobs where a person still signs off. Examples for a Jordanian trading or services company:

• Sales: a live chat agent answers routine website questions and creates a lead for a salesperson when pricing or contracts come up. In CRM, a manager asks an agent for a pipeline view filtered by quarter.
• Customer service: Helpdesk suggests answers based on similar past tickets, and an internal agent limited to your Knowledge articles answers staff questions.
• Finance: an agent creates or updates records from a PDF of instructions, such as a list of new products or contacts, and someone in finance checks them before they appear on any invoice. Bill line prediction is a separate feature, not listed under AI in the release notes.
• Management: an external AI tool connected over MCP pulls read-only reports, using only the default search and read tools.
• Marketing and web: the website assistant drafts pages, the shop assistant rewrites product descriptions, and someone checks every dinar price before publishing.
• Back office: Documents renames uploaded files with AI.

Leave tax compliance to the localization: when you send an invoice to JoFotara, Odoo 20 validates the supplier's country and tax number by fixed rules and handles errors in the Send wizard. No agent decides whether an invoice is compliant. Treat payroll the same way: social security and income tax deductions must follow Jordanian rules exactly, so keep salary data out of your first AI pilot.

Treat an AI that can write to your database like a new employee with system access. Odoo 20 provides the controls:

• Grant skills sparingly: an agent that only answers questions needs neither Create Records nor Update Records.
• Turn on Restrict to Sources so an agent answers only from chosen sources, such as Knowledge articles or PDFs.
• Treat permission buttons and the tool-call limit confirmation as checkpoints, not clicks to rush through.
• Review agent conversations regularly; they are stored for up to 30 days after the last message.
• Give MCP keys a short expiry and a dedicated user with limited rights (an internal user counts as a paid user). Only five read tools are exposed by default; add others deliberately, and tick Readonly Tool only on tools that write nothing, because it tells the external client the tool is safe to run without user approval.
• Put business rules in the Python code of the tools that AI server actions call: Odoo's documentation says the server action itself does not enforce them, and a called tool runs unconditionally.
• For audits, check the user-group changes now logged in each user's chatter, and review the MCP user's access rights, which in Odoo 20 carry a domain deciding which records they cover.

The release notes make no claim about Arabic output quality, so test with your own Arabic documents and messages, and have a person review anything customers will read. Finally, check the setup against Jordan's Personal Data Protection Law before customer data reaches an agent.

At the time of writing (October 2026), Odoo's AI service page lists IAP credits at €1 each in packs of 10, 100, 500 and 1,000, includes 20 free credits, and says usage varies with the feature, task complexity and request size. Credits are tied to one database, do not expire, and unused credits can be refunded on request within 30 days of purchase. If the balance runs out, AI features stop until credits are added, which is why the email alert threshold and the auto-refill option matter. There is no fixed cost per task, so recheck that page before budgeting.

Odoo's pricing page also places agentic AI and External API under its Custom plan, so check which plan your subscription is on before you switch AI on.

For a Jordanian company, treat credits as an operating cost in your dinar budget and run a pilot of up to 30 days, so that unused credits from a pack bought for it are still refundable if you stop:

• Pick one use case, such as Helpdesk suggestions or records created from PDFs.
• Set up one agent with narrow skills and restricted sources, and set the email alert threshold.
• Each week, check usage on the My Subscription page or under Odoo IAP in Settings, and read the stored conversations.
• At the end, expand or stop.

Upgrading first? Follow the usual path: assessment, a test copy, then training. METCH, a certified Odoo partner serving Jordan, can scope the pilot with you in a free consultation.