Skip to Content
AI for Odoo

Your Odoo, actually doing the work.

Diana works across your Odoo — drafts the quote, chases the overdue, reconciles the bill — and you approve every move. It doesn't just tell you. It does it.

Platform

A page headline, at scale.

One or two sentences that set the promise for this page — what Odient does here, and what stays in your hands. Every move is audit-logged.

09:15:03diana · agent · sale.order.confirm · S01213allowed · audit-logged
Work Odient handled todayall approved by a human
✓Drafted quotation S01213 for Birchwood Interiors$6,417.00audit-logged
✓Chased the overdue balance at Alder & Birch Design$276,570.00audit-logged
✓Reconciled a vendor bill against its purchase orderflagged 1 diffaudit-logged
✓Traced every material on MO WH/MO/000114 lotsaudit-logged

It reads, it drafts, it does — you say go.

One question crosses your whole Odoo, comes back as real work ready to run, and nothing happens until you approve it.

@Diana the Birchwood order — draft it and chase what’s overdue
Quotation S01213 · Birchwood Interiorsdraft
20 × Bar Stool (Oak, Swivel)$6,417.00
nothing leaves until you say go
Done.
Quote sent · reminder drafted · both filed to the audit trail, tied to you. Diana did the work; you kept the call.
Where you already work

On every Odoo screen, and in the chat your team already uses.

Ask from the record you’re on with the Odient panel, or mention Diana in Discuss. It answers from live data and prepares the next step, in place.

The Odient panel open on a real Odoo sale order S01212 for Marco Ricci, confirming it is fully invoiced
Overdue receivables in Odoo, with Diana drafting a payment reminder for the outstanding balance
It watches, too

The thing that’s drifting, handled before it costs you.

Overdue accounts, stock about to run dry, a deal going cold — Odient flags it, prepares the fix, and waits for your go.

½ dayback to your team, every week

Stop assembling. Start approving.

The Monday overdue-chase, the “where’s that order” hunt, the month-end reconcile — Odient does the assembling. Your team does the deciding, and gets its week back.

Before: a request in chat. After: a quote out the door.

One flow, three beats — and the only human minute in it is the one where you approve.

The ask
@Diana Birchwood wants 20 bar stools — oak, swivel. Draft the quote.
The draft
S01213Birchwood Interiors · QuotationDraft
Bar Stool (Oak, Swivel) × 20$5,580.00
Untaxed amount$5,580.00
Tax 15%$837.00
Total$6,417.00
unsent · you approve
Approve & send
$6,417.00
S01213 · sent · auditable · tied to you

You can let it act, because every move is auditable.

Who asked, what ran, whether policy allowed it, exactly when. One trail across every assistant — the reason a lean team can hand real work to AI.

Access audit · livetenant: elmwood
09:14:22Maria Gómezaccount.reminder.draft · account.moveallowed
09:14:31Diego Santanapurchase.order · readdeclined
09:15:03Diana · agentsale.order.confirm · S01213allowed
09:15:47Omar Hassanhr.employee · readdeclined
every action Odient takes — allowed, blocked, or approved — writes one record. not a sample. every write.
It will also
tell you no.

An assistant that can do real work is only safe if it can be refused. Ask Odient to touch a record you are not allowed to see, and it stops — and the refusal is logged too.

Declined · today
DSDiego Santanapurchase.order · readdenied
OHOmar Hassanaccount.move · readdenied
DADiana · agentres.users · writeblocked by policy
MGMaria Gómezreminder ≤ $50kallowed
The firewall

Five checks stand between a prompt and your data.

Every request — from Diana, from the Odient panel, from any MCP client — walks the same five gates before it touches a single Odoo record. Each gate can stop it cold. Watch two requests take the walk.

prompt_firewall.py5 layers
request in →
1Identity &
access
2Injection
screening
3Tool-scope
policy
4Per-action
approval
5Audit &
logging
outcome
Diana · agentsale.order.confirm · S01213
✓
✓
✓
✓
✓
reaches Odooallowed · logged
Diego Santanapurchase.order · read · out of scope
✓
✓
✕
·
·
stoppedlayer 3 · logged

Two requests, the same five gates. Diana's confirmed order clears all five and reaches your data. Diego's out-of-scope read is stopped at layer 3 — it never reaches Odoo, and the stop is written to the record, in the same trail as the work that went through. The firewall is not a wrapper around the model. It is the path the model has to take.

