Skip to Content

Odoo Client

Odoo Client is a multi-platform shell built with Flet: local multi-account sign-in, an embedded WebView for Odoo Web, and a JavaScript bridge for native capabilities (printing, cash drawer, barcode reader, scale, and more). It does not include Odoo business UI—POS and backend screens still run on the server.
The codebase targets five platforms (Windows, Linux, macOS, Android, and iOS). However, flet build macos and iOS (ipa) cannot be cross-compiled from Windows or Linux—they must be built on macOS (a physical Mac, cloud Mac, or CI). We currently have no macOS build host, so we cannot produce or publish macOS or iOS installers. That is a toolchain and build-environment constraint, not a missing product feature. Once a Mac build environment is available, those packages can be shipped.


Get the desktop and mobile clients. Pick a version, then choose your platform. Files are served from multi-cloud storage; we recommend a source based on your location.

2026.9.30 Latest

Channel: Stable

Windows

View notes
Published on 09/29/2026 11:27:03 PM
Odoo-Client-2026.9.30-b2-x64-Setup.exe · 92.7 MB · Build 2
SHA-256: b232ec25bcf0a19063fc285f59b2dc9fc682d3a216ad6c9e5428774d72abcba7
28 downloads
Published on 09/30/2026 02:29:57 AM
Odoo-Client-2026.9.30-b1-x64.deb · 61.4 MB · Build 1
SHA-256: c9c9727df1a6cde43ca4b2ea476de06e426b02bc75b89adc54e693e785db97dd
28 downloads

Android

View notes
Published on 09/29/2026 11:44:37 PM
Odoo-Client-2026.9.30-b2-arm64.apk · 273.7 MB · Build 2
SHA-256: 330086ef4a82ff59c31072ffb06bcf7d35e262f25f339e573b2394068fbf2470
24 downloads

Windows Release notes

↑ Back to top

Product positioning

Odoo multi-platform client for Windows for store / office desktops: embed Odoo in a local Edge WebView2 shell, with bridges for print, customer display, scale, and other local capabilities—no need to keep a separate browser window open.

Capabilities in this release

  • Embedded Odoo: Microsoft Edge WebView2 renders backend and PoS pages; session cookie injection keeps login state inside the shell.
  • Local service bridge: Pages can call host capabilities through the client bridge (e.g. printFile, customer display, scale reads) for cashier and front-desk workflows.
  • PDF print backend: The installer bundles portable SumatraPDF and Ghostscript runtimes; print flows prefer components under the install directory.
  • Accounts and local config: Multi-account management; account DB and runtime logs live in the user data directory and are not shipped in the installer; uninstall does not delete user data by default.
  • System tray: Closing the window can minimize to the tray (depending on the host environment) for always-on use.
  • Devices / local services: Configure and manage local devices and services in the client (e.g. serial scales, depending on site hardware).
  • In-app info: More in the address bar shows WebView engine / kernel version; WebView DevTools are available on desktop.
  • Update check: Can use the company release channel to detect new versions (depends on on-site Odoo / release service).

Runtime requirements

ItemNotes
OSWindows 10 / 11 (x64)
RequiredMicrosoft Edge WebView2 Runtime (Evergreen); usually preinstalled on Win10/11; the setup wizard can detect and guide download
Odoo sideOne of: ① Enterprise + custom modules; ② Community custom modules
Install locationDefault Program Files\EIST\Odoo Client; Start menu shortcut; optional desktop icon

Install and notes

  1. Run Setup.exe and complete the wizard (UI defaults to Simplified Chinese; English / Español available).
  2. If WebView2 is missing, follow the wizard to the official Evergreen installer, then start the client.
  3. This package is desktop-only; handheld scan broadcast, Gecko WebView, and related capabilities are covered in the same-day Android release notes and are not included in this Windows installer.
  4. On first use, configure the Odoo server URL in the client and sign in.

Known limitations

  • Installer size is larger than a “browser bookmark only” approach because of the desktop shell, WebView2 plugins, and SumatraPDF / Ghostscript print components.
  • Customer display and some peripherals depend on local hardware and drivers; without them, normal browser-style access to Odoo still works.

Linux Release notes

↑ Back to top

Product positioning

Odoo multi-platform client for Linux for store / office desktops: embed Odoo in a local WebKitGTK shell, with bridges for print, customer display, scale, and other local capabilities—no need to keep a separate browser window open. Feature set aligns with the same-day Windows desktop build; the engine and packaging follow Linux desktop conventions.

Capabilities in this release

  • Embedded Odoo: WebKitGTK 4.1 (this repo’s flet-webview-linux) renders backend and PoS pages; session cookie injection keeps login state inside the shell.
  • Local service bridge: Pages can call host capabilities through the client bridge (e.g. printFile, customer display, scale reads) for cashier and front-desk workflows. On HTTPS sites, the bridge script is injected in chunks so WebKit does not block in-page cleartext HTTP requests.
  • PDF / receipt printing: Uses system CUPS (cups-client is a dependency; installing the cups service is recommended). Device discovery can enumerate local print queues. Unlike the Windows package, this build does not ship SumatraPDF / Ghostscript.
  • Accounts and local config: Multi-account management; account DB and runtime logs live in the user data directory and are not shipped in the .deb; uninstall does not delete user data by default.
  • System tray: Closing the window can minimize to the tray (requires AppIndicator / StatusNotifier). If the GIR is missing or there is no StatusNotifierWatcher, close falls back to minimize.
  • Devices / local services: Configure and manage local devices and services in the client (e.g. serial scales, depending on site hardware).
  • In-app info: More in the address bar shows WebView engine / kernel version; WebView DevTools are available on desktop.
  • Update check: Can use the company release channel to detect new versions (depends on on-site Odoo / release service).

