EDI Sale order import UBL endpoint
Provide default endpoint for importing sale orders.
This module is more an example on how you can create your own endpoint to manage such exchanges.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Adds a ready-made web endpoint that accepts UBL XML sale orders and creates an incoming EDI exchange record for later processing. It is installed automatically and is disabled by default until a backend is assigned.
This module provides a default entry point for receiving customer orders in UBL XML format through a web address, so external systems can send orders directly into Odoo.
It creates an EDI endpoint record named "UBL import SO" with the route /edi/ubl/input/sale_order, using the POST method and accepting XML content. The endpoint is created inactive, so it will not receive anything until someone enables it and assigns an EDI backend to it.
When the endpoint is active and receives XML, it parses the content and, if the XML is invalid, returns a bad request error. If the XML is valid, it creates an incoming EDI exchange record and replies with a confirmation message saying the order will be processed shortly, together with a reference identifier.
Because the module is set to install automatically, it appears as soon as its dependencies are present. It relies on the sale order import, UBL sale order import and EDI endpoint features, and it touches the edi.endpoint model and the sale.order.import parsing logic. No new menus or screens are added; the endpoint is configured from the existing EDI endpoint settings.
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.