Stock Count
Stock Count is how a store finds out what is really on its shelves. Staff walk the store with a handset, count what they find, and submit the count. The counted quantities are then published, and the system that owns the stock figure corrects it.
A count asserts what the quantity is, not how it changed. That makes it different from every other stock movement in Hii Retail — a sale, a delivery or a stock correction all say "this many more" or "this many fewer". Because a count is an absolute statement about a moment in time, when each item was counted matters as much as how many were found. See Counting while the store is open.
Stock Count needs to know the stock
Stock Count does not just record numbers. It decides which items a count should list, shows each item's expected quantity, and warns about deviations — and it gets all of that from Stock Transaction Processing (STP), Hii Retail's stock ledger.
A store's assortment may hold 100 000 items while only 10 000 are actually in stock. A count should ask staff to count the 10 000, not walk the 100 000. That is only possible if Stock Count knows which items have stock — so the stock has to be held in STP, either because STP is the stock master or because an external system synchronizes its stock into STP. Without it, Stock Count can only record counts that another system plans. See Stock ownership.
Who does the counting
The work happens in the store, on a handset, done by staff. A count lists the items to find, grouped by item category. Staff scan an item, enter or scan the quantity at each place they find it, mark categories as done, review the deviations, and submit.
Extenda supplies the client — the Hii Retail Inventory app — so a customer does not have to build one. In the app, store staff can:
- create a full count of the store, and carry out full counts and cycle counts created elsewhere — by head office through the API, or generated by a recurring definition;
- do a quick count of a single item at any time, which is submitted at once;
- count an item in one go, in several numbered locations, or by scanning each unit — including items sold by weight.
The counter does not see the expected quantity while counting. It appears in the deviation review before a category is marked as done and before the count is submitted.
The app does ordinary REST, so a customer who wants to plan counts from their own system — a head-office tool, an ERP, a workforce planner — can use the same endpoints:
| Action | Endpoint |
|---|---|
| Plan a count for a store | POST /business-units/{businessUnitId}/stock-counts |
| Plan counts that repeat across stores | POST /recurring-stock-counts |
| Register a counted quantity | PUT /business-units/{businessUnitId}/stock-counts/{stockCountId}/lines |
| Count one item and submit at once | POST /business-units/{businessUnitId}/stock-counts:quick-count |
| Submit a count | POST /business-units/{businessUnitId}/stock-counts/{stockCountId}:submit |
See The API for all of them.
🛑 You plan counts and subscribe to the results — you do not drive the person holding the handset. An integration can create counts, decide which items they cover and when they are due, and consume what comes back. It does not tell staff which shelf to go to next, and there is no approval step between a submitted count and the stock correction that follows.
Where to start
| If you want to… | Read |
|---|---|
| understand the life of a count, from planning to the stock correction | How a count works |
| know whether Stock Count fits your stock setup | Stock ownership |
| see where Stock Count gets its data | Data sources |
| choose between full, cycle, control and test counts, and see how the item list is built | Types of count |
| understand how a count stays correct while customers keep buying | Counting while the store is open |
| plan counts that repeat, across many stores | Recurring counts |
| set deviation warnings | Configuration |
| plan counts or read results from your own system | The API |
| receive completed counts in your own system | Events |
Related services
- Stock Transaction Processing keeps the stock ledger. It tells Stock Count what is in stock, and it applies every submitted count.
- Stock Corrections is the other way to change a number deliberately. A count asserts what the quantity is; a correction states how much it changed by. Use a count when you have looked at the shelf, a correction when you know what left it and why.
- Product, Price and Promotion (PnP) is the master for items. It decides which items belong to a store's assortment and supplies the saved searches that scope a cycle count.