Inventory changes,recorded as they happen.
Receipts, picks, transfers, adjustments and counts are each recorded with who made the change, what changed, when, on which device and from which action. Events are kept as an append-only history you can filter by SKU, user, location or date, so a count discrepancy can be traced to the events behind it.
A stock total alone doesn't explain a discrepancy.
When on-hand quantity doesn't match the shelf, the useful question is how it got there. The current total can't answer that. A per-event history shows each change that led to the number, who made it and where it came from, so your team can investigate from records rather than recollection.
Unexplained shrink
A count comes up 14 units short. Without a per-event record, the gap is written off as shrink with no cause attached. With one, you can review the picks, adjustments and transfers that touched the item and see where the difference appeared.
Chain-of-custody requests
A customer, a regulator or your finance team asks who handled a lot and when. The log answers from recorded events: the users, locations and timestamps for that lot, which you can export for their review.
Changes nobody can place
When a quantity moves unexpectedly, the log shows the event that moved it, the user who made it and the device it came from, recorded when it happened. The discussion starts from what was recorded rather than from who was nearby.
Follow a count back to the event that changed it.
Choose a SKU and a date range, and Klovio lists the recorded events in order, with the quantity change and the running balance after each one. When on-hand quantity stops matching the shelf, you can see which event moved the balance and who recorded it.
- See the running balance after each event, not only the latest total
- Filter by SKU, user, location, device or source action
- Go from a flagged count to the events behind the variance
- Open the order, lot and location linked to an event
Changes to past events are detectable.
An audit log is only useful if earlier entries can't be rewritten without anyone noticing. Each event in Klovio carries a cryptographic hash of the event before it, so the log forms a chain rather than a set of independent rows.
If a historical value is changed, the hashes that follow it no longer match. Klovio flags the break, so you know the history has been altered and from which event.
- Events are kept as an append-only history
- Each event is linked to the previous one by its hash
- Corrections are recorded as new offsetting events, so the original entry stays visible
What one audit event contains.
Each event captures nine fields when the work is recorded and links to the event before it. Here's what's stored and how teams use it afterwards.
Audit log details.
- Fields per event. User, role, device, location, SKU, lot, quantity change, source action and a timestamp to the millisecond. Each event also keeps the quantity before and after the change.
- Role on record. The role stored with each event shows which permissions the user was working under. More on Roles & Permissions →
- Export. Export the history for a SKU, lot or date range to CSV for finance, customer or auditor review.
Features that use the same event history.
See how a discrepancy is traced in Klovio.
A 30-minute demo covering how events are recorded, filtered and exported, focused on your requirements.