Talabat Connector for Business Central

Key Features

Real-time Talabat order ingestion into Business Central as sales orders via the BC REST/OData v4 API, with idempotent de-duplication on the Talabat order reference

Menu, catalogue and price publishing from BC Items to Talabat, driven by a configurable Job Queue entry

Per-branch stock availability sync mapping each Talabat store to a BC Location and Item Availability

Order status, fulfilment and rider/dispatch updates pushed back to Talabat as picking and shipment progress

Multi-branch and multi-country support across UAE, KSA, KW and QA with per-store credentials, currency and VAT handling

Delivered as a per-tenant AL extension using table extensions, page extensions and event subscribers — no base-app modification, update-safe

Item and modifier mapping table linking Talabat SKUs/menu items to BC Items, variants and units of measure

Dedicated permission sets isolating store, dispatch and finance roles within Business Central

In-BC sync log, retry queue and error notifications for full observability of every Talabat transaction

Configurable polling or webhook ingestion to match your network and Talabat integration tier

Optional Dataverse / Power Platform surfacing for cross-branch dashboards, alerts and approval flows

Tax and rounding rules aligned to GCC VAT so marketplace orders post cleanly to the correct G/L accounts

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

The Talabat Connector for Business Central is a build-to-order AL extension that closes the gap between Talabat's q-commerce/grocery marketplace and your Microsoft Dynamics 365 Business Central back office. It is not an instant AppSource download — ECOSIRE builds it, installs it as a per-tenant extension on your BC environment, and supports it after go-live.

Talabat order webhooks (or polled order pulls) are ingested through a hardened middleware and written into BC as sales orders via the BC REST/OData v4 API, with each branch mapped to a Location and each Talabat item mapped to a BC Item. The extension ships as proper table extensions, page extensions and event subscribers — no base-app modification — so it survives Microsoft's monthly updates. A Job Queue entry drives near-real-time menu/price publishing and stock-availability sync per branch, while order-status and rider/dispatch updates flow back to Talabat as fulfilment progresses.

Multi-branch and multi-country operators (UAE, KSA, KW, QA) get per-store credential sets, currency and VAT handling, and dedicated permission sets so store and finance teams see only what they should. Telemetry, retry queues and an in-BC sync log give you observability instead of guesswork.

Because every Talabat catalogue, branch topology and BC chart of accounts differs, we scope your exact mapping during a short discovery, then deliver. The result is a maintainable extension you own on your tenant — optionally extended into Dataverse / Power Platform for dashboards and approvals — backed by an ECOSIRE support agreement rather than a one-off script.

What you get

A per-tenant Business Central AL extension (.app) installed on your sandbox then production environment by ECOSIRE

Source AL project (table/page extensions, codeunits, event subscribers, permission sets) handed over to you

Talabat-to-BC mapping configuration: branches→Locations, menu items→Items, modifiers, UoM and VAT rules

Job Queue setup for menu/price publishing and stock availability sync, with documented schedules

Configured permission sets for store, dispatch and finance roles

Deployment runbook plus an admin/operator guide and a short handover training session

Post-go-live support and update-compatibility maintenance under an ECOSIRE support agreement

Who this is for

GCC Dark-Store / Q-Commerce Operations Lead

Runs multiple Talabat-fronted grocery dark stores across UAE and KSA and needs orders, stock and dispatch reflected in Business Central per branch in near real time, without staff re-keying orders.

F&B Multi-Brand Finance Controller

Owns VAT-correct posting and reconciliation across several Talabat brands and countries; wants marketplace orders landing in BC with the right Location, currency and G/L mapping automatically.

BC Functional Consultant / IT Manager

Responsible for the Business Central tenant and resists base-app hacks; wants an update-safe per-tenant extension with permission sets, a sync log and a vendor who supports it after delivery.

How Talabat Connector for Business Central Compares

Criterion	ECOSIRE	Custom Build	Competitor
Native Talabat order ingestion into BC	Included	Partial support	Partial support
Menu/price publishing and per-branch stock sync	Included	Partial support	Partial support
Rider/dispatch status push back to Talabat	Included	Partial support	Not included
Update-safe per-tenant AL extension (no base-app changes)	Included	Partial support	Included
GCC multi-country VAT and multi-branch handling (UAE/KSA/KW/QA)	Included	Partial support	Partial support
Tailored to your exact catalogue, branches and chart of accounts	Included	Included	Not included
Vendor-backed support and BC-release compatibility maintenance	Included	Not included	Partial support
AL source ownership and no lock-in	Included	Included	Not included

Frequently Asked Questions about Talabat Connector for Business Central

Is this an instant download from Microsoft AppSource?

No. This is a build-to-order extension. ECOSIRE scopes your Talabat catalogue, branch topology and BC setup, then builds the connector and installs it as a per-tenant extension on your Business Central sandbox and production environments. You receive a maintainable, update-safe app rather than an off-the-shelf listing.

What is the typical delivery lead time?

After a short discovery to confirm your branches, menu/item mapping, country/VAT rules and Talabat integration access, a standard single-country deployment is typically delivered in about 3 to 5 weeks. Multi-country rollouts (UAE, KSA, KW, QA) or heavy custom mapping extend this; we confirm a firm timeline in writing before build starts.

How are ongoing support and Business Central updates handled?

Because the connector is a per-tenant AL extension built from table/page extensions and event subscribers, it does not modify the base app and is designed to survive Microsoft's monthly updates. An ECOSIRE support agreement covers bug fixes, compatibility checks against new BC releases, and adjustments when Talabat changes its API. You also receive the AL source so you are never locked in.

Can it handle multiple branches and countries with different VAT?

Yes. Each Talabat store maps to a BC Location with its own credentials, currency and VAT treatment, and orders post to the correct G/L accounts. The extension is built specifically for GCC multi-branch, multi-country operation across UAE, KSA, Kuwait and Qatar.

Do we keep control of the data and the code?

Yes. The extension runs entirely on your Business Central tenant, all data stays in BC (and optionally Dataverse if you choose the Power Platform extension), and ECOSIRE hands over the AL source project. Dedicated permission sets ensure store, dispatch and finance teams only access what their role requires.