Dated native checks cover Odoo 16–18 over XML-RPC and Odoo 19 over JSON-2. The reviewed pinned Odoo 20 Community candidate passed local JSON-2 qualification; authenticated hosted gateway smoke to the pinned Community 20 lab passed on October 1, 2026. The broader workflow matrix remains local evidence. Customer deployments, other editions and custom reports need separate checks. Hosted connections require public HTTPS and a live probe. The optional 20.0 Bridge's quotation PDF path was qualified locally.
Odoo compatibility matrix (16–20 Community)
- Public tool catalog: https://erpipe.com/tools
How to read this
Pass records dated automated checks for the stated scope. Odoo 20 Community has pinned local workflow qualification and a hosted gateway production smoke receipt. Customer installations, custom modules and other editions need separate qualification. Start with writes off and a least-privilege service user.
Supported majors
| Version | Transport | Status | Surface | Evidence |
|---|---|---|---|---|
| Odoo 16 | XML-RPC | Pass | Phase 1–4 read/write surface | Local live smoke + parity harness; restricted-user ACL matched Python reference. |
| Odoo 17 | XML-RPC | Pass | Phase 1–4 read/write surface | Local live smoke; diagnose_access behavior verified. |
| Odoo 18 | XML-RPC | Pass | Full hosted surface | Production Bestmix E2E: health, multi-instance fan-out, gated writes + HITL. |
| Odoo 19 | JSON-2 | Pass | Phase 1–4 + JSON-2 path | Local live smoke on JSON-2; auto-detect prefers JSON-2 when available. |
| Odoo 20 | JSON-2 | Pass with caveats | Community: reads, HR, files and approved changes | Pinned Community 20 local workflow checks passed, including owner approval and the optional 20.0 Bridge. Authenticated hosted gateway smoke to that lab passed on October 1, 2026. Quotation PDFs require the Bridge; prints that change data are refused. Enterprise, Odoo.sh, Odoo Online and customer custom workflows need separate qualification. |
Platform constraints (hosted)
- Hosted tool catalog — 48 named MCP tools as of 2026-10-15, listed at /tools. OSS self-host is 28 tools.
- HTTPS public hostname only — Private and link-local SSRF targets are rejected at create and on every call.
- Workspace MCP — One OAuth app at https://mcp.erpipe.com/mcp. Every Odoo-bound tool requires an explicit instance key.
- Writes default OFF — Enable per instance, then owner HITL approval for execute.
- Limits (free beta) — 10 instances per workspace, 5 concurrent MCP requests, 300 tool calls per 60s per instance.
- Odoo 20 qualification — Local Community 20 candidate only. Permissions still apply; security details require Odoo access. Field-restricted connections cannot download report PDFs. No claim for custom addons or other editions.
Matrix last updated 2026-10-01.
Last updated: 2026-10-01
FAQ
Which Odoo majors are smoke-tested?
Odoo 16–18 over XML-RPC and Odoo 19 over JSON-2 have native regression checks. The reviewed pinned Odoo 20 Community candidate passed local JSON-2 qualification. Authenticated hosted gateway smoke through ERPipe's public MCP endpoint to the pinned Community 20 lab passed on October 1, 2026. The broader workflow matrix remains local qualification evidence. Customer deployments, other editions and custom workflows need separate checks. Hosted connections require public HTTPS and a live probe.
Is this a warranty for every custom module?
No. Pass means automated local smoke and/or production E2E evidence for that major. Start with writes off and a least-privilege service user.
Does Community, Enterprise, and Odoo.sh work?
The Odoo 20 qualification covers Community in a local lab. Enterprise, Odoo.sh and Odoo Online need separate checks. Reachability and a successful probe alone do not qualify every edition or custom module; the connected user's permissions still apply.
Where is the hosted tool list?
The public catalog at /tools is sourced from the hosted tools/list (48 tools as of 2026-10-15).
Can I use localhost Odoo?
Not on the hosted beta. Private and link-local destinations are rejected.
What are the free beta limits?
10 instances per workspace, 5 concurrent MCP requests, and 300 tool calls per 60 seconds per instance.