Updated: 18 May 2026 for Release v230
Quick overview of core features
(Discover quick explanations of all features in our general features overview)
Automated data synchronisations
✅ Event & production content updater ✅ Automated OnSale planning based on MOS (Mode of Sale) per event ✅ Event availability checker (v16, v15 coming soon) ✅ Event prices updater ✅ Automated “Buy Tickets” url generation per event on marketing website
🗓️ planned: Data import: Sales data (for automated service mailings, etc) 💡 Potential next step: Opt-in sync
Account integration options (Tessitura v16 only)
✅ SSO (log-in & sign-up via TNEW) ✅ Obtain visitor tags of visitor after login for personal content ✅ My account: Wishlist
Purchase path integration options (Tessitura v15 & v16)
✅ Integrated TNEW Purchase path ✅ Smart & quick TNEW branding & styling solutions
💡 Potential next step: Integrated Peppered purchase path
Glossary
CultureSuite CMS | Tessitura |
Production | Production Season |
Event | Performance |
Visitor | Constituent |
Genre | Keywords |
Visitor Tags | Constituencies |
Release updates
Wishlist icons now visible when logged in via SSO (v230 - May 2026)
What changed?
- Wishlist icons now appear for visitors logged in via single sign-on (SSO) on Tessitura sites (v16+).
- When a visitor is not logged in, wishlist icons are hidden until a new redirect mechanism is in place to handle SSO login correctly. This is coming in a future release.
How do I use it?
- No action needed. This is live automatically for venues using Tessitura SSO.
Tessitura price updater now supports v15 (v230 - May 2026)
What changed?
- The price updater previously released for Tessitura v16 now also works for venues running Tessitura v15.
- It looks at all available Modes of Sale (MOS) configured for display on the website, and combines all price levels to create a single final amount per ticket per price type.
How do I use it?
- No action needed if you are already using the price updater. Contact your Customer Success team if you would like to get set up.
Thank you to Theatre Royal & Royal Concert Hall for your support with this feature!
Create Groups based on MOS (v229 - May 2026)
What changed?
- We now automatically create Groups using MOS (Mode of Sale) start dates, making it easier to organise and target communications around specific performance dates.
How do I use it?
- Contact us to activate this feature for your organisation
- Groups are created automatically using the MOS start date (e.g., "Dec-15-2025 10:00") as the group name for all events with that date.
- Find these groups in your Dashboard to build targeted campaigns.
Thank you to Ticket Omaha for sponsoring this feature!
Smart pricing imports, scheduled daily (v227 - March 2026)
What changed?
- New price updater for Tessitura v16 imports prices for a specific Mode of Sale (MOS)
- Can be scheduled to run automatically every day
- Can also be triggered manually whenever you need a fresh update
How do I use it?
- Contact our Customer Success team to configure the Mode of Sale you would like to use and set up your daily schedule.
- Import manually whenever you need it
Import Event Level information into the Side note field (v224 - January 2026)
What changed?
- The Tessitura updater can now import Event Level information into the Side note field, giving you more control over what details appear on your event pages.
How do I use it?
- Contact us to activate this feature for your organisation – we'll enable the import in your Tessitura integration settings.
Thank you to Theatre Royal & Royal Concert Hall, Nottingham for sponsoring this feature!
Import Tessitura Fulltext as event descriptions (v221 - October 2025)
What changed?
- The Tessitura updater can now import the "Fulltext" field to use as your event description, giving you more flexibility in how you display event information on your website.
How do I use it?
- Contact us to activate this feature for your organisation – we'll enable the Fulltext import in your Tessitura integration settings.
Thank you to Ticket Omaha for sponsoring this feature!
Single Sign On (Shared Sessions) improvements (v218 - September 2025)
What changed?
- Correctly display the user account options in mobile menu foldout for sites with a single sign-on
Remove Visitor tags from Peppered accounts when they are expired (v213 - June 2025)
What changed?
- When a Consituency Code has expired in Tessitura the corresponding Visitor Tag in Pepered will be removed from the Visitors Peppered Record.
How to I use it?
- No action needed - already added to your site.
Added Genres & Keywords support to Tessitura event updater (v212 - May 2025)
What changed?
- For Consortiums like Leeds Museums & Galleries and Leeds Film, both using the same Tessitura environment, we added the option to filter events by Keyword in the Event updater.
- This ensures Productions are only imported to the correct website, saving valuable time for the Leeds Team.
How do I use it?
- Contact us to activate this feature for your organisation
Sign Sign On (Shared Sessions) improvements (v210 - March 2025)
What changed?
- New "sync account" button on Peppered SSO account in case a visitor logged into TNEW with a different account than the account stored on the Peppered website.
TNEW Template Improvements (v204 - November 2024)
What changed?
- Favicon added to the TNEW purchase path
- Dynamic content alignment on confirmation page
- Our order pages when printed were adding really long URLS - this has been resolved
- Fixed v16 alignment issues around Ticket Type selection
- Removed the static login link in the header on TNEW pages (this link is only used on the marketing website to link to the TNEW pages)
How to I use it?
- No action needed - already added to your site.
Tessitura Availability Updater (v201 - September 2024)
What changed?
- Information about event availability automatically added to the Peppered platform on a regular basis to check if an event is (still) on sale or sold out.
- Booking Buttons automatically updated to reflect true availability.
How do I use it?
- In the Control Panel set which event statuses should be updated by this process, and which statuses should be left alone
Related articles