This module adds a Transporter field (link to a partner) in the delivery carrier.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Adds a Transporter field to delivery carriers so you can link each carrier to the partner that actually performs the delivery.
This module extends the delivery carrier configuration in Odoo. On the delivery carrier form, a new field called Transporter is added just before the integration level field. It is a link to a contact (partner) record, and its tooltip explains that it is the partner doing the delivery service.
- Where it appears: the delivery carrier form, the same screen where you set up shipping methods such as fixed price or rules-based carriers.
- What it lets you do: record which contact or company is the actual transporter behind a given carrier, for example the external logistics company handling shipments.
- Business rules: none. The field is optional and the module adds no automatic checks, computations, default values, restrictions, emails or scheduled jobs.
- Areas touched: only the delivery carrier model (
delivery.carrier) and its form view are modified; no other models, menus or reports are added.
Because the code is small and contains no methods, the module is purely a data-entry convenience: it stores the transporter contact on the carrier for reference and reporting purposes, without changing how shipping prices or deliveries are calculated.
Depends on
Required by other modules
Models and fields (1)
- delivery.carrier · extends an existing modelpartner_id (Transporter)
Text generated by AI (DeepSeek) from reading the Odoo 19.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: 8 confirmed, 1 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/delivery-carrier.
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.