## Overview
/erp/opentrade/list/trades queries sales orders inside Hupun ERP (the open-trade domain), returning headers, item lines, amounts and statuses. As an omnichannel order hub aggregating 30+ marketplaces, Hupun exposes those orders in one unified structure through this API — ideal for syncing into Kingdee/Yonyou as sales orders and receivables, or into a reconciliation store.
### Request essentials
1. Build _app/_t/_sign per the call convention; submit business parameters as form fields.
2. Paginate with page and limit; bill_code pins the query to one order.
3. Time/status filters follow the official docs; for incremental sync advance a modify-time window with a few minutes of overlap.
4. The data array carries internal bill number, platform order number, shop, status, paid amount and item lines (SKU, quantity, price); fulfillment tracking pairs with the order-flow API (/erp/opentrade/trade/commit) to read the state machine.
### Integration notes
- After Hupun order splitting, one platform number may map to several internal bills — key idempotency on the internal bill number and keep the platform number as the join key.
- Promotion peaks demand window slicing + retry + idempotent writes; the Qeasy blueprint ships all three by default.
### Fulfillment and after-sales linkage
Later fulfillment events (shipment, receipt) flow back into the order status, while after-sales documents (refunds and returns) live in a separate domain and must be pulled through their own APIs, then joined on the original order number. Run matching only after forward orders, after-sales and platform settlement data are all present — otherwise the engine flags missing-after-sales as amount discrepancies and floods the work queue.