Add fields, tabs, buttons, computed & related fields, and views to any Odoo model from the UI — no code. A Community-edition Studio alternative. One-time license from $299.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Add fields, tabs, buttons, computed & related fields, and views to any Odoo model from the UI — no code. A Community-edition Studio alternative.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Odoo Studio is powerful, but it is locked behind an Enterprise subscription — and its customizations live inside your database, not in reviewable, version-controlled code. This module gives your team a Studio-style, no-code customization workbench on Odoo Community (17, 18 and 19), then hands you the clean, exportable module code so nothing is trapped in the UI.
Visual field editor — add Char, Text, Integer, Float, Boolean, Date/Datetime, Selection, Html, Binary, Many2one, One2many and Many2many fields to any model from the UI, each generating a proper ir.model.fields record
Drag-and-drop form layout designer that edits view inheritance (ir.ui.view arch via XPath) — add tabs (notebook pages), groups, columns and separators without touching XML
No-code computed fields via a visual formula builder that generates @api.depends-tracked Python compute methods (store on/off, with automatic recomputation)
Related fields defined by picking a source path (e.g. partner_id.country_id.name) — generated as fields.X(related=...) with the correct type inferred
Conditional visibility, readonly and required rules built from a domain/condition editor, compiled to modern Odoo attribute syntax (invisible/readonly/required expressions)
Custom buttons and server actions — add header or statusbar buttons wired to automated actions (base.automation / ir.actions.server) with no Python required for common patterns
ECOSIRE builds and installs this as a net-new, build-to-order module tailored to your database. From a friendly point-and-click editor, business users add fields, tabs, buttons, computed and related fields, smart-button counters, and layout changes to any model — Contacts, Sales, Inventory, Projects, HR, or your own custom apps — without writing a line of Python or XML. Under the hood it generates proper Odoo primitives: ir.model.fields records for new fields, view inheritance via ir.ui.view (arch XPath), attribute rules (invisible, readonly, required with domain-based conditions), and menu/action wiring. Because everything maps to real ORM and view structures, your customizations behave exactly like hand-coded ones and survive upgrades cleanly.
The differentiator is the one-click "Export as installable module" button. Any set of changes you make in the UI is packaged into a standard Odoo addon — __manifest__.py, models/, views/, security/ir.model.access.csv and record rules — that you can drop into staging, commit to git, and deploy through your normal CI. You get the speed of no-code with the auditability and portability of real code. Computed fields you define through the visual formula builder are translated into @api.depends-tracked Python compute methods; related fields become proper fields.X(related=...) definitions; and access is scaffolded into ACL and record-rule files so you never accidentally expose data.
We deliver a working, hardened installation on Odoo 17, 18 or 19 (Community or Enterprise), configured against your models and permission model, with your team trained to self-serve. This is not an instant apps.odoo.com download — it is a 2–4 week engagement where ECOSIRE builds, installs, tests and documents the module for your exact environment, then supports it. If Enterprise Studio pricing, vendor lock-in, or "customizations we can't see in git" have been holding you back, this replaces all three.
Runs Odoo Community and needs to add fields, tabs and computed logic regularly but can't justify the Enterprise upgrade purely for Studio. Wants Studio-like self-service without the subscription — and without hand-writing XML for every small change.
Understands the business logic and wants to iterate on forms and fields as processes evolve, but isn't a developer. Needs a safe, guided UI where they can add a field or a conditional rule today without filing a ticket and waiting a week.
Builds Odoo for multiple clients and wants a faster, consistent way to capture requirements as real, exportable addons. Values that every UI change lands as clean git-committable code instead of untracked database tinkering that breaks on upgrade.
Will not allow production customizations that live only in the database. Needs the auditability, review, and rollback of code — but wants business users to move fast. The export-as-module workflow satisfies both governance and speed.
Buy the license on ecosire.com and download the Studio-Style No-Code Custom Fields & Form Builder for Odoo module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Studio-Style No-Code Custom Fields & Form Builder for Odoo, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Runs on Odoo Community (no Enterprise subscription) | ||||
| No-code, business-user-friendly editor | ||||
| Export customizations as installable, git-committable module | ||||
| Computed & related fields without writing Python | ||||
| Conditional visibility / readonly / required rules from UI | ||||
| Auto-generated security (ir.model.access.csv + record rules) | ||||
| Built, installed, tested & documented for your exact database | ||||
| Change-tracking with preview and one-click rollback | ||||
| Supported across Odoo 17, 18 and 19 with a named contact |
This is a build-to-order module, not an instant apps.odoo.com download. Typical delivery is 2–4 weeks: a short scoping call to confirm your Odoo version, edition and target models; ECOSIRE builds and hardens the module; we install it on your staging instance, test against your data and permissions, then deploy to production and train your team. You receive the full source code at handover.
Every engagement includes a defined post-launch support window with a named ECOSIRE contact and agreed response terms for bug fixes. Because you receive the complete, standard-Odoo source (manifest, models, views, security), you're never locked in — your own team or any Odoo partner can maintain it. We also offer optional ongoing support retainers and paid feature enhancements, and we validate the module against new Odoo minor releases on request.
It delivers a Studio-style no-code experience — visual field, tab, button, computed/related field and conditional-rule editing — but it runs on Odoo Community (no Enterprise subscription required) and, unlike Studio, exports every change as a standard installable module you can commit to git and deploy through CI. Studio keeps customizations inside the database; this gives you reviewable, portable code.
Yes — the module generates real Odoo primitives (ir.model.fields, view inheritance via XPath, proper compute methods with @api.depends, ACL and record rules) rather than fragile hacks, and it supports Odoo 17, 18 and 19. Because your changes are exportable as a versioned addon, upgrading is a normal module migration instead of trying to reproduce untracked UI clicks. We can also assist with the version migration as a scoped add-on.
That's the point. Business users work in a guided UI that maps to safe operations, with change-tracking so any customization set can be previewed, disabled or reverted without hand-editing the database. New fields and models are automatically scaffolded into security/ir.model.access.csv so nothing is exposed without an explicit ACL, and computed fields use validated formula building rather than free-form Python. During training we set the guardrails that fit your team's skill level.
Yes. It can add fields, tabs, buttons and views to any model in your database — Odoo core apps, your own custom modules, or third-party addons — because it uses standard view inheritance targeted by stable XPath. New logic can also integrate over XML-RPC/JSON-RPC if you drive customizations from external systems. During scoping we confirm the target models and flag any that need special handling.
Add fields, tabs, buttons, computed & related fields, and views to any Odoo model from the UI — no code. A Community-edition Studio alternative.