Users will only be able to view scrap orders that belong to their own company, reducing accidental visibility across companies. Scrap records now carry company information so related locations, movements, and numbering stay properly separated by company.

**Description of the issue/feature this PR addresses**: 
- Task: https://www.odoo.com/web#id=1930055&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
- Pad: https://pad.odoo.com/p/r.ecf7eea9d9ccdf0d1c3e288e9757ef9c

**Current behavior before PR:** 
-Users can see scrap orders of all companies.

**Desired behavior after PR is merged:**
-Users cannot see scrap orders of companies other than their own.




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

The stock module’s automated tests were updated so they can run successfully even when demo data is not installed. This improves reliability for deployments and development environments that use clean, production-like configurations without sample data.

Do not require the demo data to be able to run (and pass) the tests of stock.

task-2024202

This improvement adds a new way to show product variant attributes as descriptive information rather than variant choices. It makes product pages and comparison views easier for shoppers to read by displaying selected attribute values together in a simple comma-separated row.

Description of the issue/feature this PR addresses:
- Task link - https://www.odoo.com/web#id=1912579&action=327&model=project.task&view_type=form&menu_id=4720

- Pad - https://pad.odoo.com/p/r.5b65abecd81de14fed4e7251afcb6bae

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

This update simplifies the action dropdowns in many Odoo screens by shortening labels, removing duplicate or misplaced actions, and showing options only where they are relevant. Business users should see clearer, less cluttered menus and a more consistent experience across sales, accounting, CRM, HR, inventory, manufacturing, and related apps.

PURPOSE

The 'action' dropdown on the controlpanel is starting to get messy. Their
labels are sometimes too long/repetitive. Some actions only make sense in
formview, some in listview, some in both. Some actions should be stat buttons.

Here are some of the 'guidelines' I've followed to clean those actions:
If the action already has a dedicated button in the formview, do not display
it in the formview action dropdown. Action labels always start with a verb.
Former actions that redirected to records are changed to stat buttons

SPECIFICATION

The following drive file defines all the changes to be done on actions:
https://docs.google.com/spreadsheets/d/1G0AtYs6VIXFz1vG32IoL457c_oy-OCXF9Tv19vLQdz8/edit?usp=sharing

The actions are grouped by object, which are grouped by product owner. The
ones in green are to be kept. The 'where' column specifies whether they should
be shown in formview, listview, or both. The ones in red are to be removed or
moved somewhere else (stat button, menu item). When an action is removed, check
whether the action it is calling is used somewhere else. If it is not the
case, remove it as well (clean the code).

Linked to task ID 1984526

This update improves invoice and journal entry handling by preserving due dates more reliably when no payment terms are set. It also warns users before validating empty invoices or accounting entries, helping reduce accidental or incomplete postings.

* remove _onchange_invoice_date_due as it is superseeded by _onchange_recompute_dynamic_lines
* change invoice_date_due only if not set and if there is no payment term, it was erased and set to invoice_date_due if we did not set invoice_date_due before posting
* raise a warning if we validate an empty move/invoice




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

This update refines how content is shown while editing website pages, making it easier for users to see and manage page elements in the editor. It should improve the page-building experience without changing the published website behavior.

