datawebotJD.com product data: price context and access terms
A source-specific JD.com guide to reading public product pages as dated observations, price and destination context, and the user agreement's access and reuse terms.
Updated · datawebot team
Read a JD.com product page as a dated observation
A public JD.com product page is a shopper-facing view of a listing and its current offer context. JD says visible product prices can be invitations to offer, may be wrong or unavailable, and vary with buyer and destination context. Keep the source URL, selected SKU, destination, price conditions and observation time with each record, and recheck before acting on a quote. Visibility on a public page does not grant automated access or permission to reuse its content.
Confirm JD.com access and reuse terms before a data workflow
JD's current User Service Agreement took effect on January 20, 2026. Section 6(4) restricts copying or changing site/runtime interaction data through non-JD-authorized tools absent a legal exception or written permission; section 6(6) addresses third-party software used to log in to or use the service. Section 9(6) addresses unlawful copying, reuse and crawling, subject to legal exceptions or special written consent. Apply the clauses to the specific method and dataset.
Scroll to compare →
| Before using JD.com data | Why the context matters | What to verify or retain |
|---|---|---|
| Public-page collection or reuse | The user agreement has separate rules for site interaction and content reuse; a public URL is not an authorization grant. | Review the current agreement and applicable legal basis or written permission for the planned method and use. |
| Price and stock display | JD says visible product prices can be invitations to offer, may be wrong or unavailable, and vary with buyer and destination context. | Keep the source, selected SKU, destination, price conditions and observation time; recheck before acting on a quote. |
| Account and order information | Account, delivery and order records can contain personal information and are distinct from public product fields. | Exclude them from public-product comparisons unless a specific authorized purpose and safeguards apply. |
Content reviewed 2026-10-18.