Teams that live in Odoo all day hit the same small frictions dozens of times per hour: scrolling a 200-row list loses the column headers, there is no fast way to copy a record's technical ID or shareable URL, switching between the form and its list means a full reload, and dense screens waste vertical space on padding your power users don't need. Odoo core is deliberately conservative about the web client — the backend OWL interface ships one opinionated layout, and none of these quality-of-life behaviors exist out of the box. The cost is invisible but real: seconds lost per action, multiplied across every user, every day.

Web Utils is a build-to-order OWL/JavaScript layer that ECOSIRE assembles for your exact needs. We patch the web client through Odoo's supported client-side extension points — registry-based service and component patches, OWL component inheritance, and asset bundles declared in __manifest__.py under web.assets_backend — rather than forking core files, so upgrades stay clean. Typical helpers we implement include sticky list/form headers, keyboard-shortcut navigation between records, a "copy record ID / copy shareable URL" action wired into the cog menu, list-view density toggles persisted per-user via res.users settings or ir.config_parameter, chatter/panel collapse-state memory, quick-search focus shortcuts, and optional debug/technical helpers gated behind group membership. Every widget respects existing access rules — we never bypass ir.model.access.csv or record rules, and user-scoped preferences are stored on server-side models so they survive across devices and sessions.

Because the web client is shared infrastructure, we treat compatibility as a first-class deliverable. The module is authored against a specific target series (17.0, 18.0, or 19.0) and validated on both Community and Enterprise where the requested helpers apply — a handful of behaviors differ because Enterprise ships its own web assets, and we call those out during scoping. Where a helper needs server data (persisted preferences, group-based visibility), we add small, well-tested models.Model extensions with proper fields and, where computed values are involved, @api.depends-decorated methods, plus the matching security rows so the feature is safe in a multi-user database.

Delivery is build-to-order: it starts with a short scoping call to agree the exact helper set and target Odoo version, after which we send a fixed-price quote and a written scope. We then build on a branch, hand you a staging build for UAT, and deploy to production with a rollback plan and a post-go-live support window. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); the number of distinct helpers, cross-version support (17/18/19 together), Enterprise-specific web overrides, and any persisted-preference data models increase the quoted scope.