Release 2025.10.0 of pretix
Today, we are releasing pretix 2025.10.0. This release includes a new feature for program times as well as many small changes.
Big thanks go out to Ana Rute Pacheco Vivas, Andrii Andriiashyn, CVZ-es, Hijiri Umemoto, Linnea Thelander, Núria Masclans, Sanny, Theodore, and Yasunobu YesNo Kawaguchi who contributed to this release. ❤️
pretix 2025.10.0 is now available for installation via pip. The new Docker images will appear on Docker Hub over the
next few hours. All customers of pretix Hosted are already using the new version and do not need to take any action.
Program times
Our new feature allows you to declare one or multiple "program times" for every product. This is useful when a ticket represents a part of an event that takes place on a different date or at a different time than your main event, such as a workshop day before/after your conference. This information is not used for access control, but it will control the calendar invite and wallet ticket sent to your attendees and it can also be used in your PDF ticket layout.
This feature is not available in an event series.
Tax rounding
pretix historically calculates the tax amount for every ticket or product individually and then sums them up to obtain the total VAT amount for an order. We believe this is the most sensible way to handle taxes in a system like ours, since it never causes problems during order changes and allows clear reporting across all dimensions.
However, in many countries or industries, it is customary to round taxes in a different way: By summing up the tax-exclusive price of every position and then computing the tax amount from that sum. This can lead to a result that differs up to 0,01 per ticket or product. For e-invoicing, the European standard EN16931 mandates rounding in this way.
Starting now, you can select how pretix should round taxes for your event. Regardless of the selection, pretix will still store prices incl. and excl. VAT for every ticket, however the values will be corrected such that the sums of the order match up. If you want to learn more, you can find a detailed description in our user documentation or a sample calculation in our developer documentation.
Peppol invoicing
Peppol is an international network to exchange commercial documents (such as invoices) between business entities (such as companies and governments). pretix Hosted now includes functionality to send invoices through Peppol. You can find out more in our recent blog post on Peppol.
Smaller changes and bugfixes
Ticket shop and widget
-
The shop start page as well as the cross-selling step now highlights which products are already contained in the cart.
-
The start date of ticket downloads is no longer shown if ticket downloads are disabled.
-
Bank transfer: The reference and amount are now shown as the first part of banking information to allow a consistent order between SEPA and non-SEPA accounts.
-
Bank transfer: A bug has been fixed that prevented the reference from including the invoice number when paying existing orders.
-
Bank transfer: Transfer references of system-generated refunds are now properly internationalized.
-
Stripe: Revolut may now be used with more supported currencies.
-
A bug preventing selection of a payment method when a gift card is stored in the customer account has been fixed.
-
A race condition has been fixed that allowed users to circumvent the maximum number of tickets per cart.
Ticketing backend and configuration
-
The system now allows to validate the email address of backend users. This will be the basis for additional security measures in the future.
-
The issuer address for invoices can now contain a state for countries where this is a required part of the address.
-
The PDF invoice renderer can now deal with a lot of content in a single table row, even if it exceeds the height of a page.
-
When changing existing orders in the backend, blocked seats can now be selected.
-
When configuring an OpenID Connect Identity Provider for customer accounts, the
scopesandclaimsare no longer validated against the IdP's discovery document, as the specification does not require it to be complete. -
A number of configuration fields in the settings no longer allow inputs of a length that causes issues.
-
Two columns in the order data export have been renamed to avoid them having an identical column name.
-
The product data export has been fixed to include correct prices for variations with a zero-valued price.
-
When creating a new event, the quickstart assistant now correctly declares which fields are optional or required.
-
Webhook URLs may now contain more than 255 characters.
-
It is no longer possible to change the currency for an event with existing orders.
-
When editing meta properties, a new button helps with keeping the allowed values sorted alphabetically.
Updates to official plugins and tools
-
The Bounce processing plugin has been released in version 1.5.1 to fix log entries not being linked to the respective orders.
-
The Computop plugin has been released in version 1.2.0 to fix a race condition and add support for Google/Apple wallet detection.
-
The Exhibitors plugin has been released in version 1.15.0 to add new export options.
-
The FKM Audit Module plugin has been released in version 2.2.0 to fix a wrongly categorized country and add an option to export only the first scans of every ticket per day.
-
The Offline Sales plugin has been released in version 1.12.1 to improve performance.
-
The Passbook plugin has been released in version 1.14.0 to support program times.
-
The PAYONE plugin has been released in version 1.4.0 to remove giropay support and add an option to add a reference postfix.
-
The pretixPOS backend plugin has been released in version 3.21.0 to improve Stripe test mode support and add a XLSX export for closing data.
-
The Resellers plugin has been released in version 3.1.0 to fix filtering of reports and add a new accounting report.
-
The Seating plugin has been released in version 2.5.1 to fix a performance issue when changing orders.
-
The ZUGFeRD invoices plugin has been released in version 2.6.1 to recommend setting the correct rounding mode.
Runtime and server environment
No changes.
Plugin API changes
No changes.
REST API changes
-
New endpoints for the check-in history have been added.
-
The order resource has a new attribute
tax_rounding_mode.

