Daily updates from Odoo
Wednesday, January 14, 2026
3 changes · saas-18.2
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
This update adds two new Unit of Measure codes – Minute (MIN) and Kilowatt hour (KWH) – to Odoo, aligning with UNECE Recommendation No.20 for Peppol. Previously, Odoo defaulted to a generic 'Units' code, which wasn't suitable for UBL/CII electronic invoices. This change ensures proper support for these key units, particularly benefiting localization modules like those for Chile and Turkey.
Original PR description
**Issue:** 2 UoM that is in the UNECE Recommendation No.20 for Peppol don't exist in Odoo: - MIN: Minute - KWH: Kilowatt hour Even if they are created manually, they are not used in the UBL/CII electronic invoices. Instead, the default code (i.e. "C62" for "Units" is used). Some localization modules create the "Kilowatt hour" UoM as they need it. (l10n_cl and l10n_tr_nilvera) So it's better to have a "generic" one available for every module. opw-5269119 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243333 Forward-Port-Of: odoo/odoo#238342
This update enables public users to register for document sharing without needing a traditional Odoo user account. Previously, a public user invited via link would be forced to create a user, which wasn't ideal. Now, the system intelligently creates a linked user for the partner, streamlining the document sharing process.
Original PR description
Purpose ======= We can share a document to a partner without a user, and with `access_via_link == 'none'`. In that situation, the partner is forced to create a user, but if he clicks on signup, then the new user won't be linked to the partner set on the `documents.access` (a new partner will be created). Now, when inviting a member, if he doesn't have a user, we invite him to create a user. If the partner has a user, then we just redirect him to the login page. Task-5242208 Forward-Port-Of: odoo/enterprise#100628