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.

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.