Release 2024.10.0 of pretix

Today, we are releasing pretix 2024.10.0. This release includes a new cross-selling feature, a HubSpot integration, as well as improvements to our badge printing. Big thanks go out to Anarion Dunedain, arjan-s, CVZ-es, Davide Manzella, Felix Schäfer, Patrick Chilton, Rosariocastellana, Ryo Tagami, and Yasunobu YesNo Kawaguchi who contributed to this release. ❤️

pretix 2024.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.

Cross-selling

We are introducing a big new feature that allows you to sell additional products during checkout without requiring them to be an addition to a specific other product. This extends the existing upselling functionality of pretix to a few more important use cases. This unlocks new scenarios that can be handled, such as:

• During checkout, every purchaser should be offered a parking ticket. However, the parking ticket is not well-suited for an add-on product, since it is not bound to a specific ticket. For example, if someone is buying tickets for a family of five, there is no need to offer them the parking ticket five times.

• During checkout, a merchandise item should receive special promotion based on the cart contents. For example, if someone purchases a day pass for a spa, a selection of wellness products are offered that could be used during the stay.

• During checkout, the option to make use of a discount offer should be highlighted. For example, a dinner event might offer a free welcome bottle of champaign for everyone who purchases at least 5 tickets. With a combination of our automated discount rules and the new cross-selling feature, you can make this offer visible in the checkout process and make it easy for your customers to use the discount. This example is shown in the screenshot below.

Similar to add-ons, cross-selling is configured through our ticket categories. You can set a ticket category to be shown exclusively in the cross-selling step, or both in the cross-selling step and the regular product list. Additionally, you can constrain the visibility to carts with specific contents or to carts where an automated discount rule applies but the discount has not yet been used.

HubSpot integration

One of the most popular CRM choices these days is HubSpot, and we have frequently been asked how to easily transfer event registration data from pretix to HubSpot. This is no question that can have an easy answer, as HubSpot is a complex and highly configurable tool and chances are, every organizer is using it slightly differently.

Building on the experience of a few integration projects we have done with clients recently, we are now ready to offer a HubSpot plugin for pretix as a flexible solution to handle the most common use cases.

Specifically, the plugin is able to create or update a contact in HubSpot for every attendee registered in pretix. The mapping of pretix fields to HubSpot fields (as well as the policy of whether a field should be overwritten on the HubSpot contact or only be set if it is not previously known) is fully configurable in our pretix backend:

If you are using HubSpot and pretix, we'd like to invite you to try out the workflow offered by the plugin and let us know if it works for you!

Avoid reprinting badges

Multi-day events that combine badge printing and access control in one physical location often run into the problem that starting from the second day, pretixSCAN can no longer be set to automatically print badges on every successful ticket scan because this would lead to large numbers of badges printed for people who already have their badge that was printed on the previous day.

With this release, pretix gains the functionality to remember which badges have already been printed before. When using a compatible version of pretixSCAN, an automated print will now only be performed if the badge has never been printed before. If the attendee lost their badge from the previous day, it is of course still possible to manually print the badge with the press of a button.

This feature only detects badge prints performed through pretixSCAN Android 2.10.0 or newer (currently being released), pretixSCAN Desktop 1.23.0 or newer (already available), or pretixPOS 4.3.0 (will be released soon).

Smaller changes and bugfixes

Ticket shop and widget

• A price calculation issue has been fixed that affected products with a 0% tax rate and either a negative base price or bundled products with a designated price higher than the base price.

• If the add-on choice step during checkout would show up empty, the user is now immediately redirected to the next step.

• A performance issue was fixed that could cause service interruptions when dealing with a large spike in PayPal payments and a large database.

• The waiting list page now redirects to the shop start page if no product is sold out.

Ticketing backend and configuration

• You can now specify a custom help text for the custom invoice field.

• When viewing the answer overview for a question in an event series, you can now filter by date.

• The last date of order changes is now shown in the event timeline.

• A bug has been fixed that prevented removal of a seat from a voucher.

• Redirection loops during re-authentication have been fixed when using an external authentication backend.

Updates to official plugins and tools

• The FKM Audit Module plugin has been released in version 1.5.0 to support multi-event reports.

• The Pages plugin has been released in version 1.6.2 to fix handling of lists and empty lines.

• The Reports plugin has been released in version 1.20.0 to allow reports of ticket sales relative to the event date, including cumulative charts.

• The SEPA Direct debit plugin has been released in version 2.5.2 to fix a minor presentation error on invoices.

• The pretix-banktool utility has been released in version 1.1.0 to support more configuration options for the FinTS connection.

Runtime and server environment

• A warning is now shown in the backend if the cronjob has not been executed for several hours. This warning might wrongly show up after applying the update until the cronjob is first run again.

• pretix now supports fallback secret keys to allow for easier rotation of secret keys in production.

Plugin API changes

• The signal pretix.base.signals.device_info_updated has been added.

REST API changes

• The list of subevents can now be filtered by the is_public parameter.

• An experimental API for rendering ticket PDFs has been added.