Daily updates from Odoo
Friday, June 5, 2026
5 changes · master
Enhancements to existing features
This update allows users to automatically associate return reasons with barcode scans during picking. By adding a return reason ID to the OBTRETU barcode, the system now correctly creates returns and links them to the selected reason, streamlining the return process.
Original PR description
This commit adapts OBTRETU to also fetch and select the return reason with the barcode. Details: Here we have added the `return.reason` ID after the OBTRETU barcode. When this barcode is scanned, it will also scan the return reason and pass that ID in the context of `_returnProducts`. Then it will retrieve that context and set it on the generated return for this delivery. For example is user select `return.reason` with ID 4 new barcode will be OBTRETU:4, so when user scan this QR in picking it will create return and set `return.reason` with ID 4. task-4160966 Community PR: https://github.com/odoo/odoo/pull/234112
This update streamlines the invoicing process by automatically reconciling invoices created directly from sales orders. Previously, this required manual steps; now, a new system passes a context key, enabling automatic reconciliation within the accounting system. This improves efficiency and reduces the risk of errors when generating invoices from sales transactions.
Original PR description
This commit will allow to automatically reconcile the invoice create from the sale order by passing a context key that will be used in the create_invoices function. task-5502964 Forward-Port-Of: odoo/enterprise#117875 Forward-Port-Of: odoo/enterprise#108546
This update adds detailed labels to LLM requests, identifying the source (like agents or web search) and the specific model used. This enhanced tracking allows us to better understand how our AI tools are being utilized and optimize token usage for cost efficiency.
Original PR description
Tag each completion request with a human-readable label identifying what issued it (the agent, web search, AI field, AI server action, ...) so token usage can be attributed to a given source-model combination. Agent-driven requests are prefixed with "Agent:" to set them apart from feature calls. Example: ``` AI: [Agent: Ask AI] gemini-2.5-flash-lite request [0.68s] - Tokens: 115 in (0 cached)|5 out|0 reasoning AI: [Agent: Ask AI] gemini-3-flash-preview request [2.64s] - Tokens: 5295 in (4050 cached)|79 out|186 reasoning AI: [web search] gemini-3-flash-preview request [21.24s] - Tokens: 562 in (226 cached)|708 out|1343 reasoning AI: [Agent: Odoo Image Generation Agent] gemini-2.5-flash-image request [8.25s] - Tokens: 423 in (0 cached)|1324 out|0 reasoning ``` Forward-Port-Of: odoo/enterprise#118811
This update enhances the creation of TSS (Tax Service Statements) in the Odoo Enterprise system by requiring user confirmation before creation. Once created through Fiskaly, the associated IDs are made read-only, and a copy button is added for easy record retrieval. This improves data accuracy and simplifies tracking.
Original PR description
In this commit: -------------- - We have introduced a “Create TSS” button. The system now asks for user confirmation before creating the TSS and client. - Once the TSS and client are successfully created in Fiskaly, the fields displaying their IDs become read-only. Additionally, a Copy button has been added to allow users to easily copy these values for later investigation or reference. task- 5457231
This update streamlines the import of invoices by introducing a generic reload flow. The system now intelligently prioritizes structured XML attachments over OCR-processed versions, ensuring data accuracy and efficiency. This change improves the reliability of invoice data within the system.
Original PR description
The account module now provides a generic reload flow for imported invoices. Keep the OCR-specific reload data behavior for invoices which must be handled by OCR, while letting invoices with regular imported source attachments fall back to the generic account reload flow. task-6159853 ----------------------------------------------------------------------------------------------------------------- In case there is a structured attachment like xml whether it's the original imported attachment or an embedded one, disable the OCR logic as structured attachments are 100% accurate and don't require digitization tokens so we should always prefer them, for example if the uploaded file is an xml having a pdf as an embedded attachment or the uploaded is a pdf having an xml as an embedded attachment then in both cases we will prefer the xml. task-6158911