Guests
Pulled live from the ticketing API — SMDD 2026 tickets only.
Print run
Cards ahead of the event, or a batch of labels to catch up.
What are you printing?
Full cards are finished and ready to hand out. Labels carry only what a blank card is missing, for sticking on at the desk.
Who?
Nothing selected means everyone. Each category carries its own family: press + family on the ones whose family should be printed too.
Who has RSVP'd?
Only guests who answered are printed. A family ticket answers for itself, so it is filtered on its own reply.
Which wave?
Print everyone who has claimed by a cut-off now, then come back later for whoever claimed since — family included, as they claim for themselves and usually long after their host. Leave it off to print the lot.
This run
What goes on the badge?
The name and the category are always there. These stack underneath, in this order, until the space above the category runs out.
Layout & options
One file or many?
Either way the order is the same: the categories you picked, in order, and every family badge straight after its host.
Blank templates
The artwork with the white panel left empty, for running cards off ahead and sticking a label on at the desk. Each category is saved as its own file, named for it. Nothing selected means every category.
Preview
A real guest from the current selection.
Desk settings
Set the printer's paper to the label size and choose 100% / actual size — the page is sized in the document, so nothing gets rescaled.
API calls from this device
The ticketing service's daily quota is shared with check-in, so this is what the badge app spends of it. Scanning, printing and searching cost nothing — they run on the list already loaded.
Scanner test
Open this and scan a badge. Nothing is looked up — it only reports what the scanner actually sends, which is the quickest way to tell a mis-configured scanner from a broken one.
QR decryption secret not set
With the event's secret the desk reads any
SMDD ticket QR, including the one a guest was emailed. Without it,
only badges printed on this device match. This is the ticketing
service's TICKET_QR_ENCRYPTION_SECRET — a passphrase,
not a key file. It stays on this device and is never sent anywhere.