跳至主要内容
产品详细信息以英文显示。翻译即将推出。
JD.com Connector for Business Central — A build-to-order AL extension that connects JD — 1/1示意预览

A build-to-order AL extension that connects JD.com (domestic and JD Worldwide cross-border) to Business Central:

order import, listing publish with Chinese category mapping, inventory and price sync, JD Logistics reconciliation, and returns/after-sales handling. Built, installed per-tenant, and supported by

ECOSIRE on your BC environment.

什么是 JD.com Connector for Business Central?

A build-to-order AL extension that connects JD.com (domestic and JD Worldwide cross-border) to Business Central: order import, listing publish with Chinese category mapping, inventory and price sync, JD Logistics reconciliation, and returns/after-sales handling. Built, installed per-tenant, and supported by ECOSIRE on your BC environment. 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.

核心功能

Imports JD.com orders (domestic POP and JD Worldwide cross-border) into Business Central as sales orders via scheduled Job Queue calls to the JD JOS/360buy OpenAPI, preserving the JD order number, buyer info, and order status
Publishes and updates JD listings from BC items with a configurable Chinese category tree and attribute (SKU) mapping table, so a single item master drives both ERP and marketplace listings
Two-way inventory and price sync: BC item availability and unit prices push to JD on a schedule, with a mapping layer for JD price/promotion fields and per-location stock
JD Logistics (JDL) fulfillment reconciliation: matches JD shipment and waybill data against BC warehouse shipments and posted sales shipments to flag mismatches
Returns and after-sales (售后) handling: imports JD return/refund requests and posts them as BC return orders and credit memos with reason-code mapping
Dedicated JD Connector Setup page and connection record storing app key, app secret, and OAuth access/refresh tokens, with token refresh handled in code
AL table and page extensions on Sales Order, Item, and Customer that surface JD-specific fields (JD order no., JD SKU, listing status) inline in standard BC pages
Event subscribers on posting and inventory routines so sync stays consistent with BC's native document and ledger flows rather than bolting on a parallel data store
Sync log and error queue table with retry, so failed JD API calls are visible, diagnosable, and re-runnable instead of silently lost
Ships with permission sets (JD setup admin vs. JD sync operator) to control who configures the connection and who runs syncs
Optional Dataverse / Power Platform surfacing of JD order and listing data for Power BI dashboards and Power Automate flows
Configurable field and category mapping (no hard-coded JD taxonomy) so the connector adapts to your assortment and JD storefront type

按需定制,全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

  1. 1

    您下单

    以一次性构建价格开始。我们在启动时与您共同确定范围。

  2. 2

    我们构建与安装

    ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。

  3. 3

    上线 + 支持

    约一个工作周内上线,并包含两周上线支持。我们交付的代码中的缺陷免费修复。

关于此产品

Selling on JD.com from a Western or regional brand means living in two worlds: JD's POP open platform (the 360buy OpenAPI / JOS gateway, with its Chinese category tree, SKU model, and JD Logistics flows) on one side, and your Business Central ERP on the other. Most teams bridge the gap with spreadsheets and manual re-keying. This extension removes that gap.

The JD.com Connector for Business Central is a per-tenant AL extension that ECOSIRE designs, builds, and installs directly on your Business Central environment (cloud/SaaS or on-prem). It is not an instant AppSource download — it is built to order against your chart of accounts, item setup, locations, and JD seller account, then deployed and supported by us.

Architecturally it is real AL: table and page extensions for sales orders, items, and customers; a dedicated setup page and connection record holding your JD app key, app secret, and OAuth access token; event subscribers on posting and inventory routines; and scheduled Job Queue entries that call the JD JOS REST API. Orders flow into BC as sales documents with JD order numbers retained; listings publish from BC items with a configurable Chinese category and attribute mapping; inventory and price changes sync outward on a schedule; JD Logistics shipments reconcile against BC warehouse shipments; and returns/after-sales (售后) requests post as return orders and credit memos.

Permission sets ship with the extension so you control who can run sync and edit JD setup. Where you run Power Platform, we can surface JD order and listing data through Dataverse for Power BI and Power Automate. You own the source; ECOSIRE supports and updates it.

你得到什么

  • A per-tenant Business Central AL extension (.app) built for your environment, version-pinned to your BC release, installed by ECOSIRE
  • JD Connector Setup configured with your JD seller (POP/JD Worldwide) app key, secret, and OAuth tokens, validated against the live JD JOS gateway
  • Category and SKU/attribute mapping tables populated for your assortment, plus return reason-code mapping
  • Job Queue entries scheduled for order import, inventory/price sync, and logistics reconciliation, tuned to your volume
  • Permission sets assigned and a short admin runbook covering setup, re-auth, and reading the sync log
  • Source code handed to you, a UAT pass on a sandbox tenant, and go-live support plus an agreed post-launch support window

