Odoo Changelog — 2025-10-24

Friday, October 24, 2025

8 changes · saas-18.2

Bug Fixes(8)

Resolved issues and error corrections

[FIX] industry_fsm: fix To Schedule filter record visibility

Enterprisesaas-18.2industry_fsm

The Field Service 'To Schedule' filter now excludes completed or cancelled tasks. This keeps the list focused on work that still needs scheduling or assignment, reducing confusion for dispatchers and planners.

Original PR description

**steps to reproduce:**
Go to field service
Go to all tasks > to schedule

**issue:**
The To Schedule filter was also displaying tasks in cancelled or done state, whereas it should only show open tasks that need to be scheduled or assigned.

**cause:**
The filter domain did not exclude cancelled/done state, causing closed tasks to appear in the filtered view.

**fix:**
Updated the filter domain to exclude cancelled/done state, to ensure only open tasks are shown under the To Schedule filter.

task-5138590

Forward-Port-Of: odoo/enterprise#96600

#field-service#scheduling#tasks

[FIX] pos_self_order_preparation_display: make cancel button conditional

PR #95770

Enterprisesaas-18.2pos_self_order_preparation_displayMEDIUM

Customers can no longer cancel self-order restaurant orders from their order page once the order has been sent to the kitchen display. This prevents mismatches where the backend order is cancelled but kitchen staff are not informed, reducing operational confusion.

Original PR description

Currently, it is possible to cancel orders that have been sent to the kitchen display. However when doing so, the kitchen displayd does not receive any information about the cancellation.

Steps to reproduce:
-------------------
- Modify restaurant and enable self ordering
- Open self an place an order (not paid but sent to kitchen)
- Go back to "My orders" and cancel it
> Order is cancelled in backend but not in the kitchen display

Why the fix:
------------
When an order is sent to the kitchen the only way to cancel it should be by going to the register. Therefore now, if an order is present on the kitchen display we will not show the cancel button.

opw-5030223

Community: https://github.com/odoo/odoo/pull/229039

#self-ordering#restaurant#kitchen display#order cancellation

[FIX] mrp_workorder: backorder displayed quantity

PR #97983

Enterprisesaas-18.2mrp_workorderMEDIUM

The shop floor now shows the quantity needed for the specific manufacturing step when adjusting a backorder, instead of showing the remaining total for the full order. This helps operators register production accurately and avoid confusion when different work steps have different remaining quantities.

Original PR description

**PROBLEM** When creating a backorder, the quantity to produce during an operation is correctly displayed on the shop floor step. But when clicking to modify it, the pop over display the total…

**PROBLEM**
When creating a backorder, the quantity to produce during an operation is correctly displayed on the shop floor step. But when clicking to modify it, the pop over display the total quantity to produce, and not the quantity to produce in that specific operation.

**STEP TO REPRODUCE**
1. create a BoM of product with 3 or more operations
2. Create a Manufacturing order for i.e. 10 unit
3. Open shop floor
4. Register the production in shopfloor:
- Op1 – 10 units registered
- Op2 – 7 units registered
- Op3 – 5 units registered

5. At the end, a backorder is created for 5 units.
6. When we open the wizard to register the production on the Op2, the quantity to produce that is displayed is 5, which is wrong because we only need to produce 3 unit for that step.

**CAUSE**
When creating the confirmation dialog, we pass the wrong value `qty_remaining` which is the quantity of product we will end after finishing the Manufacturing Order.

**FIX**
We should pass `qty_production` instead which is the quantity to produce for the specific step.

opw-5011739

Forward-Port-Of: odoo/enterprise#97906
Forward-Port-Of: odoo/enterprise#93599

#manufacturing#shop floor#backorder#work orders

[FIX] pos_iot_six: undefined user_id opening session w/ different user

PR #98021

Enterprisesaas-18.2pos_iot_sixMEDIUM

Payments through Six terminals now use the active POS user's identity instead of relying on a session value that could become unavailable. This prevents payment startup issues when a different user opens or continues a POS session in another browser tab.

Original PR description

This commit fixes an undefined `user_id` on the pos session when trying to start a payment with a Six terminal from another user than the one that started the session.

Before this commit:

- open a pos session with Mitchell Admin,
- check the value of `pos.session.user_id` (it will be `2`),
- open another tab and connect as Marc Demo,
- check the value of `pos.session.user_id` again: it should be `6`, but instead is `undefined`.

After this commit:

We use `pos.user.id` instead of `pos.session.user_id.id` to get the user ID.

opw-5055977

Forward-Port-Of: odoo/enterprise#97975

#point-of-sale#payments#six-terminal

[FIX] quality_mrp: 'quality.point' object has no attribute 'operation_id'

PR #97801

Enterprisesaas-18.2quality_mrp

