When SeatGeek is your ticketing provider, loaded ticket types match barcodes by price code instead of by dollar amount — which changes how you set them up on the shared Loaded Tickets page.
Point of Sale › Loaded Tickets
https://app.fanmaker.com/admin/point_of_sale/loaded_tickets
One page serves every provider. It reads which one your program uses and adapts the forms accordingly, so a SeatGeek program never sees Ticketmaster's fields and vice versa.
On Ticketmaster and TicketReturn, a barcode finds its loaded ticket type by matching the dollar amount exactly — which is why those providers require every type to have a unique amount.
SeatGeek doesn't work that way. A SeatGeek barcode carries no value of its own. Instead, each loaded ticket type carries a price rule, and a barcode is matched to the type whose price rule it satisfies. The type's amount is then what gets loaded onto it.
Two consequences follow:
You must fill in the price rule, or the type matches nothing at all.
Several types can share the same amount. The price rule is what tells them apart, so the uniqueness requirement other providers have simply doesn't apply here.
This is the SeatGeek-only field, and it's the one that does the matching. Enter the price type exactly as it's configured in SeatGeek — for example, "Full Season Renewal."
A barcode matches this type when the sale's SeatGeek Price Type equals this value. The comparison ignores capitalization but is otherwise exact, so the wording has to line up with SeatGeek.
Two enabled types can't carry identical price rules. If you try, the admin rejects the save with "A Loaded Ticket Type with these price rules already exists" — usually a sign the type you meant to create already exists.
On a SeatGeek program this field is labelled Amount, and it's the value loaded onto each barcode that matches this type's price rules.
Because barcodes are matched by price rule rather than by value, several types on the same program are free to share an amount.
Go to Point of Sale › Loaded Tickets and select Add Loaded Ticket Type.
Enter a Name — for example "Rooftop Meal Deal." This is the label you'll see everywhere on the page.
Enter the Price Type, matching SeatGeek exactly.
Enter the Amount to load onto each matching barcode.
Optionally add a Description.
Optionally use Restrict to POS System to limit the type to specific connected point of sale apps. Leave it empty for no restriction.
Optionally set Redemption Restrictions to SKU or Location, then use the Allow and Block pickers that appear to control what the value can be spent on or where.
Leave Enabled checked and select Create Loaded Ticket Type.
On the types table, open the row's Action menu and choose Edit. The edit form carries the same fields as the create form, including Price Type and Amount.
Changing a Price Type changes which barcodes match going forward. It doesn't retroactively move value that's already been loaded.
The same Action menu offers View Barcodes to drill into a type, and Delete to remove it.
The page is scoped to a single day at a time. For SeatGeek, that day is the event date that came across with the ticket, not the date the barcode was created or scanned.
At the top, the Barcode Count card shows the surrounding week as a bar chart — click a bar to jump to that day, or use the Date picker. Below it, four tiles summarise the selected day:
Valid Barcodes — how many fundable barcodes exist for that day
Total Funding — the total value those barcodes represent
Total Spent — how much of it has been spent
Total Balance — what's left
Then the Loaded Ticket Types table lists every type you've configured, with its AV (the amount you set), Barcodes matched that day, Funding, Spent, and Balance.
If the day includes barcodes that no enabled type claimed, a red Unmatched Loaded Ticket row appears at the bottom of the table. Click it to see exactly which barcodes fell through.
On SeatGeek, unmatched barcodes show no funding — there's no type to take a value from, so they fund nothing.
A handful of unmatched barcodes is normal on a program with price types you deliberately don't fund. A sudden pile of them usually means a price type changed on the SeatGeek side and your loaded ticket type no longer matches it.
Selecting a type name, or View Barcodes from its Action menu, opens the per-type page for the same day. You get the same four tiles scoped to that type, and a Barcodes table listing each barcode with its Initial Value, Spent, and Balance.
Use Search by Account Number to find one barcode, and Clear Filter to get back to the full list. Back to All Loaded Ticket Types returns you to the dashboard on the same date.
Everything is landing in Unmatched. Compare your type's Price Type against what SeatGeek is actually sending. Capitalization doesn't matter, but wording and spacing do.
A type shows zero barcodes. Check the date first — the page is scoped to one event date. Then confirm the type is Enabled; a disabled type matches nothing.
Two types were meant to have the same value and one wouldn't save. A shared amount is fine on SeatGeek. If the save was rejected, it's the price rule that collided, not the amount.
I need everything else on this page. Restrictions, POS limits, the transactions chart, and the barcode transaction history all work the same way regardless of provider — the shared Loaded Tickets article covers them.
