Services
Odoo Third-Party App Development
Publishing on the Odoo Apps Store turns internal capability into product: recurring revenue, inbound leads, and code quality forced to third-party standard. It’s also a discipline of its own: store guidelines, version support matrices, licensing decisions and the support burden of strangers running your code.
We know because we live it: our own connectors are published, versioned and maintained as commercial products, with release notes, store listings and support processes behind them.
What the work involves
- Store-grade engineering. Code meeting Odoo’s guidelines and the unwritten standards reviewers apply: proper manifests, clean dependencies, no dubious patterns.
- Multi-version support strategy. A maintenance approach across the Odoo versions your buyers actually run, with branch management that keeps it sane.
- Listing craft. Store listing copy, screenshots and documentation that convert, informed by publishing and iterating our own product listings.
- Licensing and pricing decisions. LGPL vs OPL, one-time vs recurring, tier structure: commercial choices with long consequences, made deliberately.
- Post-launch operations. Release process, changelog discipline, support workflow and refund policy: the machinery that makes a store app a business instead of a burden.
How custom work is delivered
- Specification from the business outcome. We start from what the work must achieve, not a feature list, and write it down so both sides can point at it later.
- Fixed quote with an hours breakdown. You see where the effort goes before committing. Vague briefs get discovery questions, not padded numbers.
- Build on staging against acceptance criteria. Development happens against your real data structures, with the acceptance tests agreed upfront.
- Your sign-off on staging. You test the work where breaking things is free. Nothing promotes to production on our say-so alone.
- Deploy, document, hand over. Production release, technical documentation, and the code in your repository. No hostage situations.
Common questions
Can you productise a module we built internally?
Yes, that's the classic path: generalise the client-specific parts, harden the edges, document, list. We'll also tell you honestly if the market slot is already crowded.
What does ongoing maintenance of a store app involve?
Each new Odoo version needs a port and test cycle, plus user support and periodic fixes. Budget for it as a product cost; we can carry it under retainer.
Will you build and we publish, or you publish for us?
Either. Some clients want the store presence under their brand; others want us to own the product operationally. Both models are in writing before work starts.
Not sure where to start? Book a free discovery call and we’ll map your current setup, or request a free Odoo health check if you’re already running Odoo.