POS Customer Age Warning
This module enhances Odoo’s Point of Sale (POS) by introducing an age verification system. When a customer is selected, their age (based on their date of birth) is checked against the predefined “Age Warning” threshold set in the POS configuration.
If the customer’s age is less than or equal to this threshold, their name will be displayed in red on the POS interface to alert the cashier.
Use Cases
Case 1: Alcohol Sales
“Age Warning” threshold set to 18 years.
A customer born on June 5, 2010, is selected in March 2025.
Age: 2025 - 2010 = 14 years old.
Result: Their name appears in red, warning the cashier.
Case 2: Customer is of Legal Age
“Age Warning” threshold set to 18 years.
A customer born on February 2, 2003, is selected in March 2025.
Age: 2025 - 2003 = 22 years old.
Result: No warning, as the customer is above the age limit.
Case 3: Gaming Center (No entry for under 16s)
“Age Warning” threshold set to 16 years.
A customer born on July 15, 2009, is selected in March 2025.
Age: 2025 - 2009 = 15 years old (birthday in July).
Result: Their name appears in red because they are not yet 16.
Table of contents
Configuration
Go to POS Settings
In the POS Interface section there is the Age Warning setting
Enter the age warning
The warning will appear in POS interface for the customer with this age or younger.
Usage
Open the POS interface and if the age warning setting apply to the customer, the customer’s name will appear in red color.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Vehiana Tepuhiarii <vehi@invitu.com>
-
Parvez Qureshi <parvez.qureshi@serpentcs.com>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/pos project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-pos-customer-age-warning 17.0.0.1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_pos_customer_age_warning-17.0.0.1.0.4-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_pos_customer_age_warning-17.0.0.1.0.4-py3-none-any.whl |
Release files / odoo_addon_pos_customer_age_warning-17.0.0.1.0.4-py3-none-any.whl
| Download URL | odoo_addon_pos_customer_age_warning-17.0.0.1.0.4-py3-none-any.whl |
|---|---|
| Size | 32.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
73db1efacce7a347c78ae97bd0a4d140b1dd7e5da989e58a47d756710c481e1e
|
|
BLAKE2b-256 checksum How to use checksums |
c43d6c2e4f9b8f3571aeaec691a8f524efa71ec5e25b5c76c294074ead068100
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-pos-customer-age-warning 17.0.0.1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