Runtime requirements

ItemNotes
OSDebian / Ubuntu-family desktops (verified on Pop!_OS 24.04 and similar); x86_64 recommended
Requiredlibwebkit2gtk-4.1, libsoup-3.0, GTK3, and related libs (pulled by .deb Depends); printing needs the CUPS client; a full CUPS service is recommended for end-to-end print
Traygir1.2-ayatanaappindicator3-0.1 recommended (listed in Depends); the panel should support StatusNotifier / AppIndicator
Odoo sideOne of: ① Enterprise + custom modules; ② Community custom modules
Install locationDefault /opt/cn.com.eist.odoo-client; Freedesktop .desktop entry plus AppStream metadata

Install and notes

  1. Install the .deb (if home-directory permissions are too strict for apt, copy to /tmp first, then use apt / dpkg):

    sudo dpkg -i Odoo-Client-*.deb
    sudo apt-get install -f
    # or:
    cp Odoo-Client-*.deb /tmp/
    sudo apt install /tmp/Odoo-Client-*.deb

  2. On first use, configure the Odoo server URL in the client and sign in.

  3. Under Wayland, the client runs via XWayland (GDK_BACKEND=x11) so window size and the device toolbar work; COSMIC / GNOME docks resolve the icon by APPLICATION_ID (cn.com.eist.odoo-client).

  4. This package is desktop-only; handheld scan broadcast, Gecko WebView, and related capabilities are covered in the same-day Android release notes. Desktop print and customer display are also described in the same-day Windows notes (Windows print backend: SumatraPDF / Ghostscript).

Known limitations

  • Package size is larger than a “browser bookmark only” approach because of the desktop shell and WebKitGTK runtime dependencies; printing relies on system CUPS and does not embed the Windows portable PDF stack.
  • Customer display and some peripherals depend on local hardware and drivers; without them, normal browser-style access to Odoo still works.
  • On some virtual GPUs the launcher disables WebKit DMA-BUF (to avoid white blocks); physical machines keep hardware compositing.
  • Info-style dialogs can occasionally be covered by the WebView overlay; if that happens, switch accounts or refresh, then open About / Info again.

Android Release notes

↑ Back to top

Product positioning

Odoo multi-platform client for Android aimed at store handhelds and tablets: open Odoo backend and PoS inside an in-app WebView, and expose device capabilities to the page through the client JavaScript bridge (same approach as official Mobile JavaScript / ; see bridge docs in the repo). Business logic stays in Odoo JS—no separate native UI for the shell.web_mobile

Highlights in this release

  • Hikvision handheld scanner MV-IDP5204 (Android 11): Scan verified. The device delivers barcodes via scan broadcast; the shell queues them and PoS reads them through the bridge ( / ), then adds the matching product by barcode. HID keyboard wedge scanning can still use the web barcode path; this release focuses on broadcast + bridge. Official camera scan API () is not included; handheld use does not depend on camera preview.enableReadergetReaderDatascanBarcode
  • Redmi K80 (Android 16): Verified that Odoo can be opened and used normally.
  • About APK size: The System WebView on MV-IDP5204 is too old to render Odoo reliably. At startup the app probes System WebView major version: ≥ 110 uses system WebView; below 110 (or probe failure) uses embedded GeckoView. Older ROMs such as Hikvision therefore take the Gecko path, so the APK is noticeably larger—this is expected. Use More in the address bar to inspect the current engine.

Capabilities in this release

  • Embedded Odoo: Backend / PoS via system WebView or GeckoView; the Gecko path supports injecting bridge scripts so the reader bridge can stay online.
  • Client bridge: Same dispatch model as desktop. On Android for this release, verified or available cashier-related pieces include: in-shell account switch ( / ), PoS reader polling, Toast / SnackBar feedback; push-related methods are registered, and failure without a real FCM token does not block login.switchAccountupdateAccount
  • Accounts and local config: Multi-account supported; account DB and logs live under app data and are not shipped inside the APK.
  • Update check: Can use the company release channel to detect new versions (depends on on-site Odoo / release service).
  • Architecture: Release packages are arm64-v8a only.

Runtime requirements

ItemNotes
OSAndroid 11+ (tested: MV-IDP5204 / Android 11; Redmi K80 / Android 16)
CPUarm64-v8a (no 32-bit package)
Odoo sideOne of: ① Enterprise + custom modules; ② Community custom modules
NetworkReachable target Odoo

Install and notes

  1. Install (unknown sources / enterprise distribution per site policy).Odoo-Client-*-arm64.apk
  2. On first launch, configure the Odoo server URL and sign in.
  3. Handheld scanning: confirm broadcast conventions match the Hikvision adapter; enter PoS and confirm the bridge is “online” before testing add-to-order.
  4. This package is Android-only; Windows install, office printing, customer display, etc. are covered in the same-day Windows release notes.

Known limitations

  • APK is larger than a “system WebView only” build because of GeckoView and related components.
  • Mobile office print / PoS thermal receipt / cash drawer, system contacts, full notification shade, camera barcode, real Firebase push are not wired or are degraded in this build; use the Windows package for desktop print and customer display.
  • On newer devices using system WebView, trust the on-site PoS bridge online/offline indicator; the Gecko path on older devices is the focus of scan integration in this release.

Changelog blurb

Android arm64: System WebView ≥ 110 uses the system engine; otherwise GeckoView (old ROMs such as Hikvision). MV-IDP5204 scan broadcast → JS bridge → PoS add-by-barcode verified; Redmi K80 (Android 16) can use Odoo normally. Larger APK due to Gecko is expected. Mobile print / camera scan / real FCM push not in this build.