Skip to main content
All CollectionsOffer CreationAXS
AXS: How to Import Tickets to Create an Offer
AXS: How to Import Tickets to Create an Offer

Step by step guide to creating an offer by importing tickets

Nicole Preston avatar
Written by Nicole Preston
Updated over a week ago

SETUP

  1. Select (+) New Offer.

  2. Select your organization.

  3. Enter the 'Offer ID'

  4. Click Go.

  5. The system will attempt to match the information from your order to events already built within FEVO Enterprise. If there is no existing event you will be prompted to create the event. 

TICKETS

1. Verify that the tickets that have been imported are correct, then click Next. If more tickets must be added manually, follow these steps:

  • In the box under the Tickets tab, complete all applicable fields.

  • Verify ticket information is correct.

  • Click Add Tickets button.

  • Repeat this process for additional sets of tickets.

  • When done, click Next.

Notes: 

  1. After tickets have been added, edits can be made directly to a ticket in the table by clicking on the field you want to update then entering the update.

  2. You can edit tickets in bulk after they have been added by:

    • Selecting checkboxes in the table for the tickets, rows, sections, areas, or all to edit. 

    • Clicking the Update Prices button above the table.

    • A popup will appear where you can make bulk edits.

    • Clicking Update Prices to Save.

  3. “Payout to Group” is the amount per ticket that will be paid directly to the group through FEVO Enterprise for a fundraiser.

  4. It is possible to add multiple ‘areas’, ‘sections’, ‘rows’, or ‘seats’ at one time by either:

    • Separating multiple ‘areas’, sections’, ‘rows’, or ‘seats’ with a comma

    • If numeric or alphabetically sequential, using a hyphen to indicate sequential ‘areas’, ‘sections’, ‘rows’, or ‘seats’

  5. Be aware, however, that whenever you enter multiples for any of these fields the subsequent information entered will be the same for each of the multiples.
    ​

DEADLINE/SOLD OUT

  1. Set the date and time for the Deadline to purchase tickets (or TBA). This is the point where all sales are final for the group.

  2. If applicable, set the date and time for the On Sale to purchase tickets.

Notes:

  • These are both adjustable at any time to either go on sale earlier/later or to extend the time when buyers are able to purchase.

BUYER OPTIONS

  1. Create any New Add-Ons or Build Add-Ons from a Template (instructions can be found in the Add-Ons Help Article)

  2. Set Landing Quantity Filter - This is the default quantity of tickets that the system is set to search for when a buyer arrives at the offer page. This quantity can be adjusted by the buyer.

  3. Set Minimum Tickets per User - If the buyer is required to purchase a certain amount of tickets in their order, you can set that requirement here. This is optional and you can leave blank if no requirement is needed.

  4. Set Maximum Tickets per User - If you would like to set a limit on the number of tickets a buyer can purchase, you can do so here. This is optional and you can leave blank for no set maximum amount

  5. Set Ticket Selection Interval - This setting requires buyers to purchase tickets in multiples of the number entered. Ex. If "2" is inputted here, buyers would only be able to purchase quantities of 2, 4, 6, etc.

  6. Set your Offer Questions (instructions can be found in the Offer Questions Help Article)

GROUP

If a group leader was pulled with the import:

  1.  Select the applicable group. If no listed group applies, close this box and proceed to step 1 of “If no group leader was pulled with the import” below.

  2. Click Done.

  3. Verify the populated group information is all correct. Make any necessary edits. Then, click the Next button in the top right of the page.

If no group leader was pulled with the import:

  1.  In the field below the Group tab, begin typing the name of the group this offer will belong to.

  2. As you type, you may see two types of quick select options:
    ​

    • Pre-existing groups whose names contain a match to what you are typing. By clicking ‘View group info’ you can view that group’s info in a popup to verify if that is the correct group you would like to use. See step 3. By clicking on a group’s name you have selected that group to use. The group’s information will populate below. See step 4.

    • You will also see the option to create a new group with a name that matches what you have typed into the field. Clicking on this option will create a group with this name. Fields will populate below which will require your attention. See step 5.

  3. Pre-existing group popup: You can either choose to use this group or cancel to select another. If you choose to use this group, this group’s information will populate the underlying group page.

  4. Verify the populated group information is all correct. Make any necessary edits. Then, click the Next button in the top right of the page.

  5. After creating a group, enter the Group Leader’s information in the fields that populate below, then click Next to continue.

DETAILS

  1. Select a “‘Reason for offer’.

  2. If this offer is a fundraiser, select the checkbox to the right of the ‘Reason for offer’ field. You will be prompted with the option to ‘Add payable to address’.

  3. Review the Offer Title field. If you like what you see, leave it. If not, click the lock icon to unlock the field and update the title manually.

  4. Choose a ‘Contact on Ticket Sales Page’. The contact’s information will show on the page where the group’s members order tickets (see image below). This list consists of the sales rep whom the offer belongs to and the group leaders listed for this group.

  5. Offer information is the area where you add any details you want the buyers to know about: Parking information, what they are supposed to wear, pregame fan experience info, discount code info, hyperlinks, etc. You can also add company logos or images into the Offer Image area. This will show on the page where the group’s member order tickets (see image below).

  6. Confirm that the Ticket Delivery Option is correct for the method of how the buyers will receive their tickets. Enter any non-default information to include in the confirmation emails into the Email Fulfillment Options fields.

  7. Set any additional settings (descriptions below)

    • Allow customers to see already purchased tickets

    • Meeting time/location for the group

    • Make offer page public/private

    • Set any offer restrictions to prevent anyone from outside the group to access the ticket inventory

    • Customize the Call to Action Button Copy and Color

    • Set further restriction on type of card to be used at checkout

    • Enable additional settings; insurance, travel options, etc.

  8. At this point you can review the information you have added then click ‘Finish’
    ​

Additional Settings Descriptions

  • ‘Meeting Time’ and ‘Location’ are fields to use to indicate to ticket buyers when and where to meet the group before the event. This shows next to the event time on the page where the group’s members order tickets (see image below).

  • ‘Offer URL’ is the URL to the page where ticket buyers go to order tickets for this offer. We generate a URL based on the group’s name and URL availability. You may edit this URL by clicking the lock icon to unlock the field and making an desired update.

  • ‘Ticket delivery instruction’ is how you inform ticket buyers of how they will receive their tickets. This shows on the checkout page and is selected by the buyer in order for them to proceed with their purchase.

  • ‘Maximum Tickets per User (blank for none)’ - This limits the total number of tickets a user can order over the life of the offer.

  • ‘Offer Question’ is where you ask a mandatory question to ticket purchasers. You can ask an open ended question and allow ticket purchasers to enter in their answer. Or, you can prompt ticket purchasers to answer by choosing an option from a dropdown. The question shows as the very last step while purchasing tickets.

Did this answer your question?