See what Klovio costs for your operation. Personalized quote in your inbox in 60 seconds.
AUDIT LOG

Every inventory change,on the record forever.

Receipts, picks, transfers, adjustments, counts — each one stamped with who, what, when, which device, and the source action. An immutable, append-only ledger you can search in seconds. Shrink stops being a mystery and starts being a question with an answer.

See pricing
app.klovio.app/audit-log
EVENTS TODAY
3,842
FIELDS / EVENT
9
FLAGGED
2
Audit trail · SKU SS-500 · last 24h
Adjustment −310:42 · Daniel HPick
Receipt +4810:41 · María RReceive
Transfer A2→A409:18 · María RMove
Count match 12=1208:05 · León PCount
100%
Events logged
Every receipt, pick, transfer, adjustment, and count is written to the ledger. There is no "off" switch.
9
Fields per event
User, role, device, location, SKU, lot, quantity delta, source action, and a millisecond timestamp.
<10s
Trace time
From "this count is wrong" to the exact event that caused it. Filter, find, done — no spreadsheet forensics.
7yr
Retention
Default retention window, configurable for your compliance regime. Old events stay readable, never editable.
Why a real audit log matters

A wrong count with no history is a dead end.

Most inventory tools tell you what the number is. Almost none tell you how it got that way. So when a count is off, the investigation starts and ends with a shrug — nobody remembers, nothing was recorded, and the loss gets written off. An append-only audit log makes every number explainable.

The shrink nobody can explain

You're down 14 units and there's no record of where they went. Without a per-event trail, "shrink" is just a polite word for "we have no idea." Real history turns the write-off into a root cause.

The audit you can't pass

A customer, a regulator, or your own finance team asks to see the chain of custody on a lot. If you can't produce who touched it and when, the answer is a finding — and a finding is expensive.

The blame with no proof

When a number drifts, fingers point at whoever's closest. A tamper-evident log replaces the blame game with facts: the exact event, the exact person, the exact device — recorded the moment it happened.

Before vs. after

Best-guess history vs. a real ledger.

Same warehouse, same SKUs, same team. The only difference is whether every change leaves a permanent, searchable record.

❌ Without an audit log
  • Changes vanish. The count updated, but nothing recorded who did it or why.
  • History gets overwritten. Edits clobber the previous value — the old number is simply gone.
  • Discrepancies become arguments. No timestamp, no user, no device — just two people remembering differently.
  • Compliance is a fire drill. An audit request means weeks of digging through emails and spreadsheets.
  • Investigations stall. "Where did 14 units go?" has no answer, so it gets written off as shrink.
  • No tamper protection. Anyone with access can quietly change a record and leave no trace.
✅ With Klovio
  • Every change is on the record. Append-only — events are added, never edited or deleted.
  • History is permanent. Each event keeps the before value, the after value, and the delta.
  • Discrepancies become questions. Every event has a user, role, device, location, and source action.
  • Compliance is a filter and an export. Pull the trail for any SKU, lot, or date range in seconds.
  • Investigations close fast. Trace any count back to the exact event that caused it in under ten seconds.
  • Tamper-evident by design. Each event is hash-chained to the one before it. Altering one breaks the chain.
How it works

Three steps from event to evidence.

Nothing for your team to remember to do. The log fills itself the moment work happens — then it's there forever when you need it.

STEP 01

The change happens

Someone receives, picks, transfers, adjusts, or counts. The action itself is the trigger — there is no separate "log this" step to forget or skip.

automatic
STEP 02

Klovio writes an immutable event

One row is appended to the ledger with all nine fields and a hash linking it to the prior event. Existing rows are never touched, so the past can't be rewritten.

append-only
STEP 03

You search, trace, or export

Filter by SKU, user, location, or date range and the full story appears. Trace a discrepancy to its origin, or export a clean trail for finance and compliance.

<10 s to answer
Trace any discrepancy

Follow a count back to the exact moment it broke.

Pick a SKU, set a date range, and Klovio reconstructs the full chain of events — every quantity delta, in order, with the running balance after each one. When the on-hand stops matching reality, the offending event is right there on the line.

  • See the running balance after every event, not just the latest total
  • Filter by SKU, user, location, device, or source action
  • Jump from a flagged count straight to the event that caused it
  • One-click context: the order, the lot, and the location involved
See Cycle Counting →
Trace · Sea Salt 500g · expected 15, found 12
+24 Receipt · bal 39 → 63
María R · Handheld · 09:02:11
−48 Picks ×4 · bal 63 → 15
Daniel H · Handheld · 10:18:40
−3 Adjustment · bal 15 → 12
Daniel H · Handheld · 10:42:08 · reason: damaged
=12 Cycle count · matches ledger
León P · Tablet · 16:30:55
Hash-chained ledger
#41
Receipt +48
a1f4…9c
→ →
#42
Pick −3
7b20…e1
↓ Each event hashes the one before ↓
Chain verified
intact
Edit any past event and every hash after it breaks.
Tamper-evident

A record you can actually trust.

An audit log is only useful if it can't be quietly rewritten. Every event in Klovio carries a cryptographic hash of the event before it, so the ledger is a chain, not a pile of rows.

Change one historical value and every hash downstream stops matching. The tampering is obvious and automatically flagged — which means the record holds up to a customer, an auditor, or a courtroom.

  • Append-only writes — events are never edited or deleted
  • Per-event hash chain detects any alteration instantly
  • Corrections are new offsetting events, so the original stays visible
Under the hood

The anatomy of an audit event.

Nine fields, captured the moment work happens, sealed into an immutable chain. Here's exactly what gets recorded — and what you can do with it later.

EVENT → EVIDENCE What one audit event holds Captured automatically. Stored forever. SCAN ✓ STEP 1 · THE ACTION A worker picks, receives, or counts The action on the floor is the trigger — no separate step, nothing to remember or skip. instant LEDGER ROW STEP 2 · THE RECORD Nine fields, appended and sealed One immutable row, hash-linked to the event before it. The past is never overwritten. User Role Device Location SKU + lot Qty delta Source action Timestamp Prev. hash Search Filter by SKU, user, location, or date. Trace Walk any count back to its root cause. Export Clean CSV trail for finance & compliance. Every number on your dashboard has a story you can read.
The specifics

What the audit log guarantees in Klovio.

Related modules

Pairs well with.

Stop writing off mysteries. Start tracing them.

20 minutes is all it takes to see Klovio's audit log turn a shrink problem into a solved case on your kind of operation.

See pricing