pos/pos_restricted_customer_list/README.rst

=============================
POS: restricted customer list
=============================

.. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !! This file is generated by oca-gen-addon-readme !!
   !! changes will be overwritten.                   !!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

.. |badge1| image:: https://img.shields.io/badge/maturity-Production%2FStable-green.png
    :target: https://odoo-community.org/page/development-status
    :alt: Production/Stable
.. |badge2| image:: https://img.shields.io/badge/licence-AGPL--3-blue.png
    :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
    :alt: License: AGPL-3
.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fpos-lightgray.png?logo=github
    :target: https://github.com/OCA/pos/tree/9.0/pos_restricted_customer_list
    :alt: OCA/pos
.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png
    :target: https://translation.odoo-community.org/projects/pos-9-0/pos-9-0-pos_restricted_customer_list
    :alt: Translate me on Weblate
.. |badge5| image:: https://img.shields.io/badge/runbot-Try%20me-875A7B.png
    :target: https://runbot.odoo-community.org/runbot/184/9.0
    :alt: Try me on Runbot

|badge1| |badge2| |badge3| |badge4| |badge5| 

In the point of sale, many installations work with cash registers with
anonymous customers. In that case, loading thousands, or even tens of
thousands of customers to each cash register is completely useless, and also
a huge danger for leaking privacy sensible data.

This module will limit the download of customer data to only those customers
where this has been specifically requested.

**Table of contents**

.. contents::
   :local:

Usage
=====

To allow a customer to be displayed in the PoS, just check the 'Available in POS' field.

Development
===========

The module will add a flag 'available_in_pos' to res.partner. It will override
to domain of customers downloaded with pos to only download the partners
where this flag has been set.

Known issues / Roadmap
======================

I see two obvious extensions to the functionality already developed:
1. Add back on demand customer lookup (only when online);
2. Make customers available to pos, dependent on the pos session or user.
In pos.config or res.users (or both) there could be a selection field customer_loading with values:

 - 'no_one': disable customer loading (usefull for self service pos, without customer feature)
 - 'selection': the feature now implemented (load only checked customers) (default value)
 - 'all': for super cashier, (after sale PoS), etc.

Bug Tracker
===========

Bugs are tracked on `GitHub Issues <https://github.com/OCA/pos/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 <https://github.com/OCA/pos/issues/new?body=module:%20pos_restricted_customer_list%0Aversion:%209.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.

Do not contact contributors directly about support or help with technical issues.

Credits
=======

Authors
~~~~~~~

* Therp BV

Contributors
~~~~~~~~~~~~

* Ronald Portier <ronald@therp.nl>

Maintainers
~~~~~~~~~~~

This module is maintained by the OCA.

.. image:: https://odoo-community.org/logo.png
   :alt: Odoo Community Association
   :target: https://odoo-community.org

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 <https://github.com/OCA/pos/tree/9.0/pos_restricted_customer_list>`_ project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.