Daily updates from Odoo
Navigate
Branch
Thursday, August 29, 2019
10 changes
New functionality added to Odoo
Point of Sale now supports US-style tipping, including adding a tip after an order is completed and capturing the final amount on the card. Bars and restaurants can also open customer tabs by validating a card and linking the cardholder name to the order, with Adyen support for the required payment flow.
Original PR description
*Draft until https://github.com/odoo/odoo/pull/35702 and it's enterprise counterpart are merged.* This adds a pos_tipping module which defines some generic code meant to handle tipping. One part…
*Draft until https://github.com/odoo/odoo/pull/35702 and it's enterprise counterpart are merged.* This adds a pos_tipping module which defines some generic code meant to handle tipping. One part which is common in restaurants/bars allows a user to add a tip after the order is completed. This will result in the total + that tip being captured. Another part is meant for easily retrieving orders in a bar environment. When everybody orders drinks at the bar it's hard to keep track of all the tabs. This adds an "Open Tab" button which does two things: - Authorizes the current order amount on the credit card, this way we validate the card is good. This amount will be cancelled at the end. - Associates the card holder's name to the order. This name can be used in a new interface that allows searching for an order by name. This also includes pos_adyen_tipping which is a concrete implementation for Adyen. Adyen needs to be configured to Manual Capture mode for this to work. Additionally Adyen needs to be configured to allow overcaptures (capturing more than what was initially authorized) to handle tips. https://www.odoo.com/web?debug#id=1935923&action=327&model=project.task&view_type=form&menu_id=4720
Enhancements to existing features
This update improves how inventory and manufacturing records behave when several companies are managed in the same Odoo database. It helps keep stock moves, locations, lots, pickings, and manufacturing documents aligned with the correct company, reducing operational errors across company boundaries.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Service products always have zero stock quantity, so Odoo now assigns that value in one batch instead of processing each service individually. This improves efficiency in stock-related product calculations without changing visible business behavior.
Original PR description
Services have their stock quantities computes to 0. As it's the same value for all of them, we can do it in one batch instead of iterating over products. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Editable list views now allow users to adjust column widths more directly, making dense data screens easier to read and work with. The change also removes older automatic sizing rules that could make list layouts inconsistent.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves stock picking and inventory workflows for companies operating in multiple entities. It helps barcode and quality control processes behave more consistently across company contexts, reducing operational confusion.
The Marketing Automation app interface has been refreshed to make campaigns, activities, recipients, and email templates easier to understand and manage. The update clarifies wording and actions, adds reporting access, and removes unnecessary configuration options to help users get started faster.
Original PR description
The main goal is to improve the interface of marketing automation app, clarify buttons/actions and ease the onboarding in general. Global purpose/change : - Campaign kanban/tree/form view revamp - Marketing activity form interface improvement - "participant" name of a marketing campaign was not well descriptive, then change by "recipient" in views (model name unchanged). - clean the recipient (participant) form view - Add some reporting and remove configuration menu. - Mailing template views clarify for this app (without change the base views) More details on the task. TASK_ID : 2053221
Resolved issues and error corrections
Bank statement reconciliation now uses the invoice payment reference when matching payments to invoices. This helps payments with structured references, such as Belgian BBA or Swiss ISR references, reconcile more accurately and reduces manual correction work.
Original PR description
Since invoice_payment_ref exists on account.move it should be the reference used for reconciliation. For instance for structured refs like l10n_be_invoice_bba or ISR in l10n_ch -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes incorrect website and system URLs when Odoo runs behind a proxy using newer Werkzeug versions. It ensures Odoo correctly recognizes the public web address and secure connection details, preventing broken or misleading links for users.
Original PR description
Werkzeug 0.15 refactored ProxyFix, and as a side-effect made it only enable X-Forwarded-For by default where 0.14 also enabled X-Forwarded-Host and X-Forwarded-Proto. This breaks e.g. the proper generation of `web.base_url` as it now uses the wrong scheme (e.g. will generate an `http` URL if the proxy does SSL termination, which is common). Explicitly enable XFH and XFP when using werkzeug ≥ 0.15. See #35085 for more details. See pallets/werkzeug#1630 for tracking issue of replicating 0.14's behaviour when using the deprecated `werkzeug.contrib.fixers.ProxyFix` in 0.15.
The payment wizard now shows the payment method and bank account fields again for Mexican electronic invoicing. This prevents errors when paying multiple invoices and ensures the required payment complement can be generated correctly.
Original PR description
On this PR https://github.com/odoo/enterprise/pull/3944 was removed the fields for payment method and bank account in the payment wizard, but these fields are required to generate the payment complement, then, was returned. When the fields were removed not was removed the assignation in the methods, then I get a traceback when trying to pay many invoices. 
Features or functions removed from Odoo
The separate Mexican EDI cancellation add-on was removed because its functionality is now included in the main Mexican EDI module. This simplifies maintenance and avoids duplicate features while keeping the cancellation capabilities available through the consolidated module.
Original PR description
Removed this extra module because the features were added on `l10n_mx_edi` [here]( https://github.com/odoo/enterprise/pull/4994)