A typical unattended kiosk launcher needs a real Odoo login to open the POS automatically - which usually means a cashier's password sits in plain text somewhere on the device: a local HTML file, a browser bookmark, a kiosk-mode config script.

That creates real, ongoing operational risk:

• Anyone with physical or file access to the device can extract the password
• Rotating a compromised password breaks every other kiosk sharing that same login
• No visibility into which terminals are actually being used, or when
• No audit trail of who configured, reconfigured, or decommissioned a terminal
• A kiosk that silently goes offline is only noticed when a cashier complains
• Losing a device means scrambling to change passwords everywhere at once

This module adds a dedicated Direct POS Kiosk configuration per physical terminal: a server-generated token (stored only as a SHA-256 hash, never in plaintext), the Odoo user the terminal should run as, and the target POS to open. The kiosk launcher calls a single URL; Odoo verifies the token and redirects straight into the POS session - the real password never has to leave the server, and the token can be revoked in one click at any time.

Step 1: Install Module

Step 2: Create a Terminal Record

Go to Settings → Technical → POS Kiosk Direct → Direct POS Kiosks → New. Give the device a Site Code and a globally unique Terminal Code, then pick the POS Config it should open.

Step 3: Choose the Right Auth Mode

Two modes, two trust levels - in both cases, the kiosk itself never shows a login screen; the difference is only how strictly Odoo checks the credential behind the scenes:

• Login + password - Odoo performs a real authentication automatically, the same check as the login form, using the credential already configured on the terminal. Use this for most terminals.
• Session user without password - the token alone grants access, no password check at all. Reserve this for terminals that are physically locked down (behind a counter, kiosk-mode browser with no address bar).

Step 4: Generate and Distribute the Token

Click Generate Token. Copy the URL shown in the one-time popup and configure the kiosk launcher to open it on boot. The token is never shown again - only its last 4 characters remain visible on the terminal record for identification.

Step 5: Monitor and Respond

Use the list view's Last Start At and Is Stale columns to see the health of the whole fleet. If a device is lost, stolen, or reassigned, open its record and click Revoke Token immediately, then generate a fresh one when ready.

Which Odoo version does this support?

Odoo 19.0. It is built and tested against the Odoo 19 Point of Sale and mail chatter APIs.

Does this need Odoo Enterprise, or does it work on Community?

It works on Odoo Community. The module only depends on point_of_sale and mail, both free, Community-edition modules - no Enterprise app is required.

Do kiosk tokens expire automatically?

No. A token stays valid indefinitely until someone clicks Revoke Token on that terminal. There is no automatic time-based expiration, so build token rotation into your own security policy (for example, revoking and reissuing on a schedule, or immediately whenever a device changes hands) rather than assuming it happens on its own.

I run several companies in one database - are terminals scoped per company?

Not currently. Any user with System Administrator access can see and manage every terminal across every company from the same list view. If several companies share one database, control who has System Administrator rights accordingly.

A kiosk URL shows "No database is selected... server-wide controllers" - what does that mean?

This is a general Odoo hosting detail, not specific to this module - it appears when your Odoo server hosts more than one database and neither dbfilter nor db_name is configured, so Odoo cannot guess which database an unauthenticated kiosk request belongs to. Fix it once, server-side: set dbfilter to your database in odoo.conf (or start Odoo with -d your_database) so kiosk URLs work without ever needing a ?db= parameter - exactly how a real single-tenant kiosk deployment should be set up.

What happens to my terminals and tokens if I uninstall the module?

Every Direct POS Kiosk record, including its token, is removed along with the module - the standard Odoo behaviour for data owned by a module. Your POS configurations, orders, and users are entirely unaffected; only the kiosk-to-terminal mapping disappears. Reinstalling starts from a clean slate, so plan to recreate each terminal and generate fresh tokens afterward.