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 Forward-Port-Of: odoo/odoo#156944

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

Forward-Port-Of: odoo/odoo#156944

Issue ---- Demo company data contains a phone number of a real person, who receives phone calls from peolple asking to buy stuff :) Steps ---- Number is available on website footer. Cause ---- A real number is used in demo data. opw-3853066 Forward-Port-Of: odoo/odoo#164545

Issue
----

Demo company data contains a phone number of a real person, who receives phone calls from
peolple asking to buy stuff :)

Steps
----

Number is available on website footer.

Cause
----

A real number is used in demo data.

opw-3853066

Forward-Port-Of: odoo/odoo#164545

The Early Payment Discount (EPD) functionality is designed to work only with payment terms that include a single 100% line. A validation error is correctly displayed if a user attempts to create an EPD with multiple term lines. However, a bug existed where users could create a regular payment term with multiple lines, save it, and then enable the EPD, bypassing the validation. This allowed the record to be saved without error, leading to a traceback when the system later attempted to process

The Early Payment Discount (EPD) functionality is designed to work only with payment terms that include a single 100% line. A validation error is correctly displayed if a user attempts to create an EPD with multiple term lines.

However, a bug existed where users could create a regular payment term with multiple lines, save it, and then enable the EPD, bypassing the validation. This allowed the record to be saved without error, leading to a traceback when the system later attempted to process the EPD, as it does not support multiple term lines.

opw-3945596

Forward-Port-Of: odoo/odoo#167732

Currently, if you have `pos_restaurant` but not `pos_self_order`, if you add a note on one line of the restaurant order, it visually disappears if you change table and then come back to it. Steps to reproduce: ------------------- * Install `pos_restanrant` * Uninstall `pos_self_order` * Open the restaurant session * Select a table and add an item to the order * Write an internal note > You can see the note on the line * Select **Change table** * Come back to the previous table > T

Currently, if you have `pos_restaurant` but not `pos_self_order`, if you add a note on one line of the restaurant order, it visually disappears if you change table and then come back to it.

Steps to reproduce:
-------------------
* Install `pos_restanrant`
* Uninstall `pos_self_order`
* Open the restaurant session
* Select a table and add an item to the order
* Write an internal note
  > You can see the note on the line
* Select **Change table**
* Come back to the previous table
> The note is not visible anymore

Why the fix:
------------
The note added is correctly registered but just invisible to the waiter. It is also visible in the display if you send the order in.

The note field is added by the module `pos_restaurant` but loaded to the ui in `pos_self_order`. Technically the module `pos_self_order` gets auto-installed when `pos_restaurant` is installed but some customer might not have `pos_self_order` if they uninstalled it for example.

`pos_self_order` depends on `pos_restaurant` so we can safely move the code that exports it inside the root module (`pos_restaurant`).

The fix starts in 17.0 as in previous versions it was working fine with only `pos_restaurant` installed.

opw-3917013

Forward-Port-Of: odoo/odoo#167223

Problem: When a user saves a quotation in the POS session, the quotation gets confirmed into a SO and its invoice_status is "invoiced" but no invoice was created. This occurs because the POS has another POS as its trusted POS. The user is expected the quotation to stay as a quotation when they save it in the POS. Steps to reproduce: - Install "Point of Sale" and "Sales" apps - Create another POS that is not a bar/restaurant - On the settings of the "Shop" POS, set the newly created POS as

Problem:
When a user saves a quotation in the POS session, the quotation gets confirmed into a SO and its invoice_status is "invoiced" but no invoice was created. This occurs because the POS has another POS as its trusted POS. The user is expected the quotation to stay as a quotation when they save it in the POS.

Steps to reproduce:
- Install "Point of Sale" and "Sales" apps
- Create another POS that is not a bar/restaurant
- On the settings of the "Shop" POS, set the newly created POS as its trusted POS
- Create a sales quotation and save
- Open a session in "Shop" POS and click "quotation/order" to import the sales quotation and click on "Settle the order"
- Click on save
- The quotation is now confirmed into a SO when it should not be

Cause:
All quotations with state "draft" or "sent" are confirmed while they shouldn't if the sale is not completed

Solution:
As the variable "draft" from "create_from_ui" is True when saving a quotation and is False when confirming an order, we can use it to proceed or not the confirmation of the quotation

opw-3885845


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

Forward-Port-Of: odoo/odoo#167476
Forward-Port-Of: odoo/odoo#166485

Steps to reproduce: 1) Create product P for $1000, with 15% Tax, publish to website. 1-bis) make sure the 15% tax is "included" 2) Settings -> search 'price' -> Tax Excluded. 3) Go to website /shop page, and edit to place the Products block, and search for Issue: The price displayed on the product in "86.96" (correct) but the price on the product in the carousel displays "100.00" Cause: The price for the carousel is not fetched the same way https://github.com/odoo/odoo/blob/e829b345f0

Steps to reproduce:
1) Create product P for $1000, with 15% Tax, publish to website. 1-bis) make sure the 15% tax is "included"
2) Settings -> search 'price' -> Tax Excluded.
3) Go to website /shop page, and edit to place the Products block, and search for

Issue:
The price displayed on the product in "86.96" (correct) but the price on the product in the carousel displays "100.00"

Cause:
The price for the carousel is not fetched the same way https://github.com/odoo/odoo/blob/e829b345f0f5e5346be416b8354c29fa9acb74a7/addons/website_sale/data/product_snippet_template_data.xml#L388

And the method does not take into account this fourth scenario. That is:
- a tax with price_include set to True
- a show_line_subtotals_tax_selection config parameter set to "tax_excluded"

opw-3370999

Forward-Port-Of: odoo/odoo#139976
Forward-Port-Of: odoo/odoo#133501

In the balance sheet and Profit & Loss reports, we allow users to audit the General Ledger of a specific account if we want to look at the details of that account for the period of the report. When clicking on the link of the audit, it works well for small db, but if the account is low in the list, you don't even see it. This commit adds a default filter on the report. task-3839845 Forward-Port-Of: odoo/enterprise#60827

In the balance sheet and Profit & Loss reports, we allow users to audit the General Ledger of a specific account if we want to look at the details of that account for the period of the report. When clicking on the link of the audit, it works well for small db, but if the account is low in the list, you don't even see it. This commit adds a default filter on the report.

task-3839845

Forward-Port-Of: odoo/enterprise#60827