Audit logs: how to find out who did what, when, and why it matters before you need it
The day a price changes, stock vanishes or a refund looks odd, the first question is “who did that?” An append-only audit log answers it. Know what it records, who can read it and how to review it without drowning.
6 min read
In short: anaudit log is a time-ordered record of important actions, who took them, from which device and when. Security events (logins, logouts, overrides, deletions, settings changes, consent changes) are logged; manager PIN approvals leave a trail; the log isappend-only, and in Wameed that is enforcedin the database so nobody, including the owner, can edit or delete entries. Viewing and exporting need a specificpermission, sensitive data like phone numbers and card digits ismasked, and entries are kept for aretention period. Use the log to answer disputes, catch patterns and prove what happened. Review a short list every week. The books also have their own audit log for accounting actions.
Controls matter on the day something goes wrong. The log is the record you will wish you had.
What an audit log is for
| Use | Example |
|---|---|
| Settle a dispute | “Who gave a 100% discount on Saturday?” |
| Investigate loss | Stock adjustments and voids before a shortage |
| Prove compliance | Who changed a tax setting and when |
| Detect fraud early | Repeated overrides by one person |
| Support security | Failed logins, new devices |
| Train staff | Show mistakes without blame |
| Satisfy auditors | A trustworthy trail |
What gets recorded
An audit entry typically holds:
- Who: the user and their role.
- What: the action and the thing it affected.
- When: the timestamp.
- Where: the store, the device and the app version.
- Details: old and new values where relevant.
- Severity: informational to critical.
Typical logged events:
- Logins and logouts, including failed attempts and lockouts.
- Overrides: manager-PIN approvals for voids, discounts, refunds and price changes.
- Deletions of important records.
- Settings changes: tax, receipts, hardware, permissions.
- Role and permission changes.
- Consent changes for customers’ marketing consent.
- Device registrations and wipes.
- Special overrides, such as seating a party at an unsuitable table.
- Brand and organisation changes.
The accounting books keep a separate append-only log of ledger actions: who created, approved, posted, reversed or locked what. Seeperiod locks and audit trail.
Manager PIN approvals
When a cashier needs approval (a void, a large discount), a manager enters aPIN. A good system:
- Does not let a person approve their own action.
- Limits approvals to the right branch.
- Locks out after repeated wrong PINs.
- Records an audit row for each approval.
That record is how you later see which manager approved what.
Append-only means append-only
For the log to be trusted:
- Nobody can edit an entry.
- Nobody can delete an entry, including administrators.
- The rule is enforced in the database, not just the app.
- Old entries are removed only by an automated retention job after the configured period.
In Wameed, the audit tables are protected from updates and deletes at the database level, and a daily job prunes entries beyond the retention period.
Who can see it
- Viewing and exporting the log requires a specific permission (for examplesecurity.view_audit).
- Branch scope applies: a branch user sees their branch’s entries, not a sibling’s.
- Export is rate-limited to protect against bulk copying.
- Give the permission to owners and a small number of trusted managers.
Privacy: masking
Logs and exports mask sensitive data: phone numbers, e-mail addresses and card last-four digits appear partly hidden to most readers, and full values are visible only to authorised roles. Your logging should capturethat something happened, not store unnecessary personal data. Seecustomer data and PDPL.
Retention
Keep audit data long enough for your needs (disputes, audits, legal duties) and no longer than necessary. Wameed prunes entries older than the configured retention days; for accounting entries the books carry a six-year retention floor. Confirm the periods you require with your adviser. Seeinvoice archive and retention.
A weekly review routine (15 minutes)
| Check | What to look for |
|---|---|
| Failed logins and lockouts | Many failures on one account: attack or a forgotten PIN |
| Overrides by person | One cashier needing approval far more than peers |
| Price changes | Unexpected changes, by whom, when |
| Stock adjustments | Large or frequent write-offs, especially after hours |
| Voids and refunds | Patterns by person, time or product. Seerefunds |
| Settings and permission changes | Anything unplanned |
| New devices | A device nobody recognises |
| After-hours activity | Logins at 3 a.m. |
| Deleted records | Why? |
Filter by severity first, then by user, then by action. Don’t read everything; read the exceptions.
When something goes wrong
- Preserve the evidence: export the relevant log range now.
- Reconstruct the sequence: who did what and when, using the log and the transaction and shift reports.
- Talk to the people with the facts in hand, calmly.
- Fix the control: change permissions, require a PIN, reduce discount limits.
- Document what you found and decided.
The aim is accountability and learning, not a witch hunt. Staff who know the log exists behave better.
Set up good logging
- No shared accounts; the log is only as good as individual logins. Seemultiple cashiers in one branch.
- Keep the device clocks right.
- Require a reason for sensitive actions.
- Restrict permissions so fewer actions need logging.
- Test: perform a few actions and find them in the log.
- Explain to staff that actions are logged.
Limits
- A log shows what the system saw, not what a person intended.
- It cannot record what happens outside the system, such as cash taken from a drawer without a sale.
- It is only useful if someone reads it.
Combine it with cash counts, stock counts and CCTV where appropriate. Seepreventing till theft.
Mistakes to avoid
- Never reading the log.
- Shared logins.
- Too many people with access to export.
- Assuming the log shows everything.
- Deleting evidence “to be tidy”.
Frequently asked questions
Can an administrator delete a log entry?
No; entries are append-only, enforced in the database.
Who can view the log?
People with the audit-view permission, within their branch scope.
How long are entries kept?
For the configured retention period; confirm what you need.
Does it log customer phone numbers?
Sensitive values are masked in logs and exports.
- #سجل التدقيق
- #من فعل ماذا
- #تتبع تغييرات النظام
- #سجل الأحداث الأمنية
- #audit log
- #POS audit trail
- #who changed what
Share this article
Ask about your own shop
Thirty minutes on your products, your tax setup and your hardware — not a slide deck.
Keep reading
6 min read
The daily opening and closing routine: two checklists that prevent most bad days
Most bad days start with something that could have been checked at 8 a.m.: a printer without paper, a till not synced, a promotion not live. Two short checklists, opening and closing, turn that into a five-minute habit.
6 min read
A cash-handling policy in one page: float, drops, counts, variances and who is accountable
Most cash problems are honest mistakes made possible by a missing rule. A one-page policy that states the float, the limits, the count method and the consequences protects honest staff and deters the other kind.
5 min read
Closing the shift: four numbers that catch problems in week one
Expected cash, counted cash, the difference, and the list of discounts and voids. Read those four every evening and you find problems while they are still small.

