Release 4.12.0 of pretix

Today, we are releasing pretix 4.12.0. This release features some amazing new options for our pretixSCAN access control features. As always, there are lots of bug fixes and improvements on smaller features throughout the system as well.

Big thanks go to Hana Happl, Hans Fraiponts, Julius Rickert, Mauro Amico, Michael, Michael Stapelberg, and Tony Pavlik who contributed to this release. ❤️

pretix 4.12.0 is now available for installation via pip. The new Docker images will appear on Docker over the next few hours. All customers of pretix Hosted are already using the new version and do not need to take any action.

Single QR code for add-on check-in

One of our most powerful features is the capability to create add-on or bundle products. There are many different use cases, but the most common one is to sell some kind of "upgrade" to a ticket. For example at a conference, you can sell an exclusive workshop in addition to the conference ticket. At a zoo, you can sell a parking ticket in addition to the entrance ticket.

Up until now, however, this was not really convenient to handle on site. In case of the conference, if tickets are to be scanned both at the general entrance as well at the individual workshop, attendees needed to bring both tickets and show the appropriate one of the two QR codes.

We're now able to present a much smoother solution where the attendee only needs to bring one barcode, the one of the main ticket. This also makes it more capable for events who print the ticket QR code on a badge, allowing people to receive all of their upgrades just by showing their badge.

To use the new feature, you need to create separate check-in lists. In our example from above, create one check-in list including only the main conference ticket. Then, create a second check-in list including only the workshop add-on product. On this new check-in list, enable the new option Allow checking in add-on tickets by scanning the main ticket.

Now, if you scan a ticket and it does not directly match a product on the check-in list, the system will check if the ticket instead has a matching add-on product that can be scanned in instead.

This feature is supported with pretixSCAN version 1.15.0 or higher on all platforms. This feature does not work in offline mode if no offline data is present on the device (i.e. it does not work based on signed ticket secrets).

Multi-event check-in

For some users of pretix, one event at a time is not enough. Up until now, if you have two events going on at the same time, you were required to use separate entrances with at least one installation of our check-in apps per event.

With this release, our Android app pretixSCAN allows you to select multiple events on the same device. This way, all your attendees can pass through a single entrance and then split into the different events after being scanned. If a ticket is scanned, the system will automatically figure out which event it belongs to and process the result accordingly.

This will be a great addition mostly for venues with multiple rooms and only one entrance, such as a typical mid-sized cinema, but it can also be used in some other ways. Some pretix users operate separate ticket shops for their day-to-day operations and for season passes. The new option also allows to scan both of these on the same device at the same time.

This feature is supported only in our pretixSCAN Android app with version 2.0.0 or higher. Support for pretixSCAN Desktop and pretixSCAN iOS is currently not planned, as we consider this a high-end feature for large event organizers who usually use our Android app on purpose-built devices.

Smaller changes and bugfixes

Ticket shop and widget

• The e-mail placeholder event_admission_time now respects the event time zone correctly.

• Add-on products are now labeled as "FREE" if their cost is zero. The "FREE" is now only skipped if the add-on configuration specifies that all add-ons are included in the price of the main product.

• Invoices now always show the value of redeemed gift cards if the configuration option "Show paid amount on partially paid invoices" is set.

• A bug has been fixed that caused incorrect numbered lists to show up in Markdown-processed content.

• If a product requires a membership and a user only has one valid membership, it will now be pre-selected automatically.

• The widget now allows to filter visible variations using a variations attribute similar to the existing items attribute.

• The social media description for event series pages no longer shows an unhelpful date.

• The order of products in the cart has been changed slightly to prefer products for the same event series date being listed as a group.

Ticketing backend and configuration

• A new option has been added to the cancellation settings preventing the calculated cancellation fee being shown to the user.

• A new exporter allows downloading a list of products in an event.

• A few issues in the new PayPal integration have been fixed.

• The Stripe plugin now shows the account ID of the connected Stripe account.

Runtime and server environment

No changes.

Updates to official plugins and tools

• If you operate pretixSCAN Proxy, you need to upgrade it to version 2.0 before you update your pretixSCAN Android apps to version 2.0.

• The pretixPOS backend plugin has been released in version 3.3.0 to fix a receipt rendering bug and add a new permission for cashier teams.

• The Reports plugin has been released in version 1.13.0 to allow reporting by calendar week.

• The Resellers plugin has been released in version 2.3.1 to fix issues with invalid reseller IDs.

• The Tracking plugin has been released in version 2.4.1 to fix issues some Content-Security-Policy issues.

Plugin API changes

No changes.

REST API changes

• The quota list now supports the subevent__in filter parameter.

• The invoice address of orders now exposes the user-defined custom_field.

• When creating customers, you can now set a new parameter send_email.

• A new set of endpoints has been added to allow executing data shredders via the API.

• The name_scheme setting is now exposed through the settings API.