A keyboard-driven command palette that lets your team jump to any app, menu, record, or action in a couple of keystrokes. Built to order by ECOSIRE, installed and supported on your Odoo 17, 18, or 19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
アプリマニフェスト
あなたのワークフローに合わせて構築
A keyboard-driven command palette that lets your team jump to any app, menu, record, or action in a couple of keystrokes. Built to order by ECOSIRE, installed and supported on your Odoo 17, 18, or 19.
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
約2〜4週間で稼働し、リリース後のサポート期間が付きます。
Every day your team loses minutes to the same friction: hunting through the apps grid, drilling menu after menu to reach a form, and reloading pages to switch between Sales, Inventory, and Accounting. Multiply that across dozens of users and hundreds of navigations a day and you have a real productivity tax that never shows up on any report. Odoo's native web client gives you the apps switcher, breadcrumbs, and the global search inside a list view, but there is no single keyboard-first entry point that spans the whole system — no way to press one shortcut and immediately type your way to any menu, any record, or any action you have access to.
ECOSIRE builds a command palette for exactly this. We ship an OWL-based overlay, bound to a keyboard shortcut, that opens over any screen and gives your users an instant fuzzy-searchable index of the menus, actions, and recently-opened records they are allowed to reach. Under the hood it is a proper Odoo module: a __manifest__.py declaring an assets bundle that registers the OWL component and its service into web.assets_backend, a lightweight server controller (or ORM search_read calls over the JSON-RPC layer) that resolves searchable targets from ir.ui.menu, ir.actions.act_window, and configurable target models, and a client-side index that ranks results by relevance and recency. Because every lookup is executed as the logged-in user, the palette can never surface a menu, action, or record the user is not entitled to — ir.model.access.csv and record rules do the gating for us, exactly as they do everywhere else in Odoo.
The palette is configurable rather than hard-coded. We expose a settings model so an administrator can choose which models are searchable (customers, sales orders, products, projects, tickets — whatever matters to your workflows), define named "commands" that trigger a specific ir.actions.act_window or server action, and tune the keyboard shortcut and result limits. Recently-visited records are tracked per user so the most likely destination floats to the top, and results open in the standard Odoo breadcrumb flow so nothing about your users' mental model changes — they simply arrive faster. Where you want it, we can wire palette entries to fire automated actions or open a filtered view, so "create a new quotation for this customer" becomes two keystrokes instead of five clicks.
Because this is a made-to-order engagement, we design the scope with you first, then build against your actual database. We develop and test on a staging copy of your Odoo, run UAT with your team, and only cut over to production once you have signed off, with a rollback path prepared. The module is delivered as clean, reviewable source in a git repository you keep, documented and licensed for your use, and built specifically for your Community or Enterprise edition on Odoo 17.0, 18.0, or 19.0. Typical delivery is 2–4 weeks from confirmed scope, depending on how many searchable models and custom commands you want and the state of your environment.
Pricing starts from $249 (indicative, single-company base scope); additional searchable models, custom command actions, multi-company routing, and deep integration with bespoke modules increase the quoted scope. You receive a firm fixed quote after a short scoping call — never a surprise invoice.
Runs day-to-day operations across Sales, Inventory, and Accounting and watches staff lose time clicking through menus. Wants a single keyboard-first way for everyone to reach the right screen fast, with zero risk of exposing data users shouldn't see.
High-volume users who live in Odoo all day and switch between records constantly. They want a launcher that jumps straight to a customer, order, or ticket and fires common actions without leaving the keyboard.
Owns the Odoo deployment and is cautious about third-party code. Needs a clean, documented, access-rule-respecting module delivered as source in a git repo, tested on staging with a rollback plan, and built for the exact Odoo version and edition in production.
Focused on measurable productivity and adoption. Wants to cut navigation friction across the whole company and get a predictable, fixed-quote engagement with training and support rather than an open-ended build.
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Fit to your workflows | Built to your exact menus, models, and commands | Fully bespoke but you specify everything | Generic feature set, take it as shipped | |
| Access-rule safety | Runs as the user; respects access rights and record rules | Depends on your developers getting it right | Usually respects rules but hard to verify | |
| Odoo version & edition targeting | Built and tested for your 17/18/19, Community or Enterprise | Whatever your team targets | Version support varies; may lag new releases | |
| Delivery model | Made to order, 2–4 weeks from confirmed scope | Open-ended; depends on internal capacity | Instant download, no build | |
| Testing & rollback | UAT on staging with a tested rollback plan | Only if you build the process | You test it yourself post-install | |
| Source & ownership | Full source in a git repo you own | You own it by definition | Often closed or obfuscated source | |
| Training & support | User guide, training session, post-go-live support window | Self-supported unless contracted | Vendor tickets, variable response | |
| Total cost predictability | Fixed quote after scoping; from $249 indicative | Hard to estimate; scope creep risk | Low sticker price, integration cost hidden |
Because this is built to order, typical delivery is 2–4 weeks from confirmed scope. The exact timeline depends on how many searchable models and custom commands you need and the readiness of your environment. We agree milestones with you before development starts and build against a staging copy of your database.
No. This is a productized service, not an off-the-shelf marketplace download. ECOSIRE designs, builds, installs, and supports the module specifically for your Odoo version, edition, and workflows. You receive installable source code and a git repository as part of the handover.
Pricing starts from $249 as an indicative single-company base figure. After a short scoping call we give you a firm fixed quote. Drivers such as additional searchable models, custom command actions, multi-company routing, and integration with bespoke modules affect the final scope and price — but the quote is fixed once scope is agreed.
No. Every search runs as the logged-in user, so Odoo's `ir.model.access.csv` access rights and record rules govern exactly what appears. If a user cannot open a menu, action, or record in the normal UI, it will not surface in the palette either. Multi-company rules are respected as well.
We build for Odoo 17.0, 18.0, and 19.0, on either Community or Enterprise. We confirm your exact version and edition during scoping and target the build accordingly, since the OWL client and assets bundling differ between major versions.
Every engagement includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full source in a git repo, your team can extend it freely. We also offer ongoing support and version-upgrade services separately if you want us to maintain it across future Odoo releases.
Yes. We hand over the complete module source in a git repository with commit history, licensed for your use. There is no lock-in — your team can read, audit, maintain, and extend the module independently.
A keyboard-driven command palette that lets your team jump to any app, menu, record, or action in a couple of keystrokes. Built to order by ECOSIRE, installed and supported on your Odoo 17, 18, or 19.