Produktdetails werden auf Englisch angezeigt. Übersetzungen folgen in Kürze.
Kurze Fakten
- Preis
- $299.00 USD
- Odoo-Versionen
- 17, 18, 19
- Rüstzeit
- 21 Min
- Lizenz
- Einmalig und unbefristet
- Sprachen
- 11 Sprachen
Einmalkauf
Tamara BNPL Gateway for Odoo
Custom-built Tamara BNPL payment provider for Odoo eCommerce — interest-free installments, pay-later, promo widget, and full capture/refund sync.
$299.00USD
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Hauptfunktionen
Registers Tamara as a native Odoo payment.provider so it renders on website checkout, the customer portal, and payment links without core patches
Interest-free installment plans (2-12 splits, subject to your Tamara agreement and cart eligibility) selectable at checkout
Pay-later and split-payment flows both supported, mapped to Tamara's Pay-Later and Pay-in-X products
Real-time eligibility and spending-limit checks against Tamara before the plan is offered, so ineligible carts fall back gracefully to other methods
Product-page and cart promo widget (QWeb/OWL) showing per-installment amount and due dates, toggleable per product or category
Full transaction lifecycle tracking on payment.transaction: Authorized, Captured, Partially Captured, Refunded, Partially Refunded, and Declined states
Signed Tamara webhook handlers that reconcile authorize/capture/refund/cancel events back to the sale.order and account.move automatically
Automatic or manual capture policy — configurable to match your fulfilment model (capture on ship vs. capture on order)
Refund and partial-refund sync: issuing a credit note or refund in Odoo triggers the matching Tamara refund via API
Multi-currency and multi-company aware, with SAR/AED presentation and Arabic RTL-friendly checkout copy
Configurable merchant credentials (API token, notification token, region/sandbox toggle) stored in Odoo Settings, encrypted-at-rest, never exposed to QWeb
Compute-driven installment breakdown using @api.depends fields so the plan preview stays accurate as cart totals change
Sandbox/staging mode for safe end-to-end testing before go-live, with distinct keys per environment
Order status automation: automated actions/server actions can gate delivery or invoicing until Tamara authorization is confirmed
Structured logging and chatter notes on every state transition for finance-grade auditability
Optional XML-RPC/JSON-RPC exposure of transaction status so external systems (WMS, dashboards) can read Tamara payment state
Über dieses Produkt
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 2-4 week engagement.
Warum Tamara BNPL Gateway for Odoo wählen
Registers Tamara as a native Odoo payment.provider so it renders on website checkout, the customer portal, and payment links without core patches
Interest-free installment plans (2-12 splits, subject to your Tamara agreement and cart eligibility) selectable at checkout
Pay-later and split-payment flows both supported, mapped to Tamara's Pay-Later and Pay-in-X products
Real-time eligibility and spending-limit checks against Tamara before the plan is offered, so ineligible carts fall back gracefully to other methods
Product-page and cart promo widget (QWeb/OWL) showing per-installment amount and due dates, toggleable per product or category
Full transaction lifecycle tracking on payment.transaction: Authorized, Captured, Partially Captured, Refunded, Partially Refunded, and Declined states
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.
Was Sie bekommen
- Complete, upgrade-safe module source (proper __manifest__.py, models, views, security, data) for your Odoo 17, 18, or 19 instance — Community or Enterprise
- Tamara merchant configuration: production and sandbox credentials wired into Odoo Settings, webhook endpoints registered, and capture/refund policy set to your rules
- ir.model.access.csv access grants plus record rules scoped to your Sales and Accounting roles
- QWeb/OWL promo widget integrated into your theme with your styling, plus checkout copy tuned for SAR/AED and Arabic RTL
- Staged deployment across dev, staging, and production with a documented UAT test plan and end-to-end sandbox verification
- Admin and finance training session covering plan setup, reconciliation, refunds, and reading transaction states
- Technical handover documentation: architecture notes, configuration guide, webhook/runbook, and upgrade guidance
- Post-launch support window (bug fixes and Tamara-side change adjustments) for the agreed period after go-live
Für wen das ist
Saudi eCommerce merchant on Odoo
A KSA online retailer whose customers expect Tamara at checkout. Wants interest-free installments live inside Odoo eCommerce to lift conversion and AOV without bolting on a separate storefront.
UAE multi-brand retail operator
Runs several storefronts and companies in one Odoo database across the UAE. Needs one consistent Tamara integration, multi-company aware, with clean reconciliation into Accounting for each entity.
Finance / accounting manager
Owns settlement and reconciliation. Needs every Tamara authorization, capture, and refund to land accurately on payment.transaction and account.move, with an audit trail and role-restricted access to raw payloads.
Odoo functional consultant or IT lead
Responsible for the Odoo platform internally or for a client. Wants a maintainable, upgrade-safe provider built on standard extension points rather than a fragile off-the-shelf module that breaks on the next version bump.
Installationsübersicht
Von ECOSIRE herunterladen
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Tamara BNPL Gateway for Odoo-Moduls von Ihrem Konto-Dashboard herunter.
Auf Odoo hochladen
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Installieren Sie das Modul
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Tamara BNPL Gateway for Odoo“ und klicken Sie auf „Installieren“.
Einstellungen konfigurieren
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Verifizieren und live gehen
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.
Wie Tamara BNPL Gateway for Odoo im Vergleich abschneidet
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Native Tamara BNPL at Odoo checkout | Full — 2-12 splits + pay-later as a native payment.provider | Possible but you fund the full build | Varies; often generic or region-limited | |
| Fits your Odoo version (17/18/19) and edition | Built and tested for your exact version, Community or Enterprise | Depends on your in-house skill | Often lags new Odoo releases | |
| Eligibility & spending-limit checks | Live checks against Tamara with graceful fallback | Must design and maintain yourself | Sometimes missing or simplistic | |
| Refund / partial-capture reconciliation to account.move | Automated via signed webhooks and refund-on-credit-note | You build the reconciliation logic | Frequently manual or incomplete | |
| Product-page promo widget | Themed QWeb/OWL widget, per product/category toggle | Extra effort to design | Fixed styling, hard to theme | |
| Security: role-scoped access & secret handling | ir.model.access.csv + record rules; secrets in Settings, not QWeb | Only as good as your review | Opaque; you inherit their choices | |
| Delivery model | Build-to-order, 2-4 weeks, staged deploy + UAT | Weeks-to-months of internal effort | Instant download but self-integrate | |
| Post-launch support & upgrade path | Included support window + upgrade compatibility passes | You own all maintenance | Ticket queue, no store-specific help |
Häufig gestellte Fragen zu Tamara BNPL Gateway for Odoo
How long does delivery take and what is the process?
This is a build-to-order engagement with a typical 2-4 week lead time — there is no instant download. After purchase we start with a short discovery of your Odoo version, theme, and reconciliation rules, then build and deploy through dev, staging, and production. You get a sandbox end-to-end test and UAT sign-off before go-live. Timeline depends on complexity (multi-company, custom capture rules, theme work) and your Tamara account being ready.
What happens for support and updates after launch?
Every engagement includes a post-launch support window for bug fixes and adjustments to Tamara-side changes. We build on Odoo's standard payment provider extension points, so the module is designed to survive version upgrades; when you move between Odoo 17, 18, and 19 we can provide a compatibility pass. Extended support and maintenance retainers are available if you want ongoing coverage beyond the included window.
Which Odoo versions and editions do you support?
We build for Odoo 17, 18, and 19, on both Community and Enterprise. The module registers Tamara as a native payment.provider, so it works with the standard website eCommerce checkout and customer portal on any of those versions. Tell us your exact version and edition during discovery and we target it precisely.
Do I need my own Tamara merchant account?
Yes. Tamara approves merchants directly and issues your API and notification credentials, sets your installment plans (for example Pay-in-3 or up to 12), and defines your eligibility and limit rules. We integrate against your account and wire your credentials into Odoo Settings. We can advise on the technical onboarding but the merchant agreement is between you and Tamara.
How are refunds, captures, and declines handled?
The module tracks the full lifecycle on Odoo's payment.transaction: authorized, captured (full or partial), refunded (full or partial), and declined. Signed Tamara webhooks reconcile those events back onto the sale order and journal entry automatically, and issuing a refund or credit note in Odoo triggers the matching Tamara refund via API. Capture can be automatic or gated to fulfilment, per your policy.
Is this the same as an app on the Odoo App Store?
No. This is a custom, build-to-order module that ECOSIRE develops, installs, and supports for your specific store — not an off-the-shelf apps.odoo.com listing you download and self-install. That means it fits your theme, your reconciliation rules, and your Odoo version, and you get an engineering team behind it rather than a generic zip.
Verwandte Module
Angebot anfordern
Tamara BNPL Gateway for Odoo
Custom-built Tamara BNPL payment provider for Odoo eCommerce — interest-free installments, pay-later, promo widget, and full capture/refund sync.
- Registers Tamara as a native Odoo payment.provider so it renders on website checkout, the customer portal, and payment links without core patches
- Interest-free installment plans (2-12 splits, subject to your Tamara agreement and cart eligibility) selectable at checkout
- Pay-later and split-payment flows both supported, mapped to Tamara's Pay-Later and Pay-in-X products
- Real-time eligibility and spending-limit checks against Tamara before the plan is offered, so ineligible carts fall back gracefully to other methods