Most teams hit the same wall on their Odoo website: the standard form building-block captures a name, an email, and a message into a lead or an outbound email, and that is roughly where the road ends. The moment you need a form that writes to a custom model, enforces conditional fields, attaches uploads to the right record, routes submissions to different owners, or renders inside the authenticated /my portal for logged-in customers, you are looking at custom controllers, hand-written QWeb templates, and a fair amount of ORM plumbing. Marketing wants to launch new forms without waiting on a developer; developers do not want a fresh inheritance layer for every campaign. Native Odoo was simply not built to let non-technical users compose data-bound forms visually.

This is a build-to-order module that ECOSIRE designs and builds for your database. At its core is a website building-block — an ir.ui.view snippet registered with the website editor — that your team drags onto any page, paired with a configuration model (models.Model) holding the target model, per-field mapping, validation rules, success behavior, and notification recipients. Each published form is served by a website controller (http.Controller with a website=True route, auth='public' for anonymous pages or auth='user' for portal pages) that validates the payload server-side, honors the CSRF token, runs your @api.constrains and compute logic, and creates or updates the record you nominated — a CRM lead, a helpdesk ticket, a partner, or a custom object. Field types cover text, number, selection, date, many2one lookups, file upload (stored as ir.attachment), and conditional show/hide logic driven by other answers. Submissions can trigger an automated action, post to the record's chatter, and fire a templated acknowledgement email.

Because every business models its data differently, the build is driven by your target models and workflow rather than a fixed template. We scope which models each form writes to, the exact field mapping and validation, whether a form is public or portal-gated by record rules, the anti-spam approach (honeypot, rate limit, optional captcha), and the routing/notification logic. Security is wired through ir.model.access.csv and record rules so that public submissions can only create the records you intend, and portal users only ever see and edit their own. The submission handler is also reachable over the XML-RPC/JSON-RPC API when you need to feed forms from an external site or automation.

Delivery is build-to-order: after a short scoping call we confirm the form catalog, field mappings, and target models, then build against a copy of your database, validate on staging with your real data, and install into production behind a rollback plan. Typical delivery is one working week from confirmed scope, and the module targets Odoo 17.0, 18.0, and 19.0 on both Community and Enterprise (portal features and some website snippet niceties differ between the two, and we confirm the fit for your edition during scoping). Pricing starts from $999 (indicative, single-company base scope); additional target models, complex conditional logic, multi-company record-rule isolation, external API integrations, and localization depth increase the quoted scope.