## Overview
weimob_shop/order/list/search (v2.0) pages through Weimob mall orders by condition, returning orderNo, status, amounts, buyer info and item summaries; its companion weimob_shop/order/detail/get fetches the full detail per order number. The API capability must be granted in the Weimob Cloud console first.
### Request essentials
1. POST with Content-Type: application/json; the access_token goes on the URL as the accesstoken query parameter.
2. Body: pageNum/pageSize for paging; filters such as createStartTime/createEndTime (order-time window), orderNo (pinpoint) and statuses (state array) as needed.
3. When code.errcode is "0", data.pageList holds the orders and data.totalCount the total; an order number feeds detail/get for line-level data (items, paid, discounts, freight).
4. Incremental sync advances the creation-time window with a few minutes of overlap; slice by hour during promotion peaks so a window never exceeds the paging ceiling.
### Reconciliation use
Match Weimob receipts, freight and discount allocations against WeChat/Alipay statements and ERP receivables three-way; Qeasy keys on orderNo and auto-classifies divergences (amount gap, missing order, status gap).
### Amount semantics
Weimob splits amounts into goods total, discounts, freight and paid; discounts may combine platform and shop coupons, and line-level allocation follows the API documentation. Agree with finance upfront whether reconciliation uses the paid amount or goods-total-minus-shop-discount — otherwise a systematic gap against payment statements will be misread as a reconciliation incident.