Odoo Changelog — 2026-08-08

Saturday, August 8, 2026

5 changes · master

Improvements(5)

Enhancements to existing features

[IMP] website_sale_subscription: add recurring donation product image

Enterprisemasterwebsite_sale_subscription

The recurring donation product now includes a default placeholder image in the website shop. This gives donation pages a more complete and consistent appearance when no custom product image is set.

Original PR description

Added placeholder image for the recurring donation product.

task-6361612

Forward-Port-Of: odoo/enterprise#126209

#donations#website#product image

[IMP] timesheet_grid: add extra built in aw rules

PR #124774

Enterprisemastertimesheet_gridMEDIUM

The timesheet assistant now includes additional built-in rules based on beta tester feedback, making it more useful out of the box. The beta warning has also been removed, reflecting that the feature is now considered ready for regular use.

Original PR description

This commit's purpose is to add a few built in aw rules, as that was a demand from the odoo expert who beta tested the assistant. It also removes the 'beta' warning, as the feature is reaching a useable state.

task-6385660

#timesheets#assistant#rules

[IMP] spreadsheet_edition: translate list headers

PR #127039

Enterprisemasterspreadsheet_editionspreadsheet_dashboard_editionMEDIUM

Spreadsheet list headers can now be translated, making dashboards easier to understand for users working in different languages. The change also ensures these header terms are detected for translation when spreadsheet data is processed.

Original PR description

This commit adds the support to translate list headers in the spreadsheet, as well as the term extraction from the json.

Task: 6452895

#translations#spreadsheets#dashboards

[IMP] l10n_hk_hr_payroll: Rental System adjustment

PR #127156

Enterprisemasterl10n_hk_hr_payrolltest_l10n_hk_hr_payroll_accountMEDIUM

Hong Kong payroll users can now attach multiple rental payment proofs through a clearer button-based flow instead of a single confusing field. The rental similarity check was also refined to avoid false matches, especially after migrations or for non-overlapping rentals from the same employee.

Original PR description

As the system now starts to be used by real users, we noticed a few points of improvement that can easily be done in stable and will provide a better UX when interacting with the system.

The payment proof as a field was a consequence of multiple iterations of the system; but it ended up only as a way to input the proof and nothing else.
It is confusing, only allows one proof at a time, and is overall not nice to use.
To improve that, we will remove the field and replace it with an 'Attach Payment Proof' button similar to the expense app, allowing for a better experience.

The similar rental check was checking even if all the related fields were empty. On a database migrating from a previous version, this leads to ALL the rentals to be marked as similar, which isn't ideal.
The same check was also comparing multiple rentals from the same employee as long as they are active. As rentals for an employee cannot overlap, it makes no sense to check this case and cause false positives.

task-6448054

Forward-Port-Of: odoo/enterprise#126764

#payroll#rental#user experience#Hong Kong

[IMP] l10n_de_pos_cert: improve short and long tx synchronization flow

PR #120706

Enterprisemasterl10n_de_pos_certl10n_de_pos_res_certMEDIUM

German POS certification now handles retail and restaurant transaction synchronization separately, matching Fiskaly’s expected workflows. This improves compliance reliability by starting transactions earlier, reducing unnecessary updates for retail sales, and ensuring restaurant kitchen changes are synchronized accurately without duplicating already sent items.

Original PR description

In this commit: ------------------ - Maintain separate Fiskaly transaction flows for retail (short tx) and restaurant (long tx) orders as discussed with the Fiskaly team. - `Initialize order…

In this commit:
------------------
- Maintain separate Fiskaly transaction flows for retail (short tx) and restaurant (long tx)
  orders as discussed with the Fiskaly team.
- `Initialize order transactions` with an empty payload when the `first product` is added.
- Start `receipt transactions` with an empty payload when the `first payment line` is added.
- For retail flows, no intermediate order updates are sent to Fiskaly before finalization.
- For restaurant flows, create additional transaction updates during kitchen synchronization.
  Ensure already synchronized products are not resent, and only newly added or updated
  quantities are included in the payload.
- `Finalize order and receipt transactions` with complete order lines and payment details
  when we validate the order.

task: 6208963

Reference:
<img width="1863" height="1285" alt="de_tss_flow" src="https://github.com/user-attachments/assets/9140788e-7948-4a08-9f11-27197b22ca8b" />

Forward-Port-Of: odoo/enterprise#120529
Forward-Port-Of: odoo/enterprise#117526

#German localization#POS#Fiskaly#compliance

This commit's purpose is to add a few built in aw rules, as that was a demand from the odoo expert who beta tested the assistant. It also removes the 'beta' warning, as the feature is reaching a useable state. task-6385660

As the system now starts to be used by real users, we noticed a few points of improvement that can easily be done in stable and will provide a better UX when interacting with the system. The payment proof as a field was a consequence of multiple iterations of the system; but it ended up only as a way to input the proof and nothing else. It is confusing, only allows one proof at a time, and is overall not nice to use. To improve that, we will remove the field and replace it with an 'Attach Payment Proof' button similar to the expense app, allowing for a better experience. The similar rental check was checking even if all the related fields were empty. On a database migrating from a previous version, this leads to ALL the rentals to be marked as similar, which isn't ideal. The same check was also comparing multiple rentals from the same employee as long as they are active. As rentals for an employee cannot overlap, it makes no sense to check this case and cause false positives. task-6448054 Forward-Port-Of: odoo/enterprise#126764

In this commit: ------------------ - Maintain separate Fiskaly transaction flows for retail (short tx) and restaurant (long tx) orders as discussed with the Fiskaly team. - `Initialize order transactions` with an empty payload when the `first product` is added. - Start `receipt transactions` with an empty payload when the `first payment line` is added. - For retail flows, no intermediate order updates are sent to Fiskaly before finalization. - For restaurant flows, create additional transaction updates during kitchen synchronization. Ensure already synchronized products are not resent, and only newly added or updated quantities are included in the payload. - `Finalize order and receipt transactions` with complete order lines and payment details when we validate the order. task: 6208963 Reference: <img width="1863" height="1285" alt="de_tss_flow" src="https://github.com/user-attachments/assets/9140788e-7948-4a08-9f11-27197b22ca8b" /> Forward-Port-Of: odoo/enterprise#120529 Forward-Port-Of: odoo/enterprise#117526