01
Check happens at the register
The cashier holds the verifier; the customer taps their phone. The transaction does not leave the counter and the phone does not change hands.
Liquor retail
A register-side check that does not build a customer file.
Retail age checks happen mid-transaction, under time pressure, with a line forming. The check needs to be fast, defensible, and free of the data exhaust that a scan log leaves behind.
01 · The problem today
The scan log you did not want
Barcode-scanning an ID at the register reads the full PDF417 payload — name, address, birth date, document number — and then the operator decides what to keep. In practice, systems keep more than anyone intended, for longer than anyone remembers, in a database nobody owns.
Meanwhile the actual compliance requirement is narrow: establish that the customer is old enough. Everything beyond that is data you have taken on the risk of holding without gaining anything from it.
02 · The LaurelID workflow
How the check actually runs here.
02
One outcome, one action
Verified proceeds to payment. Under 21 refuses per your policy. Unable to verify falls back to your standard manual check.
03
Reporting rolls up by store
Counts per location and day, so a district manager can see volume and outcome mix without seeing a single customer.
03 · The privacy advantage
The narrow request is the compliance argument
LaurelID requests one element — a signed attestation that the holder is over 21 — and declares that it will not retain it. That is a materially different posture from reading a full credential and promising to be careful with it.
For a multi-store operator, this also removes an entire class of internal question: which stores retained what, for how long, and whether a franchisee's local system is doing something different. There is nothing to standardize because there is nothing being collected.
04 · Deployment
What a rollout looks like in this setting.
Scoped during qualification against your real floor, not assumed from a template.
Dimension Shape
Posture Handheld at the register
Placement One verifier per staffed lane, or shared
Network Store Wi-Fi; checks survive an outage
Rollout Per-location, bound to a location record
Reporting Aggregate counts by store and day
05 · Limitations
Where LaurelID is the wrong answer here.
If one of these is a hard requirement for you, it is better to know now than three weeks into a pilot.
Not a point-of-sale integration today
The verifier is a standalone check, not an embedded step in your POS. If you need a hard interlock between the age result and the transaction, say so during qualification — it is a scoping conversation, not something to assume from this page.
21+ only
The current release verifies age_over_21. Products gated at a different age are not covered, and the verifier cannot be configured to answer a different threshold.
06 · Other settings
Nearby verticals.
Bars and nightclubs
Door staff make a judgement call every few seconds, in bad light, with a queue behind the person in front of them. LaurelID gives them a cryptographic answer instead of a squint.
Cannabis retail
Cannabis retail sits under strict age rules and equally strict scrutiny of what operators keep about their customers. A check that collects nothing is easier to defend than a check that collects carefully.
Stadiums and venues
A venue's age checks all happen in the same twenty minutes, on the worst network of the week, run by staff who may be working their first event. Everything about that is a design constraint.
Pilot LaurelID in liquor retail.
Thirty days, one location, two to five verifiers, and a written readout against metrics you agree to first.