Ticket Purchase and Management website
Examples: [url removed, login to view] [url removed, login to view] [url removed, login to view] [url removed, login to view] [url removed, login to view]
Description: This website will serve as a ticket management resource for colleges, universities and school systems. Letting people buy, sell, tickets. Allow client venues operators to track a ticket and find out who will have the ticket and what seat they will be using. Let venue operators manage ticket resells.
The website will serve its clients by providing customized front ends to allow client users to do the following:
• Purchase tickets – Customers
• Sell and Buy tickets
Design: Following the layout of Viagogo [url removed, login to view] with different style sheets and color scheme. The database will be hosted on a MySQL database server to manage the website.
Master Admin – The Master Admin Account will have total control over the site and database. This account will manage all Venue and User settings. It will have the ability to add, edit, & delete venue and user accounts. It will also be able to manage the marketplace for buying, selling, and transferring tickets. It will be able to manage all purchases and seat assignments.
Venue Admin – Venue admin accounts will be setup via the master Admin Account. The venue administrator account will have total control of their venue. Venue administrator accounts will have the ability to assign as many restrictive sub accounts to manage the selling of tickets. Venues have the ability to offer tickets for sale, they can also facilitate ticket transfers, cancellations, and reimbursements using online or onsite transactions. Venues will be able to view the status of ticket
Venue Manager – This is a sub account of the Venue Admin with restrictions as assigned by the venue administrator. The purpose of this account is to allow multiple employees of a venue to manage ticket sales for events.
User Account - The user account will consist of collecting the user’s general information. The user will have the ability to edit or delete their own account. This account can sell, purchase, or transfer tickets using the marketplace module of the website.
Ticket Search / Event Locator – All site visitors can view the ticket search and event locator module. This module will follow the layout on [url removed, login to view] ([url removed, login to view];eo=1&ss=0), but must have a different look. The Event, Date/Time, Venue & Location, and Price Range per ticket should all be displayed.
Buying Tickets – Only members will be able to purchase tickets or place bids for tickets. When an event is found and a visitor clicks on the link, they will have the option to buy the ticket at a price set by the venue or member selling the ticket. They will also have the option to place a bid for the ticket.
Selling Tickets – Only members and venues will be able to sell tickets on the website. When adding their ticket to the system, they will provide The Event, Date/Time, Venue & Location, buy Now price, and starting bid price for the ticket. They will also need to provide seat information within the venue. This will allow users and venues to set their prices based on the location of the seats. Users can even upload two images to allow ticket users to see the layout of the venue and identify where they will be seated for the event. Once the ticket is sold, the seller (member or venue) will receive an optional email notification of the purchase.
Transferring Tickets – Ticket transfers are performed between members. If a ticket to an event is originally purchased through the website, members can transfer those tickets to another account. The receiving will need to be a member in order to receive the transfer.
Ticket Printout: We would like to implement a ticketing bar code system for buyer’s members with transferred tickets. Credit Card information can be used as verification of ownership of the ticket. We would also like to use a plastic strip with a bar code to manage ticket ownership. We will provide the format of the printouts and the layout of the tags. The database will manage the tickets assigned to the customer account associated with the bar code.
Sub-domain Creation and Management (Master Admin Account)
Venues may request to customize the site in order to integrate the website into their organization’s existing website. The Master Admin will need to have the ability to create sub-domains along with the ability to edit style sheets to match color schemes of venues. The database will only display events associated with that specific venue. The Master Admin will also need to be able to allow those same events to be listed on the main site via the database.
Example links: paperless ticket system
[url removed, login to view]
We are looking for suggestions from the programming team. Please provide suggestions or recommendations.