Friday, February 6, 2026
9 changes · 18.0
Enhancements to existing features
This update ensures that the point-of-sale system now displays currency symbols ($ for USD, € for EUR, etc.) alongside the total amount and change for customers. This change is required to meet scale certification standards and improves the overall presentation of prices in the POS interface.
Original PR description
This PR adds the currency symbol on the customer display for point of sale for the total amount + change. (formatted based on the currency, e.g. $ before, eur after the amount) This is required by the scale certification Before: <img width="777" height="604" alt="image" src="https://github.com/user-attachments/assets/28688075-b387-477a-930d-410f1107cc83" /> After: <img width="787" height="638" alt="image" src="https://github.com/user-attachments/assets/724a1360-78a7-4630-a034-e115dd09f057" /> --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This update fixes an issue where month names were incorrectly displaying based on the server's locale instead of the user's environment. The change ensures month names are displayed in the correct language for each user, improving the user experience across Odoo modules.
Original PR description
Month name is using the locale language instead of the env language Get month name in the env language Enterprise PR: odoo/enterprise#106175 Task [link](https://www.odoo.com/odoo/project.task/5902364) task-5902364
This update corrects a broken link used by Odoo to connect with the Polish Electronic Data Interchange (KSeF) system. The change ensures that Odoo can properly transmit and receive data required for Polish tax compliance. This resolves a connectivity issue impacting the functionality of the l10n_pl_edi module.
Original PR description
The production URL for the Polish EDI (KSeF) was incorrect. This commit updates the endpoint to the current valid URL to ensure proper connectivity. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects a bug where empty loyalty cards were created when multiple loyalty programs existed, even if only one applied points to an order. The fix ensures that loyalty cards are only created when points are actually earned, reducing unnecessary record creation and improving data accuracy.
Original PR description
Currently, when you have multiple loyalty program but only 1 applies points on the current order, the other will have a loyalty card created with 0 points. steps to reproduce: ------------------- * Create a loyalty program giving you 1 point per $ on product 1 * Create a loyalty program giving you 1 point per § on product 2 * Make a pos order with just product 1, add a customer * Check the programs in the backend > Observation, a loyalty card with 0 points was create for the second loyalty program Why the fix: ------------ This creates a lot of unecessary records. We now only create cards where there are points or when there 0 points because a reward has been applied, thus keeping history. opw-5405109
This update replaces a real tax ID placeholder in the Odoo Base VAT module for Turkey. This change prevents users from accidentally using the placeholder for actual transactions, ensuring data integrity and compliance. It's a minor update focused on security and accuracy.
Original PR description
The previous placeholder used a real tax ID. Replacing it with a dummy prevents users from using it to submit transactions. task-5441218 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#246837 Forward-Port-Of: odoo/odoo#242189
This update simplifies sales order reporting for subscription customers. The 'remaining hours' field, which could be misleading due to recurring subscription delivery cycles, has been hidden when a sales order line is linked to a subscription. This ensures a clearer and more accurate view for our customers.
Original PR description
This change hides the remaining_hours_so field when the sales order line is linked to a subscription. Unlike standard service or time-based sales orders, where this field reflects the difference between the quantity ordered and the quantity delivered, the concept does not translate well to subscription logic. In the context of a subscription, the service is delivered on a recurring period (monthly, yearly, etc.). Delivery quantities continuously accumulate over time, and because the subscription renews indefinitely until cancellation, the “remaining hours” calculation quickly becomes misleading. In many cases it can drift into negative values, giving the impression of an error or over-consumption when, in reality, the subscription is simply following its recurring delivery cycle. To avoid confusing end-users and to maintain a clean, intuitive interface, we hide this field whenever the line is part of a subscription. opw-5246238
This update removes the direct technical contact email (peppol.iap@odoo.com) from the Peppol integration, aligning with previous versions. This change enhances security and privacy by only displaying the service name, as was done in prior releases. It ensures clients receive accurate information without exposing internal support details.
Original PR description
…pport Our TechnicalContactUrl is peppol.iap@odoo.com, it should not be exposed to the client as the support contact. Let's just expose the name of the service like we do above 18.0. task-none Forward-Port-Of: odoo/odoo#247607
This update fixes a misleading error message displayed when validating Argentine electronic invoices (ARCA). The message has been corrected to accurately reflect the issue: the invoice date must be after the last validated invoice, not before. This ensures proper compliance with AFIP regulations.
Original PR description
WSFE error 10016-1 must be "The invoice date cannot be before the last invoice validated in AFIP." instead of "The invoice date cannot be after the last invoice validated in AFIP". Steps to reproduce: validate argentinean customer electronic invoice with invoice date before than the last invoice date validated in ARCA. Task Adhoc side: 44290 Task latam: 1376 Forward-Port-Of: odoo/enterprise#106305
This update simplifies the sales order interface for subscription customers. It hides a confusing 'remaining hours' field that could mislead users about their service consumption. This change ensures a cleaner, more intuitive experience for subscription customers, aligning with the recurring delivery model.
Original PR description
This change hides the `remaining_hours_so` field when the sales order line is linked to a subscription. Unlike standard service or time-based sales orders, where this field reflects the difference between the quantity ordered and the quantity delivered, the concept does not translate well to subscription logic. In the context of a subscription, the service is delivered on a recurring period (monthly, yearly, etc.). Delivery quantities continuously accumulate over time, and because the subscription renews indefinitely until cancellation, the “remaining hours” calculation quickly becomes misleading. In many cases it can drift into negative values, giving the impression of an error or over-consumption when, in reality, the subscription is simply following its recurring delivery cycle. To avoid confusing end-users and to maintain a clean, intuitive interface, we hide this field whenever the line is part of a subscription. opw-5246238