The write-gate

Every write is decided before it happens.

Reading is scoped to the person. Writing is held to a gate you set — each of these is a control Odient checks before a single record changes. Built and tested this way, not bolted on.

  • ✓Allow / deny / confirmPer model, per action. Each write is matched to a rule before anything runs — some go, some stop, some wait.
  • ✓Value capsA reminder over a set amount, a change past a threshold — held for a person, not sent on the assistant's say-so.
  • ✓Rate limitsHow many writes an assistant can make in a window is bounded, so nothing runs away in a loop.
  • ✓Dry-runThe write is computed and shown first, so the exact change is on screen before it ever lands.
  • ✓Human-confirmAnything above policy waits for a person to approve. Drafts stay drafts until you say go.
  • ✓PII redactionSensitive fields are stripped at egress, before anything leaves your Odoo on its way to a model.
  • ✓One audit record per writeAllowed, blocked or approved — every decision writes exactly one row, tied to the person who made the request. Not a sample. Every write.
The trace

One finished order, read all the way back.

WH/MO/00011 closed with six Ladder Bookshelf units in Oak. Ask Diana what went into it and she walks the bill of materials as it was actually consumed — the lumber, the screws, the brackets, the finish — each line tied to the receipt it came in on.

No report to build, no filter to remember, no afternoon in the archive. The trail was written while the floor was running; Diana just reads it back to whoever is allowed to ask.

Materials
4 traced
WH/MO/00011
Manufacturing · Done
Produced
6 units
Product
Ladder Bookshelf
Oak, 72″
Materials
4 / 4
Materials consumed · traced
White Oak Lumber
consumed · traced to receipt
Wood Screw Assortment
consumed · traced to receipt
Steel Corner Bracket
consumed · traced to receipt
Water-Based Wood Finish
consumed · traced to receipt

A day, in the audit trail.

This is what a shop day looks like when the assistant keeps the ledger. Four moments, time-stamped — asked, flagged, held, filed. Every one logged the moment it happens.

08:02morning check

Before the doors open, you already know where you stand.

Ask how yesterday closed and whether today is set up clean. Diana reads the registers and the day’s stock position and answers in the panel you already have open — no report to build, no export to wait on.

OOdientPoint of Sale
context · today · all registers
How did we close yesterday — and is anything worth watching today?
08:02:14 · diana · agent · pos.session.readallowed · logged
11:40low-stock flag

A fast seller dips — and the flag arrives in time.

Mid-morning, the bar stool that has been moving all week slips below its comfort level. Odient watches stock against how fast things are actually selling, not just a fixed minimum, so you hear about it while the shelf still has something on it.

