Odoo Changelog — 2026-07-10

Friday, July 10, 2026

3 changes · 17.0

New Features(2)

New functionality added to Odoo

[ADD] product_recycling: Added recycling reporting support.

Enterprise17.0product_recyclingl10n_se_product_recyclingMEDIUM

Adds product recycling reporting so businesses can track and report recycling-related product data more easily. The update also includes Swedish localization, helping companies meet local reporting needs in Sweden.

Original PR description

Product Recycling report. with Swedish localization.

Original sent as https://github.com/odoo/enterprise/pull/49404

#recycling#reporting#swedish-localization

[ADD] whatsapp_identifiers: support for business-scoped user IDs

PR #117782

Enterprise17.0whatsappwhatsapp_identifierstest_whatsappMEDIUM

Odoo can now recognize and contact WhatsApp users through business-specific identifiers when a phone number is not provided. This helps businesses keep conversations linked to the right customer and improves contact matching despite phone number formatting differences.

Original PR description

Add support for whatsapp business-scoped user ids as outline in the [documentation](https://developers.facebook.com/documentation/business-messaging/whatsapp/business-scoped-user-ids) for their introduction this June.

This effectively adds a table mapping BSUID to contacts to enable contacting users who contact the business directly, as the business will now not necessarily be provided with their number. Additionally the “whatsapp id”, i.e. the canonical form of the phone number as stored in whatsapp, is stored to help better match contacts regardless of formatting details in odoo and whatsapp.

task-5476552

#whatsapp#contacts#business messaging

Bug Fixes(1)

Resolved issues and error corrections

[FIX] appointment: get website url according to appointment config

PR #122669

Enterprise17.0appointmentwebsite_appointmentMEDIUM

Email buttons for appointments and event registrations now use the website tied to the booking or event, rather than a generic or recently visited website. This prevents customers in multi-website setups from being sent to the wrong site when managing appointments or registrations.

Original PR description

In Multiwebsite settings, when the public user interactions needs email generation (appointment or event flow), the email links are generated with a base url that does not corresponds to the one from which the request started.

Case 1:
- Have website A and website B
- Create an appointment page website A
- Log in via website B
- As public user, make an appointment in Website A
- Check the generated email

Issue: button links in the email will redirect to the wrong website, so users will encounter an issue when managing the appointment. This occurs because when an user log in, the system parameter 'web.base_url' is updated with the current url.
This parameter is then used as fallback when we need to retrieve the base url without an active record

Case 2:
- Have website A and website B
- Create an event and assign it to website B
- As public user, access the event and register to it
- Check the generated email

Issue: button links in the email will redirect to the wrong website, so users will encounter an issue when managing the event.
This occurs because the record `event.registration` has no website_id field and the base url is taken from the company default website (website A)

Backport with improvements of 15bae202d8f1b5bf70bbc63b2d89025e9237e6cf

opw-4146760
opw-4336369

#multi-website#email links#appointments#events

Add support for whatsapp business-scoped user ids as outline in the [documentation](https://developers.facebook.com/documentation/business-messaging/whatsapp/business-scoped-user-ids) for their introduction this June. This effectively adds a table mapping BSUID to contacts to enable contacting users who contact the business directly, as the business will now not necessarily be provided with their number. Additionally the “whatsapp id”, i.e. the canonical form of the phone number as stored in whatsapp, is stored to help better match contacts regardless of formatting details in odoo and whatsapp. task-5476552

In Multiwebsite settings, when the public user interactions needs email generation (appointment or event flow), the email links are generated with a base url that does not corresponds to the one from which the request started. Case 1: - Have website A and website B - Create an appointment page website A - Log in via website B - As public user, make an appointment in Website A - Check the generated email Issue: button links in the email will redirect to the wrong website, so users will encounter an issue when managing the appointment. This occurs because when an user log in, the system parameter 'web.base_url' is updated with the current url. This parameter is then used as fallback when we need to retrieve the base url without an active record Case 2: - Have website A and website B - Create an event and assign it to website B - As public user, access the event and register to it - Check the generated email Issue: button links in the email will redirect to the wrong website, so users will encounter an issue when managing the event. This occurs because the record `event.registration` has no website_id field and the base url is taken from the company default website (website A) Backport with improvements of 15bae202d8f1b5bf70bbc63b2d89025e9237e6cf opw-4146760 opw-4336369