ERPNext JD.com Seller Connector

Key Features

`JD Connector Settings` single DocType stores app key/secret and OAuth access + refresh tokens encrypted at rest, with automatic token refresh in a scheduled job

Scheduler event (configurable cadence, e.g. every 15 min) pulls new and updated JD.com orders and materializes them as ERPNext `Sales Order` records

`JD Order` and `JD SKU Map` DocTypes link JD product/SKU IDs to native ERPNext `Item` codes so mapping survives re-syncs

Inventory sync via a `doc_events` hook on `Stock Ledger Entry` pushes available quantity to JD to prevent overselling across warehouses

Price sync driven by `Item Price` updates in the selling price list, pushed to JD listings through queued background jobs

Listing / SKU push publishes or updates JD product and SKU attributes from ERPNext Item data in batched, rate-limit-aware jobs

JD Logistics (JDL) fulfillment writeback: `Delivery Note` submission pushes waybill / tracking number back to the JD order and marks it shipped

`JD Settlement` importer parses JD settlement statements, matches fees and payouts to orders, and drafts `Payment Entry` / `Journal Entry` records

All JD Open Platform calls go through signed, server-side `@frappe.whitelist()` methods — app secret and tokens never reach the browser

Cross-border (JD Worldwide) and China-domestic POP flows handled, including multi-currency Sales Orders and configurable tax templates

Client scripts add `Sync now`, `Push listing`, and `Reconcile settlement` buttons directly on the relevant ERPNext forms

Dedicated `JD Connector Manager` role profile plus DocType permission rules scope marketplace operations to authorized users only

Idempotent order import (JD order ID stored + uniqueness-checked) so repeated polls never create duplicate Sales Orders

Error log and retry handling: failed API calls surface in a `JD Sync Log` DocType with payload, status, and re-run action for support visibility

Built and tested against Frappe/ERPNext v15 and v16, installed on your own bench as a versioned Frappe app

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 ERPNext.

Go live + support

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

About this Product

Selling on JD.com — whether cross-border via JD Worldwide or China-domestic — means living inside JD's Open Platform (宙斯/Zeus) APIs, POP seller flows, and JD Logistics (JDL) fulfillment, none of which ERPNext knows about out of the box. Teams typically end up rekeying orders from the JD Seller Center into Sales Orders by hand, exporting stock levels to CSV to keep JD listings from overselling, and reconciling JD's settlement statements against ERPNext payments in a spreadsheet at month-end. ERPNext core has no JD channel, no marketplace order pipeline, and no place to store JD SKU IDs or logistics tracking — so the integration work lands on your ops team every single day.

We build the ERPNext JD.com Seller Connector as a proper Frappe app (erpnext_jd_connector) installed on your own bench, not a black-box middleware. It ships a JD Connector Settings single DocType holding your app key, app secret, and OAuth access/refresh tokens (encrypted), plus custom DocTypes such as JD Order, JD SKU Map, and JD Settlement that mirror JD entities and link cleanly to native ERPNext Sales Order, Item, Delivery Note, and Payment Entry records. Scheduler events registered in hooks.py poll JD's order API on your chosen cadence (for example every 15 minutes) and materialize new orders as Sales Orders with the correct customer, item mapping, taxes, and currency; doc_events hooks on Stock Ledger Entry and Item Price push inventory and price changes back to JD so listings never drift from ERPNext.

Technically, everything routes through JD's Open Platform REST endpoints with signed requests and token refresh handled by whitelisted server-side methods (@frappe.whitelist()), never exposing secrets to the browser. Listing and SKU push runs from queued background jobs so large catalogs don't block the request cycle; JD Logistics fulfillment writeback updates the JD order with your Delivery Note's waybill/tracking number and marks it shipped. A JD Settlement importer parses JD's settlement statements and matches them against orders and fees, producing a reconciliation view and draft Payment Entry / Journal Entry records for your accounting team. Client scripts add "Sync now" and "Push listing" buttons on the relevant forms, and a dedicated JD Connector Manager role profile plus permission rules keep marketplace operations scoped to the right users. The app targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing is shipped blind. We start with a scoping call to confirm your JD account type (JD Worldwide vs domestic POP), catalog size, warehouse/fulfillment model, tax and currency setup, and which of the capabilities below you actually need. We then build against a staging copy of your ERPNext, run UAT with your real SKUs, and hand over installable source, a git repository, technical and user documentation, and a training session. Typical delivery is 2-4 weeks from confirmed scope, followed by a post-go-live support window.

What you get

Installable Frappe app source code (`erpnext_jd_connector`) for your ERPNext version (v15 or v16), pinned to your bench

Installation and configuration on your environment, including JD Open Platform app credentials, OAuth token setup, and scheduler wiring

