示意预览A custom-built Business Central AL extension that consolidates multi-marketplace selling
— unified order import, per-channel listing and stock/price sync, fulfillment and tracking write-back, channel mapping rules, and settlement/fee import — installed per-tenant and supported by ECOSIRE.
什么是 Multi-Marketplace Connector Hub？
A custom-built Business Central AL extension that consolidates multi-marketplace selling — unified order import, per-channel listing and stock/price sync, fulfillment and tracking write-back, channel mapping rules, and settlement/fee import — installed per-tenant and supported by ECOSIRE. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
关于此产品
The Multi-Marketplace Connector Hub is a build-to-order extension for Microsoft Dynamics 365 Business Central that turns BC into the single operational layer for a multi-channel marketplace business. Instead of staff toggling between seller portals and re-keying orders, every channel flows through one set of BC tables, pages and job queue entries you already own.
This is not an instant AppSource download. ECOSIRE builds the connector in AL, scopes it to the marketplaces and SKUs you actually sell on, then installs it as a per-tenant extension directly on your Business Central environment (cloud SaaS or on-prem). We configure permission sets, job queue cadence and the API authentication, then hand over a working, supported system.
Under the hood the Hub adds table extensions and new tables for channel listings, channel mapping and settlement lines; page extensions on Item, Sales Order and Posted Sales Shipment; and event subscribers that react to inventory and posting events to push stock/price updates and fulfillment write-back. Outbound and inbound calls use the marketplace REST APIs through BC's HttpClient with retry and logging, scheduled via the job queue. Where you run Power Platform, the same channel and settlement data is surfaced through the standard BC REST/OData v4 API for Dataverse virtual tables and Power BI.
Every integration is honestly bounded by each marketplace's published API limits — we map exactly which fields, statuses and fee types each channel exposes, document the mapping, and build only what the API supports. You get a connector that fits your catalogue, your number sequences and your posting setup, with no per-order SaaS middleware tax.
你得到什么
- A per-tenant Business Central AL extension (.app) built and version-controlled by ECOSIRE for your specific marketplaces
- Installation and publish onto your BC environment (cloud SaaS sandbox first, then production) with no downtime to existing data
- Configured channel connections, API credentials, mapping rules and job queue schedules
- Permission sets for operator and finance roles, assigned to your users
- A field-level mapping document for every marketplace integrated, stating exactly which API fields and statuses are supported
- A short admin runbook plus a live handover/training session, and a defined post-go-live support window
这是给谁的
Multi-channel operations manager
Runs daily fulfillment across several marketplaces and wants every order, shipment and tracking number to live in Business Central instead of in separate seller portals and spreadsheets.
Business Central administrator / IT lead
Owns the BC tenant and needs a clean per-tenant extension with proper permission sets, job queue control and logging — not opaque external middleware syncing into the database.
Finance / margin controller
Needs marketplace settlements, commissions and fees imported and reconciled against orders in BC so channel-level profitability is accurate without manual payout matching.
Multi-Marketplace Connector Hub 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Dynamics 365 Business Central 原生 |
|---|---|---|---|---|
| Unified order import across multiple marketplaces into native BC documents | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Installed as a supported per-tenant AL extension (no base-app modification) | 包含 | 部分支持 | 包含 | 不包括在内 |
| Tailored to your exact channels, SKUs, number series and posting setup | 包含 | 包含 | 不包括在内 | 不包括在内 |
| Settlement and fee import reconciled for channel-level margin in BC | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Fulfillment/tracking write-back via posting event subscribers | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Built, installed and supported for you with documented field mapping | 包含 | 不包括在内 | 部分支持 | 不包括在内 |
| No per-order external middleware/SaaS fee | 包含 | 包含 | 不包括在内 | 包含 |
| Data exposed via REST/OData for Dataverse and Power BI | 包含 | 部分支持 | 部分支持 | 部分支持 |
关于Multi-Marketplace Connector Hub的常见问题
Is this an instant download from Microsoft AppSource?
No. This is a build-to-order extension. ECOSIRE develops it in AL for the specific marketplaces and catalogue you sell on, then installs it as a per-tenant extension on your own Business Central environment. There is no AppSource listing to click-install — you get a connector tailored to your channels, number series and posting setup.
How long does delivery take?
Typical lead time is one working week from kickoff, depending on how many marketplaces and how complex your mapping rules are. We start in a BC sandbox: scoping and field mapping first, then build, then a sandbox test cycle with your data, then production publish. You will get a delivery schedule at kickoff and we keep you updated against it.
How do ongoing support and updates work?
Every build includes a post-go-live support window for fixes and tuning. Because marketplaces change their APIs, we offer ongoing maintenance to keep each channel working as their endpoints evolve, plus enhancements like adding a new marketplace later. Support and updates are handled by ECOSIRE directly on your tenant — we publish new versions of the extension as part of your BC update cadence.
Does it work with Business Central cloud (SaaS) and on-premises?
Yes. It is delivered as a standard AL extension that installs on both BC online (SaaS) and on-premises. The connector uses BC's HttpClient and job queue, and exposes data through the standard REST/OData v4 API, so it stays inside Microsoft's supported extension model rather than modifying base application code.
How does it handle settlements, fees and accounting?
Marketplace payout and settlement reports are imported and reconciled against the originating orders, then posted as fee and commission lines against accounts and dimensions you map per channel. This gives you true channel-level margin in BC's standard analytics and Power BI, instead of manually matching payouts to orders.
相关模块
Multi-Carrier Shipping & Label Connector for Business Central
Rate-shop carriers, print labels and write tracking back to orders and marketplaces directly inside Business Central. Built, installed as a per-tenant AL extension and supported by ECOSIRE on your environment.
Newegg Marketplace Connector for Dynamics 365 Business Central
A build-to-order AL extension that connects Newegg Marketplace to Dynamics 365 Business Central — importing orders, pushing stock and price updates, exporting listings, confirming shipments and reconciling settlement payouts. ECOSIRE scopes, builds, installs and supports it for your tenant.
Noon Marketplace Connector for Business Central
A build-to-order Business Central extension that links the noon.com GCC marketplace to your BC tenant — importing orders as sales orders, publishing listings with GCC category mapping, syncing inventory and price across UAE/KSA/EG, and reconciling noon Express / FBN fulfillment. Built, installed and supported by ECOSIRE.
Multi-Marketplace Connector Hub
A custom-built Business Central AL extension that consolidates multi-marketplace selling — unified order import, per-channel listing and stock/price sync, fulfillment and tracking write-back, channel mapping rules, and settlement/fee import — installed per-tenant and supported by ECOSIRE.
- Unified order import from multiple marketplaces into BC Sales Orders with channel-tagged source documents and de-duplication on external order ID
- Per-channel product listing creation and update mapping BC Items to marketplace listings (title, price, attributes, images)
- Scheduled stock and price synchronization driven by Item Ledger and reservation availability, pushed per channel on a job queue cadence
- Fulfillment and tracking write-back: posting a Sales Shipment triggers an event subscriber that sends carrier and tracking number back to the originating channel