OdooWiki OCA HUB

Pos Partner Second Lastname

pos_partner_second_lastname folder_open OCA/pos open_in_new
Uncategorised License: AGPL-3

Edit and manage second last name inside Point of Sale Frontend.

auto_awesome What this module does

AI-generated from the code · Odoo 17.0

Adds a "Second Lastname" field to the customer form in the Point of Sale, so cashiers can capture and edit a customer's second surname directly at the till.

This module extends the Point of Sale customer editor so that a second last name can be entered and changed from the POS screen.

  • In the Point of Sale, when you open a customer's details (the partner editor screen), a new "Second Lastname" input appears next to the normal last name, but only for people, not for companies.
  • The value typed there is saved together with the customer's other name data and is loaded into the POS session, so it is available on the till.
  • The module also hooks into the name-completeness check used by the POS customer form: a person is no longer considered fully named just because the first last name is filled in; the second last name is taken into account as well.
  • When the POS builds the customer's full last name, the second last name is appended after the first one, separated by a space.

It works together with the modules that add first name and second last name handling to contacts and to the POS, and it touches the Point of Sale session loading of customer data and the POS customer editing screen. No new menus, reports, emails or scheduled actions are added.

Text generated by AI (DeepSeek) from reading the Odoo 17.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.