This module automatically assigns the EDI source to records created through the EDI mechanism.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Automatically tags records created through EDI with an 'EDI' source, so you can see which contacts, leads or other records came in via electronic data interchange.
This module links the EDI framework with Odoo's marketing/UTM tracking. It creates a ready-made source named 'EDI' in the UTM sources list.
When a record is created through the EDI mechanism, the module checks whether the record has a source field, whether it is linked to an EDI exchange record, and whether no source was already set. If all of that is true, it automatically fills in the 'EDI' source.
- The source is applied only at creation time, not when records are later edited.
- If a source is already provided, it is left untouched.
- The behaviour applies to any model that uses the EDI exchange consumer mixin, so it can affect several record types that support EDI.
There are no new menus or screens: the change happens silently in the background. Users will simply notice that records arriving through EDI show 'EDI' as their source in the usual source field, making it easier to filter and report on EDI-originated data.
Depends on
Models and fields (1)
- edi.exchange.consumer.mixin · extends an existing model
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.