**TASK**: [34646](https://www.odoo.com/web#id=34646&view_type=form&model=project.task&action=333&active_id=974&menu_id=4720)

Users can now search archived products by barcode when a barcode conflict prevents creating or updating another product. This makes it easier to identify which inactive product already owns a barcode and resolve the issue without exporting or manual investigation.

**Allow searching by barcode for the archived product**

When you create a product with a barcode that has already been taken by
some other product(which is archived), you will get an error that says
that a barcode can only be assigned to one product.

Now, if you filter all the archived products and then search with the same
barcode, you will not find the other product that has the same barcode as
your new product.

Hence, the user is unable to search as to which other product(archived)
has the same barcode.

Steps to reproduce:
- Someone archives **Product A** with barcode: 12345
- You try to a new **Product B** using barcode 12345
- It raises an error that a product with that barcode already exists
- If you try to lookup **Product A** by barcode it won't appear on archived products
- If you try to export all the archived products, **Product A** won't export the barcode.
- So we can't create **Product B** using barcode 12345, but we cant neither find the product that has this barcode.

After this PR is merged, it will allow the user to search for products by barcode even if they are archived.

**_Note: The barcode field will still remain disappeared in the template on an archived product.
This PR is just for allowing to search on an archived product._**

Task Link: https://www.odoo.com/web?#id=1978559&action=327&model=project.task&view_type=form&menu_id=4720

Pad Link: https://pad.odoo.com/p/r.1118e013e6c395157a91b17029dcea74



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

IoT users can now manually enter a network range to scan instead of being limited to the browser's current network range. This makes it easier to discover and connect IoT devices located on a chosen subnet, improving setup flexibility for businesses with more complex networks.

Before this commit it was impossible to scan a specific range.
Only the same range that the browser.
Now we can add manually a range to scan.

Task: 1892415

This update removes outdated internal coding patterns from several Odoo Enterprise apps and reports. It helps keep the platform easier to maintain and ready for future upgrades, with no expected change to day-to-day user workflows.

This update simplifies the action dropdowns across several Odoo apps by shortening labels, hiding actions where they are not relevant, and moving some record-opening actions to clearer stat buttons. Users should see less clutter and more consistent wording when working in accounting, HR, sales, helpdesk, manufacturing, and related screens.

PURPOSE

The 'action' dropdown on the controlpanel is starting to get messy. Their
labels are sometimes too long/repetitive. Some actions only make sense in
formview, some in listview, some in both. Some actions should be stat buttons.

Here are some of the 'guidelines' I've followed to clean those actions:
If the action already has a dedicated button in the formview, do not display
it in the formview action dropdown. Action labels always start with a verb.
Former actions that redirected to records are changed to stat buttons

SPECIFICATION

The following drive file defines all the changes to be done on actions:
https://docs.google.com/spreadsheets/d/1G0AtYs6VIXFz1vG32IoL457c_oy-OCXF9Tv19vLQdz8/edit?usp=sharing

The actions are grouped by object, which are grouped by product owner. The
ones in green are to be kept. The 'where' column specifies whether they should
be shown in formview, listview, or both. The ones in red are to be removed or
moved somewhere else (stat button, menu item). When an action is removed, check
whether the action it is calling is used somewhere else. If it is not the
case, remove it as well (clean the code).

Linked to task ID 1984526

This update fixes how connected hardware devices are identified so duplicate device entries are avoided. It helps ensure IoT-connected USB devices are listed more reliably, reducing confusion when multiple devices are connected.

Before this commit the identifier integrate the BUS and port to identify USB devices
Now we check if there are duplicates devices before increment the identifier

For other loop we add identifier in the iot_device object

task: 1963500




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

This update fixes and refines several website, portal, event, forum, sales, purchase, accounting, recruitment, and mailing pages. Business users and customers should see cleaner layouts, improved navigation in account areas, and small usability improvements across public-facing pages.

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 change restores the expected behavior where email-sending flows must provide a valid sender address instead of silently allowing missing user emails. It also keeps internal log-only messages from requiring a sender when no email notification is sent, helping expose configuration issues while preserving non-email logging flows.

This reverts commit 6230f72d2be58069dfd264623944a45c84c99ba4.

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 fix prevents IoT device identifiers from being recalculated when devices start up. Using the identifier already provided helps keep connected devices recognized consistently and reduces the risk of duplicate or mismatched device records.

Previously we recalculate the identifier in the init of device
Now we receive it so we don't need to recalculate

task: 1963500

The Belgian payroll demo setup now looks for accounts only within the company being configured. This prevents irrelevant cross-company account matches and makes the setup process more efficient by reducing unnecessary requests.

Restrict account search in l10n be hr payroll demo data to the considered company as an account
outside the company would not make any sense. Also reduces the amount of requests.

A bug was corrected in accounting reports that could affect closing a journal entry. This helps ensure users can complete accounting workflows without unexpected interruptions.

task - https://www.odoo.com/web?#id=2032101&action=327&model=project.task&view_type=form&menu_id=4720
pad - https://pad.odoo.com/p/r.1da9f63bb69339f195bc773e63282435

This update removes outdated internal API patterns and cleans up technical debt across several Odoo applications. It helps keep the platform easier to maintain and reduces the risk of future compatibility issues, with little expected impact on day-to-day users.

https://github.com/odoo/enterprise/pull/4722

This pull request adds a contributor license agreement signature record for ghuenlee. It confirms the contributor has completed the required legal step before contributions can be accepted into Odoo.

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