Odoo Changelog — 2026-06-15

Monday, June 15, 2026

2 changes · saas-19.1

Improvements(2)

Enhancements to existing features

[IMP] l10n_de_pos_cert: improve short and long tx synchronization flow

PR #120218

Enterprisesaas-19.1l10n_de_pos_certMedium

This update enhances the synchronization of point-of-sale (POS) transactions with Fiskaly, our payment processing partner. It separates flows for retail and restaurant orders, ensuring more accurate and timely updates are sent, particularly during kitchen synchronization for restaurants. This improves the reliability of financial reporting.

Original PR description

In this commit: ------------------ - Maintain separate Fiskaly transaction flows for retail (short tx) and restaurant (long tx) orders as discussed with the Fiskaly team. - `Initialize order…

In this commit:
------------------
- Maintain separate Fiskaly transaction flows for retail (short tx) and restaurant (long tx)
  orders as discussed with the Fiskaly team.
- `Initialize order transactions` with an empty payload when the `first product` is added.
- Start `receipt transactions` with an empty payload when the `first payment line` is added.
- For retail flows, no intermediate order updates are sent to Fiskaly before finalization.
- For restaurant flows, create additional transaction updates during kitchen synchronization.
  Ensure already synchronized products are not resent, and only newly added or updated
  quantities are included in the payload.
- `Finalize order and receipt transactions` with complete order lines and payment details
  when we validate the order.

task: 6208963

Reference:
<img width="1863" height="1285" alt="de_tss_flow" src="https://github.com/user-attachments/assets/9140788e-7948-4a08-9f11-27197b22ca8b" />

Forward-Port-Of: odoo/enterprise#119912
Forward-Port-Of: odoo/enterprise#117526

#POS#Fiskaly#Payment#Restaurant#Retail

[IMP] point_of_sale: extract `formatQuantityValue`

PR #269927

Coresaas-19.1point_of_saleMedium

This update enhances the Point of Sale system by allowing more flexible formatting and parsing of order quantities within the decrease quantity popup. This change enables other modules to enforce quantity constraints, like preventing negative values, improving overall order accuracy and data integrity.

Original PR description

We now allow formatting and parsing quantity on an orderline when using the decrease quantity popup.
This allows overriding from other modules to add contraints (e.g. `pos_blackbox_be` prevents from setting negative quantities).

see odoo/enterprise#119702
task-5942777

Forward-Port-Of: odoo/odoo#269487

#pos#quantity#order

In this commit: ------------------ - Maintain separate Fiskaly transaction flows for retail (short tx) and restaurant (long tx) orders as discussed with the Fiskaly team. - `Initialize order transactions` with an empty payload when the `first product` is added. - Start `receipt transactions` with an empty payload when the `first payment line` is added. - For retail flows, no intermediate order updates are sent to Fiskaly before finalization. - For restaurant flows, create additional transaction updates during kitchen synchronization. Ensure already synchronized products are not resent, and only newly added or updated quantities are included in the payload. - `Finalize order and receipt transactions` with complete order lines and payment details when we validate the order. task: 6208963 Reference: <img width="1863" height="1285" alt="de_tss_flow" src="https://github.com/user-attachments/assets/9140788e-7948-4a08-9f11-27197b22ca8b" /> Forward-Port-Of: odoo/enterprise#119912 Forward-Port-Of: odoo/enterprise#117526

We now allow formatting and parsing quantity on an orderline when using the decrease quantity popup. This allows overriding from other modules to add contraints (e.g. `pos_blackbox_be` prevents from setting negative quantities). see odoo/enterprise#119702 task-5942777 Forward-Port-Of: odoo/odoo#269487