Talabat / Q-Commerce Orders Connector for Business Central

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.

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.

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.

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.

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.