Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Organizers currently manage ticket resale through organizer settings and transfer rules, which display the "Resell your ticket" button, even when no active resale platform is available on the S-360 side. To streamline on-site operations and align with the new "Ticket Exchange" feature, we are pleased to simplify the management of Resale configurations. This enhancement not only improves the user experience for organizers but also for spectators, ensuring a consistent and efficient process.

...

Notes: All sales configurations—including catalog, tariffs, seat categories, contingents, and sales periods—will continue to be managed directly in S-360.

How to activate the Ticket

...

Resale feature ?

Enable the S-360 Ticket Resale feature from the organizer settings

From the Application Settings, enable the feature Ticket resale via S-360 ticketshop (key: enable-resale-ticket-shop-s360)

...

Expand
titleClick here to see the new parameters in the Ticket Rules

image-2024-10-3_13-9-20.png

Wallet behavior

Posting on Resale > User flow

to initiate Resale exchangeticket


My Tickets

Ticket detailsTicket actionsResale confirmation Confirmation popupWebview

Step

Navigate to your event and find the ticket you want to exchange

Select the ticket you want to resell

Scroll to reveal possible ticket actions (main button or floating action button) 

Tap the "ReseetResell" button.

Once confirmed, spectator is redirected to the ticketshop on the Exchange Post on Resale screen (if configured accordingly)

Screen

Image Modified Image Modified

Image RemovedImage Added

ChangesNone

None 

None.
Same b
utton "Resale on ticket shop".

New popup "Resell this ticket" including :

  • a title and a description/message
  • a button to proceed with the resale
  • a button to abandon the resale
New title for the Webview Screen "Ticket shop"
Crowdin labelN/AN/A
  • Button
  • resale_
  • ts_fab_title
  • Title → confirm_resale_ticket_dialog_title
  • Message → confirm_resale_ticket_dialog_msg
  • Button to proceed → confirm_resale_ticket_dialog_button_01
  • Button to abandon → confirm_resale_ticket_dialog_button_02
  • Webview Title → resale_ticketshop_webview_title

Removing from  Resale > User flow


Burger Menu > Ticket returned for Resale

List of tickets open for resaleTicket actionConfirmation popupWebview

Step

Navigate to the Resale screen and find the ticket you want to removed from resale

Tap the name of the event

Select the ticket(s) you want to remove from resale

Tap the "Cancel resale" button.

Once confirmed, spectator is redirected to the ticketshop on the Post on Resale screen (if configured accordingly)

Screen


Image Added

Image Added

Image Added

Image Added

ChangesNone

None 

None.
Same button "Cancel resale".

New popup "Cancel ticket

_exchange

resale" including :

  • a title and a description/message
  • a button to proceed with the resale
  • a button to abandon the resale
New title for the Webview Screen "Ticket shop"
Crowdin labelN/AN/A
  • Button → resale_cancel_button
  • Title → resale_cancel_confirm_title
  • Message → resale_cancel_confirm_msg
  • Button to proceed → resale_cancel_confirm_button_01
  • Button to abandon → resale_cancel_confirm_button_02
  • Webview Title → resale_ticketshop_webview_title

Resell Button visibility

“Resell” button visibility is determined by specific rules that define which spectators can initiate a Ticket Reale, as outlined in the table below:

...

Redirection to the ticketshop

Event configuration at injection

By default, the S-360 Ticketshop Resale URLs specified at the event level will be used to redirect spectators to the ticketshop :

Ticket override at injection

However, you can override this URL on a per-ticket basis by modifying the S-360 injection template and utilizing hidden ticket details metadata. 
To set this up, apply the following configuration in your S-360 injection template:


Info

TIXNGO differentiates how URLs are managed based on their entry points: ticketDetails.hidden and event.metadata.

  • When both fields are available, ticketDetails.hidden takes precedence.
  • Using event.metadata applies URLs uniformly to all tickets of an event and allows for easy updates via the "Edit Event" screen under the "S-360 Integration" tab.
  • Conversely, ticketDetails.hidden is ideal for assigning distinct URLs to different ticket categories, types, locations, or currencies. However, since it operates at the ticket level, bulk updates across all tickets are not feasible.


Limitations

Spectator must be the ticket S-360 Cultural Contact to perform a Ticket Resale

...