← Running the shop
Operations Updated 26 October 2026 · 7 min read

Who Changed That Bill? Audit Logs and Login Hours for Pharmacy Staff

A bill is lower than it should be, and three people had the counter that day. An audit log turns that conversation from suspicion into a lookup.

Most pharmacy owners can describe a moment like this. A bill was edited after the customer left. A purchase was deleted. A figure on the ledger doesn't match the drawer. And nobody can say who touched it, because the software only remembers the latest version of anything.

The Users table on the Organization screen with each person assigned a role (Org Leader, Shop Manager, Shop Employee) and a shop.
The Users table on sample data: every person has a role and a shop. The audit log and login hours are built on top of that.

What the audit log records

The Audit log (under Insights) lists every change from the day it is on: who created, edited, deleted or restored a sale, return, purchase, payment, expense, challan, order, journal entry, stock count, transfer, batch, medicine, customer, supplier, user or draft, and when.

  • An edit shows before and after. A bill edit shows the amount going from one figure to another. A master edit names the fields that changed, such as mrp: 120 → 135.
  • The bill itself tells you. A sale or purchase opened from its list says who made it and who last changed it, with a History link to the full trail. The list tags a changed bill Edited.
  • Drafts show who parked them, which answers "whose half-finished bill is this?"

Finding the answer

Filter by period, person, kind of record and action. Search by bill number, party or person. Export whatever the filters match to CSV, which is handy when your CA or an inspector asks for "everything that happened to bill 1042". A typical lookup takes under a minute: filter to Deleted, this week, and read the names.

It can't be quietly cleaned up

A log is only worth having if the person it might implicate can't edit it. The log is kept forever. The server refuses any change to a log row, and Wipe all data leaves it in place and logs the wipe itself. An edit made from an older app version that is still catching up is logged by the server and marked as recorded from an old version, so no device can sidestep it by being out of date.

Who can see it

  • Org Leader or Org Manager: every shop, or one at a time.
  • Shop Manager: their own shop plus the shared masters.
  • Shop Employee: never, even if the screen is ticked on their row.

That last rule matters. The people the log is about shouldn't be the ones who can browse it.

Login hours: keep a shift a shift

An owner can switch on Limit login hours on a Shop Manager or Shop Employee, pick the days and a From–Until time: for example 9:00 AM to 9:00 PM, Monday to Saturday. Outside that window the person cannot sign in, on any device, and is told their hours.

  • Night shifts work. A window that ends before it starts runs past midnight and belongs to the day it starts on, so a Friday night shift covers Saturday's small hours.
  • A warning before it ends. Anyone signed in sees a band across the top for the last ten minutes and is signed out when the window closes. A bill in progress is kept as a draft, not lost.
  • Phone tricks don't work. The window is read on the shop's clock, so changing a phone's time zone doesn't move it, and changing the device clock doesn't help either. The app also won't restore a session at launch outside the window.
  • The owner can open the door from anywhere. If you widen someone's hours from your phone, a refused sign-in checks the server for the latest before it says no, so the counter unlocks at once.

Using the two together

Login hours stop the problem you can predict: somebody on the system at 11 pm who shouldn't be. The audit log answers the one you can't: what happened, in order, whenever you thought to ask. A worthwhile weekly habit: open the log, filter to Deleted and Edited for the week, and skim. Most weeks it takes two minutes and finds nothing, which is the point.

For what each person should be able to do in the first place, which is usually the bigger win, read stopping counter leakage with staff permissions. And for the other half of the stock story, see the stock audit, which records who wrote off what and why.

Know who did what, without having to ask.

Download DravyaOS for Windows

More from Running the shop

All articles →

Give it one evening.

Install it, bring your stock across, put tonight's billing through it — free for 3 days, no card and no account needed.