Enhancing a module
Generation isn’t the only way a module’s code changes. Once a module has a finished version, you can describe a change in plain language and OdoMate updates the existing code rather than starting over — a new field, a fixed bug, an extra screen. This is different from rolling back a module version, which only restores something that already exists; enhancing asks the AI to write new changes, the same way generating your first module does, just starting from your module’s current code instead of a blank slate.
Starting an enhancement
Section titled “Starting an enhancement”Open the Modules Library and find the module’s card. Next to Open test environment is an Enhance button — click it.
-
Describe the change. Type what you want changed or added — be as specific as you would with a colleague, for example “Add a discount field to the sale order line and apply it automatically at checkout.” You can attach up to 5 screenshots alongside the description.
-
Decide on end-to-end testing. The Run end-to-end tests toggle installs and clicks through the enhanced module in Odoo before promoting the new version, the same as the toggle during generation — it adds time but catches problems a code-only check wouldn’t.
-
Click Start.
Review and refine
Section titled “Review and refine”Before changing anything, OdoMate reads the module’s current code and its spec — this step is read-only, nothing is written yet. If OdoMate can pick up the same conversation it used to build the module in the first place, it skips this and shows Continuing with full context from your previous session instead, going straight to the next step with everything it already knows about the code.
Once the review finishes, you land on a discuss screen with three ways forward:
- Enhance now — go straight to implementation with what you already described.
- Polish with AI — open a chat to refine the request first, if you want to talk through details before committing.
- Finalize requirements — lock in a written spec from your description without chatting.
Watch it implement
Section titled “Watch it implement”Once you move past discussion, an activity log streams what the agent is doing, the same as a fresh generation. If you turned on end-to-end testing, it installs the updated module and clicks through it after the code changes land.
If your connection drops mid-run, Retry picks up from where it stopped rather than starting the enhancement over — your session is preserved.
What you get
Section titled “What you get”When it finishes, you land on a Version N is ready screen, with:
- Open test environment — your module’s preview is swapped to the newly enhanced version, the same as after a fresh generation.
- Download ZIP — the enhanced module as an archive (see downloading a module).
- Guide (PDF) — an updated user guide, if OdoMate generated one for this version.
The new version gets its own entry in the module’s version-history sheet, same as any other version — nothing earlier is overwritten, and you can still roll back to an older one later.
When it doesn’t go as expected
Section titled “When it doesn’t go as expected”- No changes were needed. If the agent finds the module already does what you asked, it makes no changes and no new version is created — this isn’t treated as a failure, and you can describe a different change from the same screen.
- Ready, but not fully verified. The module installed and is available to download, but a runtime check didn’t pass, so it may need fixes before it runs cleanly — the same distinction generation makes on its completion screen.
- Implementation failed. Use Retry — it continues from where the run stopped rather than starting over.
- Enhancement unavailable. A module can only be enhanced while its archive still exists. Once a version passes the 90-day retention window (see downloading a module), enhancing is blocked with the same message rollback and download show for an expired archive.
