Odoo Module Generator

Scaffold a standards-compliant Odoo 17, 18 or 19 custom module without leaving the browser. Pick the target version, enter a module name and a model, and the generator produces a clean, ready-to-install package: __manifest__.py, a sample model, list and form views, menus, a pre-filled ir.model.access.csv, and an optional pre-translated Vietnamese vi.po. It adapts the view syntax to the version (<list> on 18/19, <tree> on 17). Preview every file, then download the whole module as a .zip. Nothing is uploaded — generation runs entirely on your device. Full guide →

Odoo Module Generator

Everything runs in your browser — nothing is uploaded to a server.

Module technical name

Main model

Odoo version

Depends

Add Vietnamese i18n (pre-filled vi.po)

Generated files (11)

sale_extension/__manifest__.py

# -*- coding: utf-8 -*-
{
    'name': 'Sale Extension',
    'version': '18.0.1.0.0',
    'summary': 'Sale Extension for Odoo',
    'author': 'atdev.blog',
    'website': 'https://atdev.blog',
    'license': 'LGPL-3',
    'category': 'Uncategorized',
    'depends': ['base', 'sale'],
    'data': [
        'security/ir.model.access.csv',
        'views/sale_bonus_views.xml',
        'views/sale_bonus_menus.xml',
    ],
    'installable': True,
    'application': False,
    'auto_install': False,
}

Scaffold an install-ready Odoo 17–19 module

What is this tool?

A scaffolder that generates a complete Odoo module (17, 18 or 19) from just a module name and a model: manifest, sample model, list/form views, menus, a pre-filled access-rights file, and optional Vietnamese i18n. Preview every file, then download it as a .zip.

Everything runs in your browser — nothing is uploaded. Unlike the bare `odoo-bin scaffold`, this fills in the parts developers forget (especially access rights), so the module installs and runs.

When should you use it?

When starting a new module and you would rather not copy-paste and edit an old one. When teaching juniors which files a module needs and how they fit together.

When a module must show Vietnamese labels for vi_VN users: enable the i18n option to get a pre-translated vi.po.

What the module contains

`__manifest__.py` (version 18.0.x.y.z, depends, data, license), a `models/` folder with a sample model, `views/` with list + form + window action, a menus file, and `security/ir.model.access.csv` with one access line pre-filled.

Views adapt to the version you pick: `<list>` + `view_mode="list,form"` for Odoo 18/19, or `<tree>` + `tree,form` for Odoo 17; the manifest version follows too (e.g. `17.0.1.0.0`). A README and static/description are included so the module is tidy from the start.

The Vietnamese i18n option

Following the Odoo convention: source strings stay English in the code; translations live in `i18n/vi.po`. The tool ships a vi.po with sample strings pre-translated (Customer → Khách hàng, Status → Trạng thái…) plus a `.pot` template.

Odoo loads vi.po automatically when the user language is vi_VN and the module is installed or upgraded. After adding fields, re-export the `.pot` and merge to update translations.

Using the output safely

Add `static/description/icon.png` so the module shows an icon in the Apps list. Always back up the database and test `-u` on staging before production.

This is a starting skeleton — review the generated code and adjust fields/permissions to your real business logic before installing on a live system.

Related Tools

All tools

QR Code & Barcode Generator

Generate customizable QR codes with colors, logos, and download options

CSV to Excel

Convert CSV files to Excel format (XLSX or XLS) with auto-sized columns

Markdown to Word

Convert Markdown (.md) files to Word documents (.docx) with formatting

Vector Embeddings Formatter

Format vector embeddings into JSON, Python, SQL (pgvector), Pinecone, or MongoDB syntax

About Scaffold Odoo modules the right way

A browser-based scaffolder for Odoo 18 custom modules. It generates the files developers always need — __manifest__.py, models, list/form views, menus, and a pre-filled ir.model.access.csv — plus an optional Vietnamese i18n file, then bundles everything into a downloadable .zip.

Key Features

-Target Odoo 17, 18 or 19 — correct view syntax and version per series
-Standards-compliant module structure (manifest, models, views, menus)
-Pre-filled ir.model.access.csv (no more "model not visible")
-List + form views and menus wired to a window action
-Sample model with Char, Text, Many2one, Float, Date and Selection fields
-Optional Vietnamese i18n: pre-translated vi.po + .pot template
-Live file preview, then one-click .zip download
-100% client-side — nothing leaves your browser

Use Cases

Bootstrap a new module

Skip the boilerplate and start from a clean, install-ready skeleton instead of copy-pasting an old module.

Teach Odoo structure

Show juniors exactly which files a module needs and how manifest, models, views, security and i18n fit together.

Vietnamese-ready modules

Generate a translation-ready vi.po so the module shows Vietnamese labels for vi_VN users out of the box.

Prototype data models

Pair it with the SQL → ERD tool to sketch relationships, then scaffold the matching module.

Frequently Asked Questions

Is this an official Odoo tool?▾

No. It is a free helper from atdev.blog that generates a clean module skeleton following Odoo 18 conventions. Always review the output before installing.

Does it replace odoo-bin scaffold?▾

It complements it. Unlike the bare odoo-bin scaffold, this fills in security access lines, list/form views, menus and an optional pre-translated Vietnamese i18n file.

Where is my data sent?▾

Nowhere. The generator runs entirely in your browser; the .zip is built locally and never uploaded to any server.

How does the Vietnamese option work?▾

It adds an i18n/vi.po with the sample strings pre-translated (Customer → Khách hàng, etc.). Odoo loads it when the user language is vi_VN. Keep source strings in English and translate via .po — the standard Odoo convention.

Which Odoo version does it target?▾

You choose: Odoo 17, 18 or 19. The generator adapts the list view tag (<tree> for 17, <list> for 18/19), the view_mode and the manifest version (e.g. 17.0.1.0.0) to the version you pick.

Tips & Best Practices

-Add static/description/icon.png so your module shows an icon in the Apps list.
-Back up the database and test the upgrade (-u) on staging before production.
-After adding fields, re-export the .pot and merge the new strings into vi.po.