Daily updates from Odoo
Monday, August 10, 2026
4 changes · 17.0
Enhancements to existing features
The point of sale preparation display now retrieves pending orders much faster, especially when many orders are shown. This reduces waiting time for staff and helps busy locations keep their kitchen or preparation screens responsive.
Original PR description
Improve the execution time of _get_stageless_orders_in_display by replacing the OR condition with IN(subquery) by using UNION ALL to improve query performance. Benchmarks: | display orders count | Time Before | Time After | |-------------------------------|---------------------|------------------| | 1k | 84 s | 0.416 s | | 500 | 37.6 s | 0.150 s | | 250 | 19.4 s | 0.110 s | | 100 | 8 s | 0.068 s | opw-6420949
Belgian payroll now includes updated fiscal employment bonus rates scheduled from August 2026 and 2028. This helps payroll calculations stay aligned with upcoming legal changes for low-wage workers and general fiscal bonus treatment.
Original PR description
Starting from August 2026: - The increased fiscal rate for low-wage workers (Volet B) rises from 52.54% to 63% (and to 72% in 2028). - The general fiscal rate (Volet A) rises from 33.14% to 35% starting in 2028. This adds new rule parameters for the fiscal rates and updates computation logic to apply these rates Task-6438319
Resolved issues and error corrections
The Chilean electronic invoicing module now recognizes five new response codes introduced by SII. This prevents supplier electronic tax documents from getting stuck during claim or acceptance status processing after the SII regulatory update.
Original PR description
**Before this PR:** After the implementation of Resolution 161 of November 13th 2025, SII responses included keys not supported by the current l10n_cl_edi implementation. This resulted in supplier DTEs not being processed as they were before the change, because the five new keys were not found in Odoo's current `l10n_cl_claim` field, causing that the documents with these responses, were kept in a loop not solved. **After this PR:** The five new values from the resolution, along with their translations, were added to the selector field, fixing the process flow. **SII Reference:** https://www.sii.cl/normativa_legislacion/resoluciones/2025/reso161.pdf (see Event Code, page 5)
This fix prevents one Dutch Digipoort tax return record with missing accounting information from stopping status updates for all other records. The system now handles the missing closing entry gracefully, improving reliability for Dutch tax reporting workflows.
Original PR description
The `l10n_nl_reports_sbr_status_info` contains the `l10n_nl_reports_sbr.status.service` class. The class is responsible for fetching the status of sent Digipoort tax returns. The status is then posted as a chatter message to the tax return's closing entry. Issues can arise when one of the status service records is, for whatever reason, missing a closing entry. In such case, the message cannot be posted, resulting in an exception being raised. Since the records are processed in a loop without a try-catch, this causes the whole action to fail. This can lead to one broken record effectively shutting down the whole module's functionality. This PR adds some if-else checks to gracefully handle the case where the closing entry is missing. Related tickets: opw-5901446 and opw-6410082