Admission with the ticket scanner
Give scanner links to your door staff, install the scanner on a phone, scan offline — and what to do about a ticket that's been scanned twice.
Web only
The ticket scanner is a web app at tickets.cori.music/scan — not an app from the App Store. It runs in any phone browser and can be added to the home screen for offline use.
On concert night your door staff scan the QR codes on the tickets. Nobody needs a cori account for that and nobody needs an app from the store: you send out a scanner link that opens in the browser of any phone — and stops working by itself after the event.
Every scanner phone has to be opened once with an internet connection before the doors open. Only that first sync loads the guest list onto the device — without it the scanner can't check anything offline.
Creating a scanner link
Open the event and switch to Door scanners on the left.
"Main entrance" or "Side entrance", for example. The name is shown in the scanner and stored with every check-in — so you can tell entrances apart afterwards. Give every entrance its own link.
cori shows the finished link exactly once: "Share this link now — it won't be shown again." Use Copy link or Share with your door staff and send it off straight away.
Whoever has the link can check in tickets for this event — no account, no password. Only send it to people who really will be on the door, and don't post it anywhere public. cori deliberately shows it only once; after that it can't be read out again, only revoked.
In the list you see each link's state — Active, Expired or Revoked — how long it's valid for and when it was last used. If a phone has gone missing or a helper can't make it after all, you revoke that one link; the others carry on working.
By default, a scanner link is valid until 12 hours after the end of the event. So a forwarded link is dead by the next morning, even if you do nothing.
What your door staff have to do
Pass on these four sentences — that's all there is to it:
It opens in any phone browser. The first time it's opened, the secret part disappears from the address bar and is stored on the phone — the scanner then keeps working after a reload, and a screenshot no longer gives the link away.
Best done at home or outside the venue. The scanner says "Ready for offline use — N tickets are stored on this phone" once it's finished.
The Install for offline use button puts the scanner on the home screen as its own icon. On Android the browser offers to install it directly; on iPhone the route is through Safari: Share → Add to Home Screen → Add.
Done.
On iPhone, an installed web app gets its own data storage, separate from Safari. So the first time you open the new icon, the scanner asks for the link again — just paste the same link in. And note: only Safari can add to the home screen on iPhone, Chrome and Firefox can't.
The four colours
The scanner answers every code with a colour. Tell your staff what they mean:
That's the whole training. Everything else is in the scanner itself under "How offline scanning works".
| Colour | Display | What it means | What to do |
|---|---|---|---|
| Green | Valid — admitted | Valid ticket, just checked in | Let them in |
| Blue | Already used | This code has already been checked in | Don't let them in, ask questions — see below |
| Amber | Can't verify | Offline, and the code isn't in the downloaded list | Your call |
| Red | Invalid | Not a ticket for this event, or the order isn't paid | Don't let them in |
Under Details the scanner shows the last ticket's type, fare, holder name and section/row/seat — and a note when a concession fare requires proof. Door staff deliberately don't see the buyer's email or the order reference.
A ticket scanned twice
Blue means: this code has already been checked in. The scanner deliberately does not tell your staff at which entrance and when — that belongs in your follow-up, not in a conversation in the queue.
Both are possible: a forwarded or repeatedly printed ticket, or someone from the same group has already shown the code. You decide on the spot. The scanner itself won't let the code through a second time — only the first scan wins, even if two entrances scan at the very same moment.
If the connection drops in the middle of a scan, it can happen that the answer is lost even though the check-in got through. cori Tickets recognises that and later reports it as your own success, not as a double scan. Your staff don't have to do anything about it.
Without a signal
At the door, a dead spot is the norm, not the exception. The scanner is built for it:
- The guest list lives on the phone. Every paid ticket for the event is downloaded and, as long as there's a connection, refreshed every 20 seconds. Only one-way fingerprints of the codes are stored, never the codes themselves — a lost phone is no good for forging tickets.
- Offline, scans are checked against that list and the check-in is remembered on the device.
- The queue empties itself as soon as the connection returns. The counter in the header shows what's still waiting; the ↻ button forces a sync.
- Even online, the scanner waits little more than a second for the server and then decides offline. So a sluggish network doesn't bring the queue to a halt.
Where offline reaches its limits
Be honest with your team here — there are two real limitations:
Offline, "already used" only knows about scans made on this device. A ticket that has just been let through at the other entrance comes up green here while offline. That only surfaces once both devices are back online. So with several entrances and no reception, a ticket being used twice is possible.
A code that isn't in the list while you're offline was most likely bought after the last sync — the scanner can't confirm that either way. The decision is down to the door staff, and the scan is uploaded with the rest. Rule of thumb: if the ticket looks plausible and the last sync was a while ago, let them in and check afterwards.
Conflicts after syncing
As soon as the queue has uploaded, the scanner reports where the server saw things differently: "N offline scans conflicted on sync (already used or invalid). Review at the door." The server decides who was first — nothing is silently dropped. Take a look at this message the same evening, not the next day.
When the camera won't play along
The scanner usually tells you what's wrong itself:
- "Camera access was blocked." Allow it in your browser settings and reload.
- "The camera only works over a secure (https://) connection." The link has been altered — use the original link.
- "The camera is busy in another app or tab." Close the other app and reload.
Use Choose camera to switch between the back and front camera; the back camera is the right one.
Take the entry list as a CSV with you to the door (under Orders & tickets). If a phone fails, you tick guests off on it. How that works is described in Keeping an eye on orders.
What's next?
- Lists and exports for the evening: Keeping an eye on orders
- Why a ticket is red: Refunds and complimentary tickets
- Before sales open: Publishing and sharing your event
- What the guest is holding: Finding your tickets again
Still need help?
Can’t find what you’re looking for? Send us a message and our team will get back to you.
Contact support