datawebotPinduoduo listings, purchase modes and seller data
Map Pinduoduo merchant-entered listing fields, team and 免拼 terms, market-specific price context, seller tools, and dated access and privacy boundaries.
Pinduoduo sits within PDD Holdings; Temu is a separate platform
Pinduoduo (拼多多) is the marketplace service described by the Pinduoduo User Service Agreement. That agreement names Shanghai Xunmeng Information Technology Co., Ltd. and its affiliates as the operator (§1.2). PDD Holdings’ 2025 Form 20-F defines the Pinduoduo and Temu platforms separately and reports different geographic coverage.
Scroll to compare →
| Name in the evidence | What the source says | Record boundary |
|---|---|---|
| Pinduoduo (拼多多) | The agreement covers its marketplace services across listed web, app, WeChat and other service carriers (§1.1). | Identify the source as Pinduoduo; a carrier or market context belongs with each observation. |
| Shanghai Xunmeng Information Technology Co., Ltd. and affiliates | Named as the operator in the User Service Agreement (§1.2). | Use this legal attribution when describing the operator; keep it separate from seller identity. |
| PDD Holdings Inc. | The 2025 Form 20-F describes PDD Holdings and the two platform businesses in its corporate reporting. | Parent-company reporting is not a Pinduoduo item listing or merchant record. |
| Temu | A separately named platform with different geographic coverage; the filing says both platforms primarily serve merchants in China. | Do not join product, offer, market or identifier records merely because both platforms belong to PDD Holdings. |
A Pinduoduo price needs its purchase mode, market and time
PDD Holdings describes Pinduoduo’s team-purchase model in its 2025 filing. The User Service Agreement V4.2 says an order is received when submitted; the purchase contract is formed after payment and takes effect after a successful 拼单 or 免拼 purchase, or another group condition shown on the item page (§4.3). Store what the page labels and keep that display separate from a completed transaction.
Scroll to compare →
| Observation | Useful context to retain | What it does not establish |
|---|---|---|
| 拼单 (team purchase) | The exact page label, displayed amount, selected option, currency or region, and observation time. | A displayed team amount is not evidence that a team completed or an order was paid. |
| 免拼 (purchase without completing a team) | Record this mode only when the observed page uses the label; keep its amount tied to that mode. | The label does not establish a separate universal one-person price for every listing. |
| Other group or activity condition | Use the condition and any limits shown on that item or activity page; the agreement says limits are page-specific (§4.7). | Do not treat an activity rule or amount as timeless or applicable to every option. |
| Displayed price observation | A point-in-time amount plus source, selected option, displayed market/currency, and timestamp. | Do not infer seller revenue, order volume, or sale completion from a product-page display. |
Merchant-authored item details and URL locators need provenance
Unless a rule says otherwise, Pinduoduo’s agreement says merchants edit and upload item names, prices, quantities, models, specifications, dimensions, shipping commitments, quality or service promises, defects and usage restrictions (§4.5). It also says Pinduoduo cannot comprehensively pre-review every item for truth, legality, accuracy, timeliness or effectiveness (§6.1). Keep those fields attributed to the merchant and the observed page.
Scroll to compare →
| Field group | Source-specific treatment | Evidence limit |
|---|---|---|
| Name, model, specification and dimensions | Keep the merchant’s wording with the exact selected option and item context. | Seller-entered description is not independent platform verification. |
| Price and quantity | Attach the purchase mode, market or currency, selected option and observation time when visible. | A page display does not establish checkout, stock at a later time, or completed orders. |
| Shipping, service, defect and usage statements | Preserve whether text is a merchant commitment, stated defect or use restriction. | A promise is not an observed delivery or a platform guarantee. |
| Observed URL keys | Selected official mobile URL examples reviewed on 2026-10-07 contained names such as goods_id, sku_id and region. | These are observed locators from particular URLs, not a published universal ID schema or API response contract. |
The Open Platform describes merchant software workflows
The Pinduoduo Open Platform describes e-commerce software providers, merchant service providers, and merchants with development capability. Its public overview names seller software for product, transaction, inventory and logistics work, and shows developer verification and app or service creation in its onboarding flow. The portal loaded on 2026-10-07; its JavaScript-rendered overview and API-docs entry do not establish a public catalog feed or endpoint fields.
Scroll to compare →
| Surface | Publicly described purpose | Scope that remains unverified |
|---|---|---|
| Software and service providers | Tools or services for merchants’ e-commerce operations, including business software and store services. | The overview does not grant a particular provider access to another seller’s information. |
| Merchant-built or custom systems | The portal describes merchant-developed or custom software for product, transaction and logistics management. | No buyer-facing listing API, anonymous access scope or specific response fields were verified. |
| Developer and app workflow | The portal lists developer verification and app or service creation, with an API documentation area. | The reviewed public overview does not confirm the requirements or methods for a specific app or data set. |
| Buyer-facing item page | A marketplace view of an item and its current page conditions. | It is a different surface and role from a merchant’s software integration. |
Dated terms, privacy and robots observations set evidence boundaries
The Pinduoduo User Service Agreement V4.2 was announced 2026-02-08 and took effect 2026-02-16. Its §10.1 addresses specified unauthorized copying, republication, derivative services and robot or spider retrieval. This page reports the reviewed source wording and crawler files; it does not draw a legal conclusion. Rules and policy versions can change.
Scroll to compare →
| Evidence reviewed | Dated observation | How to read it |
|---|---|---|
| User Service Agreement V4.2 | Announced 2026-02-08; effective 2026-02-16. Sections 10.1.2 and 10.1.6 address specified copying, republication, derivative uses and unauthorized robot or spider retrieval. | Read the current terms for the exact service and activity; this summary is not a legal determination. |
| Privacy Policy V4.1.1 | The official indexed PDF identifies an update date of 2025-06-30 and scope including website, client and mini-program services. | Keep account, device, contact, payment, delivery, order, review and sharing or friend data outside this public source reference. |
| pinduoduo.com, www.pinduoduo.com, www.yangkeduo.com | On 2026-10-07 each robots.txt returned HTTP 200 with only a Baiduspider-image group disallowing `/`; no wildcard group appeared in the returned file. | A missing wildcard group does not grant permission or establish a reuse right. |
| yangkeduo.com and mobile.yangkeduo.com | On 2026-10-07 each file had `User-agent: *` / `Disallow: /`. Named Googlebot, Googlebot-Image and AdsBot-Google groups also disallowed `/` and allowed `/poros/h5`; HuaweiAdsSpider groups disallowed `/` and allowed `/cmlp_oppo_adx_land.html`. | Keep the user-agent and path rules tied to each host; crawler directives are not authorization. |
| open.yangkeduo.com | On 2026-10-07 the robots.txt URL returned HTTP 200 HTML for the application shell, not plain robots directives. | Do not infer a robots policy, API, feed or data-access permission from the HTML response. |
Content reviewed 2026-10-07.