This module allows Point of Sale users to select the monitor where the local customer display should be opened.
The selected monitor is stored in the browser for each Point of Sale configuration. When the customer display is opened again, the module automatically places and resizes the window on the previously selected monitor.
The module uses the browser Window Management API when available and keeps the standard Odoo customer display rendering and synchronization.
auto_awesome What this module does
AI-generated from the code · Odoo 17.0Lets Point of Sale users choose which monitor shows the customer display, and remembers that choice per Point of Sale so the display reopens on the same screen.
This module adds a new option in the Point of Sale interface to pick the monitor used for the customer-facing display. It appears as a menu entry called "Select customer display screen" in the Point of Sale navbar, but only when the Point of Sale is configured to show a customer display directly (not through a proxy).
When you click it, Odoo asks the browser for the list of connected screens and shows a popup where you can select one. The list shows each screen's label, size, and whether it is the primary screen. After you confirm, the customer display window is closed and reopened on the chosen screen, sized to fill it.
The choice is saved in the browser for that specific Point of Sale, so the next time the customer display opens it automatically goes back to the same monitor. If the saved screen is not available, the module tries to find the best match based on size and position, or falls back to a non-primary screen.
If the browser does not support screen selection or permission is denied, an error message explains what to do. The module only changes the customer display window placement; it does not alter the display content or the Point of Sale data.
Depends on
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-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 17.0
Confirmed on 2026-11-03 in branch 17.0 of OCA/pos.
terminal Installation and usage
OCA documentation · Odoo 17.0Configuration
Source · Odoo 17.0To use this module:
- Go to
Point of Sale > Configuration > Settings. - Open the Point of Sale configuration that you want to use.
- Enable the
Customer Displayoption and save the configuration. The monitor selection option is only available for local customer displays. It is not shown whenCustomer Facing Display via Proxyis enabled. - Open the Point of Sale using a recent Chromium-based browser.
- Make sure Odoo is served over HTTPS.
- Open the Point of Sale menu.
- Click on
Select customer display screen. - Grant the browser permission to manage windows and screens.
- Select the monitor that should be used for the customer display.
The selected monitor is stored locally in the browser and is associated with the current Point of Sale configuration.
The permission and monitor selection are specific to the browser profile and device being used. They may need to be configured again if the browser site data, permissions, or local storage are cleared.
Usage
Source · Odoo 17.0Once a monitor has been selected, use the standard Odoo customer display button to open the customer display.
The module will:
- Detect the screens currently connected to the device.
- Find the screen that best matches the saved selection.
- Open the Odoo customer display on that screen.
- Move and resize the window to occupy the available screen area.
If the previously selected monitor cannot be found, the module falls back to a secondary monitor when available, or to the primary monitor.
No verified information in OCA: Installation.
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.
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.