Odoo Changelog — 2026-09-11

Friday, September 11, 2026

135 changes · master

Security(1)

Security fixes and vulnerability patches

[REV] sale: do not confirm quotes after any successful payment

CoremastersaleSecurity

Sales quotes will no longer be confirmed just because any payment succeeds. This prevents very small or incorrect payments from triggering an order confirmation, while still allowing flexible payment links and clearer payment amounts in the customer portal.

Original PR description

Partial revert of da720a8563570a6c0860699d0a542dfa2ee3c392. The automatic confirmation on first payment is error-prone since forged requests could lead to a confirmed SO with a 0.1cents payment regardless of whether a payment link was issued with the given amount.

Keep requiring the prepayment amount for SO confirmation, while keeping the payment links open for any amount.

Adapt the portal SO views so that the payment amounts are correctly displayed in most situations.




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

#sales#payments#quotes#portal

New Features(11)

New functionality added to Odoo

[MERGE] planning_field_service: add map timeline

PR #125775

Enterprisemasterplanning_field_serviceweb_mapHigh impact

Field Service managers can now plan daily work using a combined map and timeline view, making it easier to balance routes, locations, and schedules at the same time. The two panes stay synchronized for folding, hovering, routes, stop numbers, and resource colors, reducing confusion during dispatch planning.

Original PR description

Introduces a new "Map Timeline" view for Field Service (Maps > Timeline),
combining a map and a Gantt timeline side by side so managers can plan 
daily interventions from both a spatial and a temporal angle at once,
grouped by resource, with inherited features (create, edit, 
drag-and-drop, buffer times, routing, etc.) preserved in both panes.

On top of the base view, the map and timeline are also kept coherent
with each other:
- folding a resource group in one pane folds it in the other, including
  the "Open Shifts" and "Shifts to assign" groups
- hovering a pin, a pin group, or a shift highlights its counterpart(s)
  across the map and the Gantt, as well as their side panels
- hovering a pin group also highlights its route on the map, with stop
  numbers shown along it
- resource colors (including materials) stay consistent across the
  Gantt, the map pins, and the map side panel

task-6273718

Co-authored-by: Maxime de Neuville (mane) <mane@odoo.com>

Improvements(68)

Enhancements to existing features

[IMP] hr_attendance: lighten the attendance review in the systray

PR #287401

Coremasterhr_attendanceMedium

The attendance menu now shows a more compact review, with details expanded only when needed, making it easier for employees and managers to use. The kiosk also keeps users on the break entry screen when a break is too long, so mistakes can be corrected immediately without starting over, and break totals now match the attendance records shown.

Original PR description

This PR brings a few improvements to the attendance review of the systray so
that it takes less room and only details an attendance on demand.

It also fixes the break duration of the kiosk:

1. Enable "Break Management on Checkout" in Settings > Attendances and open
   the attendance kiosk
2. Identify as an employee to check in, then identify again to check out
3. On the goodbye screen, click "Add my break times" and enter a duration
   longer than the attendance that was just closed
4. Confirm -> the error is shown but the kiosk has already gone back to its
   main screen, so the break has to be entered again from scratch

With this PR, the duration is checked against the attendance before being
sent and the dialog stays open until it fits.

Task-6542050

Bug Fixes(39)

Resolved issues and error corrections

[FIX] html_builder: prevent theme edit button focus shift

PR #287773

Coremasterhtml_builder

The website theme color editor now keeps edit buttons visually stable when users navigate with the keyboard. This prevents a small but distracting layout jump, improving usability and polish in the website editor.

Original PR description

Steps to reproduce:
- Open the website editor.
- Open the theme color picker.
- Focus an edit color preset button with the keyboard. => The button shifts when it receives focus.

Before this commit, a transparent border reserved space outside focus. Since [1], the focus indicator uses a `box-shadow`, so that border disappeared on focus and changed the button size.

After this commit, the obsolete border is removed and the button keeps a stable size when focused.

[1]: 8f41224083f198c5d86cdf6f43824b42bdc73d36

task-6259086

#website editor#theme colors#keyboard navigation

Removals(2)

