A made-to-order Odoo module that lets your team drag, drop, and configure custom forms on any website or portal page, with each submission mapped straight into the Odoo records you choose. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17.0, 18.0, or 19.0 database. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.

A made-to-order Odoo module that lets your team drag, drop, and configure custom forms on any website or portal page, with each submission mapped straight into the Odoo records you choose. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17.0, 18.0, or 19.0 database.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
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.
Drag-and-drop website building-block registered with the Odoo website editor via a snippet `ir.ui.view`, usable on any page without touching code
Per-form configuration model (`models.Model`) storing target model, field mapping, validation, success behavior, and notification recipients
Server-side submission controller (`http.Controller`, `website=True`) that validates every payload, enforces CSRF tokens, and never trusts client input
Public (`auth='public'`) and portal-gated (`auth='user'`) form routes, so the same builder serves anonymous marketing pages and authenticated `/my` portal forms
Direct mapping of fields to any target model — CRM lead, helpdesk ticket, res.partner, or a custom object — with create or update semantics
Field types for text, number, selection, date/datetime, many2one relational lookups, checkbox, and multi-file upload stored as `ir.attachment` on the created record
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 2 to 4 weeks 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 $299 (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.
Runs the Odoo website and needs to launch campaign and lead-capture forms on their own, without a developer for every new field or landing page. Wants submissions to land in the right CRM stage with the right owner.
Owns the Odoo database and wants a maintainable, permissioned way to let business users build forms that write to custom models — with security rules, an audit trail in chatter, and no ad-hoc controllers piling up.
Needs authenticated forms inside the `/my` portal so logged-in customers can submit requests, updates, or documents against their own records only, enforced by record rules rather than trust.
Wants inbound submissions to auto-create helpdesk tickets or service requests, route by team, notify owners, and acknowledge the submitter — all from a form business users can adjust as processes change.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Forms • Website Snippet Builder 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Forms • Website Snippet Builder,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Drag-and-drop form building for non-developers | Website snippet plus config model, built around your models | Possible but re-implemented from scratch each time | Generic builder, limited to its own field/model assumptions | |
| Writing submissions to custom models | Mapped to any target model you nominate | Fully custom but you own all the plumbing | Often restricted to models the vendor anticipated | |
| Portal (`/my`) forms with record-rule isolation | Built in, gated by record rules per your workflow | Bespoke controllers and rules to write and test | Rarely covers authenticated portal use | |
| Conditional field logic | Configured per form, checked client and server side | Hand-coded and maintained by you | Varies; often client-side only | |
| Security and access rules | `ir.model.access.csv` + record rules scoped to your case | You design and audit it yourself | Vendor defaults, not tailored to your models | |
| Fit to your Odoo version and edition | Built and tested for 17/18/19, Community or Enterprise | Depends on your team's version coverage | Whatever versions the listing happens to support | |
| Support and ownership | Support window plus full Git repo handover | In-house only; no external backstop | Generic vendor support, shared codebase | |
| Delivery model | Build-to-order, 2-4 weeks, UAT + rollback plan | Open-ended internal project timeline | Instant install but generic behavior |
No. This is a build-to-order module. ECOSIRE scopes, builds, installs, and supports it for your specific Odoo database — there is no instant download. After a scoping call to confirm your forms, target models, and field mappings, we build against a copy of your database and deliver installable source for your version.
Typical delivery is 2 to 4 weeks from confirmed scope. Simple single-model form sets land toward the shorter end; multiple target models, heavy conditional logic, portal record-rule isolation, or external integrations extend the timeline. We give you a firm schedule with the fixed quote after the scoping call.
Pricing starts from $299 (indicative, single-company base scope). The final number depends on how many target models the forms write to, conditional-logic complexity, multi-company isolation, external API integrations, and localization depth. We hold a short scoping call, confirm the exact requirements, and then give you a fixed written quote — no firm price is committed before scoping.
We build and test against Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. Some website-snippet and portal capabilities differ between Community and Enterprise, so we confirm the exact fit for your edition during scoping and build accordingly.
Every build includes a post-go-live support window for defect fixes and configuration questions. Beyond that we offer ongoing support and version-upgrade work (for example migrating the module to a newer Odoo release) as a separate arrangement. You receive the full Git repository so your own team can maintain it too.
Yes. The builder maps fields to whichever target model you nominate — a CRM lead, helpdesk ticket, res.partner, or a fully custom `models.Model`. We configure the field mapping, validation, and `ir.model.access.csv` / record rules during the build so submissions create or update exactly the records you intend.
Submissions are validated server-side in the controller with CSRF enforced, and public routes can only create the records defined by their access rules — never arbitrary writes. We add a honeypot field, per-IP rate limiting, and optional captcha, and portal forms are gated by record rules so users only ever see and edit their own records.
A made-to-order Odoo module that lets your team drag, drop, and configure custom forms on any website or portal page, with each submission mapped straight into the Odoo records you choose. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17.0, 18.0, or 19.0 database.