Technology partners

We are your Odoo team

We are the technology partner of software companies.

Your customers run Odoo and ask you for integration. We build the connector, publish it on the Odoo App Store and maintain it version after version.

Odoo Learning Partner 117 published modules · 19.0 · 18.0 · 17.0

Tell us what API your product has See a published module

How it fits

You Your product E-signature, PIM, POS, HR, logistics…

Your API

Us FlexigoTech connector Odoo module in Python, tested on a real Odoo

Odoo App Store

Your customer Their Odoo Installs on Odoo 19.0 · 18.0 · 17.0

Already done with

117modules published on the Odoo App Store

3versions maintained: 19.0, 18.0 and 17.0

6technology partners with their connector built

1public demo where you can see it working

What you get

Being in Odoo without building an Odoo team

Your sales team stops answering "not yet" when someone asks whether your product integrates with Odoo.

01 You are where they look for you The listing lives on the Odoo App Store, which is where an Odoo customer goes looking for integrations.

02 No hiring, no training Odoo has its own rules: ORM, views, access rights, migrations. That part is ours.

03 Odoo ships a version every year The migration to the next version is planned, not improvised: we already maintain 117 modules on 19, 18 and 17.

04 Credentials belong to the customer We do not resell your service nor sit between you and the account: the customer enters their own keys for your API.

How we do it

Four steps, no surprises

The same path we followed with the partner connectors we have already built.

01 You send us the API Documentation and a test environment. We return the scope in writing.

02 We build the connector An Odoo module with its tests, run against a real Odoo, not a local one.

03 We publish it A listing on the Odoo App Store, with screenshots and description, on 19.0, 18.0 and 17.0.

04 We maintain it Changes in your API, customer issues and the new Odoo version every year.

Partners

Partners we already work with

These two are e-signature platforms and each one has its own connector: by default there is no exclusivity.

E-signature. Connector built and published on the Odoo App Store, with partner review rounds and maintenance on our side.

Published · 19.0 · 18.0 · 17.0

E-signature. Connector built and tested on Odoo 19, 18 and 17, with a demo for the partner sales team.

Built · 19.0 · 18.0 · 17.0

Connectors built for technology partners

e-Signature.eueIDAS electronic signature
ScriveElectronic signature
SignaturitElectronic signature
seQuraBuy now, pay later
B2BrouterElectronic invoicing
SERESElectronic invoicing

These are technology partners. If you are a consultancy or an Odoo partner, your door is a different one: Odoo partners and engineering for consultancies.

What we need from you

Three things to get started

Nothing else. The Odoo side is on us.

API Your API documentation Endpoints, authentication and one working example call. REST, SOAP or whatever it is.

ENV A test environment A sandbox or trial account with fake data, so we never touch your customers' data.

WHO A technical contact Someone on your team who answers concrete questions while the development lasts.

Questions

What a partner asks before signing

If your question is not here, write to us: the person who will write the connector answers.

Who owns the connector's code?

It is set in writing in the scope before we start. Some partners want the code in their repository and the App Store listing under their name; others prefer that we publish and maintain it under our partner account. Both formulas are possible; what does not change is that we do the maintenance on Odoo 17, 18 and 19.

Who bills the end customer?

It depends on how you want to distribute it: the connector can be free on the Odoo App Store (your product pays for it) or paid. Your API credentials always belong to the end customer: we do not resell your service nor sit between you and their account.

What happens when Odoo 20 comes out?

Odoo releases a new version every year. We migrate the connector, test it on a real Odoo and publish it, just as we do with our 117 modules on 17, 18 and 19. How that work is covered is agreed in the maintenance.

Is there exclusivity?

By default no: e-Signature.eu and Scrive are two e-signature platforms and each has its own connector. If you want exclusivity in your category, it is agreed in writing and with a term.

How does my team try it without installing anything?

In the public demo: a real Odoo with the connector installed, where your sales team logs in and sees it working. Also, from the App Store listing any customer can download the module and try it on a trial Odoo.sh or on their own installation.

Next step

Tell us what API your product has

Product, a link to the API documentation and how many customers are asking for it. With that we return a scope and how we would do it.

The connector is published on the Odoo App Store for 19, 18 and 17.
It is tested on a real Odoo before being published.
Your API credentials always belong to the end customer.

If your documentation is private, say so in the form: we sign an NDA before looking at it.

See a published module

Form for technology partners

The person who will write the connector answers you.