Complete and Submit a Ticket Inventory Load Sheet
The TicketOS load sheet is used to provide inventory details so tickets can be accurately reflected within the platform. Completing the load sheet with as much information as possible helps ensure inventory is loaded correctly and made available to the appropriate users. This article explains each field on the load sheet and how it should be completed.
Overview
A load sheet contains all of the information needed to configure ticket inventory, distribution rules, visibility settings, and delivery details. While some fields are optional, providing complete and accurate information helps reduce delays and ensures tickets appear correctly within TicketOS.
Step-by-Step InstructionsComplete Event Information
Provide the basic event details for the inventory being loaded:
Team/Performer
Enter the team, performer, or event associated with the inventory. If inventory applies to all events at a venue, enter ALL.
Venue
Enter the venue where the event takes place.
Date Range
If inventory is for a specific event date, provide the event date. If inventory applies to all dates, enter ALL. For events with multiple show times on the same day, specify the applicable show time or enter ALL Times.
Define Ticket Information
Complete the ticket details for each inventory line.
Ticket Type
Select the appropriate ticket type. Available options include:
- Physical
- E-ticket
- Tickets.com
- TM Mobile
- AXS Mobile
- MLB Ballpark
- SeatGeek
This information helps determine how tickets will be delivered. If you are unsure, the field may be left blank for review.
Ticket Category
Specify the inventory category. Common categories include:
- Suite
- Club
- Stadium
- Standing Room Only – Suite
- Guest Pass
- Parking Pass
Additional categories can be requested if needed for reporting purposes.
Enter Seating Information
Provide location details for the tickets.
Level, Section, and Row
Enter the seating location information. For example:
- Level: Club
- Section: 124
- Row: 1
If seating information is not yet available, enter TBD.
Seat Start, Seat End, and Quantity
Enter the starting seat number, ending seat number, and total quantity of tickets available.
Include Parking Information
If parking passes are included with the inventory, enter the quantity in the Parking Passes field.
If no parking is included, enter 0.
If parking should be managed separately from tickets, list it as a separate line item on the load sheet.
Enter Pricing Information
Face Value
Represents the actual value of the ticket and is generally visible only to administrators.
Charge Price
Represents the amount users will see and may be charged when placing an order.
If pricing is not needed, both fields may be entered as $0.
Configure Resale Settings
Use the Resale field to indicate whether tickets should be eligible for resale if they remain unused before an event.
Specify Distribution Settings
The Distribute To field determines how inventory should be handled once loaded.
Ticket Coordinator Distribution
Enter a specific individual's name if tickets should be assigned to a coordinator for future distribution.
Waitlist Distribution
Enter Waitlist if tickets should be posted for requests and routed through an approval process. Include the name of the person responsible for approving or denying requests.
Public Distribution
Enter Public if tickets should be made available through the standard request process with manager approval routing.
Undistributed Inventory
Enter Undistributed if inventory should remain hidden and no action should be taken yet.
Define Visibility Rules
If inventory is distributed through Public or Waitlist, specify who should be able to see the tickets.
Examples include:
- All Employees
- Department
- Job Title
- State
- Other eligibility criteria
Visibility settings help ensure inventory is available only to the intended audience.
Allocate Inventory to a Specific User
Use the Allocate To field only when tickets should be assigned directly to a specific employee for order completion. Enter the employee's name in this field.
Provide Ticket Account Information
If ticket transfers will be managed using a ticket account, complete the following fields:
- Username
- Password
- Online URL
This information identifies where the inventory is housed and how it can be accessed.
Add Special Instructions
Use the Notes field for any special instructions or additional details related to the inventory. If there are no special requirements, this field may be left blank.
What Happens NextOnce the completed load sheet is submitted, the inventory can be reviewed and configured within TicketOS. The information provided determines how tickets appear, who can access them, how they are distributed, and whether additional actions such as approvals or allocations are required.
Common Issues
Seating information is not available yet
Enter TBD for the seating location fields. Seating details can be updated later when available.
Unsure which ticket type to select
Leave the field blank and provide any available details about the inventory.
Parking should be managed separately
List parking as its own line item instead of attaching it to ticket inventory.
Inventory should not be visible yet
Use Undistributed in the Distribute To field so tickets remain hidden until they are ready to be released.
Important Notes
- Complete as many fields as possible to help ensure inventory is loaded accurately.
- Enter ALL when inventory applies to all events or dates within a venue.
- Enter TBD when seating information is not yet available.
- Use visibility settings to control which employees can view inventory.
- Use Undistributed if tickets should remain hidden until a later date.
- The Notes field can be used to communicate any special requirements.