BuyOrder Data Entry

BuyOrder Data Entry

The purpose of these document is to identify the columns/fields necessary to create a Buy Order and their definition or ways for the user to indicate the data to the respective column/field.


The users/agents that process/buys the tickets has a dedicated and consolidated SharePoint file to list all necessary data based from the information gathered in the email (PO information) which are to be processed thru the BuyOrder Script.

 

The columns/fields as from the SharePoint file as follows and their definition:

  • Profile Name (string, required)

    • Profile Name is the buyer name (whole name) indicated in the email or basically the recipient of the confirmation email.

      • The profile name is an alias used or multiple accounts used by agents to buy the tickets which will be basis to reference which agent/user initiated the transaction.

  • Email (string, required)

    • Email or the recipient email.

      • The Email will be used to reference together with Profile Name to pull up the Account associated.

  • Card Last 4 Digits (string, required)

    • Credit Card used in the transaction but showing only the last 4 digits for security reasons.

      • The last 4 digits will be used to reference the Card associated.

  • Event (string, required)

    • Main event

      • Sports event e.g., Home Court

      • Performance event e.g., main performer

  • Opponent (string, optional)

    • Secondary event

      • Sports event e.g., Guest Challenger

      • Performance event e.g., secondary/filler performer

  • Venue (string, required)

    • Venue of the event.

  • Date (string, required)

    • Date of the event. <yyyy-mm-dd 00:00:00>

  • Time (string, required)

    • Time of the event. <1900-01-01 hh:mm:ss>

      • if not indicated, use 03:00:00 for hh:mm:ss then set TBA to 1.

  • TBA (integer, 0/1)

    • 0 - where time of the event is indicated

    • 1 - where time of the event isn’t indicated

  • Shipping Method (string, selection)

    • Delivery/shipping method

      • Flash Seats - referenced for AXS: (refer keywords below)

        • AXS Mobile ID

        • AXS Digital Tickets

        • Paperless

      • Mobile Entry - mentions your phone being the ticket: (refer keywords below)

        • XFER

        • Mobile

        • Tickets will be available via the APP

        • Manage Tickets

      • Mobile QR - where the QR codes are used for tickets: (refer keywords below)

        • email will contain a link to your Mobile tickets

        • Apple Wallet

      • TicketFast - mentions about printing the tickets: (refer keywords below)

        • Print at home

        • E-Delivery

        • Email me my Tickets

        • Tickets Sent Via Email

        • PDF

        • Eticket

      • US Mail - physical ticket delivery: (refer keywords below)

        • U.S. Mail

        • Ships to

        • Shipping Address

  • Quantity (integer, required)

    • Ticket quantity

  • Section (string, required)

    • Seating section location.

      • For General Admission, set value to GA.

  • Row (string, required)

    • Seating row location.

      • For General Admission, set value to GA.

  • Start Seat (integer, required)

    • Start seating location

      • Use numerical representation if ticket information used Letters, e.g. A = 1, B = 2, C = 3, so on and so forth.

      • For General Admissions, random number, as long it doesn’t duplicate another event’s seating with the same event date and time.

  • End Seat (integer with equation)

    • End seating location

      • If Consecutive is 1, n = Start Seat + (Quantity - 1)

      • If Consecutive is 0, n = Start Seat + ((Quantity - 1) * 2)

  • Total Cost (required)

    • Total cost of the ticket

  • Confirmation Number (required)

    • Confirmation number of the purchase.

  • Consecutive (integer, 0 / 1)

    • 0 - seating is not consecutive or skipped/apart

      • Indicating the seating location, e.g. 2 and 6.

    • 1 - seating is consecutive or side-by-side

      • Indicating the seating location, e.g. 2 to 4.

      • For General Admission Seatings.

  • Internal Note (selection, optional)

    • How the ticket(s) will be bought:

      • NOSINGLES - by bulk or group. For Non-General Admissions.

      • ANYSPLITS - single or can be separate. For General Admissions

  • External Note (optional)

    • Note for (display) Customer.

  • PO Note (optional)

    • Note by Eibo Agent.

 

Additional Notes:

  • For Ticket Evolution, to identify the Account and Card used with email - tboatcore@gmail.com:

    • Account is “Ticket Evolution” as default (when creating the buy order entry) or better to use the client id 60876 (when creating the buy order insert.)

    • Card is “Accounts Payable” as default.

JSON Format as parameter to pass. { "profileName": "", "email": "", "cardLast4Digits": "", "eventName": "", "opponentName": "", "venueName": "", "date": "", "time": "", "tba": false, "shippingMethod": "", "quantity": 0, "section": "", "row": "", "startSeat": 0, "endSeat": 0, "totalCost": 0, "confirmationNumber": "", "consecutive": false, "internalNote": "", "externalNote": "", "poNote": "" }

Change History

Change History

Version

Content(s)

Publisher

1.0

Buy Order Entry

Thom Gamboa

1.1

  • Changed the fields needed for automated entry and their description:

  1. Username to Profile Name.

  2. Account to Email.

  3. Card to Card Last 4 Digits

 

  • Added reference for Shipping Method on how to identify them.

    • TODO: I need input for Shipping Method: US Mail.

  • Updated json format.



Thom Gamboa

1.2

  • Shipping Method: US Mail description.

  • TBA and Consecutive as integer.

Thom Gamboa

1.3

  • Updated Event default time if not indicated then set TBA = 1.

  • Start seating use of numerical representation.

    • For General Admission seating details

    • Internal, External, and PO note to Optional.

      • Internal Note

        • For General Admissions, set to ANYSPLITS

        • For Non-General Admissions, set to NOSINGLes

Thom Gamboa

1.4

  • Consecutive to 1 for General Admission Seatings.

Thom Gamboa

1.5

  • Added references for Shipping Methods such as exact word(s) or phrases to further identify specific method used.

  • Added Additional Notes for specific rules set practiced in the manual process or default values for case scenarios.

Thom Gamboa

Related content