---
title: "Tabby & Tamara for Odoo"
description: "Add both Tabby and Tamara to your Odoo shop, Point of Sale, invoices and quotations in a single install. Odoo 14 through 19."
lang: en
canonical: https://tabby.kerneltics.com/en/
alternate_ar: https://tabby.kerneltics.com/
updated: 2026-10-13
---

# Tabby & Tamara for Odoo

> Add both Tabby and Tamara to your Odoo shop, Point of Sale, invoices and quotations in a single install. Odoo 14 through 19.

Price: $200 USD. Apps Store: https://apps.odoo.com/apps/modules/19.0/payment_tabby_tamara
WhatsApp: +966 50 738 6853

## Most stores install one app for Tabby and another for Tamara. You install one.

Most listings on the Apps Store cover one provider and one screen. This one covers both providers and every place your customer pays.

- Tabby and Tamara together: Yes, one install
- eCommerce checkout: Yes
- Point of Sale: Yes, same module
- Portal invoices: Yes
- Quotations: Yes
- Instalment badge on the product page: Yes, live with quantity
- Full and partial refunds: Yes, from the back office
- API request log: Yes, with secrets redacted
- Odoo 14 to 19: Yes

## They see the plan before they click Buy

A live badge under the price on the product page and in the cart shows the number of payments and the amount of each, and updates the moment the quantity or variant changes. A breakdown modal explains the whole schedule.

- Recalculates with quantity and variant
- Breakdown modal with the payment schedule
- Only shows for providers you enabled

## Tabby and Tamara at the counter

The cashier picks a provider, a QR popup opens, and the customer scans and approves on their own phone. The server polls the gateway until it confirms, and the Validate button stays locked until the payment is actually captured.

- No terminal hardware, the customer's phone is the reader
- Validate stays locked until the gateway confirms
- Works on the legacy and the new POS

## A returning shopper cannot fake a paid order

The riskiest moment in any redirect payment flow is when the customer comes back. This module never takes that redirect at face value: it keeps only the reference, then asks the provider itself what really happened.

- The return URL supplies only a reference, the status is read from the provider's API
- Webhooks are re-verified the same way, so a forged call changes nothing
- Finalised transactions are never re-processed, so a replayed notification cannot flip them

## Frequently asked

### Do I need my own Tabby or Tamara merchant account?

Yes. The module connects your store to your account but does not issue the account. You get test and live keys from the provider's merchant dashboard, then enter them in the Odoo payment provider settings.

### How do I set up Tamara in Odoo?

After installing the module, open the Tamara provider in Odoo's payment settings, paste the API token from your Tamara merchant portal and keep it in Test Mode until a sandbox order goes through. Then swap in the live token and set the State to Enabled. Every step, plus the Point of Sale and the common errors, is in [the Tamara Odoo integration guide](https://tabby.kerneltics.com/en/tamara-odoo-integration/).

### Does it work with my Odoo version?

There is a branch for every release from 14.0 to 19.0, on both Community and Enterprise. Download the branch that matches your version.

### Why are Tabby and Tamara not showing at checkout?

The two usual causes: the provider is enabled but not published, or the order is in an unsupported currency. Both providers appear only for SAR, AED, KWD, BHD, QAR and OMR, and hide automatically otherwise.

### Does it support refunds?

Yes, full or partial refunds from the Odoo back office and straight from the invoice. A cashier's POS refund on a Tabby payment reaches Tabby automatically when the refund order syncs; a Tamara counter sale is refunded from the refund button on its payment record.

### Is the source open?

Yes, under LGPL-3. You can read, modify and extend it, and every gateway call is written in Python on the server.