AI service · Step 4 of 5
Know what your Odoo AI costs before the invoice arrives.
Odoo's AI runs on consumption credits. We measure it, cut it, and cap it.
Last reviewed
AI service
- Step in the sequence
- 4 of 5 Step in the sequence
AI operations per month, against a cap
Volume, not currency — Odoo publishes no per-operation credit rate, so the honest thing to measure is how much work you are sending it.
Monthly AI operation volume over six months, illustrative: January 1,180; February 1,340; March 1,720; April 2,450; May 3,260; June 4,180. A hard cap sits at 5,000 operations and an alert threshold at 4,000, below the cap. June has crossed the alert line.
The alert sits below the cap on purpose. An alert at the cap tells you about an outage; an alert beneath it leaves room for a decision. On this trajectory Jun is the month to look at what changed, not the month after.
Illustrative figures for one mid-size database, not a client result or a forecast. Your own volume is what the cost estimator works out.
Why this exists
Odoo's built-in AI requires Enterprise and consumption is billed against prepaid credits. Third-party AI apps on the Odoo store charge per credit per execution. A team switching AI on across accounting, CRM, helpdesk and inventory has no way to forecast next month's bill. Some switch it off entirely after the first surprise.
What we do
- Baseline actual credit consumption per module, per agent, per user
- Move high-volume, low-complexity calls to your own API key where that is cheaper
- Route simple tasks to lower-cost models and reserve expensive models for reasoning
- Set consumption caps and alerts that fire before the invoice, not after
- Report monthly on spend against manual work removed
What you get
A consumption baseline, an optimisation plan, configured caps and alerts, and a monthly cost report.
- Pricing
- Scoped after a conversation — get in touch
Next in the sequence
5. AI Assurance & Monitoring →Monthly accuracy scoring per use case, a reviewed agent action log, permission and consumption review, and a quarterly review.
Questions we get asked
-
Why can't you just tell me the monthly cost up front?
Because it runs on consumption rather than a flat fee, so it varies with how your team actually uses it. Anyone quoting a firm monthly figure before measuring your usage is guessing. We measure first, then cap.
-
Is using our own API key always cheaper?
No — it depends on volume and on which calls you move. High-volume, low-complexity work is usually cheaper on your own key; occasional reasoning-heavy work often is not worth the operational overhead.
-
What happens when a cap is hit?
The alert fires before the cap, not at it, so the decision is yours rather than a surprise outage. Caps are set per module so one runaway process cannot consume the whole allowance.
Talk to an Odoo AI consultant
A 30-minute conversation with someone who has configured Odoo's AI in production — including the parts that did not work.