Offer your Saudi and UAE shoppers the "buy now, pay later" option they already expect at checkout — natively inside Odoo eCommerce. This is a build-to-order module: ECOSIRE designs, develops, installs and supports a production-grade Tamara payment provider tailored to your store, your Odoo version, and your Tamara merchant account. It is not an off-the-shelf apps.odoo.com download, and there is no instant download — we build it for you over a one working week engagement.

The module registers Tamara as a first-class payment.provider record (extending Odoo's native payment framework) so it appears alongside your existing methods on the website checkout, in the customer portal, and in POS-adjacent flows where applicable. Shoppers see interest-free installment plans (typically 2-12 splits depending on your Tamara agreement and cart eligibility) and a pay-later option, with the exact plan, per-installment amount, and due dates surfaced before they commit — driving higher average order value and fewer abandoned carts.

Under the hood we implement a clean, upgradeable architecture: a dedicated model layer (models.Model subclasses) for provider configuration and transaction state, @api.depends computed fields for eligibility and installment breakdown, secure server-to-server session creation against Tamara's checkout API, and signed webhook handlers that reconcile authorization, capture, refund, and decline events back onto the payment.transaction and linked sale.order / account.move. Merchant secrets (API token, notification token) are stored in Odoo settings, never in the QWeb front end, and every state change is written to the chatter and Odoo's audit log.

Access is locked down with ir.model.access.csv grants plus record rules so only Sales/Accounting managers can view raw transaction payloads, while store staff see only order-level status. The product page promo widget is delivered as a QWeb/OWL template you can toggle per product or category, showing "Split in installments with Tamara" messaging that stays consistent with your theme. We build against Odoo 17, 18 and 19 (Community or Enterprise) and hand you code that survives future upgrades because it leans on the standard payment provider extension points rather than core patches.

You get a real engineering partner, not a zip file: discovery of your checkout and reconciliation requirements, a staged deployment (dev → staging → production), UAT sign-off, admin training, and a post-launch support window. If you already run Tamara elsewhere, we mirror your capture and settlement policy so finance sees one source of truth in Odoo.