Loaded tickets attach spending value directly to TicketReturn barcodes. The TicketReturn integration delivers that value automatically through its feed.
Location: Point of Sale > Loaded Tickets
Data ingestion: the TicketReturn feed carries two distinct values — the ticket's price and its loaded value.
Automatic activation: if barcodes are configured correctly in TicketReturn and arrive through the feed, they work at the POS within the event window without any setup on the Fanmaker side.
Internal mapping: you still create loaded ticket types in the admin to get named reporting and to apply optional restrictions.
The page shows one day at a time and opens on today. Change the day with the Date picker at the top right of the Barcode Count card, or by clicking a bar in the seven-day chart beside it.
Four tiles summarize the selected day:
Valid Barcodes — how many barcodes exist for that day
Total Funding — the total dollar value on them
Total Spent — how much has been redeemed
Total Balance — what's left unspent
A Transactions chart plots redemptions across the day.
Below the chart, the Loaded Ticket Types table lists every type with Name, AV, Barcodes, Funding, Spent, Balance, and Actions. Types with no activity on the selected day still appear, reading zero; a switched-off type carries a disabled pill.
Each row's Action menu offers View Barcodes, Edit, and Delete.
Optional setup: with TicketReturn, the barcodes work for their assigned value whether or not you create a type — the value comes through the feed.
Why bother: a type gives you named reporting, lets you classify different ticket products, and is the only way to attach restrictions.
1. Click Add Loaded Ticket Type.
2. Name — internal display name for reporting, e.g. "Meal Deal". Required.
3. AV Amount — must match the TicketReturn loaded value exactly. Required, and formatted plainly, e.g. 16.89.
4. Description — optional detail for your own reference.
5. Leave Enabled ticked and click Create Loaded Ticket Type.
By default a loaded ticket applies its value at every connected point of sale — concessions, merchandise, walk-in/walk-out.
Restrict to POS System limits a type to one or more specific systems. Leave it empty for no restriction.
Redemption Restrictions is a picker with three options:
None — no SKU or location conditions
SKU — reveals Allow SKUs and Block SKUs
Location — reveals Allow Locations and Block Locations
With SKU selected:
Allow SKUs — only barcodes matching these SKUs are accepted. Use it to require a specific item in the cart.
Block SKUs — barcodes matching these SKUs are rejected. Use it to keep the value off alcohol.
With Location selected:
Allow Locations — only barcodes scanned at these locations are accepted.
Block Locations — barcodes scanned at these locations are rejected.
Start typing in any of these fields to search your catalog.
Action > View Barcodes opens the drill-in page for that type on the selected date. It repeats the four tiles for just that type, then lists each barcode with its Barcode, Initial Value, Spent, and Balance.
Use Search by Account Number to find one fan's barcodes, and Action > View Transactions on a row for that barcode's full ledger.
Value availability is controlled by the timing you set inside TicketReturn: loaded value is only active between the event's gate open and gate closed times.
On the Fanmaker side, barcodes are pulled hourly, stepping up to roughly every two minutes while an event is active.
Creating loaded ticket types on TicketReturn is optional, but it's what gives you clean reporting and the ability to restrict how value is spent. Make sure each type's AV Amount matches the TicketReturn loaded value exactly and is unique across your types, and set your gate open and gate closed times carefully — they, not the admin, decide when the value works.
