oca-pos/odoo-bringout-oca-pos-pos_partner_firstname/pos_partner_firstname
Ernad Husremovic 377f346a99 Move all OCA POS modules from oca-technical to dedicated oca-pos submodule
Reorganized 74 POS-related modules for better structure:
- Moved all odoo-bringout-oca-pos-* packages from packages/oca-technical/
- Now organized in dedicated packages/oca-pos/ submodule
- Includes payment, receipt, loyalty, order, product, and partner modules
- Maintains all module functionality while improving project organization

This creates a cleaner separation between general technical modules
and Point of Sale specific functionality.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-08-30 17:15:35 +02:00
..
i18n Move all OCA POS modules from oca-technical to dedicated oca-pos submodule 2025-08-30 17:15:35 +02:00
models Move all OCA POS modules from oca-technical to dedicated oca-pos submodule 2025-08-30 17:15:35 +02:00
readme Move all OCA POS modules from oca-technical to dedicated oca-pos submodule 2025-08-30 17:15:35 +02:00
static Move all OCA POS modules from oca-technical to dedicated oca-pos submodule 2025-08-30 17:15:35 +02:00
__init__.py Move all OCA POS modules from oca-technical to dedicated oca-pos submodule 2025-08-30 17:15:35 +02:00
__manifest__.py Move all OCA POS modules from oca-technical to dedicated oca-pos submodule 2025-08-30 17:15:35 +02:00
README.rst Move all OCA POS modules from oca-technical to dedicated oca-pos submodule 2025-08-30 17:15:35 +02:00

=====================
POS Partner Firstname
=====================

.. 
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !! This file is generated by oca-gen-addon-readme !!
   !! changes will be overwritten.                   !!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !! source digest: sha256:48b300a1b3c09fed7e3c02c3b18fb619ee317caeb739ceb81ba1a91bd69eadfd
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
    :target: https://odoo-community.org/page/development-status
    :alt: Beta
.. |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/16.0/pos_partner_firstname
    :alt: OCA/pos
.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png
    :target: https://translation.odoo-community.org/projects/pos-16-0/pos-16-0-pos_partner_firstname
    :alt: Translate me on Weblate
.. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png
    :target: https://runboat.odoo-community.org/builds?repo=OCA/pos&target_branch=16.0
    :alt: Try me on Runboat

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

The module adds the support of the fields of the partner_firstname module within the point of sale interface,
allowing to view and edit them in the given customer view.

**Table of contents**

.. contents::
   :local:

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

Some features we would need to cover in the future:

* When the field ``name`` is set to be readonly the module must prevent the field to have red border and the possibility to have the cursor, and change the background color of the name field could be user friendly.
* In back office, the name *OR* the surname is mandatory. In front office, the name *AND* the surname is mandatory. Should be great to have a similar behaviour.
* In back office, default is "company". In front office, default is "individual". The behaviour should however depend by *B2B* or *B2C* setting in order to set the right default.
* In individual mode, in back office, it is possible to select the parent company. In individual mode, in front office, it is not possible. However we would also have to say that odoo doesn't permit the parent company selection.

The ticket referencing the above information can be read at https://github.com/OCA/pos/pull/775

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 to smash it by providing a detailed and welcomed
`feedback <https://github.com/OCA/pos/issues/new?body=module:%20pos_partner_firstname%0Aversion:%2016.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
~~~~~~~

* Roberto Fichera

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

* Roberto Fichera <roberto.fichera@levelprime.com>
* Lorenzo Battistini (https://takobi.online)
* Dhara Solanki <dhara.solanki@initos.com>

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.

.. |maintainer-robyf70| image:: https://github.com/robyf70.png?size=40px
    :target: https://github.com/robyf70
    :alt: robyf70

Current `maintainer <https://odoo-community.org/page/maintainer-role>`__:

|maintainer-robyf70| 

This module is part of the `OCA/pos <https://github.com/OCA/pos/tree/16.0/pos_partner_firstname>`_ project on GitHub.

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