Skip to main content

Data sources

Stock Count owns only the counts themselves. Everything it needs to plan a count, and to judge the result, comes from other Hii Retail services. None of it needs configuring per integration: if the source service is in use for the tenant, Stock Count receives its data.

 source                               what Stock Count takes from it
─────────────────────────────────    ──────────────────────────────────────────────────────────
Stock Transaction Processing (STP)    which items hold stock or have moved, the expected quantity,
  stock level updates                 and the value used for the cost of a deviation

Product, Price and Promotion (PnP)    the store's assortment, item names and identifiers,
  items, saved searches,              the saved searches that scope a cycle count,
  item categories                     the categories a count is grouped by, purchase prices

Business Unit Management (BUM)        which stores exist, which are active physical stores,
  business units, groups              and which groups they belong to — for recurring counts

Customer Controlled Configuration     deviation thresholds, suspicious-item counts
  (CCC)

The Stock Count API                   counts, counted quantities, submissions — from the
                                      Hii Retail Inventory app and from integrations

Stock levels from STP​

Stock Count subscribes to the stock level updates that Stock Transaction Processing publishes, and keeps its own copy per store and item. Only sellable stock (SalesStock) is kept; reserved, in transit, on order and returned stock play no part in a count.

From that copy it knows, for every item:

WhatUsed for
the current quantitythe expected quantity shown in the deviation review, and whether the item holds stock at all
when the quantity last movedwhether the item has moved since it was last counted
the average costthe value of a deviation, and the expected and counted values in reports

For suspicious-item counts Stock Count also reads STP's suspicious items report — slowed sales and negative stock — for the stores where those counts are switched on.

It also records, per item, when the item was last counted and what was found, each time a count is submitted. Together with the movement time, that is what the item-selection rules and the NOT_COUNTED_SINCE filter work from. See Types of count.

⚠ A negative stock figure is shown as an expected quantity of 0. The sign is kept for selection — negative stock is always worth counting, and the NEGATIVE_STOCK filter finds it — but the expected quantity and the expected value never go below zero.

⚠ The copy is updated by events, so it can trail STP by moments. An item sold a second ago may not yet show the new expected quantity. This affects only what is displayed during counting: the stock correction itself is calculated by STP, from its own ledger, when the count is submitted.

Items and categories from PnP​

Product, Price and Promotion is the master for items across Hii Retail.

WhatWhere it comes from in PnPUsed for
The store's assortmentthe items available in the business unitthe candidates for a full count
Saved searches and search queriesa saved search selection, or a PnP search querythe candidates for a cycle count
Item names, identifiers and categoriesthe itemwhat staff see, and how a count is grouped
Item categoriesthe published item categoriesthe category names a count is grouped by
Purchase pricethe item's current purchase pricethe value of an item when STP has no cost for it yet

A saved search is resolved when the list is built — at creation, and again in every nightly refresh while the count is open. An item that starts to match the search while the count is open is added to it.

Stores and groups from Business Unit Management​

Stock Count keeps a copy of the tenant's business units and business-unit groups. It is used by recurring counts: a definition scoped to the tenant or to a group is resolved to the stores under it when each occurrence is generated, and only active physical stores qualify — warehouses and closed stores do not receive counts.

Settings from CCC​

The deviation thresholds and the suspicious-item counts are Customer Controlled Configuration kinds. See Configuration.

The Stock Count API​

Counts and counted quantities enter through the Stock Count API — from the Hii Retail Inventory app, or from an integration that plans counts centrally. There is no other way in: Stock Count does not import counts from files or from other services' events.