## Overview
gy.erp.stock.get reads stock inside GuanYi C-ERP by warehouse and item/SKU, returning on-hand and available quantities. When GuanYi acts as an order hub with the stock ledger in the ERP (Kingdee/Yonyou), this endpoint mainly reconciles GuanYi-side allocations and in-flight quantities; when GuanYi is the stock ledger, it is the extraction point for omnichannel stock distribution.
### Request essentials
1. System parameters and signing follow the call convention; common business parameters: page_no/page_size, warehouse_code, and item_code/sku_code for pinpoint queries.
2. Rows carry warehouse_code, item_code, sku_code, qty (on hand) and available_qty; availability means on-hand minus order allocations.
3. Stock is a snapshot — schedule full pulls, diff in the iPaaS, and push only changed SKUs to sales channels to bound write volume.
4. Multi-warehouse setups should pull per warehouse_code to avoid full-scan timeouts.
### Typical pipeline
GuanYi stock → Qeasy snapshot diff → sellable quantity per shop quota → write-back to Jushuitan/WDT/marketplaces; drift beyond threshold raises a stock-calibration alert to stop silent overselling.
### Allocations and returns in flight
GuanYi allocations come from captured-but-unshipped orders and spike during promotions, so publish available-minus-buffer to sales channels, with the buffer sized per category velocity. Returned goods under inspection stay out of available quantity until QC releases them — mind this lag when reconciling stock, and never count uninspected returns as sellable.