Quick facts
- Price
- $299.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 20160 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
Tabby BNPL Gateway for Odoo
Offer Tabby split-in-4 buy-now-pay-later at Odoo checkout to lift Gulf conversion. Built-to-order, installed and supported by ECOSIRE.
$299.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
Registers Tabby as a native Odoo payment provider by extending payment.provider and payment.transaction, so it appears alongside card and COD at both eCommerce and Sales-order checkout
Tabby split-in-4 and pay-later options presented at checkout with amounts and schedule shown in the order currency
Cart-level pre-scoring eligibility check calling Tabby's API before payment, hiding or disabling the option when the buyer profile is declined so no shopper hits a dead end
Promo messaging widget on product and cart pages rendering Tabby's 'Pay in 4' snippet, RTL-aware for Arabic and localized per language
Explicit authorize / capture / void / refund lifecycle states on payment.transaction with @api.depends-computed fields syncing sale.order and account.move
One-click manual capture and void from the backend transaction form for orders configured to authorize-then-capture
Full and partial refunds triggered from the Odoo customer invoice/credit note, calling Tabby's refund API and posting the accounting entry
Signature-verified, idempotent webhook controller that reconciles Tabby state changes and rescues transactions abandoned mid-redirect
Sandbox and production key switching via the provider record, with a test-mode flag to validate flows before go-live
Multi-company and multi-currency ready, with record rules isolating transactions per company and AED/SAR/KWD/QAR/BHD supported
ir.model.access.csv access rights plus record rules so only Accounting/Sales roles can view or act on Tabby transactions
QWeb-rendered Tabby payment reference and status block on the sales order and invoice PDFs for clean reconciliation
Automated action / scheduled reconciliation job that re-queries Tabby for any transaction still pending past a threshold
Structured server-side logging of every Tabby API request and response for support and dispute handling
Configurable minimum and maximum order value for BNPL eligibility to match your Tabby merchant limits
About this Product
Tabby is the Gulf's most-used buy-now-pay-later brand, and shoppers in the UAE, KSA, Kuwait, Qatar and Bahrain increasingly expect a "split in 4" option before they check out. This ECOSIRE build-to-order module wires Tabby natively into your Odoo eCommerce and Sales checkout so customers can split payments interest-free while you get paid in full up front.
Why Choose Tabby BNPL Gateway for Odoo
Registers Tabby as a native Odoo payment provider by extending payment.provider and payment.transaction, so it appears alongside card and COD at both eCommerce and Sales-order checkout
Tabby split-in-4 and pay-later options presented at checkout with amounts and schedule shown in the order currency
Cart-level pre-scoring eligibility check calling Tabby's API before payment, hiding or disabling the option when the buyer profile is declined so no shopper hits a dead end
Promo messaging widget on product and cart pages rendering Tabby's 'Pay in 4' snippet, RTL-aware for Arabic and localized per language
Explicit authorize / capture / void / refund lifecycle states on payment.transaction with @api.depends-computed fields syncing sale.order and account.move
One-click manual capture and void from the backend transaction form for orders configured to authorize-then-capture
This is not an off-the-shelf apps.odoo.com download. ECOSIRE designs, builds, installs and supports a purpose-fit payment.provider integration on your own Odoo instance. The module registers Tabby as a first-class payment provider (extending payment.provider and payment.transaction), calls Tabby's checkout and pre-scoring APIs, and reconciles every state change through signed webhooks. It ships as a clean, versioned addon with a real __manifest__.py, ORM models, ir.model.access.csv access rules, record rules for multi-company isolation, backend XML/OWL views, and QWeb-rendered transaction details on the order and invoice.
The eligibility check runs at the cart. Before a customer commits, the module calls Tabby's pre-scoring endpoint with the order amount, currency and buyer context; if Tabby declines the profile, the split-in-4 option is hidden or disabled gracefully so the shopper never hits a dead end at the payment step. On success, the promo messaging widget renders the "Pay in 4. No interest, no fees." snippet on product and cart pages in the correct currency and language (English/Arabic, RTL-aware), which is exactly the placement Tabby's merchant guidelines recommend for conversion.
The full transaction lifecycle is modelled properly. Authorization, capture, partial and full refund, and void are represented as explicit states on payment.transaction, with @api.depends-computed fields keeping the linked sale.order and account.move in sync. Refunds initiated from the Odoo customer invoice call Tabby's refund API and post the corresponding credit note; captures and voids are one click from the backend with a full audit trail. A dedicated webhook controller verifies Tabby's signature, is idempotent against duplicate deliveries, and reconciles any transaction whose state drifted — so a dropped browser redirect never leaves an order stuck in "pending."
You choose your Odoo edition and version: the module supports Odoo 17, 18 and 19, on Community or Enterprise. ECOSIRE hands over source, deploys to your staging then production, trains your team, and stands behind it with a support and warranty window. Payments to Tabby happen under your own Tabby merchant account and API keys — we never touch your funds or credentials beyond the integration itself.
What you get
- Complete, version-pinned Odoo addon source for your chosen version (17, 18 or 19) and edition (Community or Enterprise), with a documented __manifest__.py
- Installation and deployment on your staging environment, then a supervised cutover to production
- Configuration of your Tabby merchant account keys, currency, eligibility limits and webhook endpoint
- Connection of the sandbox environment and a joint end-to-end test pass (checkout, pre-scoring, capture, refund, void, webhook)
- Admin and finance runbook: how to read transaction states, issue refunds/voids, and reconcile against the Tabby merchant dashboard
- A live training session for your eCommerce, sales and accounting teams plus recorded walkthrough
- Post-launch support and warranty window covering bug fixes and Tabby API compatibility during the coverage period
- Source handover to your Git/repository with upgrade notes so future Odoo version migrations are straightforward
Who this is for
Gulf eCommerce retailer
UAE/KSA/Kuwait online store owner who sees carts abandoned at the payment step and wants Tabby's split-in-4 to lift conversion and average order value without changing their Odoo checkout.
Odoo eCommerce manager
Runs the Odoo Website/eCommerce store and needs Tabby to appear as a clean, native payment option with promo messaging on product pages, not a bolted-on redirect that breaks the funnel.
Finance / accounting controller
Owns reconciliation and needs every Tabby authorize, capture, refund and void to map correctly onto invoices and credit notes in Odoo Accounting, with an audit trail that matches the Tabby merchant dashboard.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Tabby BNPL Gateway for Odoo module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Tabby BNPL Gateway for Odoo, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Tabby BNPL Gateway for Odoo Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Native Tabby split-in-4 at Odoo checkout | Registered as a first-class payment.provider next to card and COD | Possible but you build the whole provider integration yourself | Depends on the listing; many are generic or unmaintained | |
| Cart-level pre-scoring eligibility check | Built in — Tabby pre-scoring called before payment, option hidden if declined | Only if you design and code the pre-scoring call and UI | Rarely included; often redirect-and-fail at payment | |
| Capture / refund / void lifecycle synced to invoices | Explicit transaction states with computed sync to sale.order and account.move | You must model and reconcile every state yourself | Varies; partial refunds and voids often missing | |
| Signed, idempotent webhook reconciliation | Signature-verified controller plus scheduled re-query job | Must be designed and hardened by your developers | Often best-effort; duplicate/dropped events cause stuck orders | |
| Odoo 17 / 18 / 19, Community & Enterprise | Pinned and tested to your exact version and edition | Whatever your team targets and maintains | Listing may lag new Odoo versions or be Enterprise-only | |
| Installation, training and support window | ECOSIRE installs, trains your team and backs it with warranty support | Your own team's time and ongoing burden | Usually code-only; support quality varies by author | |
| Arabic / RTL promo messaging on product pages | RTL-aware 'Pay in 4' widget, localized per language and currency | You build the widget and localization | Sometimes English-only or no product-page messaging |
Frequently Asked Questions about Tabby BNPL Gateway for Odoo
+How long until it's live, and is this an instant download?
This is a build-to-order module, not an instant apps.odoo.com download. After purchase, ECOSIRE scopes your Tabby account, currency and checkout flow, then builds, installs and tests the integration. Typical delivery is 2 to 4 weeks depending on your Odoo version, edition and any customizations to your checkout. You receive it deployed to staging first, then a supervised production go-live.
+What support and updates do I get after launch?
Every build includes a post-launch support and warranty window covering bug fixes and compatibility with Tabby's API during the coverage period. You also get the full source, so your team or ECOSIRE can maintain it. When you later migrate Odoo versions (for example 18 to 19), we provide upgrade notes and can quote a migration; the module is structured to make that straightforward.
+Which Odoo versions and editions are supported?
Odoo 17, 18 and 19, on both Community and Enterprise. The module extends the standard payment.provider and payment.transaction framework, so it slots into your existing eCommerce and Sales checkout regardless of edition. We confirm your exact version and edition during scoping and pin the addon to it.
+Do I need my own Tabby merchant account?
Yes. You sign up as a Tabby merchant and provide your API keys (sandbox and production). The module authenticates and settles under your own account — ECOSIRE never holds your funds or credentials beyond configuring the integration. If you are not yet approved by Tabby, we can build and validate against sandbox while your merchant application is processed.
+How are refunds, captures and voids handled in Odoo?
The full lifecycle is modelled on payment.transaction. Refunds are issued from the Odoo customer invoice or credit note and call Tabby's refund API; partial refunds are supported. Captures and voids (for authorize-then-capture setups) are one click from the backend transaction form. Every action is logged and the linked sale order and account move stay in sync via computed fields.
+What happens if a customer's browser drops during checkout?
Nothing is left inconsistent. A signature-verified, idempotent webhook controller receives Tabby's state updates independently of the browser redirect, and a scheduled reconciliation job re-queries any transaction still pending past a threshold. So even if the shopper closes the tab after paying, the order reconciles to the correct paid state automatically.
+Will the Tabby promo messaging show on my product pages in Arabic?
Yes. The promo widget renders Tabby's 'Pay in 4, no interest' messaging on product and cart pages in the order currency, and it is RTL-aware so it displays correctly in Arabic alongside English. Placement follows Tabby's merchant guidelines to maximize the conversion benefit of advertising BNPL before checkout.
Why Customers Trust ECOSIRE
SOC 2 Aligned
GDPR Compliant
Secure Stripe Payment
30-Day Money Back
Lifetime Updates
LGPL-3.0 License
Related Modules
Request a quote
Tabby BNPL Gateway for Odoo
Offer Tabby split-in-4 buy-now-pay-later at Odoo checkout to lift Gulf conversion. Built-to-order, installed and supported by ECOSIRE.
- Registers Tabby as a native Odoo payment provider by extending payment.provider and payment.transaction, so it appears alongside card and COD at both eCommerce and Sales-order checkout
- Tabby split-in-4 and pay-later options presented at checkout with amounts and schedule shown in the order currency
- Cart-level pre-scoring eligibility check calling Tabby's API before payment, hiding or disabling the option when the buyer profile is declined so no shopper hits a dead end
- Promo messaging widget on product and cart pages rendering Tabby's 'Pay in 4' snippet, RTL-aware for Arabic and localized per language