This module allows the administrator to prototype new features and export them as module. Functional people can prepare the job for a developer who is left with the logic to implement in addition to everything the prototype does not export yet.
Installation
Make sure you have Jinja2 version 2.7.3 or higher installed:
$ pip install --upgrade Jinja2==2.7.3
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Lets administrators assemble a new Odoo module from existing customisations (fields, views, menus, security, reports, data) and download it as a ready-to-install zip file.
This module adds a "Module Prototypes" area under Settings for system administrators. There you create a prototype record where you describe the future module: technical name, displayed name, summary, description, author, website, version, license, icon, category, dependencies, and whether it is an application or auto-installed.
On the same screen you pick the pieces of your current database that should be included: - Fields you created or changed (new models are exported as soon as one of their fields is selected). - Views, menu items (with their window actions), groups, access rights, record rules and reports. - Data and demo records, chosen through saved filters; the matching records are exported as data or demo files.
The form has an Export button that opens a wizard where you choose the target Odoo API version (8.0, 10.0, 12.0 or 14.0). The system then generates the module files from templates and returns a zip archive you can download and install.
It also extends the technical field and model screens with extra inputs: notes for developers, a helper text, relation-table column names, a read limit and a client-side context, so the prototype carries enough detail for a developer to finish the job.
Menus it adds
Models and fields (4)
- ir.model.fields · extends an existing modellimit (Read limit), notes (Notes to developers.), helper (Helper), column1 (Column1), column2 (Column2), client_context (Context)
- module_prototyper · new modelname (Technical Name), author (Author), license (License), summary (Summary), version (Version), website (Website), data_ids, demo_ids, menu_ids, rule_ids, view_ids, field_ids, group_ids, right_ids, human_name (Module Name), icon_image (Icon), maintainer (Maintainer), report_ids, application (Application), category_id, description (Description), auto_install (Auto Install), dependency_ids
- module_prototyper.api_version · new modelname, manifest_file_name
- module_prototyper.module.export · new modeldata (File), name (File Name), state, api_version (API version)
Text generated by AI (DeepSeek) from reading the Odoo 14.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/server-tools.
terminal Installation and usage
OCA documentation · Odoo 14.0Usage
Source · Odoo 14.0To use this module, you need to:
- install the dependencies of your future module
- customize your instance by adding fields and creating inherited views
- create your menu items and their window actions
- prepare your data and demo data by creating filters
- create your own groups with access rights and record rules
- add your own access rights and record rules to an existing group
Once you have customized your instance properly, you can go to Settings > Module Prototypes > Prototypes and create a new prototype:
- fill in the information of your module (enter the name, the description, the logo, etc.)
- in the Depencencies tab, select all the other modules that yours will be depending on
- in the Data & Demo tab, select your filters for data and demo data
- in the Fields tab, select the fields you created or customized
- in the Interface tab, select your menu items and your views
- in the Security tab, select your groups, access rights and record rules
- save and click on export
You will get a zip file containing your module ready to be installed and compliant with the conventions of the OCA. You can then provide the module to a developer who have to implement things like default values or onchange methods.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.