Skip to content
Skills Library
Programming · Learning & explanation

odoo-version-reference

/odoo-version-reference

Short reference notes on selected Odoo changes between versions 10 and 19: the account.invoice merge, a few renamed or removed fields and methods, API key and RPC endpoint changes, and Odoo Online saas lines. It is not a full changelog. Use when the user asks about one of these, or whether a named model, field, method or endpoint exists in a given Odoo version.

Licence
MIT
Last repository change
10.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Short reference notes on selected Odoo changes between versions 10 and 19: the account.invoice merge, a few renamed or removed fields and methods, API key and RPC endpoint changes, and Odoo Online saas lines. It is not a full changelog. Use when the user asks about one of these, or whether a named model, field, method or endpoint exists in a given Odoo version.

Original author description

Short reference notes on selected Odoo changes between versions 10 and 19: the account.invoice merge, a few renamed or removed fields and methods, API key and RPC endpoint changes, and Odoo Online saas lines. It is not a full changelog. Use when the user asks about one of these, or whether a named model, field, method or endpoint exists in a given Odoo version.

How it works

  1. How to use these notes
  2. Models
  3. Fields and methods
  4. Odoo Online
  5. API endpoints and authentication
  6. Where to go next
Original SKILL.md headings · 40 lines, 585 words
SKILL.md preview
---
name: odoo-version-reference
description: "Short reference notes on selected Odoo changes between versions 10 and 19: the account.invoice merge, a few renamed or removed fields and methods, API key and RPC endpoint changes, and Odoo Online saas lines. It is not a full changelog. Use when the user asks about one of these, or whether a named model, field, method or endpoint exists in a given Odoo version."
---

# Odoo version differences (10 to 19)

These notes are documentation, written from the compatibility map that Transgenia keeps for its separate, full Odoo Tools plugin (not part of this plugin), as of November 2026. Transgenia read the field and method boundaries for Odoo 16.0 up to the Odoo Online line saas~19.4 in Odoo's public source. They are not live checks: this edition cannot look at the user's Odoo, and Odoo changes between releases. A boundary marked (best-effort) is not confirmed. These notes stop at Odoo 19: for Odoo 20.0 or later, say that you have no notes.

## How to use these notes

- Ask the user for the exact version and edition of their Odoo (Community, Enterprise or Odoo Online; for Odoo Online also the saas line, for example saas~18.2) before you answer a question that depends on it.
- Say that the user should confirm anything important in their own instance. If something is not covered here, say so; do not invent a boundary.
- Never ask for credentials. See the credential rule of the `odoo-start-here` skill.

## Models

- Accounting is a merge, not a rename: `account.move` (journal entries) exists on every version from 10 to 19. On Odoo 10 to 12, `account.invoice` is a separate invoice model; it is folded into `account.move` from Odoo 13, and `account.invoice.line` into `account.move.line`. On Odoo 10 to 12, name the model you actually mean, especially for writes and deletes.
- `stock.quant.package` (Odoo 18 and earlier) is `stock.package` from Odoo 19 (best-effort).

## Fields and methods

- `account.move.line`: `analytic_account_id` before Odoo 16 became `analytic_distribution` from Odoo 16 (analytic accounting became distribution-based, so the new field holds a distribution, not a single account).
- `product.template.uom_po_id` is gone from Odoo Online saas~18.1 and from Odoo 19.0: use `uom_id`. Odoo 17.0 and 18.0 still have it.
- `res.partner.company_type` is gone from Odoo Online saas~19.1: use `is_company`. Odoo 19.0 still has `company_type`.
- `name_get` is gone in Odoo 18 (deprecated in 17): read the `display_name` field, which works on Odoo 10 to 19.
- `check_access_rights` is removed from saas~19.1; `has_access` (from Odoo 18.0) replaces it.
- `read_group` is deprecated in Odoo 19.0 and absent on Odoo Online saas~19.1 to saas~19.4; `formatted_read_group` exists from saas~18.4.
- Translations: Odoo 16 and later have a native `update_field_translations` API; older versions write a translation with a language context.

## Odoo Online

- Odoo Online runs `saas~<major>.N` lines between two stable series (18.0 is older than saas~18.1, which is older than 19.0). An Online database can therefore differ from the same major version installed on a company's own server.
- External API access on Odoo Online depends on the plan (the Custom plan, at the time of writing), and API keys can expire from Odoo 18. This is background for a question about Odoo, not a way to diagnose a connection: this edition cannot connect.

## API endpoints and authentication

- API keys exist from Odoo 14. Odoo 10 to 13 have no API keys: external calls use the user's password.
- `/xmlrpc`, `/xmlrpc/2` and `/jsonrpc` are deprecated in Odoo 19. Odoo has announced that it will remove them in Odoo 22 (planned for fall 2028) and in Odoo Online saas~21.1 (planned for winter 2027); these are Odoo's plans as of November 2026 and can change. Their replacement is JSON-2 (`/json/2/<model>/<method>`), available from saas~18.4 and from Odoo 19.0, which accepts an API key only.

## Where to go next

For connecting Claude to the user's Odoo, follow the ways forward of the `odoo-start-here` skill.

Versions

The database has no other skills named odoo-version-reference.

Database snapshot: 13.11.2026 · package version 66c7bafa35c1 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 98odoo-studio-style
    Do Odoo Studio-style low-code changes (custom fields, views, automations) over RPC — on Community or Enterprise, without the Studio app. Use when the user wants to add a field, tweak a view, or automate a simple action.
  • 95odoo-setup-cli
    Configure the TypeScript CLI fallback (XML-RPC). Use when you cannot run the MCP server (no python3 3.9+) or want a lightweight scriptable surface. Odoo 17/18/SaaS tested.
  • 90odoo_20_coding_standard
    Odoo 20.0 coding standards for models, views, security (ir.access), mail tracking, icons, routes, external API, and tests. Use when developing or migrating Odoo 20 modules; carries every Odoo 19 rule forward plus the 20.0 breaking changes verified in odoo/odoo@20.0.
  • 100odoo-development
    MUST be loaded when ANY Odoo development task is detected. CRITICAL: Claude MUST use this skill for ALL tasks involving: - "odoo", "module", "model", "view", "field", "OWL", "manifest" - ANY mention of Odoo versions (14, 15, 16, 17, 18, 19) - "create odoo module", "generate odoo…
  • 90odoo_18_coding_standard
    Odoo 18.0 coding standards for models, views, security, constraints, and performance. Bridge version to 19.0 with transitional patterns. Use when developing Odoo 18 modules.
  • 90odoo-review
    Review Odoo addon code against the house rules, dispatching each changed file to the matching odoo-guidelines, odoo-web-guidelines, and odoo-security material. Use when reviewing a diff, commit, PR, or module.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.