This fix prevents an error when quality checks are used in manufacturing without the work order feature installed. It keeps quality point validation from referencing unavailable work order information, improving reliability for affected manufacturing setups.

Original PR description

**Issue:**
The attribute operation_id for quality.point is defined in the mrp_workorder module.
However, quality_mrp module does not list mrp_workorder in its dependencies. As a result in a system where quality_mrp is installed but mrp_workorder is not, the following error is raised when evaluating the constrain for quality points mesured on Operations.
`"'quality.point' object has no attribute 'operation_id'"`


**Proposed solution:**
Override the constraint in quality_mrp_workorder to include conditions related to operation_id, ensuring that it is only evaluated when the field is available.

Forward-Port-Of: odoo/enterprise#97338

#manufacturing#quality#stability

[FIX] iot: fix ingenico payments

PR #98059

Enterprisesaas-18.2iotMEDIUM

This update prevents unnecessary payment status checks from Ingenico terminals unless the status changes or a payment is actively being processed. This avoids checkout errors during card payments and removes a related deprecated system call warning.

Original PR description

Currently when paying with ingenco there is an error:

"Uncaught (in promise) TypeError: can't access property "payment_method", line is undefined."

This is due to the fact that Ingenco sends requests to the database every second even when the status of the driver didn't change since the last payment.
This PR fixes the issue by only sending requests to the database if a) THe driver status has changed
b) A payment is being processed

It also fixes the deprecation warning for isSet() replaced by is_set().

opw-5166439
opw-5181429
opw-5164612
opw-5170658

Forward-Port-Of: odoo/enterprise#98007
Forward-Port-Of: odoo/enterprise#97945

#ingenico#payments#pos#iot

[FIX] stock_barcode: prevent floating-point display issue in fulfill button

PR #98096

Enterprisesaas-18.2stock_barcode

Fixes a display issue in the Barcode app where decimal quantities could show too many digits after repeated scans. This keeps receipt quantities easier to read and helps warehouse users avoid confusion when processing inventory.

Original PR description

**Issue** In the Barcode application, floating-point values may display excessive decimals. **Steps to reproduce** - Open the Inventory app. - Create a receipt with a decimal quantity (e.g. 10.54)…

**Issue**
In the Barcode application, floating-point values may display excessive decimals.

**Steps to reproduce**
- Open the Inventory app.
- Create a receipt with a decimal quantity (e.g. 10.54) and mark it as To Do.
- Open the Barcode app, open the corresponding receipt, and click the Edit button.
- Increment the number of scans several times until you notice too many decimal digits (if you choose 10.54, you can test with 3).

