Odoo Changelog — 2026-06-05

Friday, June 5, 2026

2 changes · 18.0

Improvements(2)

Enhancements to existing features

[IMP] account_peppol,l10n_fr_pdp: reregister

Core18.0account_peppoll10n_fr_pdpMedium

This update introduces a new button to streamline the reregistration process for French users, particularly those transitioning between Peppol and PDP systems. It addresses a previous testing issue where changes to the demo company's Peppol settings caused problems during the reregistration flow. This enhancement improves usability and simplifies a key business operation.

Original PR description

#### [IMP] l10n_fr_pdp: fix visibility for peppol (non-PDP)
#### [IMP] account_peppol,l10n_fr_pdp: reregister
This commit adds a button so that users can reregister more easily.
This is i.e. useful to switch from Peppol to PDP for French users.

#### meta
task-6265603

#account#french#peppol#pdp#registration

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

PR #117526

Enterprise18.0l10n_de_pos_certMedium

This update enhances the synchronization of point-of-sale (POS) transactions with Fiskaly, a key partner for German businesses. It separates retail and restaurant order flows, optimizing data transmission and ensuring accurate reporting by only sending updated product quantities during restaurant kitchen synchronization. This improves the reliability of financial data.

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 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" />

#POS#Fiskaly

#### [IMP] l10n_fr_pdp: fix visibility for peppol (non-PDP) #### [IMP] account_peppol,l10n_fr_pdp: reregister This commit adds a button so that users can reregister more easily. This is i.e. useful to switch from Peppol to PDP for French users. #### meta task-6265603

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" />