Odoo Document Import

Order confirmations, quotes, and invoices arrive as emails and PDFs, and someone usually re-types them into the ERP. These eight modules build on the OCA's PDF-import-by-template and EDI frameworks so Odoo 18 Community can read those documents itself. You describe a document once as a template, and every matching email or PDF after that becomes a record, with a review queue for anything uncertain.

Features

• base_import_pdf_by_template_engine: extension points that let other pattern engines and tools plug into the OCA import module, plus fixes for two table-extraction bugs.

• import_from_email: plain-text and HTML extraction modes, and a mail alias that files each inbound email as a tracked, retryable EDI exchange record.

• edi_import_router: one inbox for emailed and printed documents. A TypeSafe classifier picks the document type, confident matches are filed automatically, and the rest wait for review.

• import_via_xberg: an extraction mode backed by the xberg library that parses PDFs into structured tables, with JSONPath to narrow each field before its pattern runs.

• import_preview: a saved sample per template and a live preview of each line's match while you write it.

• import_create_missing: creates the linked record (a product, say) when a lookup misses, prefilled with the required fields.

• import_create_missing_xberg: JSONPath support for those new-record values, installed automatically when both modules are present.

• edi_purchase_order_import: confirms a purchase order as soon as it is imported from an inbound document and notifies the group you choose.

Getting started

Add the repository's 18.0 branch to your addons path along with OCA's edi, edi-framework, and queue repositories. The documentation explains how the pieces fit and how to build your first template. With odoo-nix: odoo module add Avunu/edi-addons 18.0.