Odoo Changelog — 2026-04-07

Tuesday, April 7, 2026

2 changes · 19.0

Improvements(2)

Enhancements to existing features

[IMP] delivery_fedex_rest: add ETD custom invoice upload and enhanced references

Enterprise19.0delivery_fedex_restMedium

This update adds the ability to automatically upload Odoo invoices to FedEx, ensuring accurate export documentation and matching accounting records. It also introduces enhanced shipment tracking with customizable PO numbers, customer references, and invoice numbers for improved visibility. These features are optional and maintain compatibility with existing FedEx shipping configurations.

Original PR description

Add two new configurable options to the FedEx shipping integration:

1. ETD with Odoo Invoice (new documentation_type option): New 'ETD with Odoo Invoice' option in the Generate Invoice setting. When selected, the module uploads the Odoo-generated invoice PDF to FedEx Documents API (encodedmultiupload endpoint) and references it in the shipment request as an ETD attached document. This replaces the FedEx-generated commercial invoice with the actual Odoo invoice, ensuring export documents match accounting records. Requires a posted invoice on the SO before shipping. Note: FedEx Documents API uses a different base URL (documentapi.prod.fedex.com) than the Ship API.

2. Enhanced References (new Boolean field): When enabled, shipment package references include up to 3 fields:
   - PO Number: Customer Reference from SO (client_order_ref), or SO number if not set
   - Customer Reference: SO number
   - Invoice Number: Odoo posted invoice number When disabled, existing behavior is preserved (PO Number = SO number).

Both features are opt-in via carrier configuration fields, preserving full backward compatibility with existing setups.

#fedex#shipping#invoice#tracking

[IMP] databases: add list of db to res_users view

PR #112645

Enterprise19.0enterpriseMedium

This update simplifies user database access management by adding a dedicated 'databases' tab to the res.user view. Previously, administrators had to manually search for user database access, now it's readily available. This improves efficiency and simplifies user permission management.

Original PR description

The aim of this commit is to allow db_manager to see the list of databases in which a specific user has access and to allow removing this access in bulk if required.

Before this commit:
To see the list of db in which a user has access, a db_manager would have to go to the list view and make a search on the login/name of the user, potentially matching other db_user in the process.

After this commit:
The list of db is available out of the box in a databases tab on the res.user view.

Task-id: 5945298

#users#databases#permissions

Add two new configurable options to the FedEx shipping integration: 1. ETD with Odoo Invoice (new documentation_type option): New 'ETD with Odoo Invoice' option in the Generate Invoice setting. When selected, the module uploads the Odoo-generated invoice PDF to FedEx Documents API (encodedmultiupload endpoint) and references it in the shipment request as an ETD attached document. This replaces the FedEx-generated commercial invoice with the actual Odoo invoice, ensuring export documents match accounting records. Requires a posted invoice on the SO before shipping. Note: FedEx Documents API uses a different base URL (documentapi.prod.fedex.com) than the Ship API. 2. Enhanced References (new Boolean field): When enabled, shipment package references include up to 3 fields: - PO Number: Customer Reference from SO (client_order_ref), or SO number if not set - Customer Reference: SO number - Invoice Number: Odoo posted invoice number When disabled, existing behavior is preserved (PO Number = SO number). Both features are opt-in via carrier configuration fields, preserving full backward compatibility with existing setups.

The aim of this commit is to allow db_manager to see the list of databases in which a specific user has access and to allow removing this access in bulk if required. Before this commit: To see the list of db in which a user has access, a db_manager would have to go to the list view and make a search on the login/name of the user, potentially matching other db_user in the process. After this commit: The list of db is available out of the box in a databases tab on the res.user view. Task-id: 5945298