Every Odoo administrator eventually hits the wall of the native domain editor. Building a filter that spans relational fields — "show partners whose sales orders contain products in these categories" — means hand-writing a Polish-notation domain like ['&', ('order_line.product_id.categ_id', 'in', ids), ...] inside a Developer-mode text box, where one misplaced bracket or '|' silently breaks the record set. Business users can't touch it, functional consultants dread it, and dynamic filters that should adapt to the logged-in user, the current company, or a related record simply aren't expressible through the standard UI. The result is a proliferation of hard-coded server actions and one-off ir.filters that nobody dares to edit.

The Advanced Web Domain Widget is a made-to-order OWL field widget and Python domain-compiler that ECOSIRE builds for your database. It replaces the raw domain textarea with a guided, condition-by-condition builder that walks relational paths — following Many2one and Many2many chains as far as you configure — and exposes simplified operators (contains, is any of, is empty, in the last N days, is set by current user) that compile down to valid, safe Odoo domain tuples. Under the hood it is a proper Odoo module: a models.Model mixin that stores and validates domains, a fields.Char/fields.Json domain column with an @api.constrains guard that rejects malformed expressions before they ever reach the ORM, an OWL component registered in the web assets bundle, and server-side evaluation that honours record rules and ir.model.access.csv so a user can never craft a filter that leaks records they aren't entitled to see. Dynamic context values (uid, company_id, context_today) are injected at evaluation time rather than baked into the stored domain, so one saved filter behaves correctly for every user and every company.

Because it is your module, we shape it to your models and your workflows. We can wire the widget into any view (search panels, wizard fields, automated-action trigger conditions, report filters), cap relational traversal depth for performance, expose or hide operators per user group, and add domain presets that map to your business vocabulary. It works identically across Community and Enterprise — no Enterprise-only dependency — and is delivered targeting your exact Odoo series (17.0, 18.0, or 19.0) with the OWL and asset-bundle conventions of that version. Optionally we expose the compiled domains over the XML-RPC/JSON-RPC API so external tools and integrations can reuse the same saved filters rather than re-implementing your filtering logic.

Delivery is build-to-order: nothing ships until we agree on scope. We start with a short scoping call, produce a fixed written specification and quote, build against a copy of your database, run UAT on a staging instance, and only then install on production with a documented rollback path. Typical delivery is 2–4 weeks from confirmed scope, depending on how many models and views the widget must cover. Pricing starts from $249 (indicative, single-company base scope); additional target models, deeper relational traversal, multi-company evaluation rules, or integration of the compiled domains into external systems via the API increase the quoted scope.