Low stockflagged by Odientreorder soon
ProductOn handSellingStatus
Bar Stool (Oak, Swivel)
front floor
low fast running dry
Ladder Bookshelf (Oak, 72")
stockroom
low steady reorder soon
11:40:36 · diana · agent · stock.quant.readflagged · logged
15:15held for approval

The reorder is written. And then it stops.

By mid-afternoon the draft already exists — the flagged items, your usual supplier, your usual terms. Odient holds it there. Ordering stock is your call, so nothing leaves the building until you look it over and say go.

Draft reorderprepared by Dianaheld for approval
Bar Stool (Oak, Swivel)usual order size
Ladder Bookshelf (Oak, 72")usual order size
Supplieryour usual, on your usual terms
draft only · nothing ordered until you say go
15:15:22 · diana · agent · purchase.order.draftheld for approval
17:30day summary

The till closes. The day reads back as a ledger.

What was asked, what was flagged, what was held for your decision — the whole day in one trail, each entry tied to who asked and what ran. Tomorrow starts from a record, not from memory.

Today · auditable
08:02morning sales check · answeredlogged
11:40low stock · 2 items flaggedlogged
15:15reorder draft · preparedheld for approval
17:30day summary · filedlogged
17:30:41 · diana · agent · pos.session.readday filed · auditable

the rail above shows how it reads and files your own shop’s records.

The project-to-cash chain

One line, from delivered to paid.

Every project walks the same four stations. Odient keeps the line moving — and nothing advances without you.

delivered
The work ships
Sale order S01212 for Marco Ricci — confirmed, delivered, done.
$3,907.70
invoiced
The invoice follows
Posted from the order the day the work lands — not whenever someone gets to it.
fully invoiced
chased
The reminder drafts itself
Alder & Birch Design, 31–60 days past due. Diana writes the nudge and waits for your go.
$276,570.00
Overdue receivables in Odoo Invoicing filtered to Posted plus Overdue — a run of Not Paid invoices for Alder & Birch Design, with Diana drafting a payment reminder in the Ask Odient panel for the $276,570.00 outstanding balance

A real ledger, mid-chase: Posted + Overdue, and Diana already drafting the reminder for the $276,570.00 balance.

a scope you choose
BBetty
Customer-support assistant
Lives onWebsite support widget (public)
ModelOn-prem model
PersonaWarm, concise, on-brand
Can see✓ Helpdesk✓ Knowledge base✕ CRM✕ Accounting✕ Inventory
Can do✓ Answer from FAQ✓ Open a ticket✕ Read records✕ Any write

One engine. Different keys.

Give one AI the keys to your whole ERP and you have built a liability. Scope a team instead: each assistant sees only its own world, acts only where you allow, and lands every move in the audit trail.

Your teamDiana
Discuss + the Odient panel · sees all your modules · governed writes with approval · model your choice (Claude / GPT).
Your customersBetty
Helpdesk + FAQ only, never your CRM · read-only · on an on-prem model, so customer chats never leave your walls.
FinanceCass
Accounting team only · scoped to Accounting · governed writes with value caps · every action audit-logged.
Name them anything. Point them anywhere. The write-gate, per-user access, and one audit trail come with every one.
Plans

Start free today. Cloud and on‑prem come next.

The beta is live and free. Cloud is the planned default once we launch, and on-prem with Odient LM is still in development. We’d rather tell you the roadmap straight than dress it up as a price grid.

Beta

Beta

Freewhile we’re in beta
Live now

For early Odoo teams. Run the full assistant on your own Odoo, with hands-on onboarding from the people building it.

  • ✓Diana in Discuss
  • ✓Odient panel on every screen
  • ✓MCP endpoint for any MCP client
  • ✓Governed actions + per-user audit trail
  • ✓Hands-on onboarding from our team
Cloud · planned default

Cloud

Coming after betapricing announced before launch
On the roadmap

The planned default once we launch — Odient managed and hosted by Zehntech, so your team just connects Odoo and gets to work.

  • ✓Everything in Beta
  • ✓Managed and hosted by Zehntech
  • ✓Updates and upkeep handled for you
  • ✓Straightforward per-team pricing
On-prem + Odient LM

On-prem

In developmenton the roadmap · not shipping yet
In development

Odient on your own infrastructure with the on-prem Odient LM model, so everyday questions never leave your network. Still being built — tell us if this is where you need to land.

  • ✓Everything in Cloud
  • ✓Runs on your own infrastructure
  • ✓On-prem Odient LM for everyday questions
  • ✓Your data stays inside your network

when beta ends, existing teams hear about pricing well before anything changes.

The pilot

We’d rather show you than tell you.

Bring your own Odoo — or run on ours — and watch Odient do real work on it before you commit to anything. A quote drafted from your catalogue. Your actual overdue list, chased. Every move held for your approval, in the audit trail.

If it doesn’t earn its place in front of your own data, you’ve lost nothing but an afternoon.

Book a demo your Odoo or ours · 30 minutes
a pilot run · liveaudit-logged
09:14Drafted quotation S01213 · Birchwood Interiors$6,417.00
09:15Chased the overdue balance · Alder & Birch Design$276,570.00
09:16Traced every material · MO WH/MO/000114 lots
every step held for approval · nothing sent until you say go
Zehntech Technologies Inc.in the audit trail since 2013
2013building enterprise software, every year since
80+engineers who ship for a living
100+modules published on the Odoo App Store
What to expect30 min · your Odoo or ours
00:00hello + your setup
05:00Diana answers from live data
12:00a real action, held for your approvalheld
25:00the audit trail + your questions
30:00doneaudit-logged
every action from the call — drafted, held, approved — is on the trail when we hang up
Request a demo

Tell us where to start.

Prototype form · nothing is submitted or stored yet.

Let your Odoo do the work.

09:18:40 · you
ONE AUDIT TRAIL ™
demo requested · logged · tied to you