A build-to-order Dynamics 365 Business Central extension that offers Tabby split-in-4 / pay-later at checkout for GCC merchants, captures and refunds orders from BC, and reconciles Tabby settlement payouts against AR in AED, SAR and KWD. One-time license from $299.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A build-to-order Dynamics 365 Business Central extension that offers Tabby split-in-4 / pay-later at checkout for GCC merchants, captures and refunds orders from BC, and reconciles Tabby settlement payouts against AR in AED, SAR and KWD.
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Tabby BNPL for Business Central is a per-tenant AL extension that wires Tabby's buy-now-pay-later (split-in-4 and pay-later) into your Dynamics 365 Business Central order-to-cash flow. ECOSIRE builds it to your environment, installs it as a tenant-specific extension (not a generic AppSource download), and supports it after go-live.
Tabby split-in-4 and pay-later option presented at Business Central checkout for eligible customers
Eligibility and credit-limit check at order time via Tabby's checkout/sessions API before the BNPL option is shown
Authorization and capture of the Tabby order directly from the Sales Order, with status written back to BC
Full and partial refunds issued to Tabby from the Posted Sales Invoice using an AL action — no portal switching
Settlement payout reconciliation that maps each Tabby net payout to originating BC documents and clears AR
Automatic posting of Tabby merchant fees to a dedicated G/L account so the customer ledger ties out
At order time, the extension calls Tabby's checkout/sessions API to run an eligibility and credit-limit check, then presents the BNPL option to the customer. On approval, the order is authorized and captured; refunds and partial refunds are issued back through Tabby directly from the Sales Order or Posted Sales Invoice using an AL action and event subscribers on the posting routines — no separate portal switching.
The real accounting value is in reconciliation. Tabby settles net of fees on a payout cycle, so we map each Tabby payout to the originating BC documents, post the merchant fee to a dedicated G/L account, and clear the AR balance so your customer ledger and bank reconciliation actually tie out. Multi-currency GCC is handled natively for AED, SAR and KWD using BC's currency and exchange-rate framework.
Technically this is delivered as table and page extensions over Sales and Payments, event subscribers (OnAfterPost, OnBeforeRelease), a job queue entry that polls settlement status, dedicated permission sets, and a secured API/webhook endpoint for Tabby callbacks. Credentials live in isolated setup tables, never in code.
Because it is built-to-order, you get a clean fit to your chart of accounts, your tax setup and your sandbox-then-production rollout — with an honest delivery lead time rather than a one-click promise. ECOSIRE delivers, deploys to your sandbox, validates against Tabby's test environment, then promotes to production.
Wants BNPL to lift average order value without breaking the books — needs Tabby payouts, fees and AR to reconcile cleanly inside Business Central instead of a side spreadsheet.
Needs the integration delivered as a clean per-tenant extension that survives BC updates, with permission sets, isolated credentials and a sandbox-first rollout rather than risky core customization.
Wants the Tabby split-in-4 option live at checkout with real eligibility checks, and one place to issue refunds, so support and fulfilment teams don't bounce between BC and the Tabby portal.
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Tabby BNPL for Business Central-Moduls von Ihrem Konto-Dashboard herunter.
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).
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Tabby BNPL for Business Central“ und klicken Sie auf „Installieren“.
Ö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.
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.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Tabby split-in-4 / pay-later at BC checkout | ||||
| Eligibility / credit-limit check at order time | ||||
| Settlement payout reconciliation against AR in BC | ||||
| Automatic merchant-fee posting to G/L | ||||
| Multi-currency GCC (AED, SAR, KWD) | ||||
| Refunds issued from BC without portal switching | ||||
| Built, installed and supported on your tenant | ||||
| Update-safe per-tenant extension (no core changes) |
No. This is a build-to-order, per-tenant Business Central extension. ECOSIRE builds it for your specific environment, chart of accounts and tax setup, then installs it as a tenant-specific extension. It is not a one-click AppSource app, and we do not claim an instant download — you get a fit-to-purpose integration instead of a generic one.
Most builds are scoped, developed, deployed to your sandbox and validated against Tabby's test environment within roughly two to four weeks, depending on your chart-of-accounts complexity, the GCC currencies in scope and approval cycles on your side. We confirm a firm timeline in writing after a short scoping call before any work starts.
Every build includes a post-go-live support and warranty window for fixes and questions through a defined channel. Because Tabby's API and Business Central both evolve, we offer an ongoing maintenance arrangement to keep the extension compatible with BC monthly updates and any Tabby API changes — quoted separately from the one-time build.
Yes. AED, SAR and KWD are supported out of the build using Business Central's native multi-currency and exchange-rate framework, so payouts and AR clearing post in the correct currency. Additional GCC currencies can be added during scoping if Tabby supports them in your market.
It is built as table and page extensions with event subscribers, so it does not modify core BC objects — that is what keeps it update-safe. Credentials and configuration live in dedicated setup tables, and permission sets isolate access. If you run other payment or e-commerce apps, we check for event and field overlap during scoping.
A build-to-order Dynamics 365 Business Central extension that offers Tabby split-in-4 / pay-later at checkout for GCC merchants, captures and refunds orders from BC, and reconciles Tabby settlement payouts against AR in AED, SAR and KWD.