Blog ยท Access control
Scanning badges at the door and capturing leads at the booth are not the same thing
Two products are sold with the same sentence โ "scan the badge with your phone" โ and they solve opposite problems, for different buyers. How to tell them apart before you buy the wrong one, and which of the two QRACCESS actually does.
There are two tools advertised with almost identical words. One is bought by the organiser of the conference. The other is bought by the exhibitors renting a booth inside that same conference. From the outside they look so alike that people regularly buy one expecting what the other does.
What lead retrieval does
Lead retrieval is a sales tool for the exhibitor. A rep on the stand scans the badge of whoever walks up, and their name, company and email are saved as a lead. Modern versions add voice notes, on-the-spot qualification and a push into the CRM.
The goal is the conversation afterwards. What it sells is not controlling who passes, but not losing the person who came over.
What access control does
Access control is an operational tool for the organiser. Door staff validate the badge and the system decides whether this person may pass, here, right now. Nobody is collecting commercial data: a right is being checked.
The goal is the door. What it sells is not getting to know the attendee, but making sure the right people get in and the wrong ones don't.
Why the confusion costs money
Because both are bought months ahead, and the difference only shows up on the day.
An organiser who bought lead retrieval finds their tool records visits but turns nobody away: it can't say whether a badge has already been used, whether it's still valid, or whether that person was entitled to that room. An exhibitor who bought access control finds their scanner says "valid access" and leaves the lead nowhere.
Which of the two QRACCESS does
It does access control, and it does not do lead retrieval. That's worth saying before any list of features.
What it does, checked against the product:
One badge covers the whole event. The code belongs to the attendee list, not to a single session, so the same QR works at the main entrance and at every room you decide to control.
Each room can be its own checkpoint, with its own staff. A scanner user only sees the events it has been assigned to, and creating one grants access to nothing: the assignment is the step that opens the door.
You choose what the person validating sees. You don't have to hand the full attendee record to whoever is working the door.
You can limit how many times a code is valid, and when. Outside the dates, the time window or the allowed days, it is rejected at the door with the reason.
Online, the same code cannot enter through two doors at once. Offline, it keeps validating without signal and syncs afterwards.
What it does not do, plainly
There is no lead capture app for exhibitors. No lead qualification, no voice notes, no CRM sync. If what you need is twenty reps on twenty stands each taking home their own list of contacts every night, this is not your tool โ and it's better to know that now than in October.
One piece does invite confusion: an attendee can be linked to an exhibitor. That exists to accredit the staff of a stand, not to let that stand capture visitors.
The part organisers underestimate: the rooms
Most people arrive thinking about the main entrance. The entrance is the easy part โ one queue, one moment, everybody arriving at once. The hard part starts afterwards, when the programme splits into parallel sessions and somebody has to decide who goes into the workshop with forty seats.
That's where the difference between the two tools stops being theoretical. Lead retrieval has nothing to say about it: a badge scanned at a door it shouldn't have passed is recorded exactly like any other scan. Access control is the thing that turns people away, which sounds unfriendly until the forty-seat room has sixty people in it and the fire officer is asking questions.
Two things make it work in practice, and neither is technical.
Decide in advance which doors matter. Not every room needs a checkpoint. Controlling four doors properly beats controlling twelve badly, because each checkpoint costs a person standing there for the whole session.
Decide what happens when someone is turned away. This is the part that gets skipped. Your door staff need to know whether a rejected badge means "find a supervisor", "let them in anyway and note it", or "the room is full, sorry". A scanner that says no without a plan behind it just creates an argument in a corridor.
The software will tell you the badge isn't valid for that room. What the software cannot decide is what your event does next.
How to tell which one you need
Three questions settle it.
Who pays for the tool? If the organiser pays, it's access control. If each exhibitor pays separately, it's lead retrieval.
What happens when a scan fails? In access control, somebody doesn't get in โ and that is precisely the function. In lead retrieval, a contact is lost but the person carries on walking around the show.
Whose data is it? In access control, the attendee is already the organiser's. In lead retrieval, the exhibitor is acquiring data they did not have before, with everything that implies for consent.
And a common case: both at once
A large conference with an exhibition floor needs both, and they don't compete: the organiser controls the doors and the rooms, and exhibitors buy their lead retrieval separately, often from the show's own supplier.
What doesn't work is expecting one tool to do the other's job because they both "scan badges".
If yours is the door โ who gets in, into which room, and with what validity โ set it up with ten test attendees before deciding: create the event, assign a scanner user to each room, and try reading the same QR twice. Half an hour tells you whether it fits.