Template-free AI OCR that reads any document — POs, contracts, IDs, delivery notes — and writes structured data straight into any Odoo model. One-time license from $399.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Template-free AI OCR that reads any document — POs, contracts, IDs, delivery notes — and writes structured data straight into any Odoo model.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
AI Document Digitization (Universal OCR) is a build-to-order Odoo module that turns your paper-and-PDF backlog into clean, structured Odoo records — without brittle per-vendor templates. Instead of the fixed-layout OCR you find in Odoo's stock Invoice Digitization, this module uses modern AI extraction to read whatever you throw at it: purchase orders, supplier invoices, signed contracts, national IDs and passports, delivery notes, packing slips, receipts and letters. It recognizes the document type, locates the fields that matter, and maps them onto the Odoo model you choose.
Template-free AI extraction that reads mixed document types — POs, invoices, contracts, IDs, passports, delivery notes, receipts — without a fixed layout per vendor
Automatic document-type classification so each upload is routed to the correct Odoo model and field-mapping profile
Searchable OCR text layer written back onto every scan and PDF, indexed for full-text search from inside Odoo
Visual field-mapping designer that binds recognized fields to any Odoo model and field (standard or custom x_ studio fields)
Confidence scoring per field with a human-in-the-loop review queue for low-confidence extractions before records are committed
Bulk import from a watched network/SFTP folder via an ir.cron scheduled action that sweeps new files automatically
Because ECOSIRE builds this specifically for your business, the module ships as real Odoo code — a proper addon with its own __manifest__.py, models extending models.Model, computed and stored fields with @api.depends, security wired through ir.model.access.csv plus record rules, backend views in XML/OWL, and QWeb report/preview layouts. Ingestion runs through Odoo's own plumbing: ir.attachment for the scanned binaries, ir.cron scheduled actions for folder-watch and mailbox polling, and base automation for the post-extraction hand-off (create a purchase.order, attach to a res.partner, populate a custom x_document.digitized model — whatever your workflow needs). Every extracted document keeps a searchable OCR text layer indexed against the record, so your team can finally full-text search scans and PDFs from inside Odoo.
This is not an apps.odoo.com instant download and it is not a black box. It's a scoped engagement: ECOSIRE analyzes your document samples and target models, builds the extraction + field-mapping configuration, installs it on your Odoo 17, 18 or 19 (Community or Enterprise), trains your operations team, and supports it. You own the source, the mapping rules, and the data — nothing is locked behind an opaque per-page meter you can't see into.
Typical lead time is 2–4 weeks depending on the number of document types and target models. What you get at the end is a document intake pipeline that removes manual re-keying, kills transcription errors, and makes years of paper instantly findable — all native to the ERP your team already lives in.
Owns a paper-heavy intake process — supplier invoices, POs, delivery notes — and needs data in Odoo without an army of typists re-keying it. Wants accuracy, a review step for edge cases, and an audit trail.
Drowning in supplier documents from dozens of vendors with different layouts. Needs header and line-item extraction straight into vendor bills and POs, with duplicate detection and confidence scoring before anything posts to the ledger.
Responsible for the Odoo instance and integrations. Wants a real, source-available addon that fits Odoo conventions (ir.attachment, ir.cron, record rules, XML-RPC), installs cleanly on their version, and won't become an unmaintainable black box.
Manages contracts, IDs and regulated documents that must be searchable and traceable. Needs a searchable OCR layer, per-document audit history, and role-based access so only authorized staff can view sensitive scans.
Buy the license on ecosire.com and download the AI Document Digitization (Universal OCR) module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for AI Document Digitization (Universal OCR), and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Document types supported | Any type you scope — POs, invoices, contracts, IDs, delivery notes, receipts | Only what you find time to build; usually starts invoice-only | Often fixed to one or two document types per app | |
| Template-free AI extraction (no per-vendor setup) | Yes — AI classifies and locates fields across layouts | Rarely — most DIY builds rely on rigid templates or regex | ||
| Maps to any Odoo model via a field-mapping designer | Yes — bind fields to standard or custom models | Possible but hand-coded per model | ||
| Searchable OCR text layer on scans and PDFs | Yes — indexed for full-text search inside Odoo | Only if separately built | ||
| Confidence scoring + human review queue | Yes — thresholded review before records post | Rarely implemented | ||
| Bulk intake: folder-watch, email, scanner (ir.cron) | Yes — all three, configured for you | Each channel is extra build work | ||
| Works on Community and Enterprise, Odoo 17/18/19 | Yes — no Enterprise-only lock-in | Depends on your build | ||
| You own the source code and mapping rules | Yes — full commented addon handed over | Yes, but you built and must maintain all of it | ||
| Built, installed, trained and supported for you | Yes — 2–4 week engagement with support window | You resource and maintain it entirely |
This is a build-to-order module, not an instant download. Typical lead time is 2–4 weeks depending on how many document types and target Odoo models are in scope. The flow is: you share representative document samples and tell us which Odoo models the data should land in; we build and configure the extraction + field-mapping, validate it against your real samples, then install it on your Odoo instance and train your team. You'll get a validation report showing accuracy before handover.
Every engagement includes a defined post-go-live support and bug-fix window with agreed response times, plus a documented path for keeping the module working across Odoo point releases. Because you receive the full commented source, your own team (or ECOSIRE on an extended support agreement) can add new document types or adjust mappings later. We can also scope ongoing maintenance and Odoo 17→18→19 upgrade support separately.
It works on both Community and Enterprise, and supports Odoo 17, 18 and 19. Unlike Odoo's built-in Invoice/Document Digitization — which is an Enterprise, IAP-metered, invoice-focused feature — this module is a self-contained addon you own. The AI extraction runs through the configuration we build, not a locked Enterprise-only credit meter, and it covers any document type, not just invoices.
No. That's the core difference from most apps.odoo.com OCR modules. The extraction is template-free: an AI model classifies the document and locates the relevant fields regardless of layout, so a new supplier's invoice or a different ID format works without you authoring a per-vendor template. You configure mappings per document type, not per layout, and low-confidence extractions go to a human-review queue before they commit.
Extracted fields are mapped onto the Odoo model and fields you choose via the mapping designer, and can trigger base-automation actions (create a purchase.order, populate a custom model, tag a partner, start an approval). Every field carries a confidence score; anything below your threshold lands in a review queue for a human to confirm or correct before the record is posted. The original file is stored as an ir.attachment on the record with a side-by-side QWeb preview, plus a full audit trail of what the AI proposed and what was changed — so nothing hits your data silently.
Yes. Intake works three ways out of the box: a watched folder (network/SFTP) swept by an ir.cron scheduled action, a monitored mailbox that digitizes emailed attachments on a poll cycle, and direct scanner output dropped into the watch folder. For deeper integration, we can expose XML-RPC / JSON-RPC endpoints so an external DMS, scanning appliance or third-party app pushes documents into the pipeline programmatically.
Template-free AI OCR that reads any document — POs, contracts, IDs, delivery notes — and writes structured data straight into any Odoo model.