什么是 Talabat / Q-Commerce Orders Connector for Business Central？
A custom-built, per-tenant Business Central (AL) extension that ingests Talabat and food/q-commerce orders, syncs menus and prices, and reconciles commissions and payouts — built, installed and supported by ECOSIRE on your own BC environment. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $499.00 USD; request a quote for a scoped proposal.
产品详细信息以英文显示。翻译即将推出。
示意预览A custom-built, per-tenant Business Central (AL) extension that ingests Talabat and food/q-commerce orders,
syncs menus and prices, and reconciles commissions and payouts — built, installed and supported by
ECOSIRE on your own BC environment.
核心功能
Order ingestion from the Talabat / q-commerce merchant API into native BC Sales Orders via a scheduled Job Queue entry, with idempotent de-duplication on external order ID
Menu and item sync — push BC Item catalog, prices and availability to the delivery platform and pull back platform item IDs for two-way mapping
Commission, delivery-fee and platform-charge lines posted to dedicated GL accounts you nominate during scoping
Settlement and payout reconciliation that matches each platform settlement/remittance file against ingested orders and flags variances
Refund and cancellation handling that posts credit memos or reverses sales documents and keeps inventory accurate
Multi-branch order routing keyed to BC Locations and shortcut dimensions, so each outlet's orders post to the correct branch
AL table and page extensions on Sales Order and Item plus dedicated staging tables — no modification of base application objects
Event subscribers (OnAfterValidate / posting events) that enforce mapping and tax rules as orders are created
Admin setup pages for API credentials (stored via Isolated Storage), customer/item/branch mapping, and a full sync activity log
Dedicated permission set and entitlements so only authorized ops/finance roles can configure or run the connector
Configurable polling cadence and retry/back-off handling for platform API rate limits and transient failures
Optional Dataverse / Power Platform virtual entity surfacing for Power BI dashboards and Power Apps order monitoring
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
- 3
上线 + 支持
约 2–4 周内上线，并提供上线后的支持期。
关于此产品
If you run a GCC restaurant or grocery chain on Microsoft Dynamics 365 Business Central, your Talabat and q-commerce orders almost certainly live outside your ERP — re-keyed into sales documents by hand, with commissions and payouts reconciled in spreadsheets weeks later. This connector closes that gap.
It is a per-tenant Business Central extension written in AL that ECOSIRE builds to your exact platform mix, then installs and supports on your own BC environment (cloud SaaS or on-prem). It is not an instant AppSource download — it is a build-to-order engagement, scoped to the delivery platforms, branches and chart of accounts you actually use.
On the platform side, ECOSIRE wires the connector to the Talabat / q-commerce merchant API (and any additional aggregators you name) over secure outbound HTTPS, polling new orders and pushing menu and price changes. Inside BC, the extension adds dedicated staging tables, table and page extensions on Sales Order and Item, and event subscribers so incoming orders flow straight into BC sales documents with the right location, dimension and customer mapping. A Job Queue entry runs ingestion on the cadence you set.
Commission, delivery-fee and refund lines are posted to the GL accounts you specify, then matched against each platform's settlement file so payouts reconcile to the dollar. Multi-branch merchants get per-outlet routing keyed to BC Locations and dimensions.
Everything ships behind a dedicated permission set, with admin pages for credentials, mapping and a sync log. Optional Dataverse / Power Platform surfacing lets ops teams monitor order flow from a Power BI or Power Apps layer. You own the source; ECOSIRE maintains it.
你得到什么
- A per-tenant Business Central extension (AL .app package) built to your platform and branch configuration, installed on your BC environment
- Configured connection to the Talabat / q-commerce merchant API (and any additional aggregators agreed in scope) with credentials secured in Isolated Storage
- Field, customer, item and branch mapping configured against your live chart of accounts, Locations and dimensions
- A dedicated permission set plus a Job Queue entry configured for your chosen ingestion cadence
- Source code (AL project) handed over to you, plus a deployment/upgrade runbook
- Admin and operator documentation covering setup pages, the sync log, and reconciliation workflow, with a handover walkthrough session
这是给谁的
Finance / Accounts Lead
Owns the GL and month-end close. Wants commission, delivery-fee and refund postings automated and every Talabat payout reconciled against orders, so settlement variances surface in BC instead of in a spreadsheet weeks later.
Operations / Branch Manager
Runs multiple outlets and needs each platform order routed to the correct BC Location and dimension automatically, with a live sync log to confirm nothing is dropped during peak delivery hours.
IT / BC Administrator
Responsible for the BC environment. Wants a clean per-tenant extension that never touches base objects, ships behind a scoped permission set, and comes with source and an upgrade runbook so the org isn't locked to a black box.
Talabat / Q-Commerce Orders Connector for Business Central 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Dynamics 365 Business Central 原生 |
|---|---|---|---|---|
| Talabat / q-commerce order ingestion into BC Sales Orders | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Two-way menu, item and price sync | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Commission & settlement/payout reconciliation to GL | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
| Multi-branch routing on BC Locations & dimensions | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Built, installed & supported on your own environment | 包含 | 不包括在内 | 不包括在内 | 部分支持 |
| Upgrade-safe per-tenant extension, no base-object changes | 包含 | 部分支持 | 包含 | 不包括在内 |
| Source code handed over to you | 包含 | 包含 | 不包括在内 | 不包括在内 |
| Tailored to your exact GCC platform mix & chart of accounts | 包含 | 包含 | 不包括在内 | 不包括在内 |
关于Talabat / Q-Commerce Orders Connector for Business Central的常见问题
How long until the connector is live, and is this an AppSource download?
This is a build-to-order engagement, not an instant AppSource install. After a short scoping call to confirm your platforms, branches and GL accounts, typical delivery is about 2 to 4 weeks: ECOSIRE builds the AL extension, installs it as a per-tenant extension on your BC sandbox for UAT, then promotes to production once you sign off. Timelines extend if you need several aggregators or complex multi-entity mapping.
How does ongoing support and updates work after go-live?
ECOSIRE supports the extension on your environment, including fixes when the Talabat / q-commerce API changes and recompiles to stay compatible with Business Central major releases (the twice-yearly BC update waves). You also receive the AL source and an upgrade runbook, so you are never locked in. Support terms — response times and an update window — are agreed at handover; ongoing retainers are available separately.
Will it modify our base Business Central application?
No. The connector is delivered as a per-tenant extension using AL table extensions, page extensions, staging tables and event subscribers. It does not alter base application objects, which keeps your environment upgrade-safe and AppSource-compatible for your other apps.
Which delivery and q-commerce platforms are supported?
The base scope targets the Talabat merchant API. Additional aggregators or q-commerce platforms common in the GCC can be added during scoping as long as they expose a merchant/partner API. ECOSIRE confirms feasibility for each named platform before the build starts; the architecture (staging tables plus a mapping layer) is designed to add platforms without reworking your BC posting logic.
How are commissions and payouts actually reconciled?
Each ingested order carries its platform commission, delivery fee and other charges, posted to GL accounts you nominate. When a platform settlement or remittance file arrives, the connector matches its lines against the corresponding orders in BC and flags any variance — missing payouts, fee mismatches or unexpected deductions — so finance reconciles to the order rather than estimating from a bank statement.
相关模块
申请报价
Talabat / Q-Commerce Orders Connector for Business Central
A custom-built, per-tenant Business Central (AL) extension that ingests Talabat and food/q-commerce orders, syncs menus and prices, and reconciles commissions and payouts — built, installed and supported by ECOSIRE on your own BC environment.
- Order ingestion from the Talabat / q-commerce merchant API into native BC Sales Orders via a scheduled Job Queue entry, with idempotent de-duplication on external order ID
- Menu and item sync — push BC Item catalog, prices and availability to the delivery platform and pull back platform item IDs for two-way mapping
- Commission, delivery-fee and platform-charge lines posted to dedicated GL accounts you nominate during scoping
- Settlement and payout reconciliation that matches each platform settlement/remittance file against ingested orders and flags variances