Point of Sale - Load Picking by Partner Name improvment
This module extends the functionality of PoS Picking Load module to improve the loading time during the picking load.
For that purpose, its store partner name on each picking and search on that new field, instead of making a search on partner_id field.
auto_awesome What this module does
AI-generated from the code · Odoo 12.0Speeds up loading pickings in the Point of Sale by searching on a stored partner name field instead of the partner record. Users searching a customer name in the PoS picking load screen get faster results.
This module improves the picking load feature of the Point of Sale. When a user searches pickings in the PoS, the search now also matches the customer name stored directly on each picking.
- A new field
partner_nameis added onstock.picking, automatically filled from the linked partner's name and stored in the database. - The picking search used by the PoS is extended so that the typed text is compared against the picking reference (
name), the source document (origin) and the newpartner_namefield. - Because the customer name is stored on the picking itself, the search no longer needs to go through the partner record, which makes loading the list of pickings faster.
- When the module is installed, existing pickings are filled in with their partner's name so that old records are searchable too.
No new menus or screens are added; the change appears inside the existing PoS picking load screen. No new business rules, emails or scheduled jobs are introduced.
Depends on
Models and fields (1)
- stock.picking · extends an existing modelpartner_name
Text generated by AI (DeepSeek) from reading the Odoo 12.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 12.0
Confirmed on 2026-11-03 in branch 12.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.