Writing requirements

OdoMate turns a written description of what you need into an installable Odoo 19 module. You do not write Python or XML — you describe the business behaviour you want, and the platform designs the data model, screens, and access rules to match.

What a good requirement looks like

Write the way you would brief a colleague. Name the things the business cares about, what information each one carries, and who is allowed to touch it.

Track equipment loans. Each loan records the item, the borrower, the date it went out, and the date it came back. Warehouse staff can create and close loans; everyone else can only read them. Show overdue loans in red.

That description contains everything the generator needs: the records to store, the fields on them, the permissions, and one piece of interface behaviour.

Note

Requirements must be at least 10 characters and no more than 100,000. There’s no on-screen counter, so if you’re pasting in an existing spec rather than typing one, keep it under that limit.

Starting from a template

If a blank page is the hard part, click one of the example buttons below the text box — Customer Feedback, Equipment Tracking, Leave Management, Expense Tracker, or Meeting Rooms. Each fills the box with a complete, ready-to-generate requirement for that kind of module, models and business rules included. Edit it in place before continuing, or generate it as-is to see what a fully-specified requirement looks like.

What to include

• The records you want to track, in the language your team already uses.
• The fields on each record, including which are required.
• Who may see and change each thing — roles, not individual names.
• Anything that must happen automatically, such as a status that changes when a date passes.

What to leave out

Do not specify technical structure: model names, table layouts, view types, or which Odoo app to extend. Those are decisions the generator makes, and pinning them early usually produces a worse module than describing the outcome.

Attaching images

Below the text box, drag in screenshots, mockups, or diagrams — or paste one straight from your clipboard with Cmd+V. Up to 10 images, PNG, JPG, WebP, or GIF, 10 MB each. The business analyst treats them as visual context alongside your text, so a screenshot of a similar screen in another system, or a hand-drawn layout, can stand in for a paragraph describing it.

After you submit

A business analyst can refine the description in conversation before anything is built — asking for a missing field, a different permission, or an extra screen. The generated module is then installed into a sandbox so you can click through it before downloading.