Loaded tickets allow you to link spending value directly to TicketReturn barcodes. The TicketReturn integration provides automated data through its specialized feed.
TicketReturn passes specific value data directly to FanMaker.
Data Ingestion: The TicketReturn feed includes two distinct columns: Price (the ticket cost) and Loaded Value (the spending amount).
Automatic Activation: If barcodes are configured correctly in the TicketReturn system and received through the feed, they will automatically work at the POS within the defined event window.
Internal Mapping: While value is passed automatically, you still configure loaded ticket types in Fanmaker to manage specific use case reporting and apply any optional restrictions.
Location: Point of Sale > Loaded Tickets > TicketReturn
The dashboard displays real-time data based on the TicketReturn feed. It loads automatically to today's date, but you can use the date selector to view past or present data.
Displayed Data:
Valid Barcodes: Total number of barcodes for the selected day.
Total Value: Total dollar value on those barcodes.
Total Spent: Amount spent from loaded ticket barcodes.
Total Available: Remaining balance that has not been spent.
Barcode Spent Chart: During and after the game, a chart shows the number of transactions over time to illustrate how the barcodes were spent.
Loaded Ticket Type Table: Below the chart, a table lists each loaded ticket type with columns for Barcodes, Value, Spent, and Balance. Click View Barcodes next to any loaded ticket type to see the individual barcode details for that type.
Optional Setup: With TicketReturn, it is not necessary to create a loaded ticket type for the tickets to work for the assigned dollar amount. Value is passed automatically through the TicketReturn feed.
Benefits: Adding a loaded ticket type enables better reporting and classification of different ticket types, and allows for the addition of restrictions.
Steps to Add a Loaded Ticket Type:
Navigate to Point of Sale > Loaded Tickets > TicketReturn.
Click Add Loaded Ticket Type.
Fill in the required fields:
Name: Internal display name for reporting (e.g., Meal Deal).
AV Amount: Must match the TicketReturn loaded value amount exactly. It must be unique to distinguish different ticket types, even if they are close in value.
Description: Optional field to provide additional details for your own reference.
Default Point of Sale: Loaded tickets work on every connected point of sale system (e.g., concessions, merchandise, walk-in/walk-out). You can restrict a ticket type to a specific point of sale if needed.
Default Behavior: A loaded ticket will apply for its dollar value across all eligible transactions.
Custom Restrictions:
Allow Restriction: Set the ticket to only work if a specific SKU (e.g., a particular meal deal) is in the cart.
Block Restriction: Specify SKUs that the ticket cannot be applied to (e.g., alcohol).
You can enter restrictions by:
Typing an exact SKU.
Entering a SKU category or SKU group as set up in the settings panel.
Value availability is strictly controlled by the timing parameters set within the TicketReturn system.
Activation Window: Loaded value is only active between the Gate Open and Gate Closed times configured for the event.
While creating loaded ticket types in TicketReturn is optional, doing so provides better reporting and the ability to apply detailed redemption restrictions. Ensure that the Buyer Type on each loaded ticket type matches the TicketReturn buyer type code exactly to avoid discrepancies.
