OdooWiki OCA HUB

Carrier accounts configuration with server_environment

carrier_account_environment folder_open OCA/delivery-carrier open_in_new
Tools License: AGPL-3

This module allows to configure carrier informations using the server_environment mechanism: you can then have different servers for the production and the test environment.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Lets administrators store carrier account credentials (account and password) in server configuration files instead of typing them in Odoo, so production and test servers can use different carrier logins.

This module extends the carrier account feature so that its sensitive connection details can be kept outside the database, in the server configuration files used by the server_environment mechanism.

  • The carrier account record gains two configuration-managed fields: account and password. Their values are read from the server configuration files rather than entered manually in Odoo.
  • A global configuration section named carrier_account is used to organise these settings in the configuration files.
  • Because the values come from the server environment, the same Odoo database can behave differently on a production server and on a test server, each pointing to its own carrier credentials.
  • The module depends on server_environment and delivery_carrier_account, so it only adds this configuration behaviour on top of the existing carrier account model (carrier.account).

No new menus, buttons, reports, scheduled jobs or business rules are introduced by the code shown. The change is limited to how carrier account credentials are supplied and stored.

Models and fields (1)
  • carrier.account · new model

Text generated by AI (DeepSeek) from reading the Odoo 18.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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 3 confirmed, 6 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

OCA documentation · Odoo 18.0

With this module installed, the delivery carrier are configured in the server_environment_files module (which is a module you should provide, see the documentation of server_environment for more information).

In the configuration file of each environment, you may first use the section [carrier_account].

Then for each server, you can define additional values or override the default values with a section named [carrier_account.resource_name] where "resource_name" is the name of the server.

Example of config file :

[carrier_account] # here is the default format file_format = 'ZPL'

[carrier_account.mycarrier] name = mycarrier account = 587 password = 123promenons-nous-dans-les-bois456cueillir-des-saucisses

[carrier_account.mycarrier2] name = mycarrier2 account = 666 password = wazaaaaa file_format = PDF

As an alternative of server_environment_files, there is also a module named server_environment_data_encryption which allow to set the environement dependent values directly in the database, by the user itself. It will be encrypted, to avoid security issues with secrets, see the documentationn of server_environment_data_encryption for more information. The advantage of setting the environment dependent value directly in the database is that it does not require a developper/odoo administrator to change a carrier account.

Once configured, Odoo will read the carrier values from the configuration file related to each environment defined in the main Odoo file or in carrier.account model.

No verified information in OCA: Installation.

info

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.