Tabby on Odoo Community or Enterprise: What Really Changes
Whether Tabby and Tamara run on Odoo Community, what Enterprise adds, and why Odoo Online cannot install the module while Odoo.sh and on-premise can.
The question comes up in almost every first conversation with a store on Odoo Community: does Tabby actually work here, or is instalment payment one of those things that quietly needs Enterprise? The short answer is that it works, in full, on Community. The longer answer is that the edition is the wrong question. What decides whether you can offer Tabby or Tamara at all is where your database is hosted, and that is a separate choice from which edition you pay for.
This page separates the two, using Tabby & Tamara for Odoo as the example because it is the module we maintain and can speak for line by line. Everything about Odoo itself comes from Odoo's own documentation and is linked.
Two questions, not one
Odoo comes in two editions. Community is the free, open source one, licensed under LGPLv3. Enterprise is the paid one that adds apps, official support, hosting and the upgrade service. Odoo's editions comparison lists app by app which is which.
Separately, an Odoo database lives in one of three places. Odoo Online, hosted and run by Odoo. Odoo.sh, Odoo's platform where you deploy from a Git repository. Or on-premise, meaning your own server, a VPS or a container you control. Odoo's hosting overview compares the three and explains how a database moves between them.
Edition decides which Odoo apps you get. Hosting decides whether you are allowed to add code Odoo did not write. A BNPL module is code Odoo did not write, so hosting is the question that can actually block you.
What the module needs from Odoo
The manifest of Tabby & Tamara for Odoo declares five dependencies: payment, account_payment, website_sale, point_of_sale and mail. Every one of them ships with Community. The payment provider framework, the online payment button on invoices, eCommerce, the Point of Sale and the messaging layer are all in the free edition, and Odoo's comparison page lists Invoicing, Payments, eCommerce and Point of Sale as available in both.
There is no dependency on the Enterprise accounting app, Studio, the IoT box or the mobile app. The Point of Sale flow is a QR code in a browser popup and a server that polls the gateway, so nothing sits between the register and Tabby except your own Odoo server. The only Python library imported beyond Odoo itself is requests, which Odoo already requires. The licence is LGPL-3, so your partner can read and maintain the code on either edition.
One consequence of that list: the module pulls in Point of Sale even on a website-only store, and eCommerce even on a counter-only business. On Community that costs nothing. On Enterprise the plans on Odoo's pricing page currently include all apps for one per-user price, so an extra app should not change the bill, but read that page against your own contract rather than taking it from us.
On Odoo Community
Everything the module does works on Community: the checkout option, the promo badge under the price, portal invoices and quotations, the register, refunds from the back office, the API log and the Test Connection button. There is no Community-only branch and no reduced feature set. If you are setting it up for the first time, the step by step guide to adding Tabby to Odoo applies unchanged.
Three things do differ, and none of them are inside the module.
The menu is called Invoicing
Community has the Invoicing app, not Accounting. Payment providers live under Invoicing, then Configuration, then Payment Providers. Guides written for Enterprise say Accounting, and a Community user following one can stop there and assume the module did not install. Same screen, different app name. Website, then Configuration, also reaches it.
Matching the payout is manual
Tabby and Tamara pay you in settlements, not per order. Matching a settlement to the orders inside it is where the editions genuinely diverge. Odoo's comparison places bank statement reconciliation under the Enterprise accounting app. On Community you record the payout as a payment in Invoicing and match it by hand, or add a community reconciliation module. It works, and plenty of stores run that way, but budget the bookkeeper's time for it.
The upgrade is your project
An Enterprise subscription includes Odoo's upgrade service for the database. Community does not. That matters for the module because it is built per Odoo version, one branch for each release from 14.0 to 19.0, and when you move the database you switch branches with it. On Community the whole migration is yours or your partner's to run; the BNPL module is the easy part of it.
On Odoo Enterprise
Enterprise changes nothing in how the module installs or behaves. What it adds around it: the full Accounting app with the reconciliation screen and reconciliation models for the settlement work above, Odoo's upgrade service between major versions, and official support for Odoo itself. Support for the module still comes from us on either edition, because Odoo's support covers Odoo's own code.
The register is identical on both. The IoT box and the mobile app that come with Enterprise play no part here, since the QR flow runs inside the Point of Sale session in the browser.
On Odoo Online: this is the wall
Odoo Online is Enterprise hosted by Odoo, and Odoo's documentation for it states that it is incompatible with custom modules and with modules from the Odoo Apps Store. Not just this module: any third-party module, including the ones sold on Odoo's own store. The Odoo.sh documentation says the same from the other side.
Part of the reason is that Odoo Online runs intermediate versions, 19.1, 19.2 and so on, released every two or three months and only on Odoo Online. Third-party modules are built against the major releases.
So if your store is on Odoo Online, the honest answer is that no Tabby or Tamara module can be installed, ours included. The options are:
- Move the database to Odoo.sh or to your own server. Odoo's pricing page says the Custom plan covers either, with Odoo.sh hosting billed on top, and the hosting page describes the move as downloading a backup and restoring it.
- Stay on Odoo Online and use only what Odoo's built-in payment providers offer on their own hosted pages. Whether one of them adds instalments is a question for that gateway, not for Odoo.
Check this before buying any module, from anyone. A refund request is far more paperwork than a two minute check.
On Odoo.sh
Odoo.sh requires an Enterprise plan that includes Odoo.sh hosting, so there is no Community on Odoo.sh. Deployment is by Git: you add the module folder to a branch of the GitHub repository linked to the project and Odoo.sh detects module folders on its own. Odoo's project setup guide suggests submodules for publicly available modules; for a purchased one, commit the folder into your own repository.
Push to a staging branch first. Set the provider to test mode there, click Test Connection, run a sandbox order, then merge to production and switch to live keys.
On your own server
On-premise is the only place where both editions run with third-party code. Copy payment_tabby_tamara into a directory on the addons path, restart Odoo, turn on developer mode, update the apps list and install. With the official Docker image the extra addons directory is /mnt/extra-addons. The steps are identical on Community and Enterprise; Enterprise only adds registering your subscription code.
The decision in one table
| Where you are | Module installs? | Note |
|---|---|---|
| Community, on-premise | Yes | Menu is Invoicing, payout matching is manual |
| Enterprise, on-premise | Yes | Same steps plus subscription registration |
| Enterprise, Odoo.sh | Yes | Deploy through the GitHub repository |
| Odoo Online, any plan | No | No third-party modules at all |
Two checks before you pay for anything
First, know where you are hosted. If you signed up on odoo.com, never installed anything on a server and never connected a GitHub repository, you are on Odoo Online. An Odoo.sh project and an on-premise server are both things you would remember setting up.
Second, know your exact major version, because the module is sold and built per version. Odoo's support table gives each major release three years of standard support, and lists 17.0 as planned to end in September 2026. A store still on 17.0 should plan the move to 18.0 or 19.0 and take the matching module branch with it.
Once those two are settled, what remains is which surfaces you take money on and which providers you want, which the buyer's comparison of Tabby and Tamara modules walks through. The counter has its own guide to BNPL at the Point of Sale.
Frequently asked
Does Tabby work on Odoo Community?
Yes, with every feature. The module depends on payment, account_payment, website_sale, point_of_sale and mail, all of which ship in the free edition. There is no separate Community branch and nothing is removed; the only difference is that Payment Providers sit under the Invoicing app rather than Accounting.
Can I install a Tabby module on Odoo Online?
No. Odoo's documentation states that Odoo Online is incompatible with custom modules and with modules from the Odoo Apps Store, and that applies to every Tabby or Tamara module from any vendor. If you need instalments inside Odoo, the route is moving the database to Odoo.sh or to your own server, which Odoo describes as downloading a backup and restoring it.
Does the Point of Sale part need Enterprise or an IoT box?
No. The cashier picks Tabby, a popup shows a QR code, the customer scans it and approves on their phone, and the server polls the gateway for the result. All of that runs inside the Point of Sale session in the browser on both Community and Enterprise, with no IoT box and no mobile app.
How do I deploy the module on Odoo.sh?
Odoo.sh requires an Enterprise plan that includes its hosting, and deployment is through Git. Add the payment_tabby_tamara folder to a branch of the GitHub repository linked to your project and Odoo.sh detects module folders on its own. Start on a staging branch, set the provider to test mode, click Test Connection and run a sandbox order, then merge to production and switch to live keys.
What does Enterprise actually add for BNPL?
Nothing inside the module itself, only things around it. The full Accounting app with the bank statement reconciliation screen, which makes matching Tabby and Tamara settlements to orders easier. And Odoo's upgrade service between major versions, which on Community is a project you run yourself. Support for the module comes from us on either edition.
My store is on Odoo 17. Do I need to do anything?
Odoo's support table lists standard support for 17.0 as planned to end in September 2026, so plan the move to 18.0 or 19.0. The module has one branch per version from 14.0 to 19.0, so take the matching branch with you when the database moves. On Enterprise the upgrade service covers the database; on Community the migration is yours or your partner's to run.