WEIMI solution resource
Compliance & Age Verification
Deployment knowledge center
Compliance is a deployment requirement, not a sticker or feature that can be added after the machine is ordered.
The same machine and product may be treated differently across countries, states, cities and venues. WEIMI uses a responsibility-led review to identify what the buyer, venue, technology provider and manufacturer must confirm before specification and launch.
Implementation layer
Five layers to review
A compliant project considers the whole operating system.
- Product: legality, labeling, warnings, shelf life, tax, recalls and category restrictions
- Customer: minimum age, accessibility, consumer rights and support
- Venue: licensing, youth access, building rules, landlord and local authority permission
- Machine: electrical, radio, food contact, temperature, fire and physical safety requirements
- Data and payment: identity, privacy, cybersecurity, processor rules, receipts and records
Implementation layer
Age assurance is a workflow
A birth-date screen or “I am old enough” button does not prove age. The acceptable method must come from current destination requirements.
- Determine whether unattended sale is permitted at all
- Identify the products and ages covered
- Confirm whether the venue itself provides a lawful access boundary
- Define the approved identity/age method and data roles
- Fail closed when required verification cannot be completed
- Document audit, deletion, exception and support procedures
Implementation layer
Do not overstate certification
A component certificate, test report or conformity mark applies only to its stated scope.
- Confirm the exact model, components, destination and report validity
- Separate product certification from site installation approval
- Do not reuse evidence across modified configurations without review
- Keep technical files, labels and declarations aligned with the shipped unit
- Use qualified market specialists where local interpretation is needed
Implementation layer
Restricted-product decision gate
Vape, alcohol, adult products, medicines and other regulated categories require a documented go/no-go decision before commercial work proceeds.
- Written legal eligibility for unattended or controlled sale
- Venue and licensing approval
- Approved products and promotional presentation
- Age/access and data-protection design
- Accepted payment processor and insurer
- Ongoing regulatory-monitoring owner
Implementation layer
Operator launch record
Before opening, compile evidence that controls are assigned and tested.
- Approvals and responsible contacts
- Installation and electrical sign-off
- Product and planogram approval
- Payment, delivery and exception test results
- Cleaning, replenishment, recall and complaint procedures
- Staff training and incident escalation
Continue the decision path
Related planning resources
Connect this implementation topic to the machine, scenario and commercial decisions around it.
Apply the decision gate to an age-restricted product category.
Explore →Controlled categoryAdult wellness vendingPlan discreet retail with product, venue and market boundaries.
Explore →Technology guidePayment & software integrationDefine approved transaction, identity and exception workflows.
Explore →Project input
Information required for a project review
WEIMI can review machine-side requirements after the operator provides the legal and commercial context.
- Destination and exact venue
- Product categories and SKU examples
- Applicable licences, approvals or legal advice
- Age/access-control and data-processing plan
- Required technical standards and local installation owner
Bring the technical and commercial owners into one brief.
Discuss the project →Decision support
Compliance and age-verification FAQ
Does CE or another mark make the whole project legal?+
No. Equipment conformity is only one layer. Product, channel, venue, payment, data, installation and operator obligations must also be addressed.
Can WEIMI give legal approval for my country?+
No. WEIMI can discuss equipment and integration requirements. The operator should obtain current advice or authority confirmation for the destination and business model.
Is staff supervision always enough for restricted products?+
Not necessarily. The law may define specific access, identity, licensing or vending restrictions. The required control must be confirmed locally.
What does “fail closed” mean?+
If a required identity, age or safety control cannot complete, the restricted transaction does not dispense. The exact customer and refund flow must also be tested.
When should compliance review begin?+
Before selecting the final machine. Requirements can change the venue, interface, payment, product mix, data design and whether the project is feasible.
Market review
Check eligibility before choosing an access-control feature
Product eligibility
Confirm that the product category may be sold through the intended unattended format in the destination market.
Operator permissions
Identify the responsible business, required licenses, site permissions and age or location restrictions.
Verification design
Define the accepted method, rejection behavior, customer notices and the handling of unavailable verification.
Data handling
Review what is collected, purpose, retention, access and vendor responsibility. Minimize collection.
Operational evidence
Agree checks, audit records, refunds and escalation for verification or dispensing exceptions.
Configuration boundary
A feature does not establish legal permission
Does an age-verification reader make a deployment compliant?
No. Product eligibility, operator licensing, site restrictions and the accepted verification workflow must be reviewed for the intended market. The selected hardware is one part of that review.
What should the project brief include?
Share the country and region, product category, intended site and operating model. Describe the required verification process before selecting a reader or integration.
Your project, next
Review my market and verification requirements
Share your project brief
Start with your installation country, location and intended products. Pack dimensions, a site photo and an estimated quantity help us discuss a practical configuration.
Early-stage enquiries are welcome. Configuration and local requirements are confirmed for each project.