This is a build-to-order module, not an instant apps.odoo.com download. After purchase we run a short discovery to agree the data domains, access scopes, LLM backend and tone, then build, test and install it in your staging and production databases. Typical delivery is one working week, depending on how many models and custom fields you want covered and your Odoo version. You get a clear timeline at kickoff.

Every build ships with a post-launch support window covering bug fixes and minor adjustments. We also document the upgrade path so the module can move with you across Odoo 17, 18 and 19. Beyond the initial window we offer ongoing support and enhancement retainers. Because the source lives in a repo you own, you're never locked in — your team can maintain or extend it too.

No. Every query the bot runs is executed as the logged-in user through Odoo's own ORM, so it fully respects ir.model.access.csv and your record rules. A salesperson only sees their own pipeline, a support agent only their permitted accounts, and multi-company boundaries are honoured. On top of that, admins define per-model and per-field access scopes, and the LLM only ever produces safe parameterised query plans over whitelisted models — never raw SQL.

AskOdoo is built for Odoo 17, 18 or 19, on Community or Enterprise. We target your exact version in the __manifest__.py and test against your database. The widget uses OWL and QWeb and the data layer uses standard ORM calls, so it works on either edition as long as the sale, purchase and account modules you want queried are installed.

You choose. AskOdoo can use a language-model provider via an API key you own and control, or a self-hosted model for data-residency-sensitive deployments where nothing leaves your infrastructure. In all cases the LLM only receives the question and a schema description to plan the query — it does not get direct database access, and results are fetched by Odoo. Every interaction is logged so you have a complete audit trail.

Yes. The module ships with sale.order, purchase.order and account.move (invoices) coverage, but the model catalogue is configurable. During the build we can extend it to CRM leads, stock pickings, projects, helpdesk tickets or any custom model in your database. It can also do aggregations — totals invoiced, open PO value, overdue receivables, counts by customer or period — and optionally post scheduled digests to a mail channel via an automated action.

Filters and pivots are powerful but require people to know the model structure and build the view every time. AskOdoo removes that friction: a new support agent can ask 'what has ACME ordered recently?' on day one and get a linked answer. It complements — not replaces — Odoo's UI: the bot's answers link straight back to standard form and list views, so people go deeper in Odoo whenever they need to.