API
Every Goods Received endpoint grouped by the question it answers, and which endpoints an external integration should use
Every Goods Received endpoint grouped by the question it answers, and which endpoints an external integration should use
The register of the suppliers and manufacturers a tenant trades with: one record per party, a set of roles, pushed from the ERP and published as events.
What has to be set up before a store can receive goods — reason codes, store identity and permissions — and how to diagnose it when receiving does not work
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.
Tenant, business unit and item settings that control Hii Retail stock handling
How Stock Transaction Processing determines the cost of a stock movement — weighted average cost, batch selection with FIFO, FEFO and LIFO, and the purchase price prerequisite
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.
Every way a delivery reaches Goods Received, and the Hii Retail services it depends on to resolve items, stores and reason codes
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.
Where Stock Transaction Processing gets its data — PosLog sales from the POS, events from other Hii Retail services, item master data from PnP, and the Input API
How Stock Transaction Processing keeps a stock count's result when a movement that happened earlier arrives later
The states a delivery and its lines move through, the three ways to approve one, how corrections work, and why every write is asynchronous
Which devices run the Hii Retail Inventory app, how staff sign in and choose a store, the Home screen, and what access a user needs.
The event Goods Received publishes when a delivery is approved, and how to consume it correctly
Subscribing to Hii Retail stock events as an external system — stock level updates, processed transactions, delivery semantics and the published schemas
Overview of Hii Retail Goods Received — how deliveries reach a store, how staff approve them, and what is published when they do
The JSON schema of the event Goods Received publishes when a delivery is approved
The Hii Retail profile of the GS1 despatch advice — which elements are required, which are ignored, and how each maps to a delivery
How an external ERP, OMS or WMS sends a delivery note into Hii Retail as a GS1 despatch advice, and what the import accepts
A complete, known-good GS1 despatch advice document for Goods Received, with each section explained
The life of a stock count — planning, preparing the item list, counting, submitting — and what happens to the stock when it is submitted.
The Hii Retail Inventory app: the handheld app store staff use to receive deliveries, move stock between stores, pick Click and Collect orders, and count and correct stock, on iOS and Android.
The modules of the Hii Retail Inventory app, with the highlights of each: Goods receivable, Store transfers, Click & Collect, Store Layout, Stock counting, Stock correction, Stock events and Control tasks.
Why one business operation produces several stock transactions, with the stock transfer and store transfer flows step by step
The push notifications the Hii Retail Inventory app receives on iOS and Android, who gets them, how they resolve themselves when the work is done, and the Control tasks list.
The business operations Stock Transaction Processing supports, the operationType each publishes, and which stock types it moves
Read seller-confirmed quantities and expected delivery dates for items you have on order — served from your own system.
Expected, approved, adjusted and delta quantities — the arithmetic, the sign convention, and how reason codes explain a difference
Reading stock from Hii Retail — quantity lookups, batch lookups, transaction search and the suspicious items report
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.
How the Hii Retail Inventory app scans with a camera or a Zebra trigger, reads scale labels for weighed items, and decides whether a quantity takes decimals.
What a transfer does to stock at each step, and how the receiving store takes the goods in.
Recording deliberate stock adjustments — damage, theft, expiry, write-offs — and publishing them as events for whichever system owns the stock figure.
Counting the stock in a store with the Hii Retail Inventory app, and publishing the counted quantities so the stock figure is corrected.
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.
What Stock Transaction Processing calculates, how transactions flow through it, and what it publishes
Overview of Hii Retail Stock Transaction Processing — what it calculates, where its data comes from, and how to consume its events
Moving stock between two stores: how a transfer is raised, picked, shipped and received, and what an integrator can subscribe to.
How Stock Transaction Processing handles bundles and packages — selling one item that consists of several others
Running Stock Transaction Processing alongside an external system that owns the stock — full master, synchronized, or a combination
Stock types, batches, quantity signs and precision — how to read a stock quantity from Stock Transaction Processing correctly
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.
How the Hii Retail Inventory app keeps store staff working through dead spots and unstable networks, what the status strip and Pending sync show, and what it means for systems consuming the events.