Publish an app on the Omnifloo store
The store is open to Omnifloo partners. App pages are generated from your Git repository: you enter nothing online; your manifest and your description are authoritative.
Journey
- Application: become a partner (free for now).
- Active partner: in your workspace (/my/partenaire), submit the URL of a public
Git repository (GitHub or GitLab), branch
20.0. - Immediate pre-check against the rules below (a few seconds).
- Quarantine: trial installation in a disposable Odoo 20 database, checks on size, links and sensitive calls.
- Validation by the Omnifloo team, then publication of the verified commit (never the branch head). An update goes through quarantine again.
- Your app pages appear at the next (daily) synchronisation, with your publisher page.
Automatic checks
| Check | Effect | Rule |
|---|---|---|
| Manifest readable without execution | blocking | Python literal dictionary |
| Series | blocking | 20.0.x.y.z version on the 20.0 branch |
| Licence | blocking | LGPL-3, AGPL-3, GPL-3, OPL-1, MIT, Apache-2.0 or another OSI licence; OEEL-1 refused |
| No Odoo Enterprise code | blocking | no dependency, no import, no Enterprise licence header |
| Declared author | blocking | author key |
| Icon | downgrades | static/description/icon.png |
| Description | downgrades | static/description/index.html (no script) or README |
| Tests | downgrades | tests/test_*.py |
| French translation | information | i18n/fr.po |
| “What the module does not do” | information | section present in the description |
Content rules
- Describe only what is in the delivered code: never present a planned feature as done.
- A “What the module does not do” section is expected on every app page.
- No Odoo S.A. icon or screenshot; no third-party trademark in the app name.
- Declared support (email or web address); visible customer reviews, with your reply.