This change adds subcontracting workflows so companies can send components to suppliers and receive finished products while keeping ownership and valuation of materials. It also connects purchase prices to subcontracting costs and improves related manufacturing, stock, and accounting behavior.

task 1831382

Adds Italian e-invoicing support so businesses can generate compliant XML invoices, send them through certified email, and process incoming invoice-related messages. This helps Italian companies reduce manual invoice handling and better comply with local electronic invoicing requirements.

Generate E-invoice in xml, send E-invoice by PEC, manage mail (create new income invoice, manage response)


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

IoT boxes will now regularly send device status information to the server every five minutes, helping businesses monitor connected hardware more reliably. Printer detection and installation are also improved, reducing setup delays and making point-of-sale hardware easier to manage.

With this commit dict of devices will be send every 300 seconds to server

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

The mail composer was streamlined by removing unnecessary message-related behavior and keeping only the fields it actually uses. This reduces complexity and avoids unsupported forum channel notifications that did not work, making email and message composition more reliable.

Purpose
 * unnecessary inherit of composer on mail.message: lot of unused fields and
   message specific behavior (notify, check access) not relevant for
   composer;
 * simply duplicate fields to use and remove inheritance;

This update refreshes internal counter values used by developers when checking mail-related test performance. It helps ensure community and enterprise test counters stay accurate, reducing confusion during development checks.

Some counters are not up to date notably taking in to account community-only
and test-mail with enterprise only counters. Those are used notably when
developing to ease quick check of counters.

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

Payments are now categorized as customer or supplier payments based on the partner type, not whether money is being received or sent. Point of Sale payments are consistently treated as customer payments, reducing confusion in payment menus and reimbursement workflows.

Task 1934667

1. That's the partner type (and not the payment type) that should define if a payment is a customer or a supplier payment :
a. When the partner type on the payment is "customer", the payment should be considered as a customer payment
(and thus be visible from the menu customer payments)
b. When the partner type on the payment is "supplier", the payment should be considered as a supplier payment
(and thus be visible from the menu supplier payments)

2. The PoS should only create customer payments (you never pay suppliers through the PoS)
The payment created should be with a partner type "Customer"
But the partner field can stay empty if the customer wasn't set on the PoS Order

3. When I change the payment type while creating a payment from scratch, it shouldn't change the partner type
Example : I'm creating a payment for a reimbursement, I'll create it from the customer payments menu (as I'm paying a customer), I'll tick the payment type "Send money"
I don't expect the partner type to change to vendor.


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

New stock operation types now enable detailed operations automatically when the company setup makes them useful, such as multi-location inventory or lot and serial number tracking. The separate “Show Reserved” option has also been removed to simplify operation type settings and reduce configuration choices.

In case it's appropriate (using multilocation or lots/serial numbers) the 'show detailed operations' option is active by default when a new operations type is created.

Task #1944853

Creating records from a calendar popup now opens the specific form configured for that calendar instead of always using the default form. This helps users see the right fields and layout for the task they are creating, reducing confusion and data entry mistakes.

When creating a record from a calendar view,
the default form view is always used when using the popup mode,
ignoring the `form_view_id` attribute of the `<calendar/>` tag.

After this commit, the `form_view_id` is no longer ignored.


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

This update combines translation refreshes with several small fixes across accounting, sales, purchasing, inventory, website reporting, and localization features. It improves invoice reporting accuracy, purchasing labels, dropship returns, analytics display, and localized invoice details, reducing user confusion and operational errors.

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 fixes several website-facing issues, including errors when users download event calendar files and navigation problems on scrolled pages. It also improves forum author cards and layout spacing so names, points, logos, and page elements display more cleanly.

Description of the issue/feature this PR addresses:

- After creating an event and user register on it and click on add to ical/outlook button is rendering a internal server error.
- Name of the user and karma points are not shown properly in boxed body.
- px in logo and main layout is taking unwanted space
- Related task: https://www.odoo.com/web#id=1938637&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
- Pad: https://pad.odoo.com/p/r.800ba7770c62ede5fd8eb79362d031fa

Current behavior before PR:
- Above mention points are showing internal server error/ data is not shown properly

Desired behavior after PR is merged:
- Issues are fixed after PR will be merged.


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

Project color changes made through Studio now appear correctly in the Gantt view. This keeps planning views visually consistent with the project settings users choose.

Task:https://www.odoo.com/web#id=1958703&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
Pad:https://pad.odoo.com/p/r.e9bc77fa14e14718cc3caf4c37b57b12

Manufacturing accounting files were reorganized so the enterprise module now focuses on the bill of materials cost report, while shared functionality moves to the community module. A related manufacturing lifecycle view issue was also fixed, improving reliability without changing day-to-day workflows significantly.

task 1831382