HomeModulesPoint of SalePOS Age Verification | Restricted Products, ID Check & Refusal Register
POS Age Verification | Restricted Products, ID Check & Refusal Register
Point of SaleAuraOdoo Verified

POS Age Verification | Restricted Products, ID Check & Refusal Register

Stop under-age sales at the till: flag alcohol, tobacco, vaping and

Technical Specifications & Compatibility

Technical Module Name
Supported Odoo Versions
v19.0
License
Odoo
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
1315 lines (Python / XML / JS)

Overview & Description

Odoo 19 Community and Enterprise OPL-1 Version 19.0.1.0.0 POS Age Verification Flag alcohol, tobacco, vaping and pharmacy lines, hold the cashier before payment, record who approved each sale, and keep the refusal register an inspector asks for. Selling to a minor is the kind of mistake that costs a licence. This makes the check part of the till instead of part of someone's memory. Module Overview What this module does. The check belongs in the till Standard Point of Sale has no concept of a restricted product. Nothing stops a sale, nothing records that an ID was seen, and nothing proves afterwards that your staff refused the sales they should have refused. This module adds all three. Stopped at payment, not mid-scan Interrupting every restricted scan trains cashiers to dismiss dialogs without reading them. The cashier is asked once, at validation, for the strictest rule on a complete basket, using the pre-payment gate that Point of Sale provides for exactly this. Privacy by default. Dates of birth are not stored. The age is computed at the till and only the decision is kept: the threshold, the age it was decided on, the method and who decided. A shop whose regulator demands the date can switch that on. Key Features Everything included in the module. What Counts As Restricted Restrictions carry a minimum age and a cashier prompt Point a rule at POS categories; child categories are included Or flag a single product, which always wins over its categories Where two rules could apply, the higher age wins Restrictions can be limited to specific shops Restricted tiles carry an age badge on the product grid The Check At The Till Held before payment, never interrupted mid-scan Asked once for the strictest rule, not once per item Approve on a date of birth, with the age shown in plain words Or approve on a sighted document: passport, licence, national ID An under-age date disables Approve outright Dismissing the dialog leaves the sale unpaid Refusing A Sale Refuse in one tap, with a reason Only the restricted items are removed; the rest of the sale stays The tender is cleared, because the total just changed The cashier is returned to the order, ready to carry on The refusal is logged the moment it happens Manager override available, off by default, and always logged The Register Every check recorded: approved, refused or overridden Cashier, shop, session, rule, age required, products and reason The order reference is copied as text, so evidence outlives the order A Refusal Register view and a printable PDF for an inspector Filters by result, cashier, restriction, shop, today, this month Entries cannot be edited or deleted by anybody, manager included Privacy By Default Dates of birth are not stored; only the decision is kept The date can be stored per shop where a regulator demands it Only the type of document is recorded, never its number The printed register carries no customer identity It records the shop's conduct, not the person turned away No data leaves your Odoo instance Enforcement The till blocks the sale at validation The server blocks it again on sync, as a backstop A restricted order with no recorded check is refused outright Catches a tab opened before the rule existed, or a second till Catches a replayed offline queue, without duplicating the check Nothing happens where the feature is off or nothing is restricted Business Benefits Why it matters day to day. Protect The Licence The sale is held by the software rather than by a cashier remembering, so a busy Friday night is no more dangerous than a quiet Tuesday. Evidence For Inspection A printable register of every refusal, with the cashier, the shop and the reason, produced from records nobody can edit. Train Nobody To Click Through One prompt per basket at payment, not one per scan, so the dialog still means something when it appears. Keep The Rest Of The Sale A refusal removes the restricted lines only, so the customer still buys their bread and the queue keeps moving. Screenshots A tour of the interface. Age Badge On The Product Grid Screenshot Placeholder Restricted tiles carrying their minimum age, so the cashier sees it coming. The Verification Dialog Screenshot Placeholder The prompt, the restricted items, date of birth or ID, and the three buttons. Refusal Register Screenshot Placeholder Every refusal with cashier, shop, rule and reason, filterable by period. Age Restrictions Setup Screenshot Placeholder A rule with its minimum age, categories, prompt and the shops it applies to. Workflow What happens at the till. The cashier scans normally. Restricted tiles show an age badge, and nothing interrupts the scan. The basket is built exactly as it always was. Validate is pressed. The till works out the strictest rule on the whole order and holds the sale before any payment is taken. The dialog asks once. It shows the required age, your prompt and which items triggered it, with a choice of a date of birth or a sighted document. Approve, override or refuse. An under-age date disables Approve. An override, where allowed, records the manager's name. A refusal takes one tap and a reason. On refusal the sale continues. Only the restricted lines are removed, the tender is cleared because the total changed, and the cashier is back on the order. The register is written. Every outcome is logged, refusals immediately, and the server checks again when the order syncs. The Three Outcomes Outcome What happens to the sale What is recorded Approved Proceeds to payment as normal Cashier, rule, required age, age decided on, method Overridden Proceeds, only where overrides are enabled All of the above, plus the approving manager Refused Restricted lines removed, tender cleared, sale continues All of the above, plus the refusal reason, logged at once Dialog dismissed Sale is left unpaid rather than let through Nothing; the cashier must still decide Configuration Settings, menus and access. Point of Sale Settings, Per Shop Setting Default What it does Age Verification Off Turns the whole feature on for this shop Default prompt Ask for ID if they look under 25 The line the cashier reads when no rule sets its own Record the ID type On Keeps the kind of document sighted, never its number Allow manager override Off Permits an override, always logged with the manager's name Store the date of birth Off Off by default; enable only where a regulator demands it Print on receipt On Adds an age-verified line to the printed receipt Menu Structure Menu Purpose Age Verification, then Refusal Register The refusals, filterable and printable for an inspector Age Verification, then All Age Checks Every outcome, approved and overridden included Age Verification, then Age Restrictions The rules themselves, managers only Product form Flag one product, overriding its categories Who Can Do What Action POS User POS Manager Read the register Yes Yes Edit age restrictions No Yes Edit or delete a recorded check No No The standard Point of Sale roles are used, so there are no extra groups to assign. Multi-company record rules apply to restrictions and checks. Starter Restrictions Included Restriction Minimum age Alcohol 18 Tobacco and Vaping 18 Spirits 21 Pharmacy and Solvents 16 The starters are examples, not legal advice. They ship unpointed, so nothing is enforced until you attach them to your own categories and set the ages your jurisdiction and your licence actually require. Technical Details Models, dependencies and design. Module Information Technical Name pos_age_verification_aura Version 19.0.1.0.0 Category Sales / Point of Sale License OPL-1 Dependencies point_of_sale only External Libraries None beyond a standard Odoo installation External Service None. No data leaves your Odoo instance. Automated Tests 22 tests, including two browser tours driving the real till Models Model Description pos.age.restriction A rule: minimum age, categories, prompt and shops pos.age.check One recorded outcome, and the register's row pos.config Extended with the six per-shop settings pos.order Extended with the server-side backstop and an Age Check tab product.template Extended so one product can be flagged directly Design Notes Core's pre-payment gate is used. Not a custom interception, so the dialog appears where Point of Sale intends it and the rest of the till behaves normally. The server checks a second time. An order can arrive from a tab opened before the rule existed, from another till, or from a replayed offline queue. Refusals are written immediately. A refused customer usually walks out, so a register that waited for a paid order would miss what it exists to prove. The register is evidence, so it is immutable. No role can edit or delete a check, and the order reference is copied onto it as text so it survives the order. Resolution is deterministic. A product-level flag beats its categories, child categories inherit from their parent, and where two rules could both apply the higher age wins, never whichever record happened to be created first. Compatibility Where the module runs. Item Supported Odoo Version 19.0 Current Hosting Odoo.sh, On-Premise and any self-managed deployment Point of Sale Standard POS, including restaurant and shop configurations Offline Mode Yes, the rules are loaded into the session and enforced offline Multi-Company Yes, with record rules on restrictions and checks Multi-Shop Yes, settings and restrictions are both per Point of Sale Multi-Language Yes, all labels, prompts and messages are translatable Touchscreen and Tablet Yes, the dialog is built for the POS interface Supported Editions Both editions, one code base. Community Edition Supported Depends on Point of Sale alone, so it runs on a plain Community installation with nothing else required. Enterprise Edition Supported Runs unchanged on Enterprise, alongside the standard Point of Sale modules and hardware integrations. Odoo.sh Supported No extra Python packages to install, so it deploys with no change to your build configuration. Installation Four steps to an enforced till. Copy the module. Place the pos_age_verification_aura folder in your Odoo addons path, then update the apps list from developer mode. Install POS Age Verification. Search for it in Apps and install. Only Point of Sale is required. Enable it for a shop. Point of Sale, then Configuration, then Settings. Pick the shop and switch on Age Verification, then review the five other settings. Point the rules at your products. Open Age Restrictions, attach each rule to your own POS categories, and adjust the ages to your jurisdiction. Nothing changes at the till until a shop has the setting on and at least one product resolves to a restriction, so the module can be installed and configured safely during trading hours. Frequently Asked Questions The questions asked most often. Because interrupting every restricted scan teaches cashiers to dismiss the dialog without reading it. Holding the sale once, at validation, on a complete basket and for the strictest rule on it, keeps the prompt meaningful and keeps the queue moving. Not by default. The age is computed at the till and only the decision is kept: the age required, the age it was decided on, the method and who decided. Storing the date is a per-shop switch for regulators who demand it. Only the type of document is ever recorded, never its number. Only the restricted lines are removed. Everything else stays, the tender is cleared because the total has changed, and the cashier is returned to the order to take payment for what the customer may still buy. An under-age date of birth disables Approve outright, and dismissing the dialog leaves the sale unpaid rather than letting it through. The server then refuses any restricted order that arrives with no recorded check, which catches a second till, a tab opened before the rule existed and a replayed offline queue. Manager override is off by default and always logged with the manager's name. A flag on the product itself always wins over its categories. Otherwise the higher age wins, never whichever rule was created first. Child categories are included automatically, so a rule on Alcohol covers Beer and Spirits without listing them. No. Recorded checks cannot be edited or deleted by anyone, managers included, because the register only has value as evidence if nobody can tidy it. The order reference is copied onto each entry as text, so it still reads correctly even if the order itself is gone. Yes. The restrictions are loaded into the session, so the till enforces them with no connection. When the queue is replayed the server validates the orders again, and re-syncing an order never duplicates its check. It enforces your policy and records what happened; it does not know your jurisdiction. Minimum ages, whether an override is lawful, and how long records must be kept all differ by country and by licence. Set the ages, decide whether overrides are allowed, and check the retention rules that apply to you. Changelog Release history. Version 19.0.1.0.0 Initial Release Age restrictions on POS categories, with child categories included Product-level flags that override their categories Highest-age-wins resolution where several rules could apply Restrictions limitable to specific shops Age badges on restricted product tiles Verification held at payment, once per basket, for the strictest rule Approval by date of birth or by sighted document type Under-age dates disable approval; dismissal leaves the sale unpaid Manager override, off by default and logged by name One-tap refusal that removes only the restricted lines Immutable register of every check, with a printable refusal PDF Server-side backstop on order sync, safe against replays Six per-shop settings, with dates of birth not stored by default Four starter restrictions and an optional receipt line 22 tests, including two browser tours driving the real till Support We answer, and we keep our modules current. Email odooaura@gmail.com Website www.auraodoo.tech YouTube youtube.com/@Auraodoo Free support for bug fixes on the Odoo version you downloaded. Customisation and installation help available on request. Aura Odoo Tech Odoo modules built to be understood, not just installed. Odoo 19 OPL-1 pos_age_verification_aura www.auraodoo.tech | odooaura@gmail.com | youtube.com/@Auraodoo

