## Overview
gy.erp.trade.get pages through orders inside GuanYi C-ERP, returning headers, item lines, amounts and statuses. GuanYi also ships gy.erp.trade.history.get (archived orders) and gy.erp.trade.detail.get (per-order detail) — the three together cover full order extraction.
### Request essentials
1. Build appkey/sessionkey/method/sign per the call convention and submit business parameters in the same JSON body.
2. Pagination: page_no (1-based) and page_size; the total field gives the full count under current conditions for paging.
3. Common filters: start_date/end_date (confirm whether the window means created or modified), shop_code, order_state and code for pinpoint lookup.
4. Line items live in the order's details array: item_code, sku_code, qty, price, amount.
### Integration scenarios
- Orders → ERP sales orders: GuanYi as the order hub pushes into Kingdee/Yonyou sales orders and receivables.
- Reconciliation: three-way match of paid amount, freight and discount against marketplace statements.
- After-sales: returns flow through gy.erp.trade.return.get separately and join to the original order number.
### Idempotency
Qeasy keys on order code + line sequence, so re-pulls and replays never create duplicate downstream documents.
### Backfilling archived orders
Older orders are archived and invisible to gy.erp.trade.get — use gy.erp.trade.history.get for that range. On a first-time full backfill, run the history API before switching to incremental so the timeline has no gaps. The archived API mirrors the online field structure but responds more slowly, so keep backfill concurrency low and checkpoint progress for resumability.