Daily updates from Odoo
Wednesday, January 14, 2026
16 changes
1 change
Enhancements to existing features
This update allows system administrators to customize the main Odoo Enterprise home menu with a targeted message. Administrators can set a message via a database configuration, such as a maintenance notification, which will then be displayed to all users. This provides a flexible way to communicate important information directly to users.
Original PR description
Display a message on home menu based on an ir.config_parameter that can be added directly in the database by the system administrator.
The ir.config_parameter is sysadmin.message and should be a json loadable. The format shoud be something like this:
{
"type": "warning",
"replace": false,
"warning_type": "user",
"message": "`<span>A maintenance operation is planned on your server on <strong>2026-01-15</strong> between 14h and 15h</span>`"
}
Forward-Port-Of: odoo/enterprise#103831
Forward-Port-Of: odoo/enterprise#1022391 change
Enhancements to existing features
This update adds three new fields to invoices generated within the Chorus Pro system: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields ensure invoices comply with Chorus Pro requirements, improving data accuracy and facilitating seamless integration with the Chorus Pro platform.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
1 change
Enhancements to existing features
This update adds three new fields to invoices generated for Chorus Pro compliance – Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header, allowing for accurate documentation required by Chorus Pro and improving data tracking for financial reporting.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
1 change
Enhancements to existing features
This update adds three new fields to Odoo invoice PDFs – Buyer Reference, Contract Reference, and Purchase Order Reference – to ensure compliance with Chorus Pro requirements. These fields allow users to accurately document key purchase information directly on the invoice, simplifying the invoicing process for Chorus Pro clients.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
5 changes
Enhancements to existing features
This update enhances our document generation to meet the stricter PDF/A-3A standard, ensuring compatibility with a wider range of PDF viewers and archiving systems. The changes address previous validation failures and incorporate new requirements for PDF/A-3A compliance, improving document accessibility and long-term preservation.
Original PR description
This commit upgrades our PDF/A compliance from 3B to 3A, and fixes a few issues previously undetected due to the different PyPDF libraries we're currently supporting that made the previous PDF fails…
This commit upgrades our PDF/A compliance from 3B to 3A, and fixes a few issues previously undetected due to the different PyPDF libraries we're currently supporting that made the previous PDF fails even the 3B validation. Improvement 1: PDFA validators were previously detecting our file as 3B. Hence we update the metadata content `conformance` to `A`. Issue 2: When using `._pypdf` library, we failed the 6.1.2-2 and 6.8-1 rule even though we have implemented them on the previous version. It seems that this is caused by the `if SUBMOD...` check only ensuring it's not equal to `_pypdf2_2` (which makes it trigger for the new `_pypdf`). Hence, we reclarify the comments and fix the IF check. Issue 3: After implementing issue 2, it seems that a traceback occurs every time we're using `._pypdf` and calling the pdf write method. This is because the added characters on the header can't be decoded with `UTF-8`. Hence we change it to other greater-than-127-bytes characters that can still be decoded with `UTF-8`. (The actual character used here doesn't matter). Improvement 4: To be compliant with the new 3A rules (additional rules not there in 3B when we first implemented them), we add a minimal mark info dictionary and document structure on the PDF catalog object (`_root_object`). task-None Forward-Port-Of: odoo/odoo#243171 Forward-Port-Of: odoo/odoo#234960
This update enhances the offline experience by visually disabling unavailable menus, view switchers, and records within kanban and list views. The system now intelligently uses IndexedDB to track visited items, ensuring a more responsive and user-friendly offline experience. This prepares for a future offline search bar feature.
Original PR description
With this commit, when being offline, menus, view switchers and records (in kanban and list views) that aren't available are disabled (i.e. displayed with opacity and not-allowed cursor). Those disabled elements are still clickable though, but it's highly unlikely that clicking on them would lead to anything but an empty screen (due to the lack of connection). All such items aren't disabled though: we store in indexeddb the list of visited items (actions, view types, records), s.t. we know what is available in cache, and what is then accessible offline. This commit also prepares the ground for the next task, which is to have an offline search bar, allowing to select among previously enabled filters, in kanban and list views. Task~5424765
This update improves the Odoo Enterprise application's performance when operating offline. Specifically, the home menu now intelligently disables unavailable menus, preventing users from attempting to access features that aren't supported in offline mode. This enhances the user experience and reduces potential errors.
Original PR description
This commit is the counterpart of https://github.com/odoo/odoo/pull/242494. When being offline, we disable menus that aren't available offline in the home menu. Task~5424765
This update enhances the visual appearance of Odoo’s onboarding samples across several modules, including loyalty and point-of-sale. By aligning the layout, colors, and icons with Odoo’s established UI standards, this change improves the overall user experience and ensures a more polished look for new users. This work addresses previous inconsistencies and strengthens brand consistency.
Original PR description
*: survey, point_of_sale, pos_restaurant - requires : https://github.com/odoo/enterprise/pull/98400 - extracted from: https://github.com/odoo/odoo/pull/228308 Before this commit, some onboarding suggestions were not fully aligned with Odoo’s UI standards. This commit readjusts the layout, colors, icons to ensure better visual consistency with others onboarding suggestions samples. task-5089102 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances the visual appeal of the Odoo onboarding experience by aligning colors with Odoo’s design standards. The changes focus on improving the overall look and feel, ensuring a more polished and professional first impression for new users. This improves brand consistency and user experience.
Original PR description
*: marketing_automation_website_sale, marketing_automation_crm, appointment - requires : https://github.com/odoo/odoo/pull/233666 - extracted from : https://github.com/odoo/enterprise/pull/95384 Before this commit, some onboarding suggestions were not fully aligned with Odoo’s UI standards. This commit adjusts colors to ensure better visual consistency. task-5089102
4 changes
Enhancements to existing features
This update adds key reference fields – Buyer Reference, Contract Reference, and Purchase Order Reference – to the invoice PDF generated by the l10n_fr_facturx_chorus_pro module. These fields are required for Chorus Pro compliance, ensuring invoices meet the necessary documentation standards.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
This update allows system administrators to customize the main Odoo home menu with a targeted message. Administrators can set a message through a database configuration, such as a planned server maintenance notification. This provides a flexible way to communicate important information directly to users.
Original PR description
Display a message on home menu based on an ir.config_parameter that can be added directly in the database by the system administrator.
The ir.config_parameter is sysadmin.message and should be a json loadable. The format shoud be something like this:
{
"type": "warning",
"replace": false,
"warning_type": "user",
"message": "`<span>A maintenance operation is planned on your server on <strong>2026-01-15</strong> between 14h and 15h</span>`"
}
Forward-Port-Of: odoo/enterprise#103831
Forward-Port-Of: odoo/enterprise#102239This update clarifies the certificate scope field in the Spanish EDI SII localization module. It now only displays this field when the company is located in Spain, preventing confusion for users working with other Odoo localizations. This ensures accurate reporting and simplifies the certificate management process for Spanish businesses.
Original PR description
Will make it visible the scope fiel only if the company country is ES. The field will remain invisible as defined in the certificate module for other cases. This way we avoid to show this field on certificates that use other localizations that can confuse to the user. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances error tracking within the Stripe expense module by providing full traceback logs when errors occur during webhook events. Additionally, a fix was implemented to prevent unnecessary communication with Stripe when a card is being destroyed, streamlining the process and improving efficiency.
Original PR description
## [IMP] hr_expense_stripe: full traceback logging When a pyhon error is raised during a webhook event we only get the error main line, not the full traceback. This adds the full traceback message to the log ## [FIX] hr_expense_stripe: Fix returned card error When a card is returned to the factory for destruction, when Stripe sends us the information, we sent a payload to stripe. This makes no sense as the card has been updated by Stripe into a state that doesn't allow further changes
3 changes
Enhancements to existing features
This update adds three new fields to Odoo invoice PDFs – Buyer Reference, Contract Reference, and Purchase Order Reference – to ensure compliance with Chorus Pro requirements. These fields allow users to accurately document key purchase information directly on the invoice, streamlining the Chorus Pro process. This change improves data accuracy and reporting.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
This update optimizes the process of determining user permissions for documents, resulting in faster performance. This change enhances the overall responsiveness of the Enterprise application when working with documents. It's a performance improvement focused on the Documents module.
Original PR description
This commit is a backport of the improvement introduced in the following commit 706ee0c68c774f01b76802fe513aec52df16678c.
This update simplifies the process of generating UBL invoices for Colombia and Mexico by refactoring internal code and automating the customer/supplier swap for vendor bills. This change enhances the flexibility and maintainability of the UBL export functionality, ensuring compliance with local tax regulations.
Original PR description
For the Self-billing backport, we made two modifications which entail a small change in the l10n_co_dian and l10n_mx_edi code: - `_check_move_constrains` has been refactored to call a new `_get_move_constraints` method, which is more easily extensible. We perform the same modification in l10n_mx_edi. Note `_check_move_constrains` is still there, so any overrides will still work. - The customer and supplier are now swapped by default when exporting a vendor bill UBL, so it's no longer needed to do this specifically for the DIAN UBL. Community PR: https://github.com/odoo/odoo/pull/232548 Backport of https://github.com/odoo/enterprise/pull/92205 task-5153851