Odoo Changelog — 2026-03-17

Tuesday, March 17, 2026

4 changes

Refactoring(4)

Code cleanup and technical improvements

[REF] website_helpdesk_livechat: livechatVisitorMember on channel

Enterprisemasterwebsite_helpdeskMEDIUM

This pull request enhances the Odoo Enterprise website's live chat functionality by streamlining the connection between live chat visitors and helpdesk channel members. Specifically, it moves relevant data fields to the channel level, improving organization and efficiency for support teams. This change ensures a smoother experience for both visitors and agents.

Original PR description

PR community: https://github.com/odoo/odoo/pull/242575

#live chat#helpdesk#channel

[MERGE] l10n_mx_reports: merge Mexican reporting modules

PR #103445

Enterprisemasterl10n_mx_reports

This update combines the Mexican reporting modules into a single, streamlined package. This simplifies maintenance and installation for users needing Mexican accounting reports, ensuring consistent reporting across the Odoo Enterprise platform. It maintains existing functionality without impacting current operations.

Original PR description

This PR merges the `l10n_mx_reports_closing` and `l10n_mx_xml_polizas` modules into `l10n_mx_reports`, as they all provide Mexican accounting reports and are required for standard reporting flows for any company.

This consolidation keeps all existing features unchanged while simplifying module maintenance and installation.

Related PR-https://github.com/odoo/odoo/pull/247185
Upgrade PR-https://github.com/odoo/upgrade/pull/9202/

task-5431997

#reporting#Mexico#accounting

[REF] pos_urban_piper: restructure & merge related modules

PR #100506

Enterprisemasterpos_urban_piperpos_restaurant_urban_piperMEDIUM

This update streamlines the integration with UrbanPiper by consolidating related modules and making the data synchronization process more efficient. The changes improve how order and store information is sent to UrbanPiper, leading to smoother delivery operations and better data management.

Original PR description

- Merged UrbanPiper modules into the `pos_urban_piper` module:
  - `pos_urban_piper_enhancements`
  - `pos_urban_piper_ubereats`

- Modularized the integration code.
  Each model now exposes its own methods for handling UrbanPiper data, such as:
  - `get_urban_piper_data` for preparing payloads sent to UrbanPiper.
  - Webhook event handlers implemented directly in their respective models:
    - Order-related events in `pos.order`
    - Store-related events in `pos.config`

- Removed the `product.urban.piper.status` model.
  Sync information is now stored in a JSON field: `urbanpiper_synced_json`.

Related: https://github.com/odoo/upgrade/pull/8966

task-[5361075](https://www.odoo.com/odoo/project/1737/tasks/5361075)

#urbanpiper#pos#delivery

[REF] l10n_mx_edi: adapt test to Store changes

PR #110943

Enterprisemasterl10n_mx_edi

This pull request updates the tests for the l10n_mx_edi module to align with recent changes in Mexican VAT reporting requirements. This ensures the Odoo Enterprise system continues to accurately handle and validate invoices related to Mexican e-invoicing (CFDI).

Original PR description

Enterprise counter-part.

https://github.com/odoo/odoo/pull/253922

#mexico#vat#edi#compliance

This PR merges the `l10n_mx_reports_closing` and `l10n_mx_xml_polizas` modules into `l10n_mx_reports`, as they all provide Mexican accounting reports and are required for standard reporting flows for any company. This consolidation keeps all existing features unchanged while simplifying module maintenance and installation. Related PR-https://github.com/odoo/odoo/pull/247185 Upgrade PR-https://github.com/odoo/upgrade/pull/9202/ task-5431997

- Merged UrbanPiper modules into the `pos_urban_piper` module: - `pos_urban_piper_enhancements` - `pos_urban_piper_ubereats` - Modularized the integration code. Each model now exposes its own methods for handling UrbanPiper data, such as: - `get_urban_piper_data` for preparing payloads sent to UrbanPiper. - Webhook event handlers implemented directly in their respective models: - Order-related events in `pos.order` - Store-related events in `pos.config` - Removed the `product.urban.piper.status` model. Sync information is now stored in a JSON field: `urbanpiper_synced_json`. Related: https://github.com/odoo/upgrade/pull/8966 task-[5361075](https://www.odoo.com/odoo/project/1737/tasks/5361075)