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. One-time license from $499.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

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.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
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.
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
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.
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.
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.
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.
Buy the license on ecosire.com and download the JD.com Connector for Business Central module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for JD.com Connector for Business Central, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| 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 |
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.
Typical delivery is about 3 to 5 weeks 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.
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.
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.
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.
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.