19 September 2026 · 3 min · Custom Odoo
A Studio for Odoo Community: customise your screens without code
Odoo Studio, the official no-code customisation tool, is Enterprise-only; in Odoo Community you can get most of its features — editing PDF invoices, adding fields, designing labels, setting access rules — with dedicated apps such as Ramira Studio, published on the official store for Odoo 18, 19 and 20. Here is what you can do, what you cannot, and when to switch to a custom module.
The problem: Community without Studio
Odoo Community is an excellent, free foundation. But everyday requests come fast:
- “Can we add the project number on the invoice?”
- “We need a ‘warranty date’ field on products.”
- “Sales reps must not see the cost price.”
- “We want to print labels with barcodes and locations.”
With Enterprise, Studio answers in a few clicks. With Community, until now you needed a developer or developer mode.
Developer mode: possible but fragile
Community’s developer mode lets you create fields (prefixed x_) and edit views or reports by changing their XML. Useful for a quick fix, but you need to know Odoo’s structure, a mistake can break a screen, direct changes can be overwritten or block an upgrade, and nothing is documented or cleanly exportable. See adding custom fields in Odoo.
The Ramira Studio apps
| App | What it does |
|---|---|
| PDF Report Editor | Edit invoices, quotes and orders: fields, texts, columns, watermarks, preview on a real document |
| Label Designer | Product labels, EAN-13 and Code 128 barcodes, QR codes; PDF sheets, rolls and ZPL |
| Word Templates | Contracts, certificates and letters written in Word with fields, printed from any record |
| Custom Fields | Text, number, date, checkbox, selection, link or tags on any screen |
| Access Rules | Hide or lock fields, buttons, tabs and menus per group or user |
| Menus and Batch Sending | Rename, reorder or hide menus; email PDFs in batches |
| Approvals | Require approval before any button, in several steps |
| Audit Log | Who changed what and when, with restore |
All rely on a free shared engine, Ramira Studio Base. Prices and store links are on our Odoo apps page.
What happens to customisations
Customisations made with Ramira Studio are stored as data, not as changes to Odoo’s code. They survive module updates, can be exported and imported (from test to production) and follow the migration to a new Odoo version (see migrating an Odoo module).
Concrete examples
- Invoice with project number and site address: a custom field on the order, shown on the invoice with the report editor — see customising Odoo invoices.
- Warehouse labels: barcode, reference, location and lot on a thermal printer — see Odoo product labels and barcodes.
- Cost price hidden from sales reps: an access rule — see managing access rights in Odoo.
When to go custom
Studio apps cover adjustments. For a complete process — a new business object with screens, calculations, workflow and reports, or a connection to other software — a custom module is more robust. Our Studio for Odoo Community offer combines app installation, configuration and training.
In short
No official Studio in Community, but no need to code every adjustment: Ramira Studio covers the essentials, cleanly and durably. Still choosing an edition? Read Odoo Community vs Enterprise. A question about your case? Write to us.
FAQ
Do Ramira Studio customisations survive upgrades?
Yes. Customisations are stored as data, separate from Odoo’s code, and can be exported and re-imported into another database or a new version.
Do I have to buy all the apps?
No. Each app is sold separately, for example only the PDF report editor. Packs bundle several apps for those who want more.
Does Ramira Studio also work with Enterprise?
The apps are designed for Community, where Studio does not exist. On an Enterprise database, the official Studio already covers these needs.
Sources
Mohamed Rahmouni — founder of Ramira, app developer and Odoo consultant in Niort, France. More