Odoo Changelog — 2025-10-10

Friday, October 10, 2025

3 changes · 17.0

Improvements(3)

Enhancements to existing features

[IMP] base: Removing ZIP code requirement for Peru

Core17.0base

Peruvian customer records no longer require a ZIP code. This makes customer data entry easier and better reflects local addressing practices, where ZIP codes are not commonly used.

Original PR description

As ZIP codes are not widely used in Peru, the requirement for a ZIP code to be provided for a Peruvian customer should not be present.

task-5012593


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#peru#zip-code#customer-data

[IMP] iot: use local targetAddressSpace for LNA

PR #96850

Enterprise17.0iotpos_iotMEDIUM

This update prepares Odoo IoT and POS IoT connections for upcoming Chrome local network access restrictions. It helps ensure local IoT devices remain reachable from Odoo in the browser, including when accessed through the odoo-iot domain, while also modernizing the connection code.

Original PR description

Community PR: https://github.com/odoo/odoo/pull/231014

Local Network Access restrictions will start shipping by default in
Chrome 142.

As part of this change, local requests will be allowed to use HTTP in an
HTTPS context (gated by a browser permission prompt). This will work
automatically when the IP is provided directly, however in the case of
IoT we often use the odoo-iot DNS domain to resolve the IP. In this
case, you must specify the option `targetAddressSpace: "local"` in the
`fetch` request.

This PR simply adds this change where appropriate. As part of this
we have also backported the change from jquery -> fetch.

task-5157145

#IoT#Chrome#local network#POS

[IMP] point_of_sale: use local targetAddressSpace for LNA

PR #231014

Core17.0point_of_saleMEDIUM

This update helps Odoo Point of Sale continue connecting to local IoT devices, such as hardware connected through an IoT box, as Chrome introduces stricter local network access rules. It reduces the risk of disruption for businesses using POS hardware when browsers enforce the new permission behavior.

Original PR description

Enterprise PR: https://github.com/odoo/enterprise/pull/96850

Local Network Access restrictions will start shipping by default in Chrome 142.

As part of this change, local requests will be allowed to use HTTP in an HTTPS context (gated by a browser permission prompt). This will work automatically when the IP is provided directly, however in the case of IoT we often use the odoo-iot DNS domain to resolve the IP. In this case, you must specify the option `targetAddressSpace: "local"` in the `fetch` request.

This commit simply adds this change where appropriate.

task-5157145

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#point-of-sale#iot#chrome#hardware

As ZIP codes are not widely used in Peru, the requirement for a ZIP code to be provided for a Peruvian customer should not be present. task-5012593 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Community PR: https://github.com/odoo/odoo/pull/231014 Local Network Access restrictions will start shipping by default in Chrome 142. As part of this change, local requests will be allowed to use HTTP in an HTTPS context (gated by a browser permission prompt). This will work automatically when the IP is provided directly, however in the case of IoT we often use the odoo-iot DNS domain to resolve the IP. In this case, you must specify the option `targetAddressSpace: "local"` in the `fetch` request. This PR simply adds this change where appropriate. As part of this we have also backported the change from jquery -> fetch. task-5157145

Enterprise PR: https://github.com/odoo/enterprise/pull/96850 Local Network Access restrictions will start shipping by default in Chrome 142. As part of this change, local requests will be allowed to use HTTP in an HTTPS context (gated by a browser permission prompt). This will work automatically when the IP is provided directly, however in the case of IoT we often use the odoo-iot DNS domain to resolve the IP. In this case, you must specify the option `targetAddressSpace: "local"` in the `fetch` request. This commit simply adds this change where appropriate. task-5157145 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr