Loaded tickets attach spending value to ticket barcodes. This guide covers the feature as it works on programs running Ticketmaster: the dashboard, creating loaded ticket types, and setting redemption restrictions.
Location: Point of Sale > Loaded Tickets
The page opens on today's date. Two controls change that: the Date picker at the top right of the Barcode Count card, or clicking any bar in the seven-day chart beside it.
Four tiles summarize the day you're viewing:
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
Below the tiles, a Transactions chart plots redemptions across the day, so you can see how the value was actually spent during and after the game.
The Loaded Ticket Types table lists every type you've defined, with columns for Name, AV, Barcodes, Funding, Spent, Balance, and Actions.
Every type shows, even ones with no activity on the day you're viewing — those simply read zero. A type that's switched off carries a disabled pill next to its name.
Each row's Action menu offers:
View Barcodes — the individual barcodes for that type on the selected date
Edit — opens the type's edit window
Delete
Optional setup: with Ticketmaster, the tickets work for their assigned dollar value whether or not you create a matching type — Ticketmaster passes the AV amount through.
Why bother: creating 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. Enter a Name, for internal reference — "Meal Deal", "Rooftop Package". Required.
3. Enter the AV Amount. Required, and it must exactly match the dollar value configured in Ticketmaster. Format it plainly, e.g. 16.89.
4. Add a Description if you want more detail on hand later. Optional.
5. Leave Enabled ticked, and click Create Loaded Ticket Type.
By default a loaded ticket applies its dollar 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, like a particular meal deal.
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 jump to one fan's barcodes, and each row's Action > View Transactions to see that barcode's full ledger.
Fanmaker pulls Ticketmaster AV barcodes hourly. On days with an event in the sync window, retrieval steps up to roughly every two minutes so gameday sales land quickly.
Tickets must be sold into an account before they sync — Fanmaker does not ingest unsold inventory.
Creating loaded ticket types on Ticketmaster is optional, but it's what gives you clean reporting and the ability to restrict where value can be spent. Keep every AV Amount unique and exactly matched to Ticketmaster, and check the Unmatched Loaded Ticket row after an event to catch any value arriving without a type behind it.
