JD.com + NetSuite Integration

Without a NetSuite connection, your finance team picks apart RMB settlements, commission splits, and promo deductions in spreadsheets every morning.

Oracle ERP Expertise CertifiedTransparent PricingPost Go-Live Support

JD.com logo

The Problem

Every JD.com sale triggers a net settlement. Getting those numbers into NetSuite fast enough to act on is hard.

Whether you ship direct or use JD Fulfillment, orders flow through JD's systems first. Settlements come bundled with deductions your team has to unpack before posting to NetSuite. Most sellers rely on someone who really knows the settlement reports, plus CSV exports. That holds until order volumes spike during 618 or Singles' Day and reconciliation backs up for weeks.

When a JD.com + NetSuite Integration Becomes the Better Fit

ORDERS EXPORTED AS CSV EVERY MORNING

Someone downloads yesterday's orders from JD's merchant backend, reformats the columns, and imports them into NetSuite. Miss a promotion weekend and you're buried.

JD.COM ORDERS FLOW INTO NETSUITE WITHOUT CSV EXPORTS

Sales orders from JD.com create corresponding records in NetSuite with customer details, line items, and RMB pricing. No manual exports, no reformatting, no Monday morning catch-up.

SETTLEMENT RECONCILIATION TAKES DAYS

JD's settlement reports arrive as a lump sum minus commissions and fees. Finance spends days each cycle matching settlements to orders and tracking down the difference.

SETTLEMENTS BROKEN DOWN AND MATCHED TO ORDERS

Each settlement is split into gross revenue, platform commission, logistics fees, and promotional deductions. Every line maps back to the originating sales orders in NetSuite.

INVENTORY ON JD.COM UPDATED HOURS TOO LATE

Stock levels are updated once or twice a day via manual upload. During high-volume periods, that lag means overselling and penalty fees.

INVENTORY PUSHED TO JD.COM FROM NETSUITE IN NEAR REAL TIME

Available-to-promise quantities in NetSuite push to JD.com throughout the day. When stock is allocated or received, JD listings reflect the change within minutes.

RETURNS AND REFUNDS PROCESSED WEEKS LATE

Refund approvals happen on JD's platform, but the credit memos and inventory adjustments in NetSuite are done by hand, often weeks after the fact.

RETURNS AND REFUNDS SYNC BACK TO NETSUITE

Approved returns on JD.com generate credit memos and inventory adjustment records in NetSuite. Refund amounts account for the original commission so your revenue reversal is accurate.

PRODUCT CATALOG MAINTAINED IN TWO PLACES

New SKUs get created in NetSuite, then someone manually builds the JD.com listing with translated descriptions, RMB pricing, and category mappings. Every update has to happen twice.

CATALOG AND PRICING MANAGED FROM NETSUITE

Product data, RMB pricing, and availability push from NetSuite to JD.com. Price changes during promotions can be staged in NetSuite and published to JD on schedule.

JD.com + NetSuite Integration

What We'd Confirm Before Scoping

JD.com's fulfillment models and settlement mechanics shape the integration design.

CHANNEL AND FULFILLMENT MODEL

Whether you sell via JD domestic, JD Worldwide (cross-border), or both, and if you use JD's warehousing (FBJ) or self-fulfill.

FEES AND SETTLEMENT

How JD's commission, platform fees, and promo deductions get recorded in NetSuite, and if settlement reports reconcile against invoices.

CROSS-BORDER TAX AND ENTITIES

How customs duties, cross-border taxes, and bonded warehouse costs are handled, and which NetSuite subsidiary and currency JD maps to.

RETURNS AND DISPUTES

How returns, refund disputes, and JD-mediated after-sales claims are managed, and whether those flow into NetSuite automatically.

Crash illustration

We can then map the integration to JD's fulfillment model, fee structure, and settlement cycles.

Mattia

ONE Pacific built a custom wholesale portal powered by Workato, allowing distributors to enter order details on their own without involving our staff.

Mattia Lolli

Chief Operating Officer

D1 Milano

JD.COM + NETSUITE

How the Integration Works

JD.com orders, settlements, returns, and product catalog data sync with NetSuite through API-based event ingestion, structured settlement parsing, and scheduled inventory pushback.

Order Ingestion via JD Merchant API
JD.com orders pull through the merchant API and write as NetSuite sales orders. Customer, line items, and RMB pricing map through a field layer.
Settlement Parsing and Order Matching
JD settlement files parse into gross revenue, commission, fees, and deductions, then map to originating NetSuite orders for per-order margin tracking.
Near-Real-Time Inventory Pushback
NetSuite available-to-promise quantities push to JD.com throughout the day. Allocation and receipt events trigger updates, not a fixed batch schedule.
Catalog and Pricing Management
Product data, RMB pricing, and availability push from NetSuite to JD.com. Promotional pricing staged in NetSuite can be scheduled for JD publication.
Return and Refund Record Creation
Approved JD.com returns generate credit memo and inventory adjustment records in NetSuite. Refunds are net of platform commission before posting.

Most JD.com + NetSuite integrations scope in two weeks and go live within 6 to 8 weeks. Let's talk about yours.

More E-Commerce Integrations

Showing 6 of 34 E-Commerce Integrations

JD.com + NetSuite Integration

FAQ's

Cost for a JD.com integration depends heavily on custom development since there's no pre-built NetSuite connector—you'll need to work with JD's Open Platform APIs for orders, logistics, and tracking.

The main drivers are handling JD's 2-30% commission structure by product category, syncing with JD Logistics' multi-warehouse network, and managing Chinese regulatory requirements like PIPL compliance and cross-border documentation with HS codes. If you're processing high volumes through Alipay or WeChat Pay, you'll also need to account for payment reconciliation complexity and potential API throttling on JD's platform.

Available-to-promise quantities push from NetSuite to JD.com multiple times per day. The exact frequency depends on your volume and how sensitive you are to overselling. During major events like 618 or Singles' Day, sync intervals can be tightened to keep up with rapid stock movement.

Yes. The self-operated model (where JD buys inventory from you and resells it) and the marketplace model (where you sell directly through JD's platform) have different order flows, settlement structures, and fulfillment responsibilities. The integration handles both and maps each to the appropriate NetSuite workflow.

Expect 6 to 8 weeks from kickoff to go-live. The first two weeks cover scoping: mapping JD.com's order structure, settlement format, and commission tiers to your NetSuite configuration. Build and testing runs four to six weeks, including a parallel period where automated orders are validated against your existing manual process.

It can. JD.com's cross-border channel (JD Worldwide) lets brands outside mainland China sell to Chinese consumers. The integration handles the additional complexity: bonded warehouse inventory, cross-border tax calculations, and settlement in RMB that needs to convert back to your home currency in NetSuite.

JD.com settles on a cycle, paying you gross revenue minus platform commissions, logistics fees, and promotional cost shares. The integration breaks each settlement into its components and matches them back to the originating sales orders in NetSuite. Commission and fee amounts post as separate line items so you can report on true margin per order, not just the net deposit.

Hero background

Ready to connect JD.com and NetSuite?

Our engineers will review your setup, map your systems, and, if it makes sense to move forward, provide a clearly scoped proposal. No pressure.