Features or functions removed from Odoo

[REM] base: remove account_winbooks_import

PR #287851

CoremasterbaseMedium

The Winbooks import feature has been removed from Odoo. This matters for businesses that previously relied on this import option, as they will need to use another supported way to bring Winbooks accounting data into Odoo.

Original PR description

removing account_winbooks_import

task-id: [6560446](https://www.odoo.com/odoo/project/967/tasks/6560446)

#winbooks#import#accounting

[REM] account_winbooks_import: remove winbooks module

Refactoring(14)

Code cleanup and technical improvements

[REF] spreadsheet_edition: convert static props to useProps

PR #131232

Enterprisemasterspreadsheet_edition

Updated internal spreadsheet component setup to use the current supported approach for handling component inputs. This helps keep the spreadsheet experience maintainable and reduces the risk of future compatibility issues, with no expected functional change for users.

Original PR description

Replaced deprecated uses of `static props` with calls to `useProps()`, providing actual props validation for Owl components.

Whenever possible, also removed "empty" props definition, being either:
- `static props = ["*"]` with no use of `this.props`;
- `static props = {}`.

#spreadsheet#maintenance#compatibility

Partial revert of da720a8563570a6c0860699d0a542dfa2ee3c392. The automatic confirmation on first payment is error-prone since forged requests could lead to a confirmed SO with a 0.1cents payment regardless of whether a payment link was issued with the given amount. Keep requiring the prepayment amount for SO confirmation, while keeping the payment links open for any amount. Adapt the portal SO views so that the payment amounts are correctly displayed in most situations. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Introduces a new "Map Timeline" view for Field Service (Maps > Timeline), combining a map and a Gantt timeline side by side so managers can plan daily interventions from both a spatial and a temporal angle at once, grouped by resource, with inherited features (create, edit, drag-and-drop, buffer times, routing, etc.) preserved in both panes. On top of the base view, the map and timeline are also kept coherent with each other: - folding a resource group in one pane folds it in the other, including the "Open Shifts" and "Shifts to assign" groups - hovering a pin, a pin group, or a shift highlights its counterpart(s) across the map and the Gantt, as well as their side panels - hovering a pin group also highlights its route on the map, with stop numbers shown along it - resource colors (including materials) stay consistent across the Gantt, the map pins, and the map side panel task-6273718 Co-authored-by: Maxime de Neuville (mane) <mane@odoo.com>

This PR brings a few improvements to the attendance review of the systray so that it takes less room and only details an attendance on demand. It also fixes the break duration of the kiosk: 1. Enable "Break Management on Checkout" in Settings > Attendances and open the attendance kiosk 2. Identify as an employee to check in, then identify again to check out 3. On the goodbye screen, click "Add my break times" and enter a duration longer than the attendance that was just closed 4. Confirm -> the error is shown but the kiosk has already gone back to its main screen, so the break has to be entered again from scratch With this PR, the duration is checked against the attendance before being sent and the dialog stays open until it fits. Task-6542050

Steps to reproduce: - Open the website editor. - Open the theme color picker. - Focus an edit color preset button with the keyboard. => The button shifts when it receives focus. Before this commit, a transparent border reserved space outside focus. Since [1], the focus indicator uses a `box-shadow`, so that border disappeared on focus and changed the button size. After this commit, the obsolete border is removed and the button keeps a stable size when focused. [1]: 8f41224083f198c5d86cdf6f43824b42bdc73d36 task-6259086

Replaced deprecated uses of `static props` with calls to `useProps()`, providing actual props validation for Owl components. Whenever possible, also removed "empty" props definition, being either: - `static props = ["*"]` with no use of `this.props`; - `static props = {}`.

Purpose ======= Support direct messages for Facebook and Instagram pages. For Instagram, we have 24h to respond to a user, we also need to inform the Instagram user that he's talking to an automated agent when it's the case. Only professional account are supported. See https://developers.facebook.com/docs/instagram-platform/instagram-api-with-instagram-login/messaging-api/ When a message arrive, we fetch the last messages to get the user / LLM some context of the previous conversation. One limitation for Instagram, when fetching the message, we can get only the 20 last messages. See: https://developers.facebook.com/docs/graph-api/reference/v25.0/conversation Like `ai_livechat`, we can configure an LLM to answer to the user (if no operators are available, etc). For traditional live chat, the visitor has a button "Ask Human". This is not possible for all media, so the LLM has a tool and it can ask a human when it's necessary. Configuration Facebook ====================== Configure the webhook URL in the settings of the application ("Messenger" -> "Messenger API Settings" -> "Configure webhooks") Configure the verify token in the settings of Odoo / IAP with the value you want (you will need to use the same token in the Facebook application settings). Enter - "<url of the database>"/social_facebook/webhook - "<url of IAP>"/api/social/facebook/1/webhook Then subscribe to the "messages" and "message_reactions" in the list. The permission `pages_messaging` and `pages_manage_metadata` are needed. Configuration Instagram ======================= For Instagram, we need to setup the callback URL in "Messenger -> Instagram Settings", the configuration is very similar to the Facebook steps. Task-5948062

Lets each signer sign the document with their own itsme® qualified certificate, producing a qualified electronic signature (QES) attributable to the signer instead of the company seal alone. In sign, the completed document is now built as a chain of incremental updates over the original bytes and sealed once at the end, so the signatures already applied stay valid. The model `sign.completed.document` becomes `sign.request.document`, a working copy that belongs to one request and carries the file through its whole life. A signer can now sign the document themselves (using external service), which puts the request in a strict signing order so that every signature covers the contributions made before it, and freezes the file while their signature is being produced before it is embedded or discarded. Because such a signature attests values that must not move under it, the flow is guarded on every side. The signer reviews the frozen bytes before their signature is collected. An answer changed afterwards gives the pending attempt up instead of signing content that is no longer current. The authentication of a role can no longer change once its turn has started, and a request can only hold one working copy per document. Those working copies and the signatures they carry are read only for sign users and they are removed together with the request. Signing for everyone in one session is refused if at least one signer signs the document externally, because each of them has to sign in person. In `sign_itsme`, a new signing role produces the signature with itsme®, charged in itsme® credits. Unlike the identity check it cannot be skipped when credits are missing, because here the qualified signature is the signature itself. A signer can sign several documents of the same request in one itsme® action (up to 70 documents). `sign_emsigner` is adapted to the incremental flow. --- task-4951149 Depends on odoo/odoo#253372 (incremental PDF signing utilities) and on the "generalize PDF signing with incremental merge" PR this branch is stacked on, #110345.

In this [PR](https://github.com/odoo/odoo/pull/223685), the Buy, Manufacture and Resupply Subcontractor on Order routes were made warehouse routes to simplify product configuration. Adding a vendor or a BoM is enough to make a product ready to buy or manufacture, without manually selecting the corresponding route on the product. Later, this [PR](https://github.com/odoo/odoo/pull/274672) made the ORM check the comodel domain when linking records to x2many fields and set `product_selectable` to [True](https://github.com/odoo/odoo/pull/274672/changes/c758a2dcd9ecf464ca8b9aa8f19dfadf30bf4755#diff-e018fe59e11c4e0078e9bc19879f9e98c731bb84c71766ef360ccc482c59d2d8), making these routes available for selection on the product form again. This commit makes routes as warehouse routes [again](https://github.com/odoo/odoo/pull/280682/changes#diff-e018fe59e11c4e0078e9bc19879f9e98c731bb84c71766ef360ccc482c59d2d8L393) to simplify product configuration and updates the affected tests to explicitly enable `product_selectable` when they need to assign a route to a product. Enterprise PR:- https://github.com/odoo/enterprise/pull/126863 TaskId:- 6442488

Add a dedicated ai_tool_create_update_automation tool so agents manage base.automation records without going through the generic create/update tools: it takes model and field names instead of ids, validates the trigger and the ai_action_prompt against the target model, and shows a single preview instead of one per underlying record. Log automation runs properly in their own chat: post a kickoff note with field placeholders resolved to the record's actual values instead of their labels, log "has run <automation>" when triggered from the chat, and steer the agent to update the right automation when asked to change one. Forbid Markdown in ai_action_prompt (the field only renders HTML) and fall back to converting it when the model writes it anyway. Ship the full agent avatar set: 3 silhouettes x 5 colors x 8 job roles, under a consistent AvatarN-<Color>[-<Role>] naming. An agent gets a random silhouette on creation; picking a role via the Self Update skill redraws it in the same color and number. Rewrite the standard agent subtitles in the first person, and align the Self Update skill so agent-generated subtitles follow the same voice. Fix a crash in ai_tool_update_records's preview when a Selection field being updated is currently unset (e.g. res.partner.type, ai.agent.avatar_role): field._selection[value] raised a KeyError on a falsy value instead of falling back to displaying "None". task-6512101

Before, `ai.embedding` was geared specifically towards `ai.agent.source` and its attachments: every source had to materialise an `ir.attachment` before it could be vectorised, and RAG retrieval could only look at one model at a time. This PR generalises the embedding layer so that any model can be embedded and retrieved, and converts the existing source types to use it. ### `ai.embedding.mixin` New mixin owning the `embedding_ids` one2many and the embedding lifecycle. A model inheriting it implements the hooks: content extraction, chunking (tabular-aware), duplicate detection by checksum, domain of the records to embed, and the embedding models to use. Embedding creation is cron-driven, which supersedes `_update_sources_status`. `ai.embedding` itself loses `attachment_id`/`checksum` and gains `res_model`/`res_id`, so a chunk can point at any record. ### Direct embedding of every source type | Source | Before | Now | |---|---|---| | Attachment | embedding logic carried by `ir.attachment` | `ir.attachment` inherits the mixin | | Document | copied into an attachment, then embedded | `documents.document` embedded directly | | Knowledge article | HTML extracted into an attachment | `knowledge.article` embedded directly | | Web page | fetched into an attachment | `ai.web.page` embedded directly | The attachment-copy flows (`_sync_sources_content`, `_recreate_attachments_for_sources`) are dropped. Each model only picks up the records actually linked to an agent source. ### Retrieval - `_get_similar_chunks` now takes a `target_by_model` mapping instead of a single `res_model`, so one similarity search spans embeddings of heterogeneous models. `ai.agent.source._get_rag_target` is the overridable hook returning the (model, id) pair a source is embedded through, and `_get_models_map` builds the mapping. - Chunks whose `embedding_vector` is still NULL are excluded from retrieval. Their similarity was NULL and `NULLS FIRST` is the default for `ORDER BY ... DESC`, so between the creation of a source and the next cron run they outranked every genuine match and took all the `top_n` slots. ### Citations Inline citations reference `ai.agent.source` ids instead of attachment ids, and the link rendering is delegated to `_get_source_link`, implemented per source type (attachment/url in `ai`, document in `ai_documents_source`, article in `ai_knowledge`) instead of a hardcoded `/web/content` URL. The prompt instructions are updated accordingly. ### Also in this PR - `ai.agent.source.type` becomes a computed field, derived from whichever record field is set (`attachment_id`, `web_page_id`, ...). - `ai_app` accepts `.md` files as agent sources: the allowed extensions are extracted into a single `allowedExtensions` getter used both by the file input `accept` attribute and by the client-side validation. Markdown attachments are indexed as plain text, so no server-side change is needed. task-6283960 Upgrade PR: odoo/upgrade#10929

**[IMP] payment_paypal: add seller onboarding via OAuth** First party Integrated Sign-Up enables partners to integrate the seller onboarding into their software allowing to seamlessly and securely onboard sellers before activating PayPal payments. In this commit, we integrate First party Integrated Sign-Up to Odoo. --- **[IMP] payment_paypal: add payment methods** We currently only support PayPal Wallet, but PayPal can also be integrated as a regular payment provider, offering many payment methods, and worldwide coverage. In this commit, we add the following payment methods: - Via PayPal's JS SDK: Pay Later, Venmo, and Advanced Credit and Debit Cards. - Via Orders API: Bancontact, BLIK, EPS, iDEAL, Multibanco, MyBank, Przelewy24, and Trustly. We also migrate PayPal Wallet integration from JS SDK to Orders API to uniformize the look of payment methods through different payment providers. --- **[IMP] payment_paypal: add tokenization support** Before this commit, customers had to re-enter their payment details for every PayPal transaction, and merchants could not charge them offline (e.g., for subscriptions or invoice follow-ups). This commit introduces the ability to tokenize PayPal Wallet and PayPal-provided cards. Tokenization is available if the merchant's account has the advanced vaulting capability enabled. We also handle the case where PayPal creates the vault asynchronously, generating the token via a webhook rather than the immediate checkout response. --- task-6095035

South Korean tax law classifies each transaction under a specific proof of issuance (세금계산서, 계산서, 신용카드, 현금영수증, ...), and which VAT report box a transaction is reported under depends on that classification, not just on its taxes. Add `l10n_kr_issuance_type` to `account.move` so this can be recorded per invoice and used to drive VAT report generation. Since a given customer or vendor typically uses the same proof of issuance across transactions, add `l10n_kr_default_issuance_type` on `res.partner` (under Customer Invoices) so users don't have to pick it manually every time. `sale.order` carries the same field and passes it along when an invoice is created from the order, so issuance type can be set from the Sales app without needing access to Accounting. Also add: - `l10n_kr_edocument_number` on `account.move`, next to Customer Reference, to record the e-document number issued for the transaction. - South Korea's Tax ID label (`res.country.vat_label`) as "BRN" (Business Registration Number), matching local terminology. Now that proof of issuance is tracked separately, the `account.tax` templates no longer need one tax per rate/issuance-type combination: collapsed ~64 taxes (e.g. separate `10% TI`, `10% CR`, `10% Card` sales taxes) down to ones keyed only by rate and nature (standard, zero-rated, exempt, fixed-asset, non-deductible, deemed/recycled input VAT, ...), carrying just the base VAT tag. `general_tax_report.xml` and `simplified_tax_report.xml` were updated to derive their per-issuance-type boxes from `l10n_kr_issuance_type` on the move directly instead. [task-6216393](https://www.odoo.com/odoo/my-tasks/6216393)

[IMP] calendar,hr_calendar: UX improvements Several smaller ux improvements: - Updated the homeworking location wizard to work with mobile view - Updated header and sync status for mobile view - In the worklocation wizard, if the user doesn't have a linked employee_id but has the rights to set one, they now see a button redirecting them to the employees view [IMP] web: prevent scrolling and swiping at the same time In the calendar view on mobile devices, if the user starts scrolling vertically and then switches to horizontal swiping, both motions are triggered at the same time, leading to some very janky movements. When scrolling up/down, the swiper input is very sensitive to left/right motions, which means you can very easily accidentally swipe to the next day when scrolling The idea behind this change is to: - scroll down or up OR left or right - NEVER both at the same time This commit introduces an `axis lock` which only enables scrolling in one direction at a time. Test changes: The drag called in tests performs an initial movement to start up the dragging motion. This motion can happen on either axis, which can trigger the axis lock before the actual drag we want to test happens. The change to the test removes this initial motion. When calling navigate, the swipe was performed from (0, 0) to the middle right of the target element. This introduced a significant Y offset to the drag, and was considered a vertical scroll. With this update, we start the swipe in the center of the element to ensure a ~0 Y delta. Task-6396805

In Peru, the printed PoS receipt is the legal electronic invoice/receipt (Factura/Boleta Electronica): it must carry the QR code and the summary hash from the signed e-invoice. Since 19.4, PoS invoice PDF/EDI generation became asynchronous by default (deferred to a cron) to speed up checkout, but l10n_pe_edi_pos was never updated to opt out of that for Peru, so the signed data doesn't exist yet when the receipt is printed right after validating the order. Steps to reproduce: ------------------- * Install l10n_pe_edi and activate SUNAT Signature Provider Setting * Create and validate a PoS order and set "invoice" to true * Print the receipt (Full Receipt or Simplified Receipt) > Observation: Neither receipt includes the QR code or the summary hash, so the printed receipt is no longer a valid electronic document. Why the fix: ------------ Forcing the whole invoice (PDF + email + e-invoice) to be generated synchronously would block checkout on a live SUNAT call, and would leave failed orders with no way to be retried by the deferred-invoice cron. PosOrder._generate_pos_order_invoice() now lets the PDF/email stay deferred to the cron as before, but posts the e-invoice to SUNAT synchronously on its own (no PDF, no email), so the receipt gets its QR code/hash right away. This matches the pattern already used by l10n_sa_edi_pos (generate_pdf=false + a synchronous EDI-only step), as opposed to l10n_co_edi_pos, the only module forcing generate_pdf=true. A chatter message is posted on the invoice if SUNAT rejects it, since calling the EDI step directly bypasses the notification that account.move.send would otherwise post. opw-6426510 Forward-Port-Of: odoo/enterprise#126345

Problem: A time off request is saved with a duration of 0 days instead of 1 day as soon as an automation rule on Time Off has an action that creates an activity. Cause: `_compute_field_value` runs the actions while the fields of the computation it wraps are still protected and not written yet. On `hr.leave` the actions run from a computation nested in `_compute_date_from_to`, so `date_from` is empty when the activity notification reads `display_name`, and `_compute_duration` stores 0. Setting `date_from` afterwards does not mark `number_of_days` to compute again since it is protected. Solution: Extract the snapshot `_filter_pre` already does into `_keep_to_compute` and wrap the post filter and the actions with it, so the fields depending on the running computation stay to compute. Same treatment as 488419a5ca49 (odoo/odoo#243611) on the pre filter. Steps to reproduce: - Enable the developer mode. - Go to Settings > Technical > Automation Rules and create a rule on the Time Off model with the trigger On create and edit. - Add an action of type Create Activity, set its Responsible to another user, and save. - Go to Time Off > New, pick an employee and a time off type, and request one working day. - Observe that the request shows a duration of 0 days. Ticket [link](https://www.odoo.com/odoo/project.task/6498783) opw-6498783 Forward-Port-Of: odoo/odoo#287536 Forward-Port-Of: odoo/odoo#286791

## [FIX] voip: one registration binding per softphone window Asterisk identifies a registration binding by its Contact URI alone: the registrar compares candidates with pjsip_uri_cmp() and names the stored object after the MD5 of that URI. Neither `+sip.instance` nor `reg-id` is consulted, RFC 5626 section 5.4.1 not being implemented on the inbound registrar side. Every window of a user therefore advertised the same Contact and collapsed into a single binding, so only the last one to REGISTER could be rung - across tabs and across devices alike. The discriminator has to be a URI parameter rather than part of the user part: res_pjsip_path.c matches the user part against the AOR name to decide whether to attach the edge proxy's RFC 5626 flow-token Path, and without that Path an inbound INVITE cannot be routed to the browser at all. Parameters after the host are ignored by that lookup yet do make two URIs compare unequal, so `x-odoo-unique` buys distinct bindings at no cost to the Path. It is assigned once per user agent instead of being computed in the configuration getter, so that reading the configuration twice cannot yield two different Contact URIs. ## [FIX] voip: restrict voip.extension range Before this commit: - voip module validates against voip.extension number length: between 100 and 99999 - phone service configures tenants to allow extensions between 10 and 9999 As there is a discrepancy between those 2, we decided to allow the ranges that overlap between both parts. So, after this commit: - voip module allows extensions numbers between 100 and 9999. Rationale We decided to remove the 5-number range on that part instead of adding it in the phone service part, because: - 9900 extension numbers is plenty enough and it can lower a bit the complexity of the asterisk dialplan, which makes the asterisk dialplan regeneration more lightweight - it is easier to add a range in the future than remove one, due to migration nightmare

Security(1)

[REV] sale: do not confirm quotes after any successful payment

New Features(11)

[MERGE] planning_field_service: add map timeline

Improvements(68)

[IMP] hr_attendance: lighten the attendance review in the systray

Bug Fixes(39)

[FIX] html_builder: prevent theme edit button focus shift

Removals(2)

[REM] base: remove account_winbooks_import

[REM] account_winbooks_import: remove winbooks module

Refactoring(14)

[REF] spreadsheet_edition: convert static props to useProps

Security(1)

[REV] sale: do not confirm quotes after any successful payment

New Features(11)

[MERGE] planning_field_service: add map timeline

Improvements(68)

[IMP] hr_attendance: lighten the attendance review in the systray

Bug Fixes(39)

[FIX] html_builder: prevent theme edit button focus shift

Removals(2)

[REM] base: remove account_winbooks_import

[REM] account_winbooks_import: remove winbooks module

Refactoring(14)

[REF] spreadsheet_edition: convert static props to useProps

[ADD] l10n_fr_accountant_knowledge: add the Plaquettes as in PCG

[IMP] (ai_)social(_facebook,_instagram): support direct messages

[ADD] l10n_es_ecommerce: Include a new module for simplified invoices in spain.

[MOV] hr_holidays: add leave_ids to hr.employee

[IMP] l10n_in: add support for the Composition Tax Scheme

[IMP] ai(_website): ai tool to fetch text and images from urls

[IMP] l10n_in_reports: add returns and reports for the Composition Scheme

[ADD] l10n_pk_edi_pos: submit POS orders to the FBR

Master esg policies action target mane

[IMP] sign, sign_itsme: qualified electronic signatures with itsme®

Website icon styles

[IMP] *: sales menu simplification

[IMP] timesheet_grid_hr_attendance: lighten the systray of the two features

[IMP] sale_*: simplify sales/rental menu

[IMP] account_accountant: set account multiple amount

[IMP] hr_holidays, resource_calendar: link accural plans to working s…

[IMP] base: reflect field groups

[IMP] stock,*: make routes warehouse specific again

[IMP] l10n*_payroll: adapt existing accrual plans

[IMP] pos_**: enforce employee role-based access control

[IMP] ai, ai_app: automations tool and agent avatars updates

[IMP] account_bank_statement_import_{camt,ofx,qif}: fill transaction_details

[REF] ai: generalise ai.embedding and embed sources directly

[IMP] {quality_,}mrp_workorder,*: make routes warehouse specific again

[IMP] approvals: remove ordering of approving in approvals

[IMP] obox: increase obox queue lifetime

[IMP] hr_payroll: remove payrun steps

[IMP] payment_paypal: support OAuth, alternative payment methods and tokenization

[IMP] hr_work_entry, hr_holidays: unassimilated work entry types

[IMP] mail: support direct messages in `social`

[IMP] web, mail: refine status bar layout

[IMP] l10n_be_hr_payroll: 281-mapping, report 281.45 and 273S

[IMP] l10n_be_hr_payroll: end of collaboration seniority default

[IMP] l10n_be_hr_payroll: unassimilated work entry types

[IMP] account_reports: show applied filters count in Partners filter

[IMP] l10n_be_reports: Advance payment return view improvements

[IMP] web_enterprise: refine status bar layout

[IMP] account_reports: add tax closing rounding accounts on return type

[IMP] l10n_es_reports: Update spanish balance and PandL reports

Master voip move tenant seba

[IMP] documents(,_hr(,_*)): link folders, use hr groups, force bridge

[IMP] l10n_kr, l10n_kr_sale: track proof of issuance for VAT reporting

[IMP] product,website_sale: support barcode search for products

[IMP] mail: allow headers to hide when rendering mail layout

[IMP] web_tour: add active field on web_tour.tour

[IMP] l10n_kr_reports: warn on moves missing proof of issuance

[IMP] l10n_fr_reports: import export fiscal declaration

[IMP] l10n_be_hr_payroll: add NSSO immatriculation date

[IMP] stock_barcode_barcodelookup: access right based on product

[IMP] website_generator: version 3.0.0 for odoo 20

[IMP] l10n_mx_edi: Add logging for failed automatic cancellations

[IMP] l10n_uk_reports: Add fields for multi-company implementation

[IMP] account, l10n_cz: Invoicing QR code workflow

[IMP] Use multi ID on invoice templates