Wednesday, August 20, 2025
16 changes
5 changes
Enhancements to existing features
The accounting tax helper documentation was improved to make it clearer which capabilities are available in point-of-sale JavaScript code and which are only available on the server side. This helps teams avoid confusion when maintaining tax-related logic across different parts of the system.
Original PR description
Since some of them are copy pasted javascript side, adding such docstring is helping to distinguish what is available directly js-side from point_of_sale from what is only accessible python-side. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#223330 Forward-Port-Of: odoo/odoo#223258
Point of Sale and related payment, loyalty, restaurant, and self-order modules now produce clearer diagnostic logs. This helps support and development teams identify where POS issues occur faster, reducing investigation time without changing the customer-facing checkout flow.
Original PR description
*: pos_adyen, pos_loyalty, pos_online_payment, pos_restaurant, pos_stripe Improve console logging in the Point of Sale and related modules. By using the `logPosMessage` utility function more…
*: pos_adyen, pos_loyalty, pos_online_payment, pos_restaurant, pos_stripe Improve console logging in the Point of Sale and related modules. By using the `logPosMessage` utility function more informations are now included in the console logs, such as the module name, function name, and a message. This makes it easier to track down issues and understand the flow of the application. Also when unfolding the console logs, some additional context is provided: - Variable values (if given to the console method) - Call stack trace (if available) Example of a log message: [IndexedDB]: put - Processing 40 items in store pos.order.line ### With its call stack: logPosMessage @ pretty_console_log.js:13 (anonymous) @ indexed_db.js:113 promises @ indexed_db.js:92 create @ indexed_db.js:193 synchronizeLocalDataInIndexedDB @ data_service.js:182 ..... ## Screenshots: <img width="779" height="764" alt="image" src="https://github.com/user-attachments/assets/6be024e4-e849-478b-9cdd-653300fc015a" /> https://github.com/user-attachments/assets/2342ca52-719c-4368-94e6-1e692faf12e0 Forward-Port-Of: odoo/odoo#222339
Users now receive a clear warning when enabling WhatsApp debug mode. This helps prevent surprises by explaining that media files will stop being received while debug mode is active.
Original PR description
#### Step to reproduce: - go to WhatsApp > Configuration > WhatsApp Buisness Account - enable debug mode #### Previous behavior: - active debug mode #### Expected behavior: - active debug mode - warn user that WhatsApp debug mode will stop medias from being received Other solutions would include the use of: - warning. They are triggered only on `onchange` methods. However, debug_logging is updated through buttons which do not trigger `onchange`. Therefore, to update it through a field it requires some changes in the XML which aren't appropriate for stable. - confirm using a wizard. It would require a new view which is not stable either. opw-4678542 Forward-Port-Of: odoo/enterprise#89995
The website generator now checks whether a provided URL can be reached before starting the scraping step. This helps avoid failed generation attempts and gives users a smoother setup experience when entering website addresses.
Original PR description
This commit checks that the URL is reachable before making the scraper request.
Point of Sale and related localization, IoT, enterprise, and mobile modules now produce clearer console logs with more context. This helps support and development teams diagnose POS issues faster without changing day-to-day user workflows.
Original PR description
*: l10n_de_pos_cert, l10n_de_pos_res_cert, l10n_it_pos, pos_enterprise, pos_iot, pos_mobile Improve console logging in the Point of Sale and related modules. By using the `logPosMessage` utility…
*: l10n_de_pos_cert, l10n_de_pos_res_cert, l10n_it_pos, pos_enterprise, pos_iot, pos_mobile Improve console logging in the Point of Sale and related modules. By using the `logPosMessage` utility function more informations are now included in the console logs, such as the module name, function name, and a message. This makes it easier to track down issues and understand the flow of the application. Also when unfolding the console logs, some additional context is provided: - Variable values (if given to the console method) - Call stack trace (if available) ## Example of a log message: [IndexedDB]: put - Processing 40 items in store pos.order.line ### With its call stack: logPosMessage @ pretty_console_log.js:13 (anonymous) @ indexed_db.js:113 promises @ indexed_db.js:92 create @ indexed_db.js:193 synchronizeLocalDataInIndexedDB @ data_service.js:182 ..... ## Screenshots: <img width="779" height="764" alt="image" src="https://github.com/user-attachments/assets/6be024e4-e849-478b-9cdd-653300fc015a" /> https://github.com/user-attachments/assets/2342ca52-719c-4368-94e6-1e692faf12e0 Forward-Port-Of: odoo/enterprise#92021
3 changes
Enhancements to existing features
This update adds automated test coverage for key Restaurant Point of Sale workflows, including table management, order courses, bill splitting, floor views, and tips. This helps reduce regressions and improves confidence that core restaurant operations continue to work reliably after future changes.
Original PR description
This commit introduces HOOT test coverage for the POS Restaurant module: - Added tests for primary models: restaurant.table, restaurant.order.course, and patched pos.order - Added tests for patched pos_store.js. - Added component tests for SplitBillScreen, FloorScreen and TipScreen. task-4945629
7 changes
Enhancements to existing features
Users are now warned when enabling WhatsApp debug mode that media files will stop being received. This helps prevent accidental disruption to WhatsApp media handling by making the impact clear before the setting is used.
Original PR description
#### Step to reproduce: - go to WhatsApp > Configuration > WhatsApp Buisness Account - enable debug mode #### Previous behavior: - active debug mode #### Expected behavior: - active debug mode - warn user that WhatsApp debug mode will stop medias from being received Other solutions would include the use of: - warning. They are triggered only on `onchange` methods. However, debug_logging is updated through buttons which do not trigger `onchange`. Therefore, to update it through a field it requires some changes in the XML which aren't appropriate for stable. - confirm using a wizard. It would require a new view which is not stable either. opw-4678542 Forward-Port-Of: odoo/enterprise#89995
1 change
Enhancements to existing features
The Point of Sale browser tab now displays the standard Odoo favicon. This makes the PoS page easier to recognize among open tabs and keeps it visually consistent with the main Odoo interface.
Original PR description
Before this commit: ==================== The POS UI did not display a favicon in the browser tab. After this commit: ================== The standard Odoo Point of Sale favicon is now displayed in the browser tab for the POS UI, consistent with the backend interface. Task-4978320
This update adds automated test coverage for loyalty features in Point of Sale, including gift cards, rewards, order handling, and related screens. It helps reduce the risk of loyalty-related issues reaching customers by validating key workflows during development.
Original PR description
In this commit: ======================= - Added HOOT tests for the `pos_loyalty` module. - Included tests for main models like `loyalty.card` and patched models: `pos.order` and `pos.order.line`. - Added tests for popups and screens related to loyalty features. task - 4945628
Users now see a warning when turning on WhatsApp debug mode, explaining that media files will stop being received. This helps administrators understand the operational impact before enabling the setting and reduces accidental disruption.
Original PR description
#### Step to reproduce: - go to WhatsApp > Configuration > WhatsApp Buisness Account - enable debug mode #### Previous behavior: - active debug mode #### Expected behavior: - active debug mode - warn user that WhatsApp debug mode will stop medias from being received Other solutions would include the use of: - warning. They are triggered only on `onchange` methods. However, debug_logging is updated through buttons which do not trigger `onchange`. Therefore, to update it through a field it requires some changes in the XML which aren't appropriate for stable. - confirm using a wizard. It would require a new view which is not stable either. opw-4678542 Forward-Port-Of: odoo/enterprise#89995
Signer labels in Sign templates now stay in sequence when people are added or removed. This avoids confusing gaps like “Signer 1, Signer 2, Signer 4” while preserving any custom names users have entered.
Original PR description
Currently, the sidebar of a sign template has an internal id which starts at 0 and is used as an id when you make an orm call to create a new sign.role.item record (a signer on the template). Until…
Currently, the sidebar of a sign template has an internal id which starts at 0 and is used as an id when you make an orm call to create a new sign.role.item record (a signer on the template). Until now, the id is also used to create the name of the signer, as "Signer {id}" but this is problematic if you eliminate signers and then create new ones because it leaves holes in the signer naming. The solution is to always use the length of the array containing the currently assigned signers as the number to insert into the name, since the new signer is always added at the end. Furthermore, when a signer is deleted, we should compute the names of the remaining signers to match their position in the array containing the assigned signers.
For example, if we create 4 signers, Signer {1,2,3,4} and then delete Signer 3, we would like Signer 4 to be renamed Signer 3, since the next added signer will be named Signer 4 according to the length of the array containing them. A small caveat is that we don't want to rename already renamed Signers, because we don't want to lose personalization.
This is the objective of this PR.
Task: 4985491Point of Sale and related country-specific POS modules now produce clearer diagnostic logs with added context such as where messages come from, variable details, and call traces. This helps support and development teams investigate POS issues faster without changing normal cashier workflows.
Original PR description
*: l10n_de_pos_cert, l10n_de_pos_res_cert, l10n_it_pos, pos_enterprise, pos_iot, pos_mobile Improve console logging in the Point of Sale and related modules. By using the `logPosMessage` utility…
*: l10n_de_pos_cert, l10n_de_pos_res_cert, l10n_it_pos, pos_enterprise, pos_iot, pos_mobile Improve console logging in the Point of Sale and related modules. By using the `logPosMessage` utility function more informations are now included in the console logs, such as the module name, function name, and a message. This makes it easier to track down issues and understand the flow of the application. Also when unfolding the console logs, some additional context is provided: - Variable values (if given to the console method) - Call stack trace (if available) ## Example of a log message: [IndexedDB]: put - Processing 40 items in store pos.order.line ### With its call stack: logPosMessage @ pretty_console_log.js:13 (anonymous) @ indexed_db.js:113 promises @ indexed_db.js:92 create @ indexed_db.js:193 synchronizeLocalDataInIndexedDB @ data_service.js:182 ..... ## Screenshots: <img width="779" height="764" alt="image" src="https://github.com/user-attachments/assets/6be024e4-e849-478b-9cdd-653300fc015a" /> https://github.com/user-attachments/assets/2342ca52-719c-4368-94e6-1e692faf12e0 Forward-Port-Of: odoo/enterprise#92544 Forward-Port-Of: odoo/enterprise#92021
This update streamlines how WhatsApp and live chat participant information is handled behind the scenes. It reduces unnecessary complexity, helping keep messaging features easier to maintain without changing the day-to-day user experience.
Original PR description
This commit reduces the usage of persona for the channel member model, unless we need to support guest and partner, the use of persona should be avoided. Follow up on task-4675777 PR community: https://github.com/odoo/odoo/pull/220063
The automated tests for rental and subscription combo product flows were updated to match the redesigned combo selection window. This helps keep checkout quality checks reliable after the interface change, reducing the risk of unnoticed issues in these sales flows.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/222337 task-4981539
The VoIP call list now shows the most recent calls at the top by default. This makes it easier for users to quickly review the latest activity without manually sorting the list.
The French VAT report submission wizard now includes an express mention option for reports sent through the Aspone service. This helps businesses correctly flag expedited submissions in the required report section.
Original PR description
This commit adds express mention in the wizard to send the tax report to aspone api. The express mention will be added in the zone BC of the tax report. Task-4933083