Current concept for a customer-facing lobby intake screen. Final hardware is not confirmed.
Giosk FROG (Coming Soon)
Giosk FROG is a coming-soon lobby intake concept for dispensaries. The planned workflow covers ID data parsing, customer-information prepopulation, queue entry, and a barcode handoff before checkout. Final hardware, integrations, privacy requirements, and availability have not been confirmed.
Lobby intake before checkout starts
Inspect the coming-soon check-in hardware: 21 inch PCAP touchscreen, facial-recognition camera, ID scanner, receipt pass printer, proximity sensor, Windows PC, and the handoff path into staff, kiosk, POS, and loyalty workflows.
Giosk FROG (Coming Soon)
Coming-soon lobby check-in kiosk for ID data parsing, queueing, and customer handoff.
Core Features:
- 21-inch PCAP touchscreen
- Facial recognition camera
- ID scanner with Veriscan handoff
- Receipt printer for profile barcode handoff
- Proximity sensor for walk-up detection and idle-screen media
- POS, loyalty, queueing, and self-service handoff paths
Planning baseline
Plan FROG as a possible front-desk intake station, not a floor checkout kiosk. The fit conversation starts where customers arrive, present an ID, join the queue, and pass basic information into the next supported workflow.
Display conceptplanned 21 inch customer-facing touchscreen
Placement conceptcounter-based lobby intake unit
Workflow conceptarrival, ID data parsing, queue entry, and profile prepopulation
Handoff conceptprinted barcode for a supported staff, kiosk, POS, or loyalty workflow
Integration pathevery scanner, software, and downstream-system connection requires validation
Coming Soon notefinal enclosure, dimensions, privacy requirements, hardware, integrations, and launch availability remain subject to confirmation
Plan the lobby intake workflow
FROG is intended to help operators explore a more repeatable path from arrival to the next step in service. The current concept focuses on reducing repeated data entry and mapping a clear queue and barcode handoff without representing unconfirmed validation capabilities as available.
Join the Coming Soon List- Repeated customer-information entry or manual queue setup slows the path from arrival to service
- The store wants to evaluate a consistent lobby intake process before selecting hardware or integrations
- Customer information should move into a supported downstream workflow without asking the shopper to start over
A clearer intake plan starts at the door
The entrance can create repeated administrative work for a store team. The FROG concept is being planned around parsing ID data, prepopulating customer information, creating a queue entry, and printing a barcode that can support the next step after the required integrations are confirmed.
Parse and prepopulate, enter the queue, then print and hand off.
Lobby flow, privacy requirements, hardware, and integrations must be reviewed before any deployment is proposed.
Parse. Queue. Hand off.
The coming-soon concept is organized around the first minutes of a retail visit and the information that needs to move into the next supported workflow.
Parse and prepopulateRead supported ID data and use it to prepopulate customer-information fields.
Enter the queueCreate the planned queue entry after the store confirms its intake rules and connected systems.
Print and continueUse a planned barcode receipt to pass the record into a supported staff or self-service workflow.
Capabilities that still require validation
This page describes a coming-soon workflow concept, not a final product specification. Dispensify will not represent identity verification, image matching, fake-ID detection, Veriscan support, or specialized UV, hologram, infrared, watermark, or anti-spoofing checks as available unless those capabilities are documented and tested in the final configuration.
- Final scanner model and supported ID data fields
- Camera purpose, privacy requirements, data retention, and any image-processing behavior
- Queueing, POS, loyalty, and self-service integration compatibility
- Barcode format and downstream record-retrieval behavior
- State-specific privacy, accessibility, and deployment requirements
Coming Soon fit review
Before any Giosk FROG configuration is proposed, the planning conversation should map the actual lobby workflow: where customers enter, what information is collected today, which systems need the handoff, and where the line forms during rush periods.
Confirm front-door fitentry flow, lobby traffic, customer-information intake, and handoff location
Confirm system pathPOS, loyalty, queueing, and self-service workflow requirements
Confirm validation scopehardware, integrations, privacy review, barcode behavior, and data handling
Confirm launch timingproduct availability, final dimensions, install path, and rollout order
Frequently Asked Questions
01Is Giosk FROG available now?
No. Giosk FROG is a coming-soon concept. Dispensify must confirm the final hardware, integrations, dimensions, privacy requirements, and launch availability before proposing a configuration.
02Is FROG a checkout kiosk?
No. The current concept is for lobby intake, ID data parsing, customer-information prepopulation, queue entry, and barcode handoff. Checkout would happen downstream in a separately supported workflow.
03Where would FROG be placed?
The planned placement is a reception desk or lobby intake point where customers already present information and join the queue. Final placement depends on the store layout and confirmed hardware.
04Does FROG verify an ID or customer identity?
No verification claim is being made at this stage. The planned scanner workflow parses supported ID data and can prepopulate customer-information fields. Identity, age, or document-authenticity verification would require separately documented and tested capabilities.
05Are image matching, fake-ID detection, or Veriscan included?
Those capabilities are not confirmed. Earlier concepts referenced camera-based matching, document-security checks, and a third-party validation path, but Dispensify will not present them as supported unless the final hardware and integration are documented and tested.
06What would the barcode receipt do?
The planned barcode would hand a customer record into the next supported workflow. Its exact format, the systems that can read it, and the retrieval behavior still require integration validation.
07Can FROG connect to POS, loyalty, queueing, or kiosk workflows?
Those are planned handoff paths, not confirmed integrations. The fit review must validate each specific platform, data field, workflow, and deployment requirement before it is quoted.
08What should a dispensary confirm before joining the Coming Soon list?
Confirm store count, current intake workflow, POS, loyalty and queueing systems, privacy-review needs, lobby line formation, and launch timing. That gives Dispensify enough context to plan a responsible fit review.
Configuration planning
Spec it for your floor.
Tell us which unit, payment path, cash workflow, and site constraints you’re working with. We’ll help map the setup before you commit.