POS Cashier Control: Where Shop Money Leaks and How the Till Stops It
POS cashier control is the part of running a shop that owners think about only after the stock count comes up short, and by then the question is not how to stop it but who did it — which is the wrong question, asked too late, with no evidence to answer it.
The leak was never one dramatic theft. It was a sale rung up at a lower price for a friend, a void after the customer left with the goods, a discount nobody authorised, a drawer opened with no sale, an M-Pesa payment sent to a personal number instead of the till, a receipt not printed so the sale never existed, and a stock count that nobody could tie to any cashier because all three of them used the same login.
Each is small. Across a month across three attendants they are the difference between a shop that makes money and one that mysteriously does not. And the honest cashier — usually most of them — is the one who suffers, because when the owner finally notices, suspicion falls on everyone equally and nobody can prove it was not them.
Control is what changes that. One login per person, permissions matched to the role, an activity log that records every action, shifts that open with a float and close with a count, voids and discounts that need a second person, M-Pesa confirmed on the system before goods leave, and variance reported by cashier so the pattern is visible while it is small.
This guide covers all of it: logins and roles, the log, shifts and the float, drawer reconciliation and end-of-shift reports, voids, refunds, discounts and overrides, no-sale opens, receipts, ghost sales and under-ringing, M-Pesa leakage, daily variance, stock variance by cashier, exception reporting, cameras and their limits, investigation before accusation, fair process, training, rotation, banking, remote oversight, multi-branch and offline.
The value of POS cashier control is that leakage becomes visible and attributable, and POS cashier control done properly protects the honest majority as much as it catches the rest — which is why POS cashier control should be presented to staff as their protection rather than the owner’s suspicion.
Table of Contents
- Where Shop Money Actually Leaks
- The Kenyan Context
- Control Protects Honest Cashiers
- One Login Per Cashier
- Roles and Permissions
- The Activity Log
- Shift Open and Close
- The Float
- Cash Drawer Reconciliation
- X and Z Reports
- Voids
- Refunds and Returns
- Discounts and Price Overrides
- No-Sale Drawer Opens
- Receipt Discipline
- The Ghost Sale
- Under-Ringing and Sweethearting
- M-Pesa to a Personal Number
- M-Pesa Confirmation Before Goods Leave
- The Daily Cash Variance
- Stock Variance by Cashier
- Exception Reporting
- Cashier Performance Reports
- Cameras and Their Limits
- Investigation Before Accusation
- Fair Process and the Law
- Training and Onboarding
- Rotation and Separation of Duties
- End-of-Day Banking
- Owner Absence and Remote Oversight
- Multi-Branch Cashier Control
- Offline Mode and Control
- Data Protection
- Systems and Costs
- Frequently Asked Questions
Where Shop Money Actually Leaks {#where-leaks}
The leaks are ordinary and the ordinariness is why they persist.
Sales rung at a lower price than the shelf.
Sales not rung at all, with cash pocketed and stock gone.
Voids after the customer has left with the goods.
Refunds for returns that never happened.
Discounts applied without authority.
Drawer opened without a sale to make change or to remove cash.
M-Pesa payments directed to a cashier’s own phone.
Receipts not printed, so the sale has no record.
Goods taken from stock without a sale.
Cash short at the end of a shift and nobody accountable because the shift was shared.
Each is a control gap, and POS cashier control closes them one at a time, since POS cashier control that requires a login, logs the action, needs authority for the exception and reconciles the drawer has removed the conditions each leak depends on.
The Kenyan Context {#kenyan-context}
Local conditions shape both the leakage and the controls.
Shared logins are the norm, with one password on the till and everyone using it.
Cash and M-Pesa are mixed on every shift, which doubles the reconciliation.
M-Pesa to a personal number is a recognised leakage route, since a customer will send to whatever number they are given.
Attendants are frequently paid modestly, which is context rather than excuse and it shapes how controls should be introduced.
Owners are absent for much of the day, running other things.
Family members work in the shop and are assumed trustworthy, which removes the control rather than the risk.
Staff turnover is high, so training must be repeatable.
Power interruptions force offline operation, which the offline section addresses.
Suspicion is the default response to a shortfall and accusations are made without evidence, which damages the honest and rarely catches the dishonest.
Cameras are common and their footage is rarely reviewed.
A POS cashier control approach that begins by ending shared logins addresses the single largest gap, and POS cashier control that confirms M-Pesa on the system before goods leave addresses the second.
Control Protects Honest Cashiers {#protects-honest}
This is the argument that makes control acceptable to the people it applies to, and it happens to be true.
When money is short and three people share a login, all three are suspected.
When each has their own login and their own shift, the shortfall belongs to a shift, and two of the three are cleared.
A cashier whose voids are authorised by a supervisor cannot be accused of voiding to steal.
A cashier whose drawer was counted at handover cannot be blamed for the previous shift’s shortage.
A cashier whose M-Pesa sales are confirmed on the system cannot be accused of diverting them.
The log is the honest cashier’s alibi.
Present it that way, since POS cashier control introduced as “this protects you when something goes missing” is accepted, and POS cashier control introduced as “we think one of you is stealing” produces resentment and turnover.
An honest cashier who understands the controls will ask for them.
One Login Per Cashier {#one-login}
Individual logins are the foundation and everything else depends on them.
A username and password or PIN per person.
Never shared, never written on the till.
Logged in at the start of the shift, out at the end.
Every sale, void, refund, discount and drawer open attributed to the logged-in user.
Disabled the day a person leaves.
Changed if compromised.
With shared logins nothing is attributable, and POS cashier control starts here because a shortfall on a shared login belongs to nobody, while POS cashier control with individual logins turns every action into a record with a name on it.
Enforce it, since a shop where the rule exists and the login is still shared has the rule and not the control.
Roles and Permissions {#roles}
Not everyone should be able to do everything, and the permissions should match the job.
Cashier: sell, take payment, print receipts.
Supervisor: authorise voids, refunds and discounts above a threshold, open the drawer without a sale, view shift reports.
Manager: adjust prices, adjust stock, view all reports, manage users.
Owner: everything, including audit.
Permissions enforced by the system rather than by instruction.
A cashier who can void their own sales has been given the means to steal, and POS cashier control that limits the cashier to selling and routes exceptions to a supervisor has removed it, since POS cashier control is largely a matter of who is allowed to do what.
Review permissions when roles change, since a supervisor demoted to cashier who keeps supervisor rights has kept the authority.
The Activity Log {#activity-log}
The log is the record of every action and it should be complete and unalterable.
Every sale with user, time, items, amounts and payment method.
Every void with the original sale, the user, the time and the reason.
Every refund likewise.
Every discount and price override with authoriser.
Every no-sale drawer open.
Every login and logout.
Every price and stock adjustment.
Unalterable by cashiers and supervisors, since a log the user can edit is not a log.
Searchable by user, date and action type.
The log is what turns a suspicion into a question with an answer, since POS cashier control with a complete log lets the owner see that one cashier voided nine sales last Tuesday between two and four, and POS cashier control without one leaves the owner with a shortage and a feeling.
Review it, since a log nobody reads deters nobody.
Shift Open and Close {#shifts}
Shifts bound accountability to a person and a period.
Shift opened by the cashier with the float counted and recorded.
All activity attributed to the open shift.
Shift closed with the drawer counted and recorded.
Handover between cashiers as a close and an open, never a shared drawer.
Shift report generated at close.
Variance between expected and counted cash recorded.
Signed off, physically or in the system, by the cashier and a supervisor.
Without shifts the day is one undivided pool, and POS cashier control with shifts makes every shortage belong to a specific person’s period, since POS cashier control cannot attribute what it cannot bound.
Never let two cashiers share one open shift.
The Float {#float}
The float is the starting cash and its handling is where the first discipline is set.
A fixed amount at shift open, counted by the cashier and confirmed.
Recorded on the shift.
Kept separate from personal money.
Not topped up from sales without record.
Counted out at close and reconciled.
A float that is never counted is a float that can be short from the start, and POS cashier control that records the float at open means the close variance is real, while POS cashier control that assumes the float is always the same amount will attribute yesterday’s shortage to today’s cashier.
Count it every time.
Cash Drawer Reconciliation {#drawer-reconciliation}
At the end of every shift, the drawer should equal the float plus cash sales minus cash refunds and paid-outs.
Expected cash calculated by the system from the shift’s transactions.
Actual cash counted by the cashier.
Counted again by a supervisor where the value warrants.
Variance recorded, whether over or short.
Reason recorded where known.
Over is as much a signal as short, since a drawer consistently over is a cashier under-ringing and not yet removing the surplus.
Pattern by cashier over time.
Daily, without exception, since POS cashier control that reconciles every shift catches a variance the day it happens, and POS cashier control that reconciles weekly has seven shifts to search.
Never let a shift close without a count.
X and Z Reports {#x-z-reports}
The two standard reports serve different moments.
An X report shows the shift’s activity so far without closing it, for a mid-shift check.
A Z report closes the shift and finalises the figures.
Both show sales by payment method, voids, refunds, discounts, no-sale opens and expected cash.
The Z report is the shift’s permanent record.
Numbered sequentially so a missing one is visible.
Reviewed by the supervisor and owner.
The Z report is where the day’s exceptions appear in one place, since POS cashier control that produces a Z with nine voids and four no-sale opens has surfaced the question, and POS cashier control with sequential Z numbers means a shift that was never closed is a shift that shows as missing.
Voids {#voids}
A void cancels a sale and it is the most common route to cash theft.
The sale is rung, the customer pays cash, the customer leaves, the sale is voided, the cash is removed and the drawer still balances.
Controls: voids require supervisor authorisation; voids after payment require a reason; voids are logged with the original sale; void rate by cashier is reported.
Pre-payment voids for genuine errors are different from post-payment voids and the log should distinguish them.
A cashier with a void rate far above colleagues has a pattern to explain.
Authorisation is the control, since POS cashier control that requires a second person for every void has made the theft require a collaborator, and POS cashier control that lets cashiers void freely has left the door open.
Review voids daily.
Refunds and Returns {#refunds}
A refund without a return is cash out for nothing.
Refunds require the original receipt or transaction.
The returned item is received into stock.
Supervisor authorisation.
Customer details where the value warrants.
Refund rate by cashier reported.
A refund for an item that was never returned shows as a stock variance later, since POS cashier control that ties refunds to stock receipt means the item must physically come back, and POS cashier control that refunds cash without the item has paid for something it does not have.
Make the return the condition of the refund.
Discounts and Price Overrides {#discounts}
Discounts reduce revenue invisibly unless controlled.
Standard discounts configured in the system, applied by selection rather than typed.
Manual discounts above a threshold requiring authorisation.
Price overrides restricted to managers.
Every discount logged with user and authoriser.
Discount rate by cashier reported.
Reason codes.
The friend at the counter is served by a discount nobody sees, and POS cashier control that reports discount value by cashier makes the friend visible, since POS cashier control without discount limits has let each cashier set their own prices.
Watch for the cashier whose discounts cluster at particular times or for particular items.
No-Sale Drawer Opens {#no-sale}
Opening the drawer without a sale is sometimes necessary and always worth logging.
Making change for a customer.
Removing excess cash to the safe.
Genuine reasons exist.
Every open logged with user and time.
Count of no-sale opens by cashier reported.
Supervisor authorisation where the shop chooses.
A cashier opening the drawer twenty times a shift with no sale has a pattern, and POS cashier control that counts them makes it visible, while POS cashier control that ignores no-sale opens has left the drawer unwatched between sales.
Receipt Discipline {#receipts}
A receipt is the customer’s evidence and the shop’s, and its absence is the ghost sale’s cover.
Every sale prints or sends a receipt.
Customers told to expect one.
A sign that says so.
Receipt reprints logged.
Receipt numbers sequential.
A cashier who does not print receipts may be ringing sales in a way that leaves no record, or not ringing them at all, and POS cashier control that makes the receipt automatic removes the choice, since POS cashier control depends on every sale producing a record the customer holds.
Customers who ask for receipts are the shop’s auditors.
The Ghost Sale {#ghost-sale}
The sale that never entered the system is the hardest leak to see and stock is how it shows.
Cash taken, goods handed over, nothing rung.
No receipt, no log entry, no cash expected.
The drawer balances because the system expects nothing.
Stock is short by the items sold.
Detection is stock variance, since POS cashier control that counts stock and compares to recorded sales finds the gap, and POS cashier control that reconciles only cash will never see a sale that was never recorded.
Prevention is receipts, customer expectation and stock counts frequent enough that the gap is attributable to a period and a shift.
Under-Ringing and Sweethearting {#under-ringing}
Ringing less than the customer paid, or less than the goods are worth, is the friend’s discount by another route.
A cheaper item rung for an expensive one.
Fewer items rung than handed over.
A sale rung at a lower quantity.
Cash pocketed for the difference, or the friend simply pays less.
Detection is stock variance by item and by cashier, since POS cashier control that shows expensive items short and cheap items over on one cashier’s shifts has found the substitution, and POS cashier control with barcode scanning rather than manual item selection makes the substitution harder.
Barcode everything that can be barcoded.
M-Pesa to a Personal Number {#mpesa-personal}
This is the leakage route most specific to this market and it needs a specific control.
A customer asks how to pay; the cashier gives their own number.
The customer sends; the cashier confirms; the goods leave.
The system shows a cash sale, or no sale, or a sale marked M-Pesa with no reference.
The shop’s till receives nothing.
Controls: the till or paybill number displayed prominently so customers use it; cashiers prohibited from giving any other number; M-Pesa sales require a transaction reference entered and confirmed against the till statement; till statement reconciled to M-Pesa sales daily.
STK push from the system where available, so the customer’s phone is prompted with the shop’s till and the cashier never gives a number.
The STK push is the strongest control, since POS cashier control that sends the prompt from the system to the customer’s phone removes the cashier from the payment routing entirely, and POS cashier control that reconciles every M-Pesa sale to the till statement catches the diversion the same day.
Tell customers to pay only to the number on the sign.
M-Pesa Confirmation Before Goods Leave {#mpesa-confirmation}
The other M-Pesa leak is the payment that was promised and never arrived.
Customer says they have sent; cashier releases goods; nothing arrives.
Or a screenshot is shown that is not a real confirmation.
Control: the system confirms the payment against the till before the sale completes.
No confirmation, no release.
Cashiers not permitted to override on the customer’s word.
Failed and reversed transactions flagged.
Automatic confirmation is what makes this practical, since POS cashier control that shows the cashier the confirmed payment on screen means the goods leave only when the money has arrived, and POS cashier control that relies on the cashier reading the customer’s phone has trusted a screenshot.
The Daily Cash Variance {#daily-variance}
Expected against actual, every shift, is the single most diagnostic figure.
Expected cash from the system.
Actual cash counted.
Variance, over or short.
By shift and by cashier.
Trend over weeks.
Threshold for investigation.
Small consistent shortages are more telling than one large one, since a cashier short by a few hundred every shift has a habit, and POS cashier control that plots variance by cashier over a month shows the habit, while POS cashier control that looks only at large variances misses the steady leak.
Investigate patterns, not single events.
Stock Variance by Cashier {#stock-variance}
Stock counts are where ghost sales and under-ringing surface, and tying them to cashiers is the detection.
Regular stock counts, full or cycle.
Variance between counted and system stock.
Attributed to the period since the last count.
Cross-referenced with which cashiers worked that period.
Variance by item category, since substitution shows as expensive short and cheap over.
Patterns over several counts.
Attribution requires frequent counts and individual logins, since POS cashier control with weekly cycle counts on high-value lines can narrow a variance to a few shifts, and POS cashier control with an annual stocktake can only say something went missing at some point in the year.
The retail analytics article covers stock turn; this is stock loss.
Exception Reporting {#exceptions}
The owner should see the exceptions, not the whole log.
Voids by cashier, count and value.
Refunds by cashier.
Discounts by cashier, count and value.
No-sale opens by cashier.
Cash variance by shift.
M-Pesa sales without reference.
Receipt reprints.
Price overrides.
Logins outside shift hours.
Each as a daily or weekly view with outliers highlighted.
The exception report is what makes control possible for an owner with no time, since POS cashier control that shows one cashier at three times the void rate of the others has done the analysis, and POS cashier control that requires the owner to read every transaction will not be read.
Ten minutes a day on the exception report is the owner’s whole job here.
Cashier Performance Reports {#performance}
Performance and control are the same data read two ways.
Sales per cashier per shift.
Average transaction value.
Items per transaction.
Speed.
Void, refund and discount rates.
Cash variance.
Customer complaints.
Good cashiers deserve recognition, and POS cashier control that shows who sells well and reconciles cleanly is as much a reward tool as a control tool, since POS cashier control used only to find fault will be experienced as surveillance, while the same reports used to recognise the reliable cashier build the culture that reduces the need for control.
Share performance figures with cashiers so they see their own.
Cameras and Their Limits {#cameras}
Cameras are common and they are less useful than owners believe.
They record; they do not analyse.
Footage is rarely reviewed unless something is already suspected.
They deter the opportunistic and not the practised.
They are most useful when the log says when to look, since POS cashier control that flags a void at 14:32 tells the owner which two minutes of footage to watch, and POS cashier control without the log leaves the owner with a day of video and no timestamp.
Privacy applies, since staff should know cameras exist and footage should be used for the stated purpose.
Cameras support the log; they do not replace it.
Investigation Before Accusation {#investigation}
A variance is a question, not an answer, and how the question is asked matters.
Establish the facts from the log and the counts.
Consider innocent explanations: training gaps, system errors, genuine customer returns, miscounts, previous shift’s shortage carried forward.
Talk to the cashier privately.
Listen.
Look for a pattern across shifts before concluding anything.
Never accuse on a single variance.
Never accuse in front of colleagues or customers.
Document what was found and what was said.
A wrong accusation destroys an honest employee and the shop’s reputation as an employer, and POS cashier control gives the owner facts to raise rather than suspicions to voice, since POS cashier control that shows a pattern over twenty shifts is evidence, and a feeling about one shift is not.
Most variances have explanations, and the log finds them.
Fair Process and the Law {#fair-process}
Where the evidence does point to dishonesty, the response has legal dimensions.
Employment law governs how an employee may be disciplined or dismissed, and the process requirements are real.
Summary action without process may be unlawful even where the theft is real.
Recovery of losses from wages has limits.
Involving the police is a decision with consequences and should be evidenced.
Documentation from the log and the counts is the evidence base.
Take qualified advice before acting, since POS cashier control produces the evidence and a lawyer or HR adviser determines what may be done with it, and POS cashier control followed by an unlawful dismissal has converted a loss into a liability.
Treat the person with dignity throughout, whatever they did.
Training and Onboarding {#training}
Controls that cashiers do not understand are controls they work around.
Training on the system before the first shift.
The controls explained with their purpose, particularly the protection argument.
Shift open and close practised.
Void and refund procedure with the authorisation step.
M-Pesa procedure: the number on the sign, the reference, the confirmation.
Receipt discipline.
What to do when the system is offline.
Repeatable, since turnover is high and POS cashier control depends on every new cashier being trained the same way, and POS cashier control that assumes the outgoing cashier trained the incoming one has passed on whatever shortcuts the outgoing one had.
Write it down and use it every time.
Rotation and Separation of Duties {#rotation}
Certain combinations of duties should not sit with one person.
The cashier who sells should not authorise their own voids.
The cashier who counts the drawer should not be the only one who counts it.
The person who adjusts stock should not be the person who sells it.
The person who banks should not be the only person who reconciles.
Rotation of cashiers across shifts and tills so patterns are attributable.
Rotation of who counts.
In a small shop with two staff, the owner is the second person, and POS cashier control in a small shop means the owner authorises and counts, since POS cashier control cannot separate duties that all belong to one person.
Family members are staff for this purpose, since trust is not a control.
End-of-Day Banking {#banking}
Cash that sits is cash at risk and the banking should close the loop.
Cash from closed shifts counted and consolidated.
Banked daily or as often as practical.
Deposit slip matched to the day’s Z reports.
M-Pesa till balance reconciled to M-Pesa sales.
Difference between banked and recorded investigated.
Who banks recorded.
The bank is the final witness, since POS cashier control that matches the deposit to the Z reports proves the day’s cash reached the account, and POS cashier control that stops at the drawer count has not confirmed the cash went anywhere.
The gap between drawer and bank is where cash disappears after the count.
Owner Absence and Remote Oversight {#remote}
The owner is not there most of the time and the system should be their presence.
Live sales on the owner’s phone.
Shift open and close notifications.
Exception alerts: a large void, a large discount, a variance over threshold.
Daily summary at close.
Ability to review the log from anywhere.
Presence replaced by information, as the multi-site salon article argues, and POS cashier control that sends the owner the exceptions means they are managing the shop from wherever they are, since POS cashier control that requires the owner to be in the shop to see anything has no effect during the hours they are not.
The absent owner who reviews the exception report is more present than one who visits and sees a tidy counter.
Multi-Branch Cashier Control {#multi-branch}
Across branches the same controls apply and comparison adds a layer.
Individual logins and shifts at every branch.
Same permission structure.
Exception reports per branch and across branches.
Variance by branch and by cashier.
Branch managers reviewing daily, owner reviewing exceptions across all.
Stock transfers between branches controlled and logged, since transfers are a leak route of their own.
Comparison shows the outlier branch, and POS cashier control that shows one branch’s void rate at twice the others has found something the branch manager may not have, since POS cashier control across branches is what lets an owner see a problem two towns away.
The multi-branch discipline the site describes rests on this.
Offline Mode and Control {#offline}
Power and connectivity fail and the controls must survive it.
Offline sales recorded locally with user, time and items.
Same login and permission enforcement offline.
Sync when connectivity returns.
M-Pesa confirmation impossible offline, which means either cash-only during the outage or a documented manual confirmation procedure reconciled later.
No “offline” as an excuse for a shift with no records.
Test it, since POS cashier control that lapses during every power cut has a gap exactly when the shop is busiest, and POS cashier control that continues to log offline and syncs afterwards keeps the record whole.
Data Protection {#data-protection}
Cashier records and customer receipts are personal data and the Data Protection Act applies.
Cashier login records, activity logs and performance data are the employee’s data.
Customer details on receipts and refunds.
Camera footage of staff and customers.
Access to logs and reports limited by role.
Performance data shared with the individual, not published across staff.
Footage used for the stated purpose and retained for a defined period.
Confirm obligations with qualified advice, and POS cashier control should be configured to whatever position that establishes, since POS cashier control that posts each cashier’s variance on the staff noticeboard has disclosed something the individual should have received privately.
Systems and Costs {#systems}
Cashier control is built into a POS worth having, and the log and the exception reports are what to assess.
Individual user accounts with roles.
Shift management with float and close count.
Expected-versus-actual cash by shift.
Void, refund and discount authorisation with reason codes.
No-sale open logging.
Automatic receipts and reprint logging.
M-Pesa STK push and confirmation against the till.
Barcode scanning.
Activity log, unalterable and searchable.
Exception reports by cashier.
Stock counts with variance by period.
Owner alerts and mobile access.
Offline mode with full logging.
Pricing for the platform commonly from a modest monthly figure for a single shop, rising with branches and users, with control features included rather than extra.
Implementation should begin with individual logins on day one, since POS cashier control without them has nothing to attribute, then shifts with a counted float and close, then authorisation thresholds, then the STK push for M-Pesa.
Introduce it with the protection argument, and review the exception report every day.
Weigh it against the leak, since POS cashier control that stops a few hundred shillings a shift across three attendants has paid for the platform inside a month.
Frequently Asked Questions {#faqs}
Our stock count came up short. How do we find out who did it?
If your cashiers share one login, you cannot — the shortfall belongs to nobody and suspicion falls on everyone. That is the wrong question asked too late. Start with individual logins and shifts so the next variance is bounded to a person and a period, then use the activity log and stock counts by period to see patterns rather than events.
Won’t staff resent all this control?
Not if it is introduced honestly, because it protects them. With shared logins, all three cashiers are suspected when money is short; with individual shifts, two are cleared. A cashier whose voids need a supervisor cannot be accused of voiding to steal, and the log is the honest cashier’s alibi. Say that, and honest cashiers will ask for the controls.
What is the single most common leak?
Voids after payment — the customer pays cash, leaves, the sale is voided and the cash removed, and the drawer still balances. Require supervisor authorisation for every void, log each with the original sale and a reason, and report void rate by cashier. A cashier at three times colleagues’ void rate has a pattern to explain.
How does M-Pesa money leak?
A cashier gives the customer their own number instead of the till’s. Display the till number prominently, prohibit any other number, require a transaction reference confirmed against the till, and reconcile M-Pesa sales to the till statement daily. Where the system supports STK push, use it — the prompt goes from the system to the customer’s phone and the cashier never gives a number at all.
The drawer is always slightly over. Is that a problem?
Yes. A drawer consistently over is a cashier under-ringing and not yet removing the surplus. Over is as much a signal as short, and small consistent variances are more telling than one large one. Plot variance by cashier over a month and investigate patterns, not single shifts.
Do cameras solve this?
They record; they do not analyse, and footage is rarely reviewed unless something is already suspected. Their value is when the log says when to look — a void flagged at 14:32 tells you which two minutes to watch. Cameras support the log; they do not replace it. Staff should know cameras exist and footage should be used for its stated purpose.
A cashier’s numbers point to theft. Can we dismiss them?
Not without process. Employment law governs discipline and dismissal, summary action may be unlawful even where the theft is real, and recovery from wages has limits. Investigate privately first — most variances have innocent explanations the log will find — and take qualified advice before acting. A wrong accusation destroys an honest employee, and an unlawful dismissal converts a loss into a liability.
How much time does this take an owner?
Ten minutes a day on the exception report — voids, discounts, no-sale opens, variance and M-Pesa sales without reference, by cashier, with outliers highlighted — plus the daily close and banking match. POS cashier control that shows the owner the exceptions rather than the whole log is what makes it possible for someone who is not in the shop.