Key Capabilities & Features

  • Restrictions carry a minimum age and a cashier prompt
  • Point a rule at POS categories; child categories are included
  • Or flag a single product, which always wins over its categories
  • Where two rules could apply, the higher age wins
  • Restrictions can be limited to specific shops
  • Restricted tiles carry an age badge on the product grid
  • Held before payment, never interrupted mid-scan
  • Asked once for the strictest rule, not once per item
  • Approve on a date of birth, with the age shown in plain words
  • Or approve on a sighted document: passport, licence, national ID
  • An under-age date disables Approve outright
  • Dismissing the dialog leaves the sale unpaid
  • Refuse in one tap, with a reason
  • Only the restricted items are removed; the rest of the sale stays
  • The tender is cleared, because the total just changed
  • The cashier is returned to the order, ready to carry on
  • The refusal is logged the moment it happens
  • Manager override available, off by default, and always logged
  • Every check recorded: approved, refused or overridden
  • Cashier, shop, session, rule, age required, products and reason
  • The order reference is copied as text, so evidence outlives the order
  • A Refusal Register view and a printable PDF for an inspector
  • Filters by result, cashier, restriction, shop, today, this month
  • Entries cannot be edited or deleted by anybody, manager included
  • Dates of birth are not stored; only the decision is kept
  • The date can be stored per shop where a regulator demands it
  • Only the type of document is recorded, never its number
  • The printed register carries no customer identity
  • It records the shop's conduct, not the person turned away
  • No data leaves your Odoo instance
  • The till blocks the sale at validation
  • The server blocks it again on sync, as a backstop
  • A restricted order with no recorded check is refused outright
  • Catches a tab opened before the rule existed, or a second till
  • Catches a replayed offline queue, without duplicating the check
  • Nothing happens where the feature is off or nothing is restricted
  • The cashier scans normally. Restricted tiles show an age badge, and nothing interrupts the scan. The basket is built exactly as it always was.
  • Validate is pressed. The till works out the strictest rule on the whole order and holds the sale before any payment is taken.
  • The dialog asks once. It shows the required age, your prompt and which items triggered it, with a choice of a date of birth or a sighted document.
  • Approve, override or refuse. An under-age date disables Approve. An override, where allowed, records the manager's name. A refusal takes one tap and a reason.
  • On refusal the sale continues. Only the restricted lines are removed, the tender is cleared because the total changed, and the cashier is back on the order.
  • The register is written. Every outcome is logged, refusals immediately, and the server checks again when the order syncs.
  • Core's pre-payment gate is used. Not a custom interception, so the dialog appears where Point of Sale intends it and the rest of the till behaves normally.
  • The server checks a second time. An order can arrive from a tab opened before the rule existed, from another till, or from a replayed offline queue.
  • Refusals are written immediately. A refused customer usually walks out, so a register that waited for a paid order would miss what it exists to prove.
  • The register is evidence, so it is immutable. No role can edit or delete a check, and the order reference is copied onto it as text so it survives the order.
  • Copy the module. Place the pos_age_verification_aura folder in your Odoo addons path, then update the apps list from developer mode.
  • Install POS Age Verification. Search for it in Apps and install. Only Point of Sale is required.
  • Enable it for a shop. Point of Sale, then Configuration, then Settings. Pick the shop and switch on Age Verification, then review the five other settings.
  • Point the rules at your products. Open Age Restrictions, attach each rule to your own POS categories, and adjust the ages to your jurisdiction.
  • Age restrictions on POS categories, with child categories included
  • Product-level flags that override their categories
  • Highest-age-wins resolution where several rules could apply
  • Restrictions limitable to specific shops
  • Age badges on restricted product tiles
  • Verification held at payment, once per basket, for the strictest rule
  • Approval by date of birth or by sighted document type
  • Under-age dates disable approval; dismissal leaves the sale unpaid
  • Manager override, off by default and logged by name
  • One-tap refusal that removes only the restricted lines
  • Immutable register of every check, with a printable refusal PDF
  • Server-side backstop on order sync, safe against replays
  • Six per-shop settings, with dates of birth not stored by default
  • Four starter restrictions and an optional receipt line
  • 22 tests, including two browser tours driving the real till
  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.

Screenshots & Previews

1 image available
POS Age Verification | Restricted Products, ID Check & Refusal Register screenshot 1
Expand Preview
The AuraOdoo Quality Guarantee
100% Tested

Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.

Clean Architecture

Built according to official Odoo guidelines and PEP 8 standards with zero bloat.

Dedicated Support

Free installation assistance and quick bug turnaround from our team.