pos_hr Receipt Replace User By Trigram
Link module between pos_receipt_replace_user_by_trigram and pos_hr
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Adds a trigram field to employees so the Point of Sale can show a short code instead of the cashier's name on receipts. It is a technical link module that installs automatically.
This is a hidden technical module that connects two other modules: the one that replaces the cashier name on POS receipts with a short code (trigram), and the one that lets employees log into the Point of Sale.
What it changes for users:
- Employees now have a pos_trigram field, a short text code taken from their related contact record.
- When the Point of Sale loads employee data (for example when a cashier logs in), this short code is included in the data sent to the POS screen.
Where it appears:
- The field is added to the employee model hr.employee.base, so it is visible wherever employee data is shown, including the related contact.
- The Point of Sale session loader is extended so the code is available in the POS interface.
Business rules and automatic behaviour: - The value is not typed directly on the employee: it is a related field that reads the code stored on the employee's work contact. Changing the contact's code updates the employee automatically. - There are no checks, restrictions, emails or scheduled jobs in this module.
Areas touched:
- Employees (hr.employee.base) and Point of Sale sessions (pos.session).
Because this module only links existing features, it does not add menus, buttons or reports of its own.
Depends on
Models and fields (1)
- hr.employee.base · extends an existing modelpos_trigram
Text generated by AI (DeepSeek) from reading the Odoo 16.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-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/pos.
terminal Installation and usage
No verified informationInstallation 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.
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.