Talabat / Q-Commerce Orders Connector for Business Central

主な機能

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 が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Dynamics 365 Business Central 上で構築・設定・インストールします。

本番稼働 + サポート

約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.