02 ·Agnidoot In-Odoo AI

Stop typing into Odoo. Start approving work already prepared.

Customer purchase orders, supplier quotations and vendor invoices become complete Odoo drafts—including every line item. Your team checks the few exceptions, approves the record and moves on.

Inside the Odoo your team already uses. Draft first. Human review always. Every action recorded.

Incoming paperworkAI preparing draft
Customer PO · scanned PDF

The document your team would normally retype

Customer, delivery details, products, quantities and prices—all read together.

READMATCHCHECKDRAFT
Sales Order · DraftReview ready
Customer matched to existing record
No duplicate created
Ready
Order lines prepared
Products, quantities and rates
Ready
One unclear quantity
Held for a person to check
Review
Nothing posted automaticallyWaiting for approval
Typing becomes checkingYour team spends its time on exceptions, not repetitive entry.
Every line item mattersComplete order and invoice lines—not just the document header.
Your Odoo stays cleanCustomers, vendors and products match existing master records.
Your people stay in controlAI prepares the draft. The right person decides what becomes real.

Built around the work your team dislikes

The slowest part of Odoo should not be your keyboard.

Most ERP delays begin before a workflow even starts: someone must read a document, find the right records and type everything into Odoo. Agnidoot removes that queue without removing human judgement.

01

Data entry consumes the day

A full draft arrives in minutes, ready to review. Customer details, products, quantities and prices are prepared together, so a 15-line order is no longer a 15-line typing job.

02

One typo creates three more problems

Confidence checks expose uncertainty before it reaches the business. An unclear rate or quantity is held for review instead of quietly becoming a wrong delivery, invoice or payment dispute.

03

Scans and phone photos break basic OCR

The system detects image-based paperwork and uses vision when configured. Stamped scans, photographed invoices and imperfect PDFs can enter the same review flow.

04

Duplicate records slowly damage Odoo

Names resolve to your existing customers, vendors and products. If two records could match, the AI asks instead of guessing or creating another master record.

05

Large documents interrupt everyone

Extraction runs in the background. Your employee keeps working, returns to a prepared draft and can retry a failed job without losing the request.

06

Owners automate—and fear losing control

Approval thresholds and permissions remain enforceable. High-value decisions go to the right senior person, whether the draft began with AI or a keyboard.

Faster reports start with current, reliable Odoo data.

When orders, quotations and bills reach Odoo sooner—and with fewer entry errors—operational reports reflect the business sooner. Your team spends less time chasing missing transactions and correcting the data behind the report.

One experience across departments

Three paperwork queues become three review queues.

The same governed engine serves sales, purchasing and finance. New document-to-draft workflows are configured against Odoo models rather than rebuilt from scratch.

Sales

Customer PO draft Sales Order

Customer and order lines are prepared. Sales checks delivery details and exceptions, then confirms.

Purchasing

Supplier quotation draft RFQ

Vendor, products, quantities and rates are matched. The buyer compares and approves instead of retyping.

Finance

Vendor invoice draft Bill

Invoice details and lines are prepared for verification. Nothing is posted to the books until a person reviews it.

The trust promise

The AI drafts.
Your people decide.

Agnidoot is designed like a very fast junior clerk with a disciplined review process—not an unsupervised accountant. Creating a draft is easy. Committing a consequential change remains controlled.

Field confidence

It shows you exactly where it is unsure

Low-confidence fields are not applied by default. A user must inspect them and explicitly choose whether to accept them.

Row-level checks

One bad line does not destroy nineteen good ones

Invalid or unclear rows are isolated for review while the rest of the document remains useful.

Entity matching

It asks before choosing between similar records

Names are resolved against real Odoo records. Ambiguous matches are surfaced to a person rather than silently selected.

Approval workflow

Risky changes wait for the right authority

Approval rules can require a senior sign-off before anything is written or confirmed. The requester cannot approve their own controlled action.

Audit trail

Every action has an answer to “who, what and why?”

The document, model, extraction, risk level, reviewer, approval and refusal outcomes are recorded in Odoo.

Security

Your existing Odoo access rules still apply

Users only work with the records their Odoo permissions allow. Approved providers and models are managed centrally.

What changes for your team

Less administration. Faster decisions.

Sales

Customer orders enter the queue faster, with fewer quantity and pricing mistakes.

Purchasing

Supplier paperwork becomes comparable Odoo drafts without repetitive entry.

Finance

Bills arrive for verification sooner, while uncertain values remain visible and controlled.

Owners

Approvals, exceptions and AI activity remain visible without slowing routine work.

Clear operating boundary

Agnidoot does not automatically confirm orders, post bills or invent missing master data. Scans and photos require a vision-capable model. The system prepares work, identifies exceptions and routes approvals; your authorised people make the final business decision.

02 · Agnidoot In-Odoo AI

Documents become draft records.
A human still decides.

Fifteen AI modules working inside the Odoo screens your team already uses. Paste an email or drop a PDF and it becomes a draft order — every line item, with per-cell confidence — and nothing saves until the right person approves.

15 AI modules Inside your own Odoo Odoo permissions stay in force
6

AI modules
inside Odoo

9

Configuration
customisers

3

Workflows ready
on day one

0

Records invented
in our benchmark

The everyday win

Paperwork stops being typing.

The single biggest time sink in any ERP is a person retyping a document into a form. That disappears — and the controls that make it safe live in the write path, not in a policy document.

Step one

Drop in the document

Email text, PDF, Word, Excel or CSV — or a scan or photo, read by OCR with a vision model.

Step two

Review what it found

Header fields and every line item, each cell carrying its own confidence — not one score for the row.

Step three

Approve, and it's saved

A real Odoo record, with the requester and the approver both recorded against the change.

What it does

Everything the fifteen modules give you.

01

