TL;DR: in Odoo, the official tool for customizing your screens without code (Studio) requires the Enterprise edition, Custom plan. Our Forge module brings the essentials back to the Community version: adding fields, smart buttons, default values and shared filters, all point-and-click, with guardrails that protect your critical data.
Your Odoo has been doing the job for two years. Invoicing hums along, projects move forward. Then one morning, the office manager asks for something very simple: a "File number" field on the client record, to stop jotting it down in the comments. A five-minute request, on the surface.
Odoo's official answer to that request is called Studio. And Studio comes with a condition: the Enterprise edition, Custom plan, starting at $55 CAD per user per month on annual billing. Since Odoo bills every user in the database at the same plan, your five-minute field costs a ten-person team about $6,600 per year. Every year.
The real price of a missing field
We've already written about choosing between Odoo Community and Enterprise : Enterprise has real merits, and for some organizations it's the right call. But when the only reason to migrate is "we're missing a field", the bill is hard to justify. The Community version is open source, complete for the vast majority of an SMB's operations, and it's the one we deploy by default.
The problem is that without Studio, adding a field in Community takes a developer: building a small module, testing it, deploying it, maintaining it through every update. It's doable, we do it regularly, but it's out of proportion for simple needs. There was a missing middle between "pay for Enterprise for everyone" and "call a developer for every field".
Forge, the concept
Forge is that middle. A wizard in your Odoo Community where an authorized person, not necessarily technical, can:
Add a field to just about any record: contact, task, project, product. Text, number, date, checkbox, selection list, image. You choose where it shows up: in the form, after a given existing field or in a given tab, and whether it also appears in lists and kanban boards.
Display related information without retyping it: for example, showing the client's country directly on their tasks. The field fills itself in from the original record.
Make a field conditional: visible only in certain cases, required from a given stage onward, read-only once the file is closed.
Add a smart button that counts related records, "3 invoices", "7 tasks", and opens the list in one click.
Set default values and shared filters for the whole team, without everyone cobbling together their own views.
And the detail that matters down the road: your customizations survive Odoo updates. The module keeps its own list of what you've created and restores it automatically if an update wipes it out. A field added in 2026 will still be there in 2028.
Why we made it cautious
A tool that changes your system without code is also a tool you can hurt yourself with. So we added guardrails, and we stand by them:
Critical areas are locked by default. Nobody is going to "customize" accounting, users or payments on a Friday afternoon. The right to use Forge is a separate access right, granted to one or two trusted people, not the whole team. And the module doesn't allow arbitrary code: conditions are written in a simple, controlled language, which closes the door on accidental damage and malicious mischief alike.
It's a difference in philosophy from some no-code tools that hand over every power right away. We prefer a tool that covers 80% of needs without ever letting you saw off the branch your business is sitting on.
The blind spots
Forge doesn't replace Studio 100%, and that's not the goal. It doesn't create entire new record types ("I want to manage my equipment with its own screens" is a small custom module). It doesn't redo a screen's full layout, doesn't design custom PDF reports, and doesn't automate complex business logic. Studio, on Enterprise, does part of those things, and a developer does the rest.
Our recommendation, in order:
- Check whether a standard Odoo field already does the job: there are more of them than you'd think.
- Forge for the everyday custom fields, buttons and filters.
- A small dedicated module when there's real business logic involved: it's more robust and testable.
At Blue Fox
Forge runs on our own instances and at our hosted clients, with the locks turned on. Like the rest of our modules, it's published under an open-source licence on GitHub: you can inspect it, install it yourself, or let us do it cleanly.
If your team has been living with "missing fields" for months, or if an Enterprise quote landed on your desk just for that, let's talk about your Odoo.
Sources
- Odoo pricing and edition comparison : Studio is Enterprise-only, Custom plan (checked June 2026)
- Odoo licences : Community is under the open-source LGPL v3 licence
- The
bf_studio_lightmodule on our GitHub repository and its card on our modules page