Cigars POS Automated Age-Check Decline Log
Every night, WebRun opens Cigars POS, reviews the day's checkouts for ID scan age verification declines and manual overrides, logs each incident with the time, register, and cashier to a Google Sheet, and posts a short compliance summary to Slack so a manager can spot patterns.
How do I automatically log age-verification declines at checkout?
WebRun reviews Cigars POS every night for checkouts where ID scan age verification declined or was manually overridden. It logs each incident with the time, register, and cashier to a Google Sheet and posts an internal Slack summary flagging repeat overrides, so your lounge keeps a clean compliance record without any customer details leaving the team.
- Every age-check decline and override is logged in one dated record
- Repeat overrides by a cashier surface nightly for a manager to address
- You can show inspectors a consistent compliance log without manual notes
Built for cigar lounges · tobacconists · smoke shops · compliance managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
cigarspos.comin a real browser with your saved login - no setup, no API keys. -
1
Cigars POS - review the day's age-check declines
cigarspos.com
WebRun opens Cigars POS to review the day's age-check declines. - Open Cigars POS and go to the day's transaction and age-verification records
- Find every checkout where the ID scan declined the sale on age
- Find any transaction where age verification was manually overridden
- Capture the time, register, cashier, and outcome for each incident
Done when Every age-check decline and override from the day is captured with its details.
-
2
Google Sheets - log each incident for compliance
google.com
WebRun opens Google Sheets to log each incident for compliance. - Open the Age Verification Log sheet
- Add a dated row for each decline and override with time, register, cashier, and outcome
- Tag whether the sale was declined or overridden
- Keep a rolling tally per cashier so overrides stay visible over time
Done when The compliance log holds a dated row for every decline and override with a per-cashier tally.
-
3
Slack - post the daily compliance summary
slack.com
WebRun opens Slack to post the daily compliance summary. - Post a short compliance summary of the day's declines and overrides
- Call out any cashier with repeat overrides for a manager to follow up
- Keep the summary internal to the management channel with no customer identity details
Done when A manager has a Slack summary of the day's age-check declines and overrides.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Is this Slack summary safe to post automatically?
Yes. The summary is an internal compliance recap sent only to your management channel, with no customer names or ID details, so it can post automatically. Nothing about a customer leaves your team.
What does it count as an incident?
It captures two things from Cigars POS: any checkout where the ID scan declined the sale on age, and any transaction where a cashier manually overrode age verification, each logged with the time, register, and cashier.
How does this help with compliance?
It keeps a dated, per-cashier log of every decline and override in one sheet, so if an inspector or owner asks, you can show a consistent record and spot any cashier overriding checks too often.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.