Loading…
We don't build connectors on guesswork. Each candidate is scored against demand, repeatability, customer pain, and monetization fit — and we secure design partner commitments before MVP development begins.
The first release is a Marketplace-ready MVP: secure auth, clear configuration model, automated tests, versioning, and documentation. Built on Odoo.sh-compatible patterns by default.
Marketplace listing prepared per Odoo Apps Store vendor guidelines: copy, screenshots, manifest pricing, support email. Design partners onboard first, then public release.
Bring us the constraint. We'll bring the team.
An Odoo connector is a small piece of software with a long ownership tail. Customers configure it, depend on it, upgrade it, raise tickets against it, and expect it to work two Odoo versions later. Treating connectors as side projects — built once, listed on the Apps Store, never seriously maintained — is a leading cause of broken third-party Odoo integrations. We build connectors as products, with the same engineering and commercial discipline we'd apply to any commercial software.
The Odoo Apps Store provides a viable commercial platform when paired with proper onboarding and support packages. We use it as a distribution channel — not the entire commercial model.
We don't speculate on connector market fit. Each candidate is scored against demand and repeatability (how many customers need this?), pain severity (how much friction does the absence of this connector create?), monetization fit (will customers pay for it?), build effort to MVP, and maintenance risk (is this Odoo-version coupled, vendor-API coupled, or both?). Design partners are secured before MVP development starts.
Every connector ships with a secure authentication model (no credentials in plaintext, no secrets in the repository), a clear configuration model (settings the customer can understand without reading source code), automated test coverage (unit and integration tests gating every change), and a versioning strategy compatible with Odoo's upgrade cadence.
Listings on the Odoo Apps Store follow vendor guidelines for documentation, screenshots, copy, and pricing manifest configuration. Pricing and currency are declared in the module manifest. Commission and commercial terms are accepted on publish. The listing is treated as marketing collateral — written for customers, reviewed before submission, updated when the product evolves.
Paid customers receive onboarding documentation that walks through installation, initial configuration, common workflows, troubleshooting, and integration patterns. Onboarding isn't a README — it's a structured experience that reduces time-to-value and ticket volume in equal measure.
Customers paying for the connector receive an SLA-backed support workflow with documented response times, escalation paths, and ticket management. Support is not optional — it's part of the product.
Defect fixes ship on a documented cadence. Security updates ship as soon as they're identified. Odoo version compatibility releases ship in coordination with each major Odoo release — not several months after, by which time customers are already stuck. Connectors are products with a roadmap, not artifacts.
Paid customers receive structured onboarding documentation, configuration walkthroughs, and an SLA-backed support workflow. Connectors are sold with the support model — not just the code.
Defect fixes, security updates, and Odoo-version compatibility releases ship on a documented cadence. Connectors aren't ship-and-forget — they're products.