Verify passes at the door, record attendance and redemptions, and trigger Salesforce automation from every scan — with the Kemicard Scanner add-on or hardware you already own. Use it as a membership verification scanner at the club door, an event check-in station, or a redemption counter.
The Kemicard Scanner: a managed LWC you can put anywhere
The Kemicard Scanner ships as a managed Lightning Web Component (LWC) — you add it to any Salesforce page layout or any Experience Cloud (Community) page layout, exactly like any other component. That gives your team three ways to scan:
- Desktop or iPad, via Salesforce — staff log into Salesforce in the browser and scan from the page where you placed the component: a check-in station, a front-desk console, an event command center.
- Phone or iPad, via the Salesforce mobile app — the same component works in the Salesforce app, turning any staff phone into a hand-held scanner at the door.
- Experience Cloud portal — drop the component on a portal page and partner staff, volunteers, or venue crews scan by logging into your Experience Cloud site, without full Salesforce access.
- Every scan verifies the pass in real time, shows member details, flags duplicates, and records attendance and redemptions to Salesforce.
- Works offline-tolerantly: the pass barcode displays and scans even when the member's phone is offline.
Scanner licensing
The Scanner itself requires no extra Kemicard license — it is part of the platform. The person doing the scanning needs two things: a way into Salesforce (a Salesforce license or an Experience Cloud/Community license) and an assigned Kemicard license.
Barcode format support
- QR — recommended; reliable on both Apple and Google passes.
- PDF417 — reliable alternative when a 1-D look is wanted.
- Code-128 — not reliably recognized (scanner library limitation); avoid.
Choose how you scan — once
When you open the scanner you land on a Ready to check in screen. Pick Camera to use the device's own camera, or External scanner if you have a connected handheld or scanning gun. From v2.29 Kemicard remembers the choice on that device and browser, so nobody re-selects a camera before every scan. Return to this screen any time to switch.
| Method | What it uses | Best for |
|---|---|---|
| Camera | The camera on the phone, tablet or computer you are using. | Quick check-ins on a phone or tablet at the door. |
| External scanner | A connected handheld barcode scanner or scanning gun. | High-volume entry where you scan a code and pull a trigger. |
Scan a pass
Once a method is chosen the scanner shows Waiting for a scan. With an external scanner, pull the trigger; with the camera, point it at the pass's QR code. No scanner in hand? Click Type a code instead and enter the pass code manually.
The result is a full-screen colour the attendant can read at arm's length — green for Valid, red for Not Valid — with the reason underneath and the member's details below it. Tap Scan next for the next guest, or Stop scanning when you are done. Which fields appear is set by the scanner flow on your template, so two events can show different things.
Member names and record IDs are blurred in these captures; both fields display in full in your own org.
Switching cameras
Most phones expose more than two cameras, and the one the browser picks by default is not always the one facing the guest. Tap the camera label at the top of the scan view to switch; the choice sticks with the scan method, so you set it once per device.
Confirm identity and open links
A scan result can carry more than text. When your scanner flow outputs the right fields, the result shows the member's photo so the attendant can confirm the person in front of them, plus clickable links and additional images.
| Item | What the person scanning sees |
|---|---|
| Profile photo | The same thumbnail field used on the pass, shown on the result — a visual identity check at the door. |
| Extra images | Additional image links also display on the result. |
| Avatar vs image | Several results can be set to display as an Avatar, but only the first renders as one. |
| Clickable links | The avatar and images are clickable and open the same picture in a browser. |
Scan-triggered automation
Scans map barcode values to Salesforce record IDs, so Flows can act on every scan:
ON scan → resolve barcode → Contact
→ create Check-In record (time, location, staff)
→ award points / decrement allowance
→ send follow-up offer after the event- Attendance — every entry logged as a related record for reporting.
- Redemptions — benefit usage tracked per privilege, per location, per date.
- Engagement scoring — scans can update scoring fields that drive journeys.
Using existing scanner hardware
Barcode scanners that emulate keyboard input can drive the same Salesforce mapping as the Kemicard Scanner — reuse the hardware you already own at fixed check-in stations.
Event-platform check-in
With Blackthorn Events, the proven flow is: registration page → attendee record created → welcome email with pass download → add to wallet → Blackthorn mobile app scans the Kemicard pass → attendee checked in. Generate passes from the Contact rather than the attendee object. Eventbrite and payment-platform integrations are scoped per client.
Verification & fraud checks
- Every scan validates the pass serial against the source Salesforce record; duplicates and counterfeits are rejected.
- Duplicate-scan tracking flags a barcode scanned twice at the same gate.
- Pair with a rotating barcode so a screenshot of the code stops working within seconds — the scanner validates the live value, not a stored one.
- Pair with Google sharing levels for high-value access programmes: Single User (Single Device) or Sharing Prohibited stops the pass reaching a second wallet at all. See also Security.
Background reading on the blog: how pass security and scan-time validation work.