Document upload, OCR and AI Fill

Any common format, and any Odoo form — because the form engine is data-driven rather than hard-coded.

  • Text, PDF, Word, Excel, CSV read directly
  • Scans and photos via a vision model; it spots a scanned PDF and switches
  • Line items, not just headers — a PO is its lines
  • Subtotals are never treated as products
  • Three workflows ready configured — quote→RFQ, PO→sales order, invoice→bill
  • A new document type is configuration, not code
02

It refuses to guess

The behaviour that makes it safe to let AI near your master data.

  • Unknown product or vendor — flagged, never created
  • Two possible matches — both named, and it asks
  • Low confidence arrives unticked; accepting needs a logged written reason
  • Smart matching — a misspelled vendor resolves from its GSTIN
  • Products resolve by internal code, then barcode, then name
  • Units, taxes and currencies are never substituted silently
03

Approvals enforced in the write path

Not an approval screen the API can walk around.

  • Creating a draft is frictionless — no approval, by design
  • Changing a record needs a second person, never the requester
  • Refused in the UI and against a hand-crafted API call
  • No approver configured means refused, not waved through
  • Three permission tiers — user, approver, administrator
  • No privilege escalation on any AI write path
04

An audit log inside Odoo

Who ran the AI, who approved, what changed, when — with risk levels and one request ID joining the story together.

  • Every AI action recorded, including refusals
  • Visibility follows the user's own permissions
  • Reading a trail never requires credential access
  • One reference spans document, conversation and write
05

Background jobs, so nobody waits

Submit a big document, close the window, carry on.

  • Queue any extraction as a background job
  • Failure is a state, not a lost request — retries back off
  • One bad document never stalls the queue
  • Errors read as sentences, not stack traces
06

Your models, your keys

Ten provider types behind one setting, including models running entirely on an AI-ready box in your own building.

  • OpenAI, Anthropic, Gemini, Groq and more — or fully local
  • Keys live in Odoo, masked and admin-only
  • Using a model never requires seeing its key
  • A model catalogue so teams pick from what you approved
  • An offline deterministic mode for demos and testing
07

The AI Configurator

Change how Odoo itself is set up — as reversible proposals rather than developer tickets. Seven module-scoped customisers cover sales, purchase, inventory, manufacturing, maintenance and quality.

  • Current vs proposed, previewed before anything changes
  • Author → approve → apply with a named approver
  • Drift-protected rollback — blocked if configuration moved after approval
  • Every change in the same audit timeline
08

Vertical packs and executive briefs

Industry configuration as a versioned artifact, and a morning page where every number is arithmetic.

  • Packs are data, never code — enforced at build and install
  • Installing a pack changes nothing until approved
  • Rollback restores behaviour, not just a label
  • Every brief figure computed, never generated
  • Unsourced numbers rejected — and the page says so
  • Green means good, not up
What we will not claim

Scans need a vision model configured — and the interface says so upfront rather than returning an empty result. Unusual layouts are what a pilot is for.

One vertical pack exists (engineering and manufacturing, in certification), and pack updates are not sellable yet — changed settings inside protected records don't land, a defect we have open. Brief delivery by email or WhatsApp isn't wired, and the drill-through page isn't built.

Every plan includes

Try it free for three months. Keep the support for a year.

No obligation, no card, no lock-in. And what comes with your plan isn't a discount — it's what it takes to make an ERP actually land.

Start free →
Weeks

Start in weeks

Not months. Your implementation is underway in your first week.

1 year

Free support

A full year included with every plan — not a paid add-on.

On-site

Training included

We come to you and train your team in the room, on your data.

100 hrs

Customisation

A hundred hours of our engineering, built into every plan.

No card to start  ·  No obligation  ·  Cancel any time in the three months  ·  Your data stays yours

Questions

Questions about document AI inside Odoo.

What it does to your paperwork

What happens to an invoice that arrives today?
It is read, its fields are extracted, the supplier and products are matched against your Odoo records, and a draft record is created with everything filled in. Someone opens it, glances at it, and approves. The typing is gone; the judgement stays.
Which documents does it handle?
Supplier invoices, purchase orders, quotations and similar structured business paperwork — the documents that arrive in volume and get retyped. It does not process audio or video.
Does OCR really work on our scans?
On ordinary scanned and photographed paperwork, yes. Quality varies with the source, which is exactly why nothing is posted automatically — every extraction is previewed against the original before a human accepts it.
What if it gets a field wrong?
You see it before it counts. The draft sits in front of a person with the source document beside it; correcting a field takes seconds and nothing has touched your ledger yet.

How it works inside Odoo

Is this a separate application?
No. It ships as Odoo addons — fifteen of them — so your team works in the Odoo screens they already know. There is no second system to log into and no data sitting outside your database.
Who is allowed to see which documents?
Whatever Odoo already says. Every action runs with the permissions of the person who triggered it, so document AI cannot show someone a record their Odoo user could not open.
Which AI models read the documents?
You choose. Ten providers are supported, and on Enterprise the models can run locally inside your own infrastructure — that is the default posture there, with cloud providers as an option rather than a requirement.
What is kept after a document is processed?
The Odoo record and the audit entry. Prompts are not stored after the request completes.

Getting started

How quickly can we see it on our own invoices?
Within a demo. Bring a handful of real documents and watch them become draft records — it is a more honest test than any sample file we could show you.
Do we need to change how suppliers send things?
No. The point is to absorb the paperwork as it already arrives rather than asking everyone upstream to change.

Paste a quotation. Watch it refuse to invent a product.

We'll show you the product count before and after. It's the two-minute demo that decides most finance conversations.

Book a demo

See it running on your own documents.

Thirty minutes, your paperwork, your questions. We will show you what it does — and, just as importantly, what it refuses to do.

Book a demo →