Cost depends on building a custom integration since JD Logistics doesn't have a pre-built NetSuite connector, though their Open Platform (api.jdwl.com) does provide documented APIs for waybill management, tracking, and export processes. You'll need ISV approval from JD to access their OAuth2-authenticated APIs, then develop custom SuiteScript to map their China-centric fields like bonded warehouse codes, IMEI numbers, and hazmat flags to NetSuite's data model.

Scope expands with multiple JD warehouses, cross-border shipments requiring customs declarations and incoterms, or if you're handling both small parcel exports and big bag consolidations through their different API endpoints. The integration complexity jumps compared to typical 3PLs due to UTF-8 encoding requirements, MD5 signature authentication, and JD's push/pull message architecture that requires careful error handling for their daily API call limits.

Yes. Cold chain shipments flow through the same fulfillment sync as standard orders. The difference is cost: JD charges cold chain surcharges per shipment, and those post to a separate expense account in NetSuite so you can track temperature-controlled logistics costs independently.

When a customer returns a product to a JD warehouse, the return receipt from JD triggers a return authorization in NetSuite. If JD restocks the item, inventory adjusts accordingly. If they dispose of it, a write-off posts. Refund processing follows your existing NetSuite approval workflow.

It can. JD's cross-border logistics service handles customs declarations, bonded warehouse intake, and final-mile delivery within China. The integration logs each milestone in NetSuite and attaches customs reference numbers to the transaction records. Your compliance team gets visibility without logging into JD's portal separately.

Expect 8 to 10 weeks. The first two weeks cover scoping: mapping JD warehouse locations to NetSuite inventory sites, defining which fulfillment events trigger record updates, and setting up cost posting rules for JD's various fee types. Build and testing runs another six to eight weeks, including a parallel period where automated syncs are validated against your manual process.

Each JD warehouse maps to an inventory location in NetSuite. Stock levels sync on a configurable schedule, typically every few hours. The sync covers available quantity, reserved quantity, and damaged or held stock. If you're running 5 JD warehouses, NetSuite shows stock at each location individually and rolls up to a total.

JD bills in RMB. The integration creates vendor bills in RMB and NetSuite handles the currency conversion at the transaction date rate. FX gains and losses post automatically when bills are paid, same as any other multi-currency vendor in your system.

No. Some companies use JD Logistics as a third-party fulfillment provider without selling on JD.com directly. They use JD's warehouse network for domestic China distribution while selling through their own channels. The integration works either way since it connects to JD's logistics systems, not the marketplace.