Query Goods List (weimob_shop/goods/getList)

## Overview weimob_shop/goods/getList (v2.0) pages through the goods of a given store, returning goodsId, title, price, stock and sale status; companions include weimob_shop/goods/get (full on-sale detail by goodsId) and weimob_shop/goods/getListById (batch by IDs). ### Request essentials 1. POST with Content-Type: application/json; accesstoken rides in the URL query. 2. Body: pageNum/pageSize, plus filters by store (vid/organization), goods status or keyword per the docs. 3. data.pageList carries the goods; goodsId is the input for detail and stock/price maintenance APIs, and data.totalCount drives pagination. 4. For product master integration, map Weimob goods to ERP material codes (best carried in the merchant-code field) — otherwise order lines cannot auto-match materials. ### Typical pipeline ERP item master → Qeasy mapping/cleansing → Weimob create/update; a daily pull compares price, stock and on-shelf status and emits an alignment report. When Weimob serves as the private-domain storefront, stock arrives from ERP/Jushuitan sellable pushes, and this list API verifies the pushes actually took effect. ### Multi-store semantics Weimob supports multi-store (node) catalogs where goods may be maintained at headquarters and per store. Confirm the vid scope before querying: the HQ view and store views return different goods sets, and stock is store-isolated. Draw the organization tree first, then decide the sync scope and stock-distribution policy per node, instead of accidentally rolling HQ goods out to every store.