OdooQtUi

Native Qt desktop applications on top of Odoo — without rewriting a single view.

OdooQtUi reads the form, list and search views straight from your Odoo server and renders them as real PySide6 widgets. Fields, notebooks, header buttons, invisible/readonly/required conditions, onchanges and the chatter all come from the server — you just drop the widget into your window.

Change a view in Odoo, and your desktop app follows. No XML to duplicate, no forms to hand-draw.

form = connector.initFormViewObj('res.partner')
form.loadIds([7])          # a live, editable Odoo form in your Qt window

The code above, run against Odoo 19: the partner form as the server defines it, notebook and one2many lists included.

Why OdooQtUi?

The Odoo web client is great in a browser. Some applications don't live in a browser:

• Desktop integrations — a CAD, a machine, a scale, a label printer, a local file system: talk to them from Python and show Odoo data in the same window.
• Plugins inside other software — embed an Odoo form in any Qt-based host application.
• Kiosks and shop-floor stations — a focused, native UI that exposes only what the operator needs.
• Your own UX, Odoo's business logic — build a custom window, and still let the server decide which fields exist, which are required and which buttons are allowed.

It is not a toy: OdooQtUi is the UI layer of OdooPLM, the PLM client that connects SolidWorks, Inventor, FreeCAD and other CADs to Odoo, used in production.

Features

Installation

pip install OdooQtUi

Requires Python 3.12+ and PySide6 (installed automatically). You need access to an Odoo server — if you don't have one, the official Docker image starts one in a minute.

Quick start

1. Log in

import sys
from PySide6 import QtWidgets
from OdooQtUi.connector import MainConnector

app = QtWidgets.QApplication(sys.argv)

connector = MainConnector()
if not connector.loginWithDial():      # shows the Odoo login dialog
    sys.exit("Login cancelled")

Prefer no dialog? Log in from code, over XML‑RPC or JSON‑RPC:

connector.loginWithUser('admin', 'admin', 'my_database',
                        xmlrpcServerIP='localhost', xmlrpcPort=8069,
                        scheme='http', loginType='jsonrpc')
assert connector.userLogged

2. Show an Odoo form

form = connector.initFormViewObj('res.partner', useHeader=True, useChatter=True)
form.loadIds([7])                      # load the record with id 7

window = QtWidgets.QDialog()
QtWidgets.QVBoxLayout(window).addWidget(form)
window.resize(1000, 700)
window.exec()

form.save()                            # write the changes back to Odoo

form.loadIds([]) opens an empty form filled with the server defaults, and save() then creates the record.

3. Show a list with a search bar

products = connector.initTreeListViewObject('product.product', viewFilter=True)
products.loadForceEmptyIds()           # first page of records

window = QtWidgets.QDialog()
QtWidgets.QVBoxLayout(window).addWidget(products)
window.exec()

print(products.getSelectedIds())

Double-click a row to open its form. Pass deafult_filter=[('sale_ok', '=', True)] to restrict what the list shows.

Need a specific view? Every init… method accepts viewName='…' or view_id=….

4. Talk to Odoo directly

The same connection gives you the plain RPC calls:

rpc = connector.rpc_connector
ids = rpc.search('res.partner', [('is_company', '=', True)], limit=10)
for partner in rpc.read('res.partner', ['name', 'email'], ids):
    print(partner['name'], partner['email'])

rpc.write('res.partner', {'phone': '+39 041 000000'}, ids[:1])
rpc.callCustomMethod('sale.order', 'action_confirm', [[42]])

5. Make it yours

Load a palette before creating the connector:

from OdooQtUi import theme

theme.load({'primary': '#1f4e79', 'accent': '#e67e22'})
# or theme.load('my_theme.json'), or set ODOOQTUI_THEME=/path/to/my_theme.json
connector = MainConnector()

The same partner form with the palette above: the accent on the buttons, the primary colour on the tabs.

The available colour names are listed in OdooQtUi/theme.py.

Odoo compatibility

Older Odoo versions are not officially supported by this release.

How it works

Odoo server ──fields_view_get──▶ view arch (XML) + field definitions
                                        │
                                        ▼
                             OdooQtUi parsers (views/)
                                        │
                                        ▼
                  one Qt widget per field type (objects/<type>/)
                                        │
                  read / write / onchange / buttons over RPC (RPC/)

• OdooQtUi/connector.py — MainConnector, the entry point: login and view factories.
• OdooQtUi/views/ — form, list, search and tree views, built from the arch.
• OdooQtUi/objects/ — one small widget per Odoo field type.
• OdooQtUi/RPC/ — XML‑RPC and JSON‑RPC clients behind a single RpcConnection.
• OdooQtUi/theme.py, OdooQtUi/widgets/ — palette and reusable widgets such as StatusBar.

Contributing

Contributions are very welcome — and the codebase is friendly to newcomers: every Odoo field type is a small, self-contained widget under OdooQtUi/objects/, so adding support for a missing one (monetary, html, many2many_tags, radio buttons…) is a perfect first pull request.

git clone https://github.com/OmniaGit/OdooQtUi.git
cd OdooQtUi
pip install -e .
python -m unittest discover -s test -p "test_*.py"   # no Odoo server needed

Changed how something looks? Take the README screenshots again from a running Odoo with demo data (it needs a display, and writes nothing to the server):

python tools/make_screenshots.py --db my_database    # --only list theme, --help

Found a bug or have an idea? Open an issue. Code, comments and commit messages are written in English.

License

Apache License 2.0 — use, modify and redistribute OdooQtUi freely, in open source and proprietary applications alike.

The one requirement is attribution: any redistribution or derivative work must keep the NOTICE file, or reproduce its credits in its documentation or "About" box, naming OdooQtUi and its authors.

Copyright 2011-2026 OmniaSolutions and the OdooQtUi contributors — Daniel Smerghetto, Matteo Boscolo, Jayraj Thakkar.