What is conditional visibility?

Conditional visibility is deterministic, rule-based branching on audit and checklist questions. It shows or hides a question group depending on an attribute recorded on the location's profile. It is not AI and not a general-purpose form builder. It is purpose-built branching for operations audits, and this page covers one specific dimension of it: the license or permit attribute, whether a store holds a state liquor license, a tobacco-and-vapor retail permit, both, or neither.

That's different from three other conditional-visibility dimensions covered elsewhere in this collection. Franchise-tier branching shows different questions based on who owns the unit, corporate versus franchisee. Auditor-role branching shows different questions based on who's running the audit, a DM versus corporate compliance versus a third party. Equipment-attribute branching shows different questions based on physical gear at the store, a fryer, a tap system, a drive-thru lane. License-attribute branching shows different questions based on a regulatory permit the store holds, and that permit has nothing to do with ownership or equipment. A 110-store chain can run identical kitchens, identical registers, and identical franchise agreements at every unit and still have 40 stores licensed for alcohol, 85 licensed for tobacco, and 30 licensed for neither beyond basic retail. A static template can't express that without either building a separate template per license combination or asking every store every question and living with bad data from the 30 stores that were never eligible to answer.

Conditional visibility is the ability to show or hide specific audit questions based on a recorded attribute on the location record, in this case whether the store holds an alcohol license, a tobacco and vapor permit, both, or neither. It pairs with a second feature called nullify scoring, which lets N/A items count for nothing instead of dragging down the audit score. A store without an alcohol license shouldn't be scored on an alcohol-signage group it was never allowed to run. Nullify scoring keeps that group out of the store's scoring denominator entirely, so the audit percentage reflects only what that store is actually licensed and responsible for.

Conditional visibility lets you ask different questions at different locations without penalizing stores for N/A items, the "patios vs. no-patios" problem solved for regulatory permits instead of physical amenities. One audit template handles every license combination in the chain.

Worked example, conditional visibility in action

A 110-store convenience-store chain runs one brand-standards-and-compliance audit carrying 44 questions on a fixed quarterly cadence. The permit attribute on each store's location record, not the district manager's memory, decides which compliance question groups render for that store.

A store that holds a beer-and-wine license sees the alcohol-signage group, the age-verification-prompt group, and the trading-hours group. A store with no alcohol license never sees that group at all. It's hidden, not answered "N/A." A store that sells tobacco and vapor products sees the tobacco-signage group, the ID-scan-log group, and the self-service-display-ban group. A store that doesn't carry tobacco or vapor skips that group entirely. A store holding both licenses sees both question groups layered onto the shared audit. A fuel-and-snacks-only kiosk with neither license sees only the shared cleanliness and forecourt group, no alcohol or tobacco questions at all.

| Tier / Condition | Question groups shown | Question groups hidden |
|---|---|---|
| Beer-and-wine licensed store | Shared cleanliness and forecourt, alcohol signage, age-verification prompt, trading hours | Tobacco signage, ID-scan log, self-service display ban |
| Tobacco and vapor permitted store | Shared cleanliness and forecourt, tobacco signage, ID-scan log, self-service display ban | Alcohol signage, age-verification prompt, trading hours |
| Dual-licensed store (alcohol and tobacco) | Shared cleanliness and forecourt, both alcohol and tobacco groups | None of the restricted groups |
| Fuel-and-snacks-only kiosk, no license | Shared cleanliness and forecourt group only | Both alcohol and tobacco groups |

The license attribute on the store record decides the question set. Nullify scoring, a separate but paired feature, keeps the unlicensed store from taking a scoring hit on a compliance group it was never eligible to run in the first place. Its denominator only counts the questions relevant to what it's actually licensed and required to do.

This maps to how Huck's uses conditional logic today, built specifically for stores with tap systems versus stores without. In Huck's own words, that kind of branching comes "in handy for like the cold temps because not all of our stores have like a tap system." The license-attribute pattern applies the same branching logic to a regulatory dimension instead of an equipment one.

Two regulatory facts explain why these two question groups exist at all. Federal alcohol dealers must register with the Alcohol and Tobacco Tax and Trade Bureau and keep records of quantities received, from whom, and on what date, per TTB's retail beverage alcohol dealer guidance. State ABC agencies layer state-specific license tiers on top of that federal registration, and a store's license type, beer-and-wine only versus full liquor, determines exactly which signage and age-verification steps apply. Convenience stores are now the largest channel for U.S. off-premise alcohol dollar sales, holding 43.3% of alcohol beverage sales share in Q1 2025 according to NIQ data reported by NACS, which makes license-attribute compliance a core operating concern for the channel, not a niche one.

On the tobacco side, the FDA's Tobacco Control Act bans self-service displays of cigarettes and smokeless tobacco except in adult-only facilities, per FDA's guidance on selling tobacco products in retail stores. Under the FDA's 2024 final rule, retailers must check photo ID for anyone under 30 attempting to buy cigarettes, smokeless tobacco, or covered tobacco products, up from the prior under-27 threshold, effective September 30, 2024. Roughly 93% of payroll gas and convenience stores sell tobacco products, per federal Economic Census analysis. That's why the tobacco compliance question group is one of the highest-frequency conditional groups in this vertical. Almost every store needs it, but the exact ID-scan-log and self-service-display-ban sub-items still depend on whether the local jurisdiction requires electronic ID scanning or manual verification.

How does conditional visibility differ from static audits?

A static audit asks every store the same fixed question set regardless of what that store is licensed or equipped to do. A conditional audit reads the store's recorded attributes, license status included, and renders only the questions that apply, while still running from one master template.

