Skip to main content
All CollectionsCommerceEvents
Importing event tickets
Importing event tickets

How to bulk add event tickets by importing a spreadsheet of ticket data.

Callum McFadgen avatar
Written by Callum McFadgen
Updated over a week ago

How does importing event tickets work?

Our import feature allows you to bulk add event tickets by uploading a Microsoft Excel spreadsheet that contains a single sheet of ticket data structured into specific columns.

As part of this process, new people and organisations can also be added to match the ticket data provided.

How do I bulk add event tickets?

  1. Go to Commerce > Events.

  2. Click on Events in the left hand menu.

  3. Search for the relevant event and click on it.

  4. Click the Tickets tab under the event heading.

  5. Click the Import button in the upper right.

  6. A help box will tell you how to structure your spreadsheet columns correctly, see How do I structure my spreadsheet columns?

  7. Once you've structured your spreadsheet columns, add the ticket data , see What data do I provide when adding event tickets?

  8. Once you've added your data, click the Choose File button to open a File Explorer window and select the spreadsheet from your computer.

  9. Click the Import button.

If there have been any issues with your data, an error message will be displayed with the row number and issue. Make the relevant changes to your spreadsheet then repeat the process above from step 6.

How do I structure my spreadsheet columns?

The spreadsheet must be of the .xlsx file type and only contain one sheet, any additional sheets will be ignored.

The first row of the spreadsheet must list the column headings in separate columns, see What are the columns for adding event tickets? for the supported headings. All column headings should be in uppercase.

An easy option for structuring a spreadsheet is to first export your event tickets, this will download a spreadsheet that is the correct file type (.xlsx) and already has most of the columns that are used for adding. You can then use the downloaded spreadsheet as a template.

If your spreadsheet contains any columns that are not supported then those columns and their data will be ignored but if you wish to remove any columns, simply delete them from the spreadsheet.

You can add additional columns to the spreadsheet by adding a new column and entering a supported column heading into the first row of the new column. If you wish to remove any columns, simply delete them from the spreadsheet.

What are the columns for adding event tickets?

When adding tickets, the TICKET_TYPE_TITLE, PERSON_FIRST_NAME, PERSON_LAST_NAME and PERSON_EMAIL_ADDRESS are required, all other columns are optional. The supported columns are as follows:

  • TICKET_TYPE_TITLE

  • PERSON_FIRST_NAME

  • PERSON_LAST_NAME

  • PERSON_EMAIL_ADDRESS

  • PERSON_ORGANISATION_TITLE

What data do I provide when adding event tickets?

When adding tickets using the import feature, it is important that the ticket data you provide meets certain guidelines to avoid any issues. The guidelines are as follows:

  • Each row of your spreadsheet is read as a single ticket.

  • TICKET_TYPE_TITLE - must be provided and reference an existing event ticket type title.

  • PERSON_FIRST_NAME - must be provided and cannot exceed 50 characters.*

  • PERSON_LAST_NAME - must be provided and cannot exceed 50 characters.*

  • PERSON_EMAIL_ADDRESS - must be provided, be a valid email address and cannot exceed 320 characters.*

  • PERSON_ORGANISATION_TITLE - cannot exceed 100 characters.**

* If no people exist with the same first name, last name and default email address then a new person is added using the PERSON_FIRST_NAME, PERSON_LAST_NAME and PERSON_EMAIL_ADDRESS.

** If the person exists and they already have an organisation, then the persons organisation will remain unchanged to avoid any issues with persons data becoming corrupted. If the person does not exist or does not have an organisation and no organisation exists with the same title then a new organisation is added using the PERSON_ORGANISATION_TITLE.

Did this answer your question?