Illustrative previewA 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.
What is 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.
Key Features
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.
- 3
Go live + support
You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.
About this Product
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.
What you get
- 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
Who this is for
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.
How JD.com Connector for Business Central Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Dynamics 365 Business Central Native |
|---|---|---|---|---|
| JD JOS/360buy OpenAPI order import into BC as sales orders | Included | Partial support | Partial support | Not included |
| Listing publish with configurable Chinese category & SKU mapping | Included | Partial support | Partial support | Not included |
| Two-way inventory & price sync on Job Queue schedule | Included | Partial support | Included | Not included |
| JD Logistics (JDL) fulfillment reconciliation to BC shipments | Included | Partial support | Not included | Not included |
| Returns / after-sales (售后) posted as BC return orders & credit memos | Included | Partial support | Partial support | Not included |
| Built to your tenant, item setup & JD account (per-tenant extension) | Included | Included | Not included | Not included |
| Source code ownership delivered to you | Included | Included | Not included | Not included |
| Vendor-supported with JD API change updates | Included | Not included | Included | Not included |
Frequently Asked Questions about 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.
Related Modules
Google Shopping Feed for Business Central
A Business Central AL extension that builds Google Merchant Center product feeds directly from your item, price and inventory data, then keeps them fresh on a job queue schedule. ECOSIRE builds it to your catalog structure after a scoping call — it is not an AppSource download.
HyperPay Payment Connector for Business Central
A per-tenant AL extension that wires HyperPay checkout, payment links and tokenized billing into Business Central, then auto-reconciles settlements, fees and refunds against your bank and customer ledgers. Custom-built, installed and supported by ECOSIRE.
Kaufland Global Marketplace Connector
A build-to-order AL extension that syncs Kaufland Global Marketplace orders, offers, stock and settlements directly into Dynamics 365 Business Central. ECOSIRE scopes, builds, installs and supports it for your tenant and release wave.
k-eCommerce-style B2B/B2C Storefront for Business Central
A k-eCommerce-style webstore that reads and writes live Business Central data through the BC API — real-time catalog, B2B customer pricing, credit limits, and self-service ordering. Built and installed by ECOSIRE as a per-tenant AL extension on your tenant, then supported.
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