Point of Sale Require Customer
This module was written to extend the functionality of odoo pos and allows you to require a customer for each pos order. In the pos session configuration, you can choose to require the customer for pos orders.
If a customer is not selected, the pos ui will display an error message. In the backend the customer field is required when needed.
Two new options are available:
Customer ‘Required before starting the order’;
Customer ‘Required before paying’;
‘Required before starting the order’ Option
In the frontend PoS, the default screen is the screen to select customers.
Users are not allowed to start selling before having selected a customer;
Users can not ‘deselect a customer’, only select an other one;
‘Required before paying’ Option
In the frontend PoS, the user can start selling, but if the user tries to make payment and if a customer is not selected, the pos ui will display an error message.
Table of contents
Configuration
To configure this module, you need to:
go to point of sale -> configuration -> point of sales
select the point of sales you want configure
- search for the “Require Customer” and choose between the following values:
‘Optional’; (this module has no effect on this PoS config)
‘Required before paying’;
‘Required before starting the order’;
Usage
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 smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Jos De Graeve <Jos.DeGraeve@apertoso.be>
Sylvain LE GAL <https://twitter.com/legalsylvain>
Pedro M. Baeza <pedro.baeza@gmail.com> ( reviews & feedback )
Druidoo <https://www.druidoo.io>
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 odoo12-addon-pos-customer-required 12.0.1.0.1
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 |
|---|---|---|---|---|
| odoo12_addon_pos_customer_required-12.0.1.0.1-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_pos_customer_required-12.0.1.0.1-py3-none-any.whl |
Release files / odoo12_addon_pos_customer_required-12.0.1.0.1-py3-none-any.whl
| Download URL | odoo12_addon_pos_customer_required-12.0.1.0.1-py3-none-any.whl |
|---|---|
| Size | 37.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
da2d6e960b3da849a89ff53dd3b995ba38d5b16af828fce9c4f43ac3722c421d
|
|
BLAKE2b-256 checksum How to use checksums |
c65235d651b5193ed0a6ea1fd88f5c6a64257ffa526b1d725c9ee35910d45ff4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo12-addon-pos-customer-required 12.0.1.0.1
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.
