Generating your first module

Once a requirement is finalized, OdoMate turns it into a working Odoo 19 module: it designs the data model, screens and access rules, writes the code, and installs the result into a sandbox so you can click through it before downloading anything.

Read writing requirements first — generation starts from a finalized requirement, not a raw description.

Note

Generation is limited to invited accounts, and each account gets a daily cap on generations and total cost (20 runs and $25 by default — your workspace may set a different limit). You can also only have one generation running at a time; start a second and OdoMate points you back at the one already in flight.

Configure the run

Before you generate, choose:

• AI model — Auto routes by complexity (Sonnet 5 for simple modules, Opus 5 for complex ones) and is the recommended default. Pin Opus 5 for the highest quality on a hard module, or Haiku 4.5 for the fastest turnaround on a simple one.
• Translations — pick languages to generate .po files for, alongside the module’s default English strings.
• Demo data — have OdoMate generate realistic sample records so the module isn’t empty the first time you open it.
• E2E testing — after generation, install the module in Odoo and click through it in a real browser, catching problems before you do. This adds time to the run but is the difference between “the code compiles” and “the screens actually work.”

Select what you need and click Generate Module.

Watch it build

1. Discovery — OdoMate searches its Odoo 19 knowledge base for the patterns your requirement needs (models, views, security rules similar to what you described).

2. Implementation — it scaffolds the module and writes the models, views, and access rules.

3. Validation — it checks the generated Python, XML and CSV for syntax errors and fixes what it finds.

4. Browser Testing — if you turned on E2E testing, it installs the module into a live Odoo database and drives the UI to confirm the screens work, fixing and re-testing anything that fails.

5. Complete — the module is ready.

An activity log streams what the agent is doing in real time under the phase you’re in. Simple modules usually take 10–25 minutes; complex ones — especially with E2E testing on — can take noticeably longer. You can safely close the tab and come back later: the run keeps going on the server, and reopening OdoMate reconnects you to it in progress. A Stop button is available while a run is in progress, but stopping discards all progress and marks the run as failed — there’s no resuming a stopped run.

What you get

When a run finishes you land on a summary of what was built: file count, estimated lines of code, generation time and cost, the full activity log, and a file tree of everything the agent wrote.

From there:

• Preview in Odoo opens a sandbox with the module already installed, so you can click through it as different roles before deciding to keep it. This button is only available when the agent verified the module installs cleanly — if it couldn’t verify that, you’ll see a warning instead and can still download the module, but it may need fixes.
• Download ZIP gives you the module as an archive to install into your own Odoo instance (see installing a module locally). The download link expires after 24 hours.
• User Guide is a plain-language write-up of what the module does and how to use it, generated alongside the code — copy it out or hand it to whoever will actually use the module.

Every run — whether it finished, failed, or was stopped — is saved to your account, so you can find it again later even if you close the tab before it’s done.