# Odoo's agents can now write to the system of record: what changed in v1.1.0, sgit.ai

> The changes to the article "Odoo's agents can now write to the system of record" in v1.1.0, paragraph by paragraph.

*Source: <https://newsroom.sgit.ai/articles/versions/odoo-and-our-stack/v1.1.0.html> · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.*

---

[Home](../../../index.md) / [Articles](../../index.md) / [Odoo's agents can now write to the system of record](../../odoo-and-our-stack.md) / [Versions](../odoo-and-our-stack.md) / v1.1.0

# Odoo's agents can now write to the system of record: what changed in v1.1.0

From v1.0.0 (2026-11-16, `695951e76`) to v1.1.0 (2026-11-16, `f30b266e2`), paragraph by paragraph.

16 paragraphs added, 1 removed, 4 changed in place, 42 unchanged. About 776 words added and 16 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.

[all versions](../odoo-and-our-stack.md) · [v1.2.0 →](v1.2.0.md)

# Odoo's agents can now write to the system of record: how our stack fits around OdooOdoo, from version 12 to 20, with behaviour policies for Odoo agents, an Odoo cell, plan-then-apply through a vault, aanmoduleephemeral proof of concept that measureswent from nothing to customised in under a minute on four versions, and why we use whatever version is on the grant,otherand a first showcase for SHarnessside

Summary: Odoo is the open-source business system that a very large number of small and medium companies run their sales, accounts, stock and websites on, and in September Odoo 20 gave its AI agents the ability to create and update records, on their own, from automated and scheduled actions, and to be reached through a native MCP server. That is exactly the line I keep writing about, where an agent moves from assisting to executing in a system of record, and it is now arriving at small-business scale. An agent's power in Odoo comes from the tools it is given and the access of the user behind it; Odoo's documentation, as quoted by an integrator, says the AI does not enforce business rules; and agent conversations are kept for up to 30 days. So here is how our stack could integrate with Odoo. RiskMandate writes a behaviour policy for each Odoo agent, with the grant measured from Odoo itself, ideally by an Odoo module. AgentiCCells sells an Odoo cell on its usual ladder. SGit holds the plan, the approval and the result of every agent write, signed, for as long as the business needs it, with a small broker applying changes after a person approves. PKI gives each agent a key and each approval a signature. SHarness could get its first showcase bounding the Odoo server or the coding agent beside it. And VoiceDebrief can turn a meeting into a CRM note. TheAndplannonestartsofwithit waits for Odoo 20: in this session an agent brought up Odoo 12, 15, 18 and 19, each from nothing to customised in under a demominute, used the same workflow on aallself-hostedfour,Odoo.and removed them. We use whatever version is on the other side.

8 unchanged paragraphs, under In short {#in-short}

• **Every version, not just 20:** the same agent ran on Odoo 12, 15, 18 and 19, each from nothing to customised in under a minute.

• **Use the future now:** we do not wait for the upgrade; we use whatever Odoo the customer has.

24 unchanged paragraphs, under Why Odoo, and why now {#why}, Where the gap is {#gap}, RiskMandate: a behaviour policy for every Odoo agent {#abp}…

## Every version, not just 20 {#versions}

[figure odp-versions.webp] What each Odoo version offers an integration, from 12 to 20, and where our agent ran. | table

Most Odoo customers are not on the latest version. Someone I spoke to recently, whose company runs Odoo, put it simply: they are on 19, and will have to do some upgrades to get to 20. Others are on 18, 16, 15, or older. That does not change what we can do for them, because our workflow does not depend on Odoo's agents. It depends on Odoo being the place where the customer's data and workflows already live, and every version since at least 12 can be reached through its API: XML-RPC in all of them, API keys from 14, the JSON-2 API from 19, and MCP from 20.

So the newest features are a bonus, not a requirement. An Odoo 15 with years of real data is a better data source than any fresh system, because the customer is already committed to it, and their workflows, including the manual ones that can be improved, are already in it.

## A proof of concept, in under a minute {#poc}

[figure odp-poc.webp] Odoo from nothing to customised in under a minute on versions 12, 15, 18 and 19, timed in this session. | chart

To check that this is real and not a slide, the agent writing this article brought Odoo up in its own environment, ephemerally, four times. For each of Odoo 19, 18, 15 and 12, using the official Community images: start a fresh PostgreSQL, install CRM and Invoicing, start the server, then run a small agent over the API. It adds a custom field (the town each partner is in), creates a partner, a lead and a draft vendor bill, and reads them back. Then everything is removed. From nothing to customised took 44.9 seconds on Odoo 19, 47.1 on 18, 36.4 on 15 and 49.7 on 12. The agent itself took between one and three seconds; teardown took under half a second.

[figure odp-screens.webp] The ephemeral Odoo 19 with the agent's Town field and draft bill, and the same field on Odoo 12. | screenshot

The same agent ran on all four. Only its calls adapt: on Odoo 12 a vendor bill is an `account.invoice`, from 14 it is an `account.move` with a `move_type`; older versions needed the generic chart of accounts installed before a bill could be drafted. On Odoo 19 the agent also placed the new field on the partner form through the API, and read it back over the new JSON-2 API with an API key. And the bill stayed a draft: the agent was never asked to post it.

That is the shape of an MVP or a proof of concept with a customer: a throwaway copy of their kind of Odoo, our workflow on top of it, a better interface or prototype where it helps, and nothing left behind. When it works, the same workflow points at their real instance, under a behaviour policy.

## Use the future now {#future}

This is the message I care about most. Customers do not have to wait to be upgraded to use agents with Odoo. We can bring the future to whatever they have now: agents, policies, signed approvals, a lasting record and better interfaces on an Odoo 15, and, when they move to 20, we use its agents and MCP server too, and retire whatever of ours they replace. We go to where the customer already is ([integrate with whatever is on the other side](../../integrate-with-whatever-is-on-the-other-side.md)).

1 unchanged paragraph, under The plan {#plan}

1. **A demo:** done as a self-hostedproofOdoo,of concept, above; next, one agent on vendor bills,bills on a copy of a real customer's Odoo, its behaviour policy published as RiskMandate's next example, and an article here.example. 2. **The pattern:** the vault-and-lane broker for Odoo writes, and the signed record. 3. **The offer:** an Odoo cell on AgentiCCells' ladder; the measured grant in RiskMandate. 4. **The channel:** Odoo partners, who implement Odoo for their customers and will need an answer for its agents; then the apps store.

3 unchanged paragraphs, under What to watch {#watch}

• **Old APIs are going:** the legacy XML-RPC and JSON-RPC are deprecated in favour of the JSON-2 API; sources disagree on the removal date. BuildUse what each version has: XML-RPC on older versions, JSON-2 or MCP.MCP on newer ones.

1 unchanged paragraph, under What this does not claim {#limits}

• **This is a strategy,** not an integration that exists; nothing has been built or sold.

• **This is a strategy and a proof of concept,** not a product; nothing has been sold.

• **The proof of concept used Odoo Community images,** with no demo data and an example partner; Odoo 20 and Enterprise features, including its agents, were not tested.

5 unchanged paragraphs, under Where this comes from {#sources}

[all versions](../odoo-and-our-stack.md) · [v1.2.0 →](v1.2.0.md)


---

*[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/odoo-and-our-stack/v1.1.0.html)*
