Configuration
The deviation thresholds that decide when counting staff are warned, the STP and PnP settings a count depends on, and a symptom-to-setting table.
The deviation thresholds that decide when counting staff are warned, the STP and PnP settings a count depends on, and a symptom-to-setting table.
How a stock count stays correct while customers keep buying — the count time, why an item is dated at its first counted location, the few windows where a deviation can arise, and how to keep them small.
Everything Stock Count reads — stock levels from STP, items and saved searches from PnP, stores from Business Unit Management, settings from CCC — and the API it is driven through.
How Stock Transaction Processing keeps a stock count's result when a movement that happened earlier arrives later
The two events Stock Count publishes — stock count completed and stock count changed — their payloads and attributes, and what a consumer must handle.
The life of a stock count — planning, preparing the item list, counting, submitting — and what happens to the stock when it is submitted.
Recurring stock-count definitions — scope, frequency and filters — how Stock Count turns them into dated counts every night, and how an item shared by several counts is placed.
Counting the stock in a store with the Hii Retail Inventory app, and publishing the counted quantities so the stock figure is corrected.
The JSON schema of stc.public.event.stock-count-completed.v1, the event Stock Count publishes when a count is submitted.
Which stock setups Stock Count supports — STP as master, an external system synchronizing into STP, or a lookup proxy — and what an external system must do when it owns the quantity.
Every Stock Count endpoint, grouped by what it is for — planning counts, counting, submitting, reading counts and reports, and recurring definitions — and how to call it safely.
Full, cycle, control and test counts, the purpose-built counts, how Stock Count decides which items a count lists, and what happens to items nobody counted.