Odoo can now be launched as a Jupyter notebook kernel, making it easier to run scripts and explore data in an interactive notebook environment. This helps technical teams work with Odoo data and automation workflows using familiar notebook tools.

It would be nice if scripting can be done in jupyter notebook.
However, with the constraints of both odoo and jupyter notebook,
it is not yet possible to open an odoo shell with jupyter
notebook interface. This commit bridges this gap. This is a
workaround so that jupyter notebook can be used to run an
odoo shell instance which will work as jupyter notebook's
kernel.

This commit introduces a way so that it can run a kernel
for jupyter notebook. This is the purpose of introducing the
-f option and jupyter_kernel function.

**Basic usage**

1. Create and install a kernelspec containing the odoo-bin
shell command.

kernelspec contains:
{
  "argv": [
    "/home/odoo/miniconda3/envs/saas-12.4/bin/python",
    "/home/odoo/Projects/odoo-dev/worktrees/saas-12.4/odoo/odoo-bin",
    "shell",
    "--addons-path=/home/odoo/Projects/odoo-dev/worktrees/saas-12.4/enterprise,/home/odoo/Projects/odoo-dev/worktrees/saas-12.4/odoo/addons,/home/odoo/Projects/odoo-dev/worktrees/saas-12.4/odoo/odoo/addons",
    "-d",
    "testdb-saas-12.4",
    "-f",
    "{connection_file}"
  ],
  "display_name": "Odoo - saas-12.4 - testdb-saas-12.4",
  "language": "Python"
}

install by: jupyter kernelspec install /path/to/kernelspec --user

2. Access the kernelspec command thru jupyter notebook.

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

This change allows landed costs to be used with products valued using the average cost method, giving businesses more accurate inventory valuation when extra costs such as shipping or duties are added. It improves costing flexibility in inventory operations and includes test coverage for the updated valuation behavior.

mostly thanks to rev 168f4d75ef724ee99ffaf7884730facd8ed936bb

task-1985422

This update improves the user experience around timesheets, making the module easier to understand and use during onboarding. It also refreshes related views and reporting so employees and managers can work with timesheet information more smoothly across projects and sales-linked workflows.

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

Purchase orders can now include section headers and note lines, making quotes and orders easier to read and structure. These display-only lines appear on purchase documents and portal/report views, while invoice content remains unchanged.

For the future matrix, to be able to share logic between sale and purchase, the section and note widget is added to purchase as well.

#### Section and Notes available on Purchase Order Lines 

Those display lines are applied to reports but **NOT** to invoices (account.move).

The Lunch app ordering screens have been cleaned up and reorganized to make daily meal ordering easier for employees. Alerts can now be delivered through chat messages, helping employees notice important lunch updates more quickly, and “toppings” are renamed to the clearer term “extras.”

Purpose
=======

Cleaning of the screen and new display of alert messages

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

This update improves the timesheet experience to make onboarding and day-to-day time entry smoother for users. The changes refine the timesheet grid and related views so employees can work more efficiently with less friction.

Payroll now supports employee contracts based on an hourly wage as well as a fixed monthly salary. This helps companies, especially in markets like Belgium, manage worker pay structures more accurately and transparently.

We have to support hour rate on wage as in Belgium, the wage of a
worker is hourly and not monthly.

On structure type: selection to select if the salary is a Montly
Fixed Wage or a "Hourly Wage"
On hr.contract, add a related selection near the wage to know if
it is a fixed monthly salary or hour

id=1999596

Anonymous website visitors can now start livechat conversations even when they do not have an email address. The fix ensures the conversation has a valid sender address fallback, preventing livechat from failing for public users.

The public user doesn't have an email address.
To start a livechat conversation, the email of the user that start the
conversation is used. As the conversation was started in sudo,
the system user's email address was used.

But, since changes with sudo() and with_users(),
the public user is not able to start a livechat conversation
as the system email is not used anymore in this case as sudo is not
changing the user but only skip the user's access right.

To start a livechat conversation, the user must be the system.

Pre-required for task ID: 2028059
Fix Task : 2037048

This update resolves several customer-facing issues, including incorrect company details in portal and checkout forms, wrong credit note due dates, and misleading payment confirmation messages. It also improves email links for multi-website setups and updates reporting precision for Belgian Intrastat compliance.

This fixes missing sharing controls on website slide pages, restoring the options to send a slide by email and embed it on another website. It helps users share course or presentation content as intended without needing technical workarounds.

…by email and Slide sub-template: share: embed in your website

Current behavior before PR: https://drive.google.com/file/d/1B9S704WzltwTLc1qQSdWDMp4fb8rfhEM/view

Desired behavior after PR is merged: http://www.awesomescreenshot.com/image/3578805/9294e09681484d57cbfcbee076894f5c




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

This update brings forward a set of fixes from earlier versions, improving reliability in manufacturing work orders, accounting follow-ups, documents, shipping, and Mexican localization. Business users should see fewer interface issues, better translated customer messages, and more accurate shipment and invoice data handling.