This module provides an example on how to configure and exchange type for EDIFACT standard, as well as some test coverage for importing orders with the same standard.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Adds a ready-made demo configuration for importing EDIFACT sales orders into Odoo, so users can test the EDIFACT order import flow without setting it up from scratch.
This module does not add new screens or buttons. Its purpose is to provide a demonstration exchange type for the EDIFACT standard on sales, plus the test coverage that comes with it.
What it actually creates is a demo record of the exchange type used by the EDI framework, named "Demo EDIFACT Sale Order". This record is linked to the demo EDIFACT backend and backend type, is set as an input exchange (incoming files), and expects files with the .txt extension.
The exchange type is preconfigured to process incoming files through the sale order import flow. Its default values for the import wizard are: file extension 'edi', release 'd96a', document type 'rfq', order confirmation turned off, price source taken from the order, and import type 'edifact'. In plain terms, when a user runs this demo exchange, Odoo will read an EDIFACT request-for-quote file and create a sales order from it, without automatically confirming the order and using the prices found in the file.
Because it depends on sale_order_import_edifact, edi_sale_oca, edi_edifact_oca and sale_stock, it sits on top of the existing EDI sales and stock integration. It is mainly useful for demonstrations and automated tests of the EDIFACT sales order import, not for day-to-day production use.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 16.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/edi-framework.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.