Plug sale_order_import into EDI machinery.
This module creates a default EDI exchange type needed to import sale orders.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Adds a ready-to-use EDI exchange type that lets Odoo import sales orders received as UBL XML files. It is installed automatically when the related EDI and UBL sales order import modules are present.
This module does not add any new screen or button. Its only job is to create one configuration record in the EDI machinery so that incoming UBL XML files can be recognised and turned into sales orders.
The record created is an EDI exchange type named "UBL import sale order" with the code ubl_import_so. It is set as an incoming (input) exchange, uses the UBL backend type, expects files with the .xml extension, and is linked to the processing usage input.process.sale.order.
Because the module is marked to install automatically, it appears as soon as its dependencies are installed: the generic EDI UBL module, the EDI sales order import module and the UBL sales order import module. Users then find this exchange type available in the EDI configuration area, where it can be selected when setting up an incoming exchange for a UBL backend.
In practice, this means a business can receive customer purchase orders in UBL XML format through the EDI framework and have them processed as sales orders, without manually creating a new exchange type. No models, menus, business rules, checks or scheduled jobs are added by this module itself; the actual import logic comes from the modules it depends on.
Text generated by AI (DeepSeek) from reading the Odoo 14.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 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/edi.
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.