Daily updates from Odoo
Monday, August 25, 2025
9 changes
1 change
Enhancements to existing features
The scale certification screen now displays the Point of Sale version instead of the IoT device version. This gives users the relevant version information when checking certified scale status, reducing confusion during compliance or support checks.
Original PR description
We need to display the PoS Version, not the IoT version. Forward-Port-Of: odoo/enterprise#91682
3 changes
Enhancements to existing features
This update adds automated test coverage for point-of-sale IoT device setup and core device workflows. It also validates Six payment terminal integration, helping reduce regressions in connected payment and hardware scenarios.
Original PR description
*: pos_iot, pos_iot_six In this commit: ------------------ - Loaded data for `iot.box`, `iot.device`, and `iot.channel` to test the complete IoT flow from setup to core device functionalities. - Added payment method records and validated the payment terminal integration using Six. task- 4945645 Related PR: https://github.com/odoo/odoo/pull/220801
The scale certification screen now displays the Point of Sale version instead of the IoT device version. This helps users and auditors see the relevant software version for certification checks and avoids confusion during compliance reviews.
Original PR description
We need to display the PoS Version, not the IoT version. Forward-Port-Of: odoo/enterprise#91682
OCR result fetching was streamlined by removing extra transaction checkpoints that could slow processing when many documents were handled at once. This should improve performance in document extraction workflows, with only a minor tradeoff in rare cases where a user edits a document at the same time OCR updates it.
Original PR description
Very similar to commit 7f7ff8d, see full explanation in that commit message. This savepoint was also initiated in a loop which could cause performances issues when too many of them are active at the same time. This one is much less critical and can be removed without much trouble. It was only allowing to recover from a serialization failure, in the case where a user was concurrently editing a document while it was being updated by the OCR.
4 changes
Enhancements to existing features
The salary offer form was adjusted so the salary structure field no longer shows a dropdown icon. This makes the field presentation clearer and avoids suggesting an action that may not be relevant for users preparing salary offers.
Original PR description
task-5025998
The scale certification status now shows the Point of Sale version instead of the IoT version. This makes the certification information clearer and ensures users see the version that matters for their PoS compliance checks.
Original PR description
We need to display the PoS Version, not the IoT version. Forward-Port-Of: odoo/enterprise#91682
Products in UrbanPiper point of sale can now be grouped by the delivery locations where they are available. This helps teams review and manage location-specific product availability more quickly.
Original PR description
In this commit: ------------------ - Added a groupby filter to easily organize products based on their availability at different delivery locations. task: 4942185
Marketing automation now keeps the exclusion list option hidden when it is already enabled, preventing users from turning it off by mistake. If the option was disabled through another method, it remains visible so teams can identify and restore the recommended setting.
Original PR description
We hide the field use_exclusion_list to prevent user to disable it (enabled by default). We still displays it if it has been disabled by another way (ex.: programmatically). Indeed, it doesn't make sense to disable it in a marketing context. Task-3575361
1 change
Enhancements to existing features
When an Indian EDI e-invoicing retry is triggered, Odoo now records a message on the related accounting document. This helps businesses see which user retried the process, improving traceability especially when repeated requests can lead to temporary GST request blocks.
Original PR description
Following the implementation of [Black list request by GST](https://github.com/odoo/iap-apps/pull/1039) the users are blocked for 24 hours on generating too many request. When processing through EDI there is no log when clicked on the retry button, Which is more essentially needed now to know by which user the EDI was retried and we logged the same on the move --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#223886 Forward-Port-Of: odoo/odoo#207184