[tryton-announces] Tryton News February 2026

News - Tryton Discussion: udono Sat, 31 Jan 2026 23:11:18 -0800

During the last month we focused on fixing bugs, improving the behaviour of things, speeding-up performance issues - building on the changes from our release last month. But we also added many new features which we would like to introduce to you in this newsletter.

For an in depth overview of the Tryton issues please take a look at our issue tracker or see the issues and merge requests filtered by label.

Changes for the User

Sales, Purchases and Projects

We now add the optional gift card field to the list of products. This helps to search gift card products.

Now we clean the former quotation_date when copy sale records as we already do with the sale_date.

We now display the origin field of requests in the purchase request list. When the purchase request is not from a stock supply, it is useful for the user who takes action, to know the origin of the request.

Accounting, Invoicing and Payments

Now we support allowance and charge in UBL invoices.

We now fill the buyer’s item identification (BuyersItemIdentification) in the UBL invoice, when sale product customer is activated.
On the invoice line we have properties like product_name to get related supplier and customer codes.

Now we add a cron scheduler to reconcile account move lines. On larger setups the number of accounts and parties to reconcile can be very numerous. It would consume too much time to execute the reconciliation wizard, even with the automatic option.
In this cases it will be better to run the reconciliation process as a scheduled task in background.

We now add support for payment references for incoming invoice. As the invoice manages payment references, we support to fill it using information from the incoming document.

Now Tryton warns the user before creating an overpayment. Sometimes users book a payment directly as a move line but without creating a payment record. If the line is not yet reconciled (it can be a partial payment), the line to pay stand still there showing the full amount to pay. This can lead to over pay a party without any notice for the user.
So we now ensure that the amount being paid does not exceed the payable (or receivable) amount of the party.
There is no guarantee against overpayment The proper way to avoid is to always use the payments functionality. But the warning will catch most of the mistakes.

Now we add support for Peppyrus webhooks in Tryton’s document incoming functionality.

We now set Belgian account 488 as deposit.

Now we add cy_vat as tax identifier type.

Stock, Production and Shipments

We now store the original planned date of requested internal shipments and productions.
For shipments created by sales we already store the original planned date to compute the delay. Now we do the same for the supplied shipments and productions.

Now we use a fields.Many2One to display either the product or the variant in the stock reporting instead of the former reference field. With this change the user is able to search for product or variant specific attributes. But the reference field is still useful to build the domain, so we keep it invisible.

We now add routings on BOM form to ease the setup.

Now we use the default warehouse when creating new product locations.

User Interface

Now we allow to reorder tabs in Sao, the Tryton web client.

Now we use the default digit value to calculate the width of the float widget in Sao.

New Releases

We released bug fixes for the currently maintained long term support series
7.0 and 6.0, and for the penultimate series 7.8 and 7.6.

Security

Please update your systems to take care of a security related bug we found last month.

Changes for the System Administrator

Now we allow filtering users to be notified by cron tasks. When notifying subscribing users of a cron task, messages may make sense only for some user. For example if the message is about a specific company, we want to notify only the users having access to this company.

We now dump the action value of cron notification as JSON if it is not a string (aka JSON).

Now we log an exception when the Binary field retrieval of a file ID from the file-store fails.

We now support 0 as parameter of max_tasks_per_child.
The ProcessPoolExecutor requires a positive number or None. But when using an environment variable to configure a startup script, it is complicated to set no value (which means skip the argument). Now it is easier because 0 is considered as None.