Technical documentation: DocType reference, hooks.py events, whitelisted methods, sync cadence, and API mapping notes

End-user guide plus a live training session for your ops and accounting teams

UAT on a staging copy of your ERPNext with your real SKUs and a documented rollback plan

Post-go-live support window for bug fixes and sync issues (duration agreed at scoping)

Private git repository handover with full commit history and release tags

SKU / item mapping and initial listing-push run validated against your live JD catalog

Who this is for

Cross-border brand on JD Worldwide

An international brand selling into China via JD Worldwide that runs ERPNext as its ERP and needs JD orders, multi-currency invoicing, and stock to flow automatically instead of being rekeyed from the Seller Center by hand.

China-domestic POP seller

A domestic merchant on JD's POP marketplace who wants ERPNext to own inventory and pricing across warehouses, push listing/SKU changes to JD, and write JD Logistics tracking back on shipment.

Ecommerce operations manager

The ops lead responsible for keeping JD listings from overselling and orders processed on time, who needs a reliable scheduled sync, clear sync logs, and per-user permissions rather than a fragile spreadsheet workflow.

Finance / reconciliation lead

The accountant who reconciles JD settlement statements against actual payouts and fees each cycle and wants those matched to ERPNext orders with draft Payment/Journal Entries instead of manual line-by-line matching.

How ERPNext JD.com Seller Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
JD.com channel support	Purpose-built connector for JD Open Platform, Worldwide + domestic POP	Whatever you scope and build yourself	Usually generic or Shopify/Amazon-first; JD rarely covered	No JD channel at all
Order import to Sales Order	Scheduled, idempotent, mapped to customers/items/taxes	Possible but you own all edge cases	Basic import if JD supported; mapping often shallow	Manual re-keying from JD Seller Center
Inventory & price sync	doc_events + queued jobs push stock and Item Price to JD	Build and maintain the sync logic yourself	Sometimes one-way or fixed-interval only	CSV exports / manual updates
JD Logistics writeback	Delivery Note pushes waybill/tracking, marks JD order shipped	Extra scope you specify and test	Often missing or partial	Not available
Settlement reconciliation	Statement importer matches fees, drafts Payment/Journal Entries	Typically deprioritized, done in spreadsheets	Rarely included	Manual line-by-line matching
Source code & ownership	Full Frappe app source + git repo handover	You own it (and the maintenance burden)	Closed-source, license/subscription locked	N/A
Fit to your workflow	Scoped to your account type, catalog, tax, warehouses	Fully bespoke but slow and costly to reach	Configure within the vendor's fixed model	None
Support & updates	Post-go-live window + optional retainer for JD API changes	Your team or contractor on call	Vendor SLA, roadmap not yours to steer	Community forums only

Frequently Asked Questions about ERPNext JD.com Seller Connector

Is this a ready-made app I can download and install today?

No. The ERPNext JD.com Seller Connector is build-to-order — ECOSIRE scopes, builds, installs, and supports it for your specific JD account type, catalog, and ERPNext setup. There is no instant download. We deliver installable source and a git repository as part of the engagement.

How long does delivery take?

Typical delivery is 2-4 weeks from confirmed scope. The timeline depends on which capabilities you need (order import only vs. full listing push, logistics writeback, and settlement reconciliation), your JD account type, and catalog size. We confirm the exact schedule at the scoping call before any build starts.

Which Frappe / ERPNext versions are supported?

The app is built and tested against Frappe/ERPNext v15 and v16, installed on your own bench as a versioned Frappe app. If you run a different or customized version, we confirm compatibility during scoping and target your environment specifically.

What happens with support and updates after go-live?

Every engagement includes a post-go-live support window (duration agreed at scoping) for bug fixes and sync issues. Because you receive the full source and git repository, your team can maintain it independently, and ECOSIRE offers ongoing support or feature retainers for JD API changes and new requirements.

Do you handle both JD Worldwide (cross-border) and domestic POP selling?

Yes. The connector handles both cross-border JD Worldwide and China-domestic POP flows, including multi-currency Sales Orders and configurable tax templates. We tailor the order pipeline, customer mapping, and tax handling to whichever model (or both) you sell under.

How are my JD API credentials and tokens kept secure?

Your JD Open Platform app key, app secret, and OAuth tokens are stored encrypted in a `JD Connector Settings` single DocType. All JD API calls run through signed, server-side whitelisted methods — secrets and tokens never reach the browser. Access to sync operations is restricted via a dedicated role profile and DocType permissions.

Will order import create duplicates if the scheduler runs often?

No. Order import is idempotent — each JD order ID is stored and uniqueness-checked before a Sales Order is created, so repeated polls or re-syncs never produce duplicates. Failed calls surface in a `JD Sync Log` DocType with the payload and a re-run action for full visibility.