Loaded tickets attach spending value to ticket barcodes. This guide covers the feature as it works on programs running Tickets.com (TDC): the dashboard, creating loaded ticket types, and setting SKU and location restrictions.
Location: Point of Sale > Loaded Tickets
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 below the tiles plots redemptions over the course of the day.
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.
1. Click Add Loaded Ticket Type.
2. Name — for internal reporting. Required.
3. Buyer Type — must match the buyer type on the TDC barcode exactly, and be unique for your program. Enter the Buyer Type itself, not the Buyer Type Description.
4. Amount — the value loaded onto each barcode matching this buyer type. Required; dollars and cents are fine.
5. Allow multiple redemptions per seat — see below. Off by default.
6. Description — optional detail for your own reference.
7. Leave Enabled ticked and click Create Loaded Ticket Type.
Off (default) — the value is tied to the seat, identified by event, section, row, and seat number. The first barcode that comes through for that seat is funded, and any other barcode carrying the same seat details is treated as already funded and gets nothing.
On — the value is tied to each individual barcode. Every barcode is funded in its own right, even when several of them share the same seat details.
Turn it on only for general admission events, or programs where every ticket is issued with identical seat information (Section: GA, Row: GA, Seat: 0). Without it, only the first barcode for that seat is funded — which on a GA event means one fan spends everyone's credit.
By default a loaded ticket type works 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 something specific in the cart, like a bottle of water or a meal deal item.
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.
Fanmaker checks the TDC feed continuously — about once a minute for each program that has it enabled. What actually paces things is TDC: barcodes can't sync until TDC has delivered the event file, and TDC typically sends those once or twice a day.
Plan your configuration well ahead of an event rather than the morning of it.
On TDC, every buyer type you sell loaded value against needs a matching loaded ticket type in the admin, because that's where the dollar value lives. Match the Buyer Type exactly with no spaces, set the Amount, and add SKU or location restrictions where you need to control how the value is spent.
