EDI B2B Connector
X12 (850/810/855/856/997) + EDIFACT (ORDERS/INVOIC/ORDRSP/DESADV/CONTRL) parse & build, envelope validation, file-directory transport, auto-generation from sale/invoice/delivery
Compatible with Odoo 18.0 · 19.0
Key Features
ANSI X12 transaction sets (004010)
Inbound 850 Purchase Order parsing and outbound 810 Invoice build, plus full build & parse for the 855 Purchase Order Acknowledgment and the 856 Ship Notice / ASN with its HL S/O/I hierarchy, TD5 carrier and REF tracking segments.
UN/EDIFACT message types (D.96A)
ORDERS inbound parsing, INVOIC outbound build, and full build & parse for ORDRSP (order response), DESADV (despatch advice) and CONTRL (service report) — the EDIFACT equivalents of X12 855, 856 and 997.
Envelope validation
X12 ISA13/IEA02 and GS06/GE02 control-number pairing plus SE01 segment counting; EDIFACT UNB/UNZ reference pairing plus UNT segment counting. Results are stored on the message and drive the generated 997 / CONTRL status codes.
Functional acknowledgments
Build and parse X12 997 (AK1/AK2/AK5/AK9) and EDIFACT CONTRL (UCI/UCM). A one-call helper validates a received interchange and emits the matching acknowledgment automatically.
File-directory transport
Outbound documents are written atomically (tmp + rename) to a per-partner directory with traversal-safe names; inbound documents are read, parsed into records, optionally auto-acknowledged and archived for idempotent re-runs. An ir.cron polls all file-transport partners. SFTP/VAN-relay friendly.
Auto-generation from Odoo documents
Confirming a sale order builds an 855 / ORDRSP, posting a customer invoice builds an 810 / INVOIC, and validating a delivery builds an 856 / DESADV. Hooks fire only when the partner has auto-send enabled and never block the underlying Odoo operation.
Use Cases
Screenshots
Field Mappings
Edi Messages
Trading Partners
Why Choose This Module
Most EDI add-ons for Odoo are thin shells. This one ships a genuine ANSI X12 and UN/EDIFACT engine where every advertised transaction set is implemented for real — both directions — and covered by round-trip TransactionCase tests. Envelope control numbers and segment counts are actually verified, every message stores its raw payload, parsed dictionary and validation errors for full traceability, and the AS2 wire-protocol boundary is stated honestly: the file-directory transport integrates with an external SFTP/AS2 relay rather than faking an in-process handshake. It is dependable, auditable EDI you can put into production.
Transport model & BYOK
This module is a format engine plus a file-directory transport. It generates and parses standards-compliant X12 and EDIFACT files and drops them in (or reads them from) per-partner directories. It is not a VAN, not an EDI service bureau and not a managed integrator: you bring your own SFTP/AS2 relay (BYOK) to mirror those directories to your trading partner, and your existing partner agreements and connectivity stay with you. The AS2 wire protocol (S/MIME, MIC, signed MDN) is intentionally handled by that external relay and is not faked in-process. Support is provided for the module itself at support@pokutsoft.com and the purchase is refundable per Odoo Apps Store policy if the module does not work as described.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: sale, account, stock
- Support: support@pokutsoft.com
Update date: 2026-07-09