| Attribute | Static audit | Conditional (license-attribute) audit |
|---|---|---|
| Template count | One template per license combination, or one bloated template asking everyone everything | One master template. Question groups render per store |
| Unlicensed store on alcohol group | Marked N/A or scored 0%, drags down the average | Group never renders. Nullify scoring excludes it from the denominator |
| New store opens with a fresh tobacco permit | Someone manually swaps or edits the template | Store record updates the license attribute. The tobacco group appears on the next audit automatically |
| Compliance officer's rollout effort at 110 stores | Manage 3 to 4 template variants, track which store runs which | Manage 1 template. Permit data drives the branching |
| Auditor experience | Skips through irrelevant sections manually, risk of skipping a required one by mistake | Irrelevant sections are never presented. Nothing to accidentally skip |

Competitor checklists confirm this gap is still open. POPProbe's free Tobacco and Alcohol Compliance Audit runs a flat, linear 32-point checklist across six fixed sections, with every store getting every section regardless of what it's actually licensed to sell. SafetyCulture's Liquor and Tobacco Store Compliance Audit Checklist and its companion Liquor & Tobacco Store Regulations Audit Checklist are similarly static, published as fixed templates with no per-store license branching. BottlePOS's liquor store audit guidance is written for single-format liquor stores, not multi-format chains mixing licensed and unlicensed locations. None of the three publish a conditional-by-license-attribute angle.

Zenput supports basic answer-based branching, but its documented weakness is the absence of question-level branching tied to a location attribute like a license record, a gap Xenia's best Zenput alternatives comparison already calls out directly: Zenput supports basic branching, and Xenia goes further. RizePoint sells conditional logic as an add-on rather than shipping it natively, which raises the cost of exactly this kind of license-based question routing for a multi-format chain that wants it built in.

How to set up conditional visibility in Xenia

1. Add the license attribute to each store's location record. Tag each store with its permit status: alcohol-licensed, tobacco/vapor-permitted, both, or neither. This single field drives every branch below.
2. Build one brand-standards-and-compliance audit template. Include the shared sections every store answers, cleanliness, forecourt, general safety, plus the alcohol-specific and tobacco-specific question groups.
3. Set the license attribute as the visibility condition on each restricted group. The alcohol-signage, age-verification-prompt, and trading-hours group renders only when the store record shows an alcohol license. The tobacco-signage, ID-scan-log, and self-service-display-ban group renders only when the store record shows a tobacco/vapor permit.
4. Turn on nullify scoring for both conditional groups. This keeps a store without the matching license from being scored against a group it was never eligible to run, so its audit percentage reflects only what it's actually licensed and responsible for.
5. Roll the single template out to all 110 stores. There are no per-license-combination template variants to manage or keep in sync.
6. Update the license attribute the moment a store's permit status changes. A new tobacco permit, a lapsed alcohol license, or a newly dual-licensed store updates the question set on the very next audit cycle. No template edit required.

This kind of conditional-branching build is also what the AI Template Agent is designed to speed up. Upload the existing brand-standards SOP as a PDF, and the agent converts it into a digital audit with conditional logic already structured, cutting what used to be a multi-week franchise template rollout down to days. It does not write compliance question language from scratch. The operator still supplies the regulatory question text, TTB, state ABC, local ordinance, or FDA tobacco guidance, and the agent's job is converting that SOP into a working conditional form.

Where do operators see results?

C-store operators managing mixed license portfolios are the primary audience for this pattern. OnCue runs vendor compliance workflows across its store network on Xenia, a live customer using the platform for compliance-adjacent audit work. G&M Oil migrated from iSupport to Xenia, a move driven by modernization and multi-feature consolidation, a pattern common among C-store operators replacing legacy compliance platforms that force a template-per-license-type workaround. H&S Energy runs sensor-integration work across 360+ stores, illustrating the scale at which license-mix variation becomes unmanageable without conditional logic. Huck's built conditional checklists specifically for tap-system-versus-non-tap-system stores, the same branch-by-store-attribute pattern applied here to license status instead of equipment.

The C-store area manager cares about this because a single area can contain a beer-and-wine-licensed store, a tobacco-only store, and a fuel-and-snacks kiosk with neither license, all reporting into the same weekly brand-standards audit. Without license-attribute branching, the area manager either builds three templates and manually assigns the right one to each store, a maintenance burden that compounds every time a license changes, or runs one bloated template that pads N/A answers into every unlicensed store's score and buries the real compliance signal. With license-attribute conditional visibility and nullify scoring paired together, the audit score at every store in the area reflects only what that specific store is legally responsible for, and DM walk time goes to real gaps instead of chasing down false N/A flags. That pattern shows up across C-store operations broadly, where forecourt format, fuel-only footprint, and license mix can all vary store to store inside the same banner.

Xenia does not provide legal compliance certification, does not verify that a store's license is currently valid against a state database, and does not replace a POS-level age-verification scanner. This is audit-question rendering driven by a license attribute the operator maintains on the location record. The operator supplies the regulatory question text and keeps the license attribute current. The platform's job is making sure the right question set shows up at the right store, every time, without a human remembering which of 110 stores holds which permit.

For chains carrying corrective actions past the audit itself, corrective action tracking covers how a failed compliance item, an expired age-verification sign, a missing self-service display barrier, turns into an assigned task with a deadline instead of just a flagged line item on a report. And for the general definition of the feature this page specializes, conditional audits: one template, 100+ store format variations is the collection hub for every conditional-visibility dimension Xenia supports.