## Overview
taobao.qimen.stock.query is the multi-condition stock query in the Qimen warehousing standard. It lets the ERP side actively query item quantities inside a WMS/cloud warehouse for reconciliation-style stock calibration. When Jushuitan implements this interface as the Qimen peer, callers still route to merchant data via target_app_key and customer_id.
### Request essentials
1. Use the unified Qimen gateway with the same common parameters and signing; format can be json or xml.
2. Query conditions (in the business payload/extend params): ownerCode, warehouseCode, itemCode, itemId and pageIndex/pageSize; batch condition queries over an item list are supported.
3. The items array typically carries itemCode, quantity (good stock), lockQuantity and inventoryType (ZP good, CC defective, ...); only good stock feeds the sellable quantity.
4. Qimen standard fields are camelCase while Jushuitan's own open API uses snake_case — align field mappings carefully.
### Use cases
- Hourly job: pull good-stock from the cloud warehouse, reconcile against the local ledger and alert beyond a threshold.
- Pre-promotion calibration: batch-query by itemCode list and correct per-warehouse sellable numbers.
- Segregate defective (CC) stock so it never leaks into sellable figures.
### Choosing between the two stock APIs
The same merchant can be queried through Jushuitan's native inventory/query or this Qimen standard endpoint. The native API shares Jushuitan's signing system and ERP-shaped fields; the Qimen one is an industry standard that lets a single codebase serve many WMS vendors. Qeasy defaults to the native API and keeps Qimen for Taobao-exclusive data and multi-WMS adaptation.