TODO
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Adds ready-to-use demo EDI exchange types so Odoo can receive UBL sale orders from a UBL backend and send back a UBL sale order response. It wires the incoming XML to the sale order import wizard.
This module is a configuration module for Electronic Data Interchange (EDI) on sales. It does not add new screens or models; instead it creates two demo exchange types on the edi.exchange.type model that show how UBL sale order exchanges are set up.
- An incoming exchange type named "Demo UBL Sale Order" receives XML files in UBL format from a UBL backend. It is linked to the sale order import process (
input.process.sale.order), so the received file is passed to the sale order import wizard. The demo settings passdefault_confirm_order: falseanddefault_price_source: 'pricelist'to that wizard, meaning imported orders are not automatically confirmed and prices come from the pricelist. - An outgoing exchange type named "Demo UBL Sale Order Response" produces an XML response file. The incoming type references it as its acknowledgement type, so a response can be generated for each received order.
Both exchange types use the UBL backend type and the demo UBL backend, generate XML files with a filename pattern based on record name, type code and date, and use the sale order and sale order line state workflows provided by the related EDI sales modules. Because this is demo data, it is meant as a working example to copy when configuring real UBL sale order exchanges.
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.