JD.com Marketplace Connector

Key Features

Product listing publish to JD.com via the JOS / POP Open Platform API, mapping Magento simple and configurable products to JD SKU and SPU structures

Inventory sync that pushes Magento salable quantity (MSI stock per source/website) to JD warehouse stock on a configurable cron cadence

Price sync that pushes Magento price, special price and tier/website-scoped pricing to JD, with optional markup/markdown rules per channel

Order import that polls JD orders and creates native Magento sales orders, mapping JD buyer, shipping address and line items to your customer and product records

Category and attribute mapping UI that links Magento attribute sets to JD category templates, including required brand, barcode (UPC/EAN) and logistics attributes

Bulk product management to select, queue and publish or update many products to JD at once, with per-SKU success/error reporting

OAuth token lifecycle handling — secure storage of JOS app key/secret, access-token refresh, and HMAC request signing built into a dedicated API client

Queue-backed sync with retry, exponential backoff and rate-limit awareness so JD throttling and transient errors don't drop updates

Admin configuration under Stores > Configuration, ACL-restricted, with a sync dashboard and a per-entity log of every push/pull and its JD response

Store-view / website scoping so multi-store Magento setups can route a specific catalog and currency to the JD channel

Cron-driven scheduled sync plus on-demand manual triggers for listing, stock, price and order jobs

Built on Magento service contracts, plugins/interceptors and observers — no core hacks — so it survives Magento and Adobe Commerce upgrades

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

The JD.com Marketplace Connector lets a Magento 2 (Open Source) or Adobe Commerce store sell into China's JD.com (Jingdong) marketplace without managing two catalogs by hand. JD's seller integration runs on the JOS (Jingdong Open Service) / POP Open Platform API with token-based OAuth, signed requests, and Chinese-language category and attribute requirements — none of which Magento speaks natively. This extension is the translation layer.

It ships as a proper Magento module under app/code/Ecosire/JdConnector, wired through di.xml with service contracts, an admin configuration section gated by ACL, and cron-driven sync jobs. Outbound calls (publish listing, push stock, push price) and inbound polling (order pull) run on schedules you control, with a queue and retry/backoff so JD rate limits and token refresh never silently break a sync. A normalization layer maps your Magento attribute sets to JD category templates, including required brand, barcode and logistics attributes.

Because JD's category tree, attribute dictionaries, pricing rules and order shapes differ from one seller account and product vertical to the next, this is sold build-to-order: ECOSIRE configures the connector against your JD POP seller account, your attribute sets, and your store/website/store-view structure, then installs and supports it. It is not an instant Adobe Commerce Marketplace download. After you order, we collect your JOS app credentials and JD shop details, build and test against your catalog in a staging environment, deploy to your production Magento, and hand over documentation. Ongoing API changes on JD's side are covered under support.

This is for cross-border merchants who already have Magento as their source of truth and want JD.com as an additional sales channel — kept in sync, not copy-pasted.

What you get

Custom-built Ecosire_JdConnector Magento 2 module installed in app/code (or via Composer) on your environment

Configuration of the connector against your live JD.com POP seller account and JOS app credentials

Category and attribute mapping set up for your actual Magento attribute sets and target JD categories

Staging deployment with a tested sync of a representative product set (listing, stock, price, order pull) before go-live

Production deployment, cron registration and post-deploy verification on your Magento / Adobe Commerce instance

Admin and operator documentation covering configuration, mapping, running syncs and reading the sync logs

Defined support and maintenance window covering bug fixes and JD/JOS API changes after handover

Who this is for

Cross-border merchant expanding into China

A brand or retailer that runs Magento as its source of truth and wants JD.com as a new sales channel without maintaining a separate catalog or manually re-keying orders.

Ecommerce operations manager

Owns day-to-day catalog, stock and pricing accuracy. Needs JD listings, inventory and prices to stay in sync with Magento automatically and wants clear logs when a sync fails.

Magento technical lead / agency

Responsible for the store's codebase and upgrade path. Wants a clean, service-contract-based module (no core edits) that won't break on Magento or Adobe Commerce upgrades and is supported by the builder.

How JD.com Marketplace Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor
Magento product listing published to JD.com via JOS/POP API	Included	Partial support	Partial support
Automated inventory and price sync to JD (cron + queue)	Included	Partial support	Partial support
JD order import into native Magento sales orders	Included	Partial support	Partial support
Category/attribute mapping to JD templates for your catalog	Included	Partial support	Partial support
Built to your JD account, attribute sets and store-view structure	Included	Included	Not included
Installed and configured on your environment for you	Included	Partial support	Not included
Ongoing support for JD/JOS API changes after delivery	Included	Not included	Partial support
No core hacks — service contracts, plugins, upgrade-safe	Included	Partial support	Partial support

Frequently Asked Questions about JD.com Marketplace Connector

How long does delivery take, since this is build-to-order?

Typical delivery is about 2 to 4 weeks after we receive your JD.com POP seller account access and JOS app credentials. The exact lead time depends on how many JD categories you sell into and how complex your Magento attribute sets are. We confirm a schedule with you up front, build and test in staging against your catalog, then deploy to production. This is a custom build — not an instant Adobe Commerce Marketplace download.

What ongoing support and updates are included?

After handover you get a defined support window covering bug fixes and adapting the connector to changes JD makes to its JOS / POP Open Platform API (new required attributes, auth changes, endpoint deprecations). We also support Magento and Adobe Commerce version upgrades for the module. Because it's built on service contracts and plugins with no core hacks, upgrades are low-risk. Support terms are agreed in writing at purchase and can be extended.

Does this work on both Magento Open Source and Adobe Commerce?

Yes. The module follows standard Magento 2 architecture (di.xml, service contracts, observers, plugins, ACL, cron) and runs on both Magento Open Source and Adobe Commerce, including B2B and multi-store/multi-website setups. We confirm your exact version and edition during scoping and target it specifically.

How does inventory and price syncing actually work?

Cron jobs read your Magento salable quantity (including MSI source/website stock) and your price, special price and website-scoped pricing, then push them to JD through signed JOS API calls on the schedule you set. Updates run through a queue with retry and backoff so JD rate limits or transient errors don't drop changes. Every push is logged with the JD response, and you can also trigger a manual sync on demand.

Do I need my own JD.com seller account and API access?

Yes. You need an approved JD.com POP (Pop Open Platform) seller account and a JOS app with an app key and secret. JD controls who can sell and access the API. We guide you through obtaining the JOS credentials and connecting the app, then build the connector against your specific account, shop and category permissions.