**Cause**
A floating-point precision error occurs in the getter [`quantityToFulfill`](https://github.com/odoo/enterprise/blob/4b08734124c3bc84f7d95d170b39e9909e20d66b/stock_barcode/static/src/widgets/digipad.js#L55C9-L55C50), which is rendered directly [in XML templates](https://github.com/odoo/enterprise/blob/e8063141b33a9a8aa51d1ce94a66af313b2c1c89/stock_barcode/static/src/widgets/digipad.xml#L20C25-L21C89) without rounding.

**Solution**
Round the displayed value in the `quantityToFulfill` getter in the same manner than in [barcode_model](https://github.com/odoo/enterprise/blob/d4e5b69c7ea87fba3f2a5204ed6939b97879e4a8/stock_barcode/static/src/models/barcode_model.js#L99-L103).

opw-5039796

Forward-Port-Of: odoo/enterprise#97475

#barcode#inventory#quantity#rounding

[FIX] documents_spreadsheet: create spread sheet from multi user contact

PR #98058

Enterprisesaas-18.2documents_spreadsheetMEDIUM

Users whose contact record is linked to multiple accounts can now create spreadsheets from the Documents app without hitting an error. This prevents a blocking crash in a specific contact setup, improving reliability for affected teams.

Original PR description

Before this commit:
1. connect with a user, the partner_id of which is linked to multiple users
   via the user_ids field  (this can be done by manually setting it, or
   by merging contacts, for example)
2. go to the Documents app, click new, then spreadsheet
--> expected singleton Traceback

opw-5133850

Forward-Port-Of: odoo/enterprise#97767

#documents#spreadsheet#contacts

**steps to reproduce:** Go to field service Go to all tasks > to schedule **issue:** The To Schedule filter was also displaying tasks in cancelled or done state, whereas it should only show open tasks that need to be scheduled or assigned. **cause:** The filter domain did not exclude cancelled/done state, causing closed tasks to appear in the filtered view. **fix:** Updated the filter domain to exclude cancelled/done state, to ensure only open tasks are shown under the To Schedule filter. task-5138590 Forward-Port-Of: odoo/enterprise#96600

Currently, it is possible to cancel orders that have been sent to the kitchen display. However when doing so, the kitchen displayd does not receive any information about the cancellation. Steps to reproduce: ------------------- - Modify restaurant and enable self ordering - Open self an place an order (not paid but sent to kitchen) - Go back to "My orders" and cancel it > Order is cancelled in backend but not in the kitchen display Why the fix: ------------ When an order is sent to the kitchen the only way to cancel it should be by going to the register. Therefore now, if an order is present on the kitchen display we will not show the cancel button. opw-5030223 Community: https://github.com/odoo/odoo/pull/229039

**PROBLEM** When creating a backorder, the quantity to produce during an operation is correctly displayed on the shop floor step. But when clicking to modify it, the pop over display the total quantity to produce, and not the quantity to produce in that specific operation. **STEP TO REPRODUCE** 1. create a BoM of product with 3 or more operations 2. Create a Manufacturing order for i.e. 10 unit 3. Open shop floor 4. Register the production in shopfloor: - Op1 – 10 units registered - Op2 – 7 units registered - Op3 – 5 units registered 5. At the end, a backorder is created for 5 units. 6. When we open the wizard to register the production on the Op2, the quantity to produce that is displayed is 5, which is wrong because we only need to produce 3 unit for that step. **CAUSE** When creating the confirmation dialog, we pass the wrong value `qty_remaining` which is the quantity of product we will end after finishing the Manufacturing Order. **FIX** We should pass `qty_production` instead which is the quantity to produce for the specific step. opw-5011739 Forward-Port-Of: odoo/enterprise#97906 Forward-Port-Of: odoo/enterprise#93599

This commit fixes an undefined `user_id` on the pos session when trying to start a payment with a Six terminal from another user than the one that started the session. Before this commit: - open a pos session with Mitchell Admin, - check the value of `pos.session.user_id` (it will be `2`), - open another tab and connect as Marc Demo, - check the value of `pos.session.user_id` again: it should be `6`, but instead is `undefined`. After this commit: We use `pos.user.id` instead of `pos.session.user_id.id` to get the user ID. opw-5055977 Forward-Port-Of: odoo/enterprise#97975

**Issue:** The attribute operation_id for quality.point is defined in the mrp_workorder module. However, quality_mrp module does not list mrp_workorder in its dependencies. As a result in a system where quality_mrp is installed but mrp_workorder is not, the following error is raised when evaluating the constrain for quality points mesured on Operations. `"'quality.point' object has no attribute 'operation_id'"` **Proposed solution:** Override the constraint in quality_mrp_workorder to include conditions related to operation_id, ensuring that it is only evaluated when the field is available. Forward-Port-Of: odoo/enterprise#97338

Currently when paying with ingenco there is an error: "Uncaught (in promise) TypeError: can't access property "payment_method", line is undefined." This is due to the fact that Ingenco sends requests to the database every second even when the status of the driver didn't change since the last payment. This PR fixes the issue by only sending requests to the database if a) THe driver status has changed b) A payment is being processed It also fixes the deprecation warning for isSet() replaced by is_set(). opw-5166439 opw-5181429 opw-5164612 opw-5170658 Forward-Port-Of: odoo/enterprise#98007 Forward-Port-Of: odoo/enterprise#97945

**Issue** In the Barcode application, floating-point values may display excessive decimals. **Steps to reproduce** - Open the Inventory app. - Create a receipt with a decimal quantity (e.g. 10.54) and mark it as To Do. - Open the Barcode app, open the corresponding receipt, and click the Edit button. - Increment the number of scans several times until you notice too many decimal digits (if you choose 10.54, you can test with 3). **Cause** A floating-point precision error occurs in the getter [`quantityToFulfill`](https://github.com/odoo/enterprise/blob/4b08734124c3bc84f7d95d170b39e9909e20d66b/stock_barcode/static/src/widgets/digipad.js#L55C9-L55C50), which is rendered directly [in XML templates](https://github.com/odoo/enterprise/blob/e8063141b33a9a8aa51d1ce94a66af313b2c1c89/stock_barcode/static/src/widgets/digipad.xml#L20C25-L21C89) without rounding. **Solution** Round the displayed value in the `quantityToFulfill` getter in the same manner than in [barcode_model](https://github.com/odoo/enterprise/blob/d4e5b69c7ea87fba3f2a5204ed6939b97879e4a8/stock_barcode/static/src/models/barcode_model.js#L99-L103). opw-5039796 Forward-Port-Of: odoo/enterprise#97475

Before this commit: 1. connect with a user, the partner_id of which is linked to multiple users via the user_ids field (this can be done by manually setting it, or by merging contacts, for example) 2. go to the Documents app, click new, then spreadsheet --> expected singleton Traceback opw-5133850 Forward-Port-Of: odoo/enterprise#97767