这是给谁的

Cross-border brand operations lead

Runs a brand selling into China via JD Worldwide and needs JD orders, stock, and returns to land in Business Central automatically instead of being re-keyed from a separate seller console.

Business Central / ERP administrator

Owns the BC tenant and wants the JD integration as a clean per-tenant AL extension with permission sets and a sync log, not an opaque third-party black box or a pile of manual CSV imports.

Finance and after-sales manager

Needs JD settlements, refunds, and after-sales (售后) requests reflected accurately as BC sales documents, credit memos, and return orders so revenue and inventory stay reconciled.

JD.com Connector for Business Central 如何比较

标准伊科西尔定制建造竞争对手Dynamics 365 Business Central 原生
JD JOS/360buy OpenAPI order import into BC as sales orders包含部分支持部分支持不包括在内
Listing publish with configurable Chinese category & SKU mapping包含部分支持部分支持不包括在内
Two-way inventory & price sync on Job Queue schedule包含部分支持包含不包括在内
JD Logistics (JDL) fulfillment reconciliation to BC shipments包含部分支持不包括在内不包括在内
Returns / after-sales (售后) posted as BC return orders & credit memos包含部分支持部分支持不包括在内
Built to your tenant, item setup & JD account (per-tenant extension)包含包含不包括在内不包括在内
Source code ownership delivered to you包含包含不包括在内不包括在内
Vendor-supported with JD API change updates包含不包括在内包含不包括在内

关于JD.com Connector for Business Central的常见问题

Is this a download from Microsoft AppSource?

No. This is a build-to-order per-tenant AL extension. There is no instant AppSource install. ECOSIRE builds the .app against your specific Business Central version, item setup, and JD seller account, then installs it on your tenant (sandbox first, then production) and configures the connection. You receive the source code.

What is the delivery lead time?

Typical delivery is about one working week from kickoff and JD API access confirmation, depending on your assortment size and how many JD storefront types (domestic POP vs. JD Worldwide) you sell through. The flow is: requirements and JD app credentials, build, sandbox UAT, then production go-live. We confirm a dated schedule before starting.

How do ongoing support and updates work?

Every build includes a post-launch support window agreed in your order, covering bug fixes, JD JOS API changes (endpoints, auth, category-tree updates), and re-authentication help. Because you own the source, you are never locked in. We also offer extended support and enhancement retainers if you want us to keep evolving the extension as JD's platform or your assortment changes.

Does it handle both domestic JD.com and JD Worldwide cross-border selling?

Yes. The connector targets the JD POP open platform (JOS / 360buy OpenAPI) and is configured per storefront. Cross-border (JD Worldwide) specifics — such as bonded/direct-mail fulfillment patterns and the relevant order and logistics fields — are mapped during the build to match how your account is set up.

Will it conflict with our existing Business Central customizations?

It is built as a standard AL extension using table/page extensions and event subscribers, which is the supported, upgrade-safe model. We review your existing extensions before building to avoid event and field collisions, and we test on a sandbox tenant first. If you run Power Platform, we can optionally surface JD data through Dataverse rather than altering your core pages.

申请报价

JD.com Connector for Business Central

A build-to-order AL extension that connects JD.com (domestic and JD Worldwide cross-border) to Business Central: order import, listing publish with Chinese category mapping, inventory and price sync, JD Logistics reconciliation, and returns/after-sales handling. Built, installed per-tenant, and supported by ECOSIRE on your BC environment.

  • Imports JD.com orders (domestic POP and JD Worldwide cross-border) into Business Central as sales orders via scheduled Job Queue calls to the JD JOS/360buy OpenAPI, preserving the JD order number, buyer info, and order status
  • Publishes and updates JD listings from BC items with a configurable Chinese category tree and attribute (SKU) mapping table, so a single item master drives both ERP and marketplace listings
  • Two-way inventory and price sync: BC item availability and unit prices push to JD on a schedule, with a mapping layer for JD price/promotion fields and per-location stock
  • JD Logistics (JDL) fulfillment reconciliation: matches JD shipment and waybill data against BC warehouse shipments and posted sales shipments to flag mismatches

申请报价

告诉我们您对 JD.com Connector for Business Central 的需求,我们将发送价格、许可选项和量身定制的方案,通常在一个工作日内。

现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。