Odoo integrations and apps: configure first, build last

No. Brainvire publishes one module on the Odoo App Store, EZlytix Analytics Solution, built for Odoo 12.0 and licensed LGPL-3. Everything else we build for Odoo is built for one client, in that client’s repository, and maintained with them. There is no Brainvire app catalog, and this page is deliberately not one.

Install the app if it is maintained, has a build for the version you are on, and its dependencies are ones you were going to run anyway. Build a module when the behavior does not exist in Odoo and no app covers it. Either way you are choosing who maintains it at the next upgrade.

Odoo states that a database containing custom modules cannot be upgraded until a version of those modules exists for the target version. A third-party app is a custom module as far as that rule is concerned. So the app’s version coverage decides your upgrade date unless you are willing to remove it.

Studio is enough when the change is a field, a view, a PDF report, an automation rule or a security rule with no new business logic behind it. It stores its work as data in the database. A developer is needed once the requirement is behavior, because behavior belongs in versioned code with tests.

Adobe Commerce, Shopify, Amazon, Salesforce, SAP REFX, QuickBooks and RFID readers, each with a named case study linked on this page. That list is what we can evidence. We keep it short on purpose: an integration nobody can point to a program for is a claim, not a capability.

Yes to both, and they are the first thing to try. Odoo ships an Amazon Connector that synchronizes confirmed FBA and FBM orders, and a third-party shipper setup for carriers such as UPS, FedEx and DHL. Custom work starts where those stop, which for Amazon is anything beyond sales-order data.

Yes, and it is a common way for a relationship to start. The first step is an inventory: what is installed, who wrote it, which version it targets, what it writes to the database, and whether it has tests. Only after that can anyone say honestly what an upgrade would take.

By asking what would have to be true for the integration not to exist. Sometimes the answer is a platform decision instead: Bay Alarm Medical replaced a Magento cart with Odoo commerce and ended up with zero APIs between storefront and ERP. An integration you never build cannot break at the next upgrade.

A connection that moves data between Odoo and another system, such as a storefront, a CRM or a marketplace, so orders, stock, invoices and customer records stop being keyed in twice. Odoo describes its own business apps, from CRM and accounting to inventory and point of sale, as fully integrated, so an integration only matters where the data lives somewhere else. It can be a connector Odoo ships, a third-party app, one of the middleware services that sit in between, or custom code against the external API.

Modules published on the Odoo App Store by anyone other than Odoo. You find them on odoo.com under Third party apps in the Apps menu, and the store filters them by Odoo version, by platform, and by price, open source or paid. They add features and functionality standard Odoo does not ship, and Brainvire’s EZlytix module is one of them. The database administrator, not the publisher, is responsible for how each one is used.

Each publisher sets its own price, and the store separates open-source apps from paid ones. The listing price is rarely the whole cost. Odoo warns that adding or removing apps can affect other apps in the database and modify subscription costs, the app needs a build for every version you upgrade to, and someone has to manage it through each upgrade. We would rather price that ownership up front than discover it at the first upgrade.

The Odoo Community Association (OCA) is a non-profit organization based in Switzerland that provides thousands of Odoo modules under open source licenses, independent of Odoo SA. An OCA module can be an alternative to a paid store app. It deserves the same four checks as any other app: maintainer and version coverage, the license, dependencies and uninstall, and the next upgrade.

Not under that name. Since Odoo 19 the external interface is the JSON-2 API: each call posts JSON to the /json/2 endpoint, naming a model and a method, and authenticates with a bearer API key. Odoo notes that access to the external API is only available on Custom pricing plans, not One App Free or Standard, and recommends a short key duration for interactive usage. The older XML-RPC and JSON-RPC endpoints are deprecated, and Odoo 20 removed their db service. The common and object services are scheduled for removal in Odoo 22 (fall 2028), so a connector still built on them has a deadline.

Within limits. Odoo says Studio gives you the tools to create new fields, customize views and streamline workflows without writing code, with fields added by a simple drag and drop. Its automation rules include a Send Webhook Notification action, which posts the values of selected fields to a URL and shows a sample payload so you can preview the content, and an External trigger that lets another system start a rule. Odoo recommends involving a developer or solution architect, because a misconfigured webhook may disrupt the database and take time to revert.

Odoo deletes the app’s database records with it. Apps depend on one another, so uninstalling one can also remove the apps that rely on it; Odoo’s own example is that removing Point of Sale also removes Restaurant. Rehearse it on a duplicate database first: the uninstall window lists the apps and the records that would go, so you learn the cost while nothing in production has been dropped.

For the providers it embeds, yes. Odoo offers Adyen, PayPal, Stripe and Mollie among others, each configured from the Accounting, Website or Sales settings. Odoo delegates sensitive data such as card numbers to the provider rather than storing it in the database. A custom connector is only worth scoping for a provider Odoo does not list, and the first step is checking that list for your version.

In a connector we build, the failure is written to a log someone owns, errors that are temporary are retried, and a reconciliation compares records on both sides so a missed order shows up as a count that does not match. Who receives the alert, and how fast they respond, is agreed on at scoping, inside the implementation plan. That continuing check is also what tells you, after an upgrade, that the connector still works.

Yes. We run the four checks on this page against the app on a duplicate of your database: maintainer and version coverage, license, dependencies and uninstall, and the next upgrade. You then choose between three outcomes: install it, configure standard Odoo instead, or build the behavior as a module. The choice is yours; the review exists so it is made with the upgrade in view.