Practical guide

Set ticket-type filters to match the job at each scanning position

Last materially reviewed 2026-09-28

Quick answerA filter can deliberately reject a valid ticket at the wrong station; brief operators on that distinction.
What to know

Give the position one clear job

An entrance, a merchandise desk and a separate session may handle different entitlements. List the items each position should process before configuring devices. Do not assume every QR code belongs to ordinary admission. If a volunteer is responsible only for entry, an unrelated product redemption should have another route. Keep the wording on signs and in the briefing consistent with the actual task.

What to know

Check the configured restriction

Ticket Tailor documents device filters that restrict ticket or product types and show an error for excluded types. That can be intentional, not proof that the ticket is invalid everywhere. Record the intended filter and test the accepted and excluded cases in an authorized rehearsal. A positive test alone is incomplete: the team also needs to understand what the expected rejection looks like and where to send the person next.

What to know

Avoid silent changes between shifts

If a device moves from one station to another, its filter may need to change. Put that check in the handover rather than relying on a volunteer to notice the previous setting. Label the device’s current role and identify who may alter it. Do not let an attempt to clear a confusing error quietly broaden what the station accepts. The organizer should approve changes to the admission workflow.

What to know

A fictional station change

Device D3 is used for merchandise before moving to general entry. The new operator sees several rejected admission codes. The right question is whether the device still carries the earlier restriction, not whether every attendee has a bad ticket. The lead checks the task and configuration, then verifies the intended behavior before resuming. Save the lesson in the next handover checklist without retaining unnecessary attendee details.

Continue when useful

Next: Invalid code

An error describes the current check; investigate the context without overriding the event’s rules.

Open Invalid code →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Ticket Tailor: restrict ticket types at a device — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28
  2. Ticket Tailor: attendee check-in — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28