Magento 2 JD.com Integration

主な機能

Bi-directional product sync: export Magento catalog to JD.com and import JD listings back, with SKU as the reconciliation key

Inventory & price sync via cron and MSI-aware plugins — stock and price changes propagate to JD on a schedule and on save

JD order import that creates native Magento orders, customers and invoices, preserving JD order IDs for traceability

Auto-ship (JD Logistics) order handling — fulfillment status, shipment confirmation and tracking numbers sync back to JD

Category mapping UI to align your Magento categories with JD's required Chinese category tree

Attribute & attribute-set mapping to JD's mandatory product attribute dictionary (brand, specs, certifications)

Listing profiles: group products into profiles with per-profile pricing rules, title templates and attribute maps

Admin configuration section with JD API credentials, environment toggle and sync controls under Stores > Configuration

Granular admin ACL (acl.xml) so JD listing, sync and order operations are permission-gated per role

Sync logs and error grid built on Magento UI components for retry, status and failed-listing diagnostics

Service-contract architecture (Api/ interfaces + di.xml) so behavior is override-safe and unit-testable

Currency and price-rule handling for CNY listing prices independent of your base store currency

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Magento 2 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

JD.com (Jingdong) is one of China's largest B2C marketplaces, but it has no official Magento connector and its open-platform APIs use Chinese category trees, attribute dictionaries and a fulfillment model (including JD Logistics auto-ship) that don't map cleanly onto a Western catalog. This extension is built to order by ECOSIRE for your specific store, catalog structure and JD seller account — it is not an instant Adobe Commerce Marketplace download.

We ship a proper Magento 2 module under app/code/Ecosire/JdIntegration that registers JD as a sales channel. Product export and import run as a service-contract layer (Api/ interfaces with concrete Model/ implementations wired through di.xml), so listing logic is testable and override-safe rather than hard-coded into observers. A cron_group handles scheduled inventory and price sync; Plugin interceptors keep MSI stock and catalog_product price changes flowing to JD near real time. Order ingestion pulls JD orders, creates native Magento orders, and respects JD's auto-ship (JD Logistics) workflow so fulfillment status and tracking flow back to the marketplace. Listing profiles let you batch products by category with their own attribute-mapping, pricing rules and title templates.

Everything is admin-driven: a dedicated config section, grids built on standard UI components, and proper ACL resources in acl.xml so JD operations sit behind real permissions. Works on Magento Open Source and Adobe Commerce 2.4.x. After purchase, ECOSIRE installs on your environment (or hands a deploy-ready package to your team), runs a mapping workshop for your catalog, and provides post-launch support. Delivery is typically 2–4 weeks depending on catalog complexity and JD account readiness.

得られるもの

Custom Magento 2 module (Ecosire_JdIntegration) installed under app/code, composer-installable, with registration.php and module.xml

JD.com open-platform API client wired through service contracts and di.xml, scoped to your seller account

Admin configuration, category/attribute mapping UI and listing-profile management screens

Cron jobs for scheduled inventory/price sync plus plugins for on-save propagation

Order import + auto-ship fulfillment sync flow tested against your JD account in a staging environment

Catalog mapping workshop and a documented mapping of your categories/attributes to JD's required fields

Installation on your environment (or a deploy-ready package + setup:upgrade/di:compile instructions for your team)

Technical handover doc, admin user guide, and a defined post-launch support window

これは誰のためのものですか

Cross-border brand expanding into China

A brand already selling on Magento that wants a JD.com storefront without running a second, disconnected catalog. They need one source of truth in Magento and automated push to JD.

Magento merchant adding JD as a channel

An existing Open Source or Adobe Commerce merchant who treats JD as another sales channel alongside their web store and needs orders, stock and pricing kept in sync automatically.

Operations / channel manager

The person responsible for keeping JD listings accurate and orders fulfilled. They need listing profiles, category mapping and an admin grid that surfaces sync errors instead of silent failures.

Magento 2 JD.com Integration の比較方法

基準	エコシエール	カスタムビルド	競合他社	Magento 2 標準機能
JD.com auto product export/import from Magento	付属	部分的なサポート	含まれていない	含まれていない
Scheduled inventory & price sync (cron + MSI-aware plugins)	付属	部分的なサポート	部分的なサポート	含まれていない
JD auto-ship (JD Logistics) order handling with tracking back-sync	付属	部分的なサポート	含まれていない	含まれていない
Category & attribute mapping to JD's Chinese dictionaries	付属	部分的なサポート	含まれていない	含まれていない
Listing profiles with per-profile pricing & title templates	付属	部分的なサポート	含まれていない	含まれていない
Built, installed and supported for your store with SLA	付属	部分的なサポート	含まれていない	含まれていない
Service-contract, di.xml, ACL-gated, 2.4.x upgrade-safe architecture	付属	部分的なサポート	部分的なサポート	付属

Magento 2 JD.com Integration に関するよくある質問

How long until the extension is delivered and live?

Because this is built to order for your catalog and JD seller account, typical delivery is 2–4 weeks. We start with a catalog and JD-account readiness review, build and test against your products in staging, then install on production. Larger or more complex catalogs (heavy attribute mapping, multiple listing profiles) sit at the upper end of that range.

Is this a Magento Marketplace extension I can download instantly?

No. JD.com has no official Magento connector and the integration must be tailored to your category tree, attribute mapping and JD account configuration. ECOSIRE builds, installs and supports it for you. There is no instant download or pre-existing Marketplace listing.

What ongoing support and updates do I get?

Every build includes a defined post-launch support window for bug fixes and mapping adjustments. JD periodically changes its open-platform API and category/attribute requirements; we offer ongoing maintenance to keep your integration compatible, and we version the module so updates apply cleanly via composer and setup:upgrade.

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

Yes. The module targets Magento 2.4.x and works on both Magento Open Source and Adobe Commerce. It is MSI-aware for inventory and uses standard service contracts, plugins and UI components, so it coexists with your existing customizations rather than patching core.

How are inventory and prices kept in sync with JD?

Two mechanisms work together: cron jobs run scheduled full/delta syncs, and plugins (interceptors) on product save and MSI stock updates push changes to JD near real time. JD order import reduces Magento stock through native order creation, so quantities stay consistent across both channels.

Can I control which products go to JD and how they're listed?

Yes, through listing profiles. You group products into profiles, each with its own category mapping, attribute map, pricing rules and title template. Products outside a profile are never pushed, so you stay in full control of what appears on JD.com.