Pinduoduo Store Assistant

Problem

Pinduoduo store operations often rely on open platform APIs for batch product listing, order synchronization, logistics tracking, and after-sales queries. Manually assembling system parameters, calculating signatures, and managing client_id, client_secret, and access_token is error-prone, especially when debugging signature failures, expired tokens, or permission issues. This skill organizes common POP API call patterns into a practical workflow.

How It Works

It focuses on the Pinduoduo open platform gateway https://gw-api.pinduoduo.com/api/router and covers these high-frequency capabilities:
- Products: pdd.goods.* for listing and product list operations.
- Orders: pdd.order.list.get for order queries.
- Logistics: pdd.logistics.* for tracking status.
- After-sales: pdd.refund.* for service or refund flows.
- Marketing: pdd.ddk.* for DDK or social promotion related calls.

The key steps are: confirm the target scenario; verify client_id, client_secret, and access_token; assemble param_json and system parameters; generate the uppercase MD5 signature; then call the gateway and diagnose failures by error code for expired token, signature mismatch, insufficient permission, or rate limits.

Boundaries

This skill only targets the user's own or authorized store data and is suitable for small and medium merchants configuring personal or enterprise apps. Credentials should stay local and must not be transmitted. Product information must be truthful and compliant, avoiding false advertising or restricted categories. It provides call scaffolding and troubleshooting guidance rather than holding credentials or invoking production APIs; final fields and limits follow the official Pinduoduo open platform documentation.