...

1. Create a secondary TIXNGO Shipment method that will prevent the automatic injection of the Tickets to TIXNGO but will allow the barcodes to be generated. This should be a new Shipment Mode called “Mobile – External (Away)” of the type “Blockchain” and allocate to the back office sales channel.
   
   
2. Process the Away Ticket sales within the S-360 environment to generate the barcodes/tickets for the away team ensuring the shipment mode selected is the “Mobile – External (Away)” shipment mode created in Step 1. We'd suggest making multiple files for the sale instead of 1 giant order as it will make amending post-match for reconciliation purposes much easier. The files could be against an "Away Ticket" contact or the name of the Away Club.
   We would recommend that all tickets for the away team are sold in a specific “Away Team” seat category or held within a specific contingent. This will be used in a later step to aid with ticket design.
   
   Note, any setup specifically for Access Control should be completed prior to starting the sales process.
   
   
3. Following the completion of all orders, you should provide details of the seats available to the Away team to sell including details of the Block, Row and Seat so they can build the seating map within their ticketing system.
4. The data in step 3 should be accompanied by an excel spreadsheet that includes the seating information, barcode or ticket ID relating to the seat along with space for them to enter the first name, last name and email address of the supporter. We can also add optional fields to add such as supporter number if they wish to display this on the ticket.
   
   An example of the exported data to share with the away team is below. Note, First name, Last name, email address and supporter number would all be blank at the time of sharing with the club.
   
   INSERT EXAMPLE OF THE TICKETING SALES DOCAn example of the file structure to provide to the away team is below. 
   

   View file
   name Using TIXNGO for Away Supporters traveling to Client stadium.xlsx height 250

   
   
   
5. The away team sell the tickets in their usual format and provide you with an updated copy of the extracted data which includes the original information shared (Ticket ID, Barcode, Turnstile, Area, Block, Row and Seat Number) along with the completed information of ticket type, first name, last name, email address and supporter number of the ticket holder.
   
   Note. It is these details that will be used to distribute the TIXNGO Tickets to the ticket holder and so the file should only be provided back to the Home Team once all tickets have been sold.
   
   
6. Once the data has been returned from the Away Team, this information needs to be added into a TIXNGO CSV ticket upload document and manipulated to add in the items for ticket information and ticket design. This hybrid file is a combination of the exported list of tickets (and barcodes) along with the sales information provided back by the away team. This file will include barcode, ticket holder email address & name, seat details (to show on the ticket), any imagery and transfer rules.
   
   
7. This file should include all the following details:
   1. Ticket ID (From Secutix)
   2. Barcode (From Secutix) – This must match the barcode generated from Secutix otherwise access control could fail.
   3. Seating Details (From Secutix)
   4. Turnstile Information
   5. Event Information such as name, ID, date and time.
   6. Ticket Imagery (event image, sponsor, seat map, prohibited items plus icon if required)
   7. Ticket Colours (Banners and Secure Colours)
   8. Ticket Holder Email (From other team)
   9. Ticket Holder First and Last Name (From other team)
   10. Transfer Rules
       
       
8. An example injection file format can be found below:
   

   View file
   name Base TIXNGO Ticket Injection File.csv height 250

   
   
   
9. Follow the standard CSV Injection process described on the link below: https://confluence.secutix.com/display/TIXNGO/CSV+Injection
   
   NOTE. It’s worth injecting a test file initially to confirm event information, file formatting and ticket design.
   
   
10. Once tickets have been injected to TIXNGO, fans will start to receive their tickets via the app.

...

Using TIXNGO for YOUR Fans traveling to AWAY Stadium

Option 1

1. Configure the seating layout of the away stadium within the S-360 platform and build the match with each of the different categories and prices required.
2. Sell the away tickets directly to the your fans within S-360 ensuring that users are allocated seats according to the plans shared by the opposition team. The TIXNGO Shipment mode should be used for all tickets purchased to allow them to be injected to your TIXNGO Branded Wallet. 
3. Tickets are injected into TIXNGO using the standard S-360 to TIXNGO interface. A separate template could be used for away matches compared to your home matches to alter the ticket details, imagery, and colours specifically for the away tickets to ensure they are easily identifiable at the venue.
4. Run a list of tickets report for the match ensuring all tickets that will be distributed via TIXNGO are included. The report should include the ticket barcode, ticket number, seating details (Area, Block, Row, Seat) and ticket beneficiary.
5. Once the report has ran, export this data to Excel and share with the opposition ticketing manager. 
6. The ticket manager of the opposition (home team) can import the barcodes into their access control system to ensure the TIXNGO tickets can gain entry successfully. 
7. Tickets are delivered to your fans who have travelled to the away venue via your TIXNGO Branded Wallet.
8. Fans enter the venue using their activated tickets (Based on time or proximity to the venue).

Note

To use this method, an agreement would need to be in place with the away club as they will need to import external barcodes into their access control system.

Be careful if opening exported data in Excel as the format of barcode numbers can be altered by cell formatting which would cause their to be a difference between the barcode in TIXNGO and the barcode imported to Access Control. 

Option 2

1. Configure the seating layout of the away stadium within the S-360 platform and build the match with each of the different categories and prices required.
2. From the Home Team (opposition) you'll need to request a file containing the ticket information ready for your injection. This should include (as a minimum) the following details:
   1. Ticket Number
   2. Barcode
   3. Entrance
   4. Stand
   5. Area or Block
   6. Row
   7. Seat
      
      Image Added
      
      
3. Sell the away tickets directly to the your fans within S-360 ensuring that users are allocated seats according to the plans shared by the opposition team. A secondary TIXNGO Shipment mode should be used for all tickets purchased to ensure they aren't injected to TIXNGO via the usual S-360 to TIXNGO interface.
   
   
4. Once all tickets have been sold for the match, you'll need to run a "list of seats" report that includes the following columns. Once ran, export the results as this will be used to match to the barcodes provided by the opposition in the first file. 
   1. Area
   2. Block
   3. Row
   4. Seat
   5. File Number
   6. Cultural Contact Number
   7. Cultural Contact Email
   8. Cultural Contact Name
   9. Tariff
      
      Image Added
      Note. You may need to delete rows relating to unsold seats if you didn't sell out the allocation. 
      
      
5. Combine the exported seat details with the ticket file provided by the opposition club to create a single file that links the correct barcode, seat and contact who will need to receive the ticket. 
6. Within your new file, separate the cultural contact name into a first name and last name field. 
   
   Image Added
7. Next we need to prepare our file in the correct format for importing to TIXNGO ensuring we include all mandatory fields. The most widely used fields for this purpose are below: 
   1. activationParameters.method
   2. activationParameters.time
   3. image
   4. event.id
   5. event.group.image
   6. event.address.site
   7. event.address.line1
   8. event.address.city
   9. event.address.countryCode
   10. event.address.zip
   11. event.website
   12. event.name
   13. event.startTime
   14. event.metadata
   15. purchaseDetails.price
   16. purchaseDetails.currency
   17. purchaseDetails.date
   18. purchaseDetails.priceCategory
   19. ticketDetails.main
   20. ticketDetails.extra
   21. ticketDetails.hidden
   22. purchaseDetails.taxationNumber
   23. security.barcode
   24. spectatorDetails.email
   25. spectatorDetails.firstName
   26. spectatorDetails.lastName
   27. ticketId
   28. mobileAppId
   29. transferRules.allowTransfer
   30. transferRules.allowTransferAfterActivation
   31. transferRules.maxNumberOfTransferPerTicketInGroupId
   32. design.id
   33. design.backgroundColor
       
       An example finished file can be found further down this document. 
       
       

8. Note that "ticketDetails.main" can be tricky to get into the correct format as it includes the seating details within a single field plus the required formatting. An example of the format is below:

   [{"key": "Entrance", "value": "Gate 7"},{"key": "Stand", "value": "OESTE"},{"key": "Block", "value": "S4"},{"key": "Row", "value": "B"},{"key": "Seat", "value": "1},{"key": "Tariff", "value": "Away Supporters"},{"key": "Competition", "value": "International Friendly"}]

   One method of producing the correct format is by splitting the elements into separate columns and using a concatenation, for example, add in columns in-between the variable elements and then in your "ticketDetails.main" field, use a formula such as =CONCATENATE(S2;T2;U2;V2;W2;X2;Y2;Z2;AA2;AB2;AC2). Once you've done this, copy the "ticketDetails.main" field that includes the formula and paste the values, this will leave you with the required formatting. The same approach can be taken for "ticketDetails.extra" and "ticketDetails.hidden". For Example:

   	Entrance		Stand		Area		Row	Column1	Seat	Column2	ticketDetails.main
   [{"key": "Entrance", "value": "	Gate 7	"},{"key": "Stand", "value": "	OESTE	"},{"key": "Block", "value": "	S4	"},{"key": "Row", "value": "	B	"},{"key": "Seat", "value": "	1	},{"key": "Tariff", "value": "Away Supporters"},{"key": "Competition", "value": "International Friendly"}]	=CONCATENATE(S2;T2;U2;V2;W2;X2;Y2;Z2;AA2;AB2;AC2)

   
   

9. Your file format should match that described in the TIXNGO CSV Injection documentation: CSV Injection. Once you're happy with the formatting, save the file as a semi colon delimited CSV file. An example file can be found below:
   

   View file
   name GFA-SeatDetails-S3-S42 - Event Creation.csv height 250

   
   
   
10. Go to the TIXNGO Back Office and navigate to CSV Injection
    1. Choose the file to upload and then press submit.
       Image Added
    2. After a few minutes, refresh the page and check if the import was successful or if it failed. This is shown in the status field next to the file name.
       Image Added
    3. Check the import status by downloading the output file, if it failed, this file will detail the reason. 
    4. If required, amend your file, resave and reupload. If doing this, be sure to edit in a text editor (NOT EXCEL) to avoid the barcodes being malformed. 
11. Once the file has imported successfully, tickets will be available in TIXNGO ready for the fans to travel to the away venue.

NOTES

It’s worth injecting a test file initially to confirm event information, file formatting and ticket design.

Be careful if opening exported data in Excel as the format of barcode numbers can be altered by cell formatting which would cause their to be a difference between the imported barcode in TIXNGO and the barcode in Access Control.