EDI Connector — Trade EDI With the Big Retailers
ANSI X12 purchase orders become sale orders, and ship notices and invoices go back — over signed AS2 or SFTP, the electronic exchange the large chains require, right inside Odoo. Optional AI mapping. Bring your own keys.
Inbound purchase orders and outbound invoices and ship notices in one place — document type, direction, trading partner and the linked Odoo order.
- Read the retailer's PO, type it into Odoo
- No standard format, constant errors
- Chargebacks for late or wrong documents
- 850 POs become sale orders automatically
- 856 ship notices & 810 invoices go back
- Trading partners, X12 / EDIFACT, in Odoo
Win the account that requires EDI — and stop paying chargebacks for documents typed by hand.
EDI, inside Odoo
Add your trading partners and their identifiers, and choose the transport: demo, SFTP, or signed AS2.
Inbound X12 850 purchase orders are parsed into Odoo sale orders automatically.
Generate and send 856 ship notices and 810 invoices from the matching Odoo documents, with a clear status trail.
Every document, in and out
Inbound X12 850s become sale orders and outbound 856/810 go back — each EDI document with its type, direction, trading partner and the linked Odoo order, on one work-list.
Signed AS2, or SFTP — your transport, your keys
Most retailers require AS2: every document is signed (S/MIME/PKCS7) and each delivery receipt (MDN, signed) is verified and logged, so you have real proof of delivery — not just an SFTP drop and hope. Generate a certificate in one click, or SFTP still works for partners who use a VAN folder instead. Add your own AI key for mapping tricky inbound documents. Secrets, including your AS2 private key, are encrypted at rest and admin-only.
Features
- Inbound 850 → sale order — retailer purchase orders parsed into Odoo sale orders automatically.
- Outbound 856 & 810 — ship notices and invoices generated from the matching Odoo documents and sent back.
- Trading partners — ISA / GS identifiers and per-partner settings.
- Signed AS2 — the transport most retailers actually require. Messages signed (S/MIME/PKCS7), delivery receipts (MDN) requested, verified and logged, sync or async. Generate a certificate in one click. (S/MIME encryption is not included; the exchange runs over HTTPS, which already encrypts it in transit — ask your partner if signed-only is accepted.)
- SFTP / VAN folder — also supported, for partners who use that instead. Or run in demo mode with seeded documents before you wire up a real connection.
- Live cockpit — inbound and outbound counts, errors to fix, and every document with its status and linked order.
- AI mapping (optional) — Anthropic Claude or OpenAI, your own key; helps map non-standard inbound documents, in your language.
- Secure by design — transport secrets encrypted at rest and admin-only; multi-company isolation. Community and Enterprise.
- Multilingual — English, Spanish, French, German, Italian and Portuguese (BR).
Perfect for suppliers to large retailers (Walmart, Falabella, Cencosud, Tottus and the like) that require EDI and cannot afford to re-key documents or eat chargebacks.
Keywords: EDI connector, AS2, signed AS2, AS2 gateway, MDN, X12 EDI, EDIFACT, electronic data interchange, EDI 850 purchase order, EDI 856 ASN, ship notice, EDI 810 invoice, EDI 997 acknowledgement, retailer EDI integration, big box retailer EDI, trading partner management, EDI mapping, AI assisted EDI mapping, purchase order to sale order, supermarket EDI, pharmacy chain EDI, EDI compliance, B2B integration, Odoo EDI, EDI document cockpit.
Palabras clave: conector EDI, AS2, AS2 firmado, pasarela AS2, MDN, EDI X12, EDIFACT, intercambio electrónico de datos, EDI 850 orden de compra, EDI 856 aviso de envío, aviso de despacho, EDI 810 factura, EDI 997 acuse de recibo, integración EDI para minoristas, EDI para grandes superficies, gestión de socios comerciales, mapeo EDI, mapeo EDI asistido por IA, orden de compra a pedido de venta, EDI para supermercados, EDI para cadenas de farmacias, cumplimiento EDI, integración B2B, EDI Odoo, panel de documentos EDI, IA, inteligencia artificial.
Permissions & data security
Built to respect Odoo's access model — audited so nothing leaks between users or companies.
- 🔑 Transport secrets & AI key encrypted, admin-only. Your SFTP credentials, AS2 private key and AI key are stored encrypted at rest (Fernet / AES) and are readable or editable only by a system administrator.
- 🏢 Multi-company isolation. Every record and setting is tagged to its company; a user only ever sees the companies they are allowed into. Cross-company access is impossible — verified.
- 👤 Role-based access. Dedicated EDI groups (User / Manager); the rest of your staff never sees the exchange. No portal, no public exposure.
- ✅ Secure by design — audited across the whole suite: role-based access, key encrypted at rest and admin-only, strict multi-company isolation.
Requires the Sales, Inventory and Invoicing app. Works with Odoo Community and Enterprise.
Also by Aski
The Aski app — ask your Odoo in natural language by chat or voice, and get real figures from your phone.
aski.dev
Questions, or want a quick personalized demo? Email us at soporte@aski.dev — we are happy to answer questions or set up a short demo.
Support: soporte@aski.dev · License: OPL-1
About Aski
Aski
Odoo apps · cockpits, integrations & business intelligence
5+ years of hands-on Odoo experience — building and shipping real modules, integrations and analytics for companies across LATAM and Europe. Every app we publish is maintained and supported directly.
Custom Odoo modulesIntegrations & APIsBI & analyticsOdoo 16–19
Browse all Aski apps on Odoo Apps →| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 1689 |
| Technical Name |
jjro_edi_connector |
| License | OPL-1 |
| Website | https://aski.dev |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module