Talabat / Q-commerce Integration for Magento 2

主な機能

Magento product/category/attribute mapping into the Talabat menu/catalog model (items, modifiers, categories) via service contracts under app/code/Ecosire/TalabatQcommerce/Api

Near real-time stock sync using Magento MSI source/stock data, pushed through a queued message consumer with cron reconciliation to correct drift

Price updates propagated per store/branch with currency and tier-price awareness

Order import: Talabat orders created as native Magento sales orders with customer, branch and line-item mapping

Bi-directional order status sync (accepted → preparing → picked → delivered/cancelled) via observers on order state changes

Store/branch and availability mapping linking each Magento source/website to the correct q-commerce store, including open/closed and out-of-stock toggles

Arabic (RTL) content mapping for item names, descriptions and modifier labels using Magento store-view locale values

Admin configuration section with ACL (Ecosire_TalabatQcommerce::config), encrypted credential storage and per-branch enable/disable

Resilient delivery: retry with backoff, dead-letter queue and a sync audit log of every outbound/inbound API call

REST/GraphQL-friendly architecture — extends Magento's API surface and service contracts rather than direct table writes

Webhook/callback endpoint to receive Talabat order and status events with signature verification

Plugins/interceptors on catalog and stock-save flows so any Magento edit triggers a scoped, deduplicated platform update

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

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

構築とインストール

ECOSIRE がお客様の Magento 2 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

Talabat and the wider GCC q-commerce ecosystem (vendor portal + partner APIs) expect their own menu/catalog model, branch-level availability and rapid stock/price updates — none of which Magento 2 speaks natively. This extension is the bridge. ECOSIRE builds it to order as a proper Magento 2 module under app/code/Ecosire/TalabatQcommerce, wired through di.xml with service contracts (API interfaces under Api/ and Model/), plugins/interceptors on catalog and stock save flows, and observers on order events — so your Magento store stays the single source of truth.

Catalog and menu data is mapped from Magento products, categories and attributes into the Talabat menu structure (items, modifiers, categories, store/branch scoping). Stock and price changes propagate in near real time via Magento's MSI source/stock data and a queued push, with cron-based reconciliation to catch drift. Orders placed on Talabat are imported as native Magento orders, with bi-directional status sync (accepted, preparing, picked, delivered, cancelled) writing back to the platform. Branch and availability mapping ties each Magento source/website to the correct q-commerce store, and Arabic content mapping ensures name, description and modifier labels carry the right RTL locale values.

Everything is admin-controllable: a dedicated configuration section, ACL resources (Ecosire_TalabatQcommerce::config), secure credential storage, retry/dead-letter handling and an audit log of every sync call. It runs cleanly on Magento Open Source and Adobe Commerce, and respects your existing GraphQL/REST surface rather than bypassing it.

Because every Talabat onboarding, attribute set and branch topology differs, this is sold build-to-order: we scope, build, install on your environment, validate against your real catalog, and support it. It is not an instant Marketplace download.

得られるもの

Custom Magento 2 module (Ecosire_TalabatQcommerce) installed under app/code on your environment, compatible with Magento Open Source and Adobe Commerce

Catalog/menu, stock, price, order and status sync configured against your live Talabat / q-commerce vendor account

Admin configuration, ACL roles, encrypted credentials and per-branch mapping set up for your store/branch topology

Arabic store-view content mapping verified for your RTL catalog

Cron jobs, message queue consumers and webhook endpoint deployed and tested end-to-end

Technical handover docs (architecture, config reference, runbook) plus a post-launch support and update window

これは誰のためのものですか

GCC grocery / retail brand owner

Sells via a Magento 2 storefront and wants to appear on Talabat and other q-commerce apps without manually re-entering or re-pricing the catalog in each portal.

Operations / branch manager

Needs each physical branch mapped to the right q-commerce store, with accurate open/closed and stock availability so customers never order unavailable items.

Magento developer / agency lead

Wants a clean, upgrade-safe module (di.xml, plugins, service contracts, ACL) rather than core hacks or fragile cron scripts, with proper logging and retry handling.

Talabat / Q-commerce Integration for Magento 2 の比較方法

基準	エコシエール	カスタムビルド	競合他社	Magento 2 標準機能
Talabat / GCC q-commerce catalog & menu sync out of the box	付属	部分的なサポート	部分的なサポート	含まれていない
Built, installed and supported by the vendor (no in-house Magento team required)	付属	含まれていない	含まれていない	含まれていない
Real-time stock & price sync using Magento MSI sources/branches	付属	部分的なサポート	部分的なサポート	含まれていない
Order import + bi-directional status sync as native Magento orders	付属	部分的なサポート	部分的なサポート	含まれていない
Arabic / RTL store-view content mapping	付属	部分的なサポート	含まれていない	部分的なサポート
Tailored to your exact branch topology and attribute sets	付属	付属	含まれていない	含まれていない
Upgrade-safe architecture (di.xml, service contracts, plugins, ACL, queues)	付属	部分的なサポート	部分的なサポート	付属
Instant self-service download from Adobe Commerce Marketplace	含まれていない	含まれていない	付属	含まれていない

Talabat / Q-commerce Integration for Magento 2 に関するよくある質問

How long until it's delivered and live?

This is built to order. After a short scoping call we confirm your Talabat/q-commerce account access, branch topology and attribute mapping. Typical delivery is 2–4 weeks depending on the number of branches, catalog complexity and platform onboarding state. We install on your staging environment first, validate against your real catalog and orders, then go live on production with you.

What about ongoing support and updates?

Each build includes a post-launch support window covering bug fixes and configuration adjustments. We track Magento (Open Source and Adobe Commerce) version changes and Talabat/q-commerce API changes, and offer an ongoing maintenance arrangement so the module stays compatible through your Magento upgrades and platform API revisions.

Does it work on Adobe Commerce as well as Magento Open Source?

Yes. The module is built on standard Magento 2 framework concepts — di.xml, service contracts, plugins, observers, message queues and ACL — that are shared by both editions, so it installs cleanly on Magento Open Source and Adobe Commerce. We confirm your exact version and edition during scoping.

Will it overwrite my catalog or fight with manual edits in Magento?

No. Magento stays the source of truth. Catalog, price and stock changes flow outward from Magento to Talabat; orders and statuses flow inward. Sync is scoped and deduplicated via plugins on save flows, and a cron reconciliation job corrects any drift rather than blindly overwriting.

How are Talabat orders handled inside Magento?

Orders placed on Talabat are imported as native Magento sales orders, mapped to the correct branch/source and customer, with line items and modifiers preserved. Status changes sync bi-directionally, so updating an order in Magento (or on the platform) keeps both sides consistent, with every call written to an audit log.