Every Odoo rollout hits the same wall: new users log in, stare at an unfamiliar screen, and either flood your admins with "where do I click?" tickets or quietly stop using the module. Odoo ships a lightweight tour engine (web_tour) used internally for its own onboarding, but it is not exposed as a business-facing tool — you cannot author, target, or measure tours from the UI, tours are not scoped by company or user group, and there is no way to trigger contextual guidance the moment a user opens a specific view. Off-the-shelf onboarding modules exist, but they force your process into their fixed tour format and rarely understand your custom models and studio fields. That gap is exactly what we close.

ECOSIRE builds a Guided Tours module tailored to your Odoo instance: interactive, step-by-step overlays that highlight real UI elements, explain what each field and button does in your context, and walk users through your actual workflows — creating a quotation, confirming a manufacturing order, filing an expense — rather than a generic demo. Under the hood we define a guided.tour and guided.tour.step model pair (models.Model) so tours are stored as data, not hardcoded XML, with @api.depends compute fields for progress and completion state. Steps bind to DOM anchors and OWL components, render through QWeb templates, and are sequenced with trigger conditions (open a view, click an element, reach a specific stage). Targeting is driven by res.groups, company (res.company), and even record rules, so a warehouse user and an accountant each see only the tours relevant to them — and multi-company deployments keep tours isolated per company.

The build integrates cleanly with how your team already works. Tours can auto-launch on first login via an ir.actions hook, be re-triggered from a persistent help launcher, or fire through an automated action when a user lands on a screen for the first time. Completion and drop-off are recorded per user so your admins can see, in a normal Odoo list/pivot view, which tours are finished and where people get stuck. Everything ships behind proper ir.model.access.csv rules and record rules, is translatable through Odoo's standard i18n so tours render in each user's language, and — where you want to push content or completion data to another system — is reachable over the XML-RPC/JSON-RPC API. We build against Community or Enterprise as your edition requires and target Odoo 17.0, 18.0, or 19.0, noting any edition-specific view or asset-bundle differences up front.

Because this is build-to-order, nothing is shipped until we have agreed scope. We start with a short scoping call, confirm which workflows and user groups need tours, then build on a staging copy of your database, run UAT with your team, and deploy to production with a rollback plan. Typical delivery is one working week from confirmed scope, depending on how many tours and how much custom-model targeting is involved. Pricing starts from $999 (indicative, single-company base scope); more tour flows, multi-company targeting, deep custom-model/Studio-field coverage, and localization depth increase the quoted scope. You receive a firm fixed quote after the scoping call — never a surprise bill.