Skip to content

Overrides and loss prevention

Four things at a till move money without a customer paying for goods: voiding an item, overriding a price, cancelling a whole order, and opening the drawer without a sale. MyShopie records every one of them with a reason code, the cashier who asked, and the manager who approved. The result is the override log — the single screen worth reviewing weekly if you care about shrinkage.

Plans: Retail, Growth, Enterprise

Requires app: Point of Sale. Install Point of Sale from Settings → Apps before these screens appear.

  • Reading the log in the dashboard needs view_reports.
  • Approving another cashier’s override needs authorize_pos_override. Grant it to supervisors, not to every cashier, or the approval step stops meaning anything.
  • Anyone who will approve overrides should set an override PIN before their first shift.
Action What it is Typical legitimate use
void_item Removing a line from a sale in progress Scanned twice, wrong size, customer changed their mind at the counter
price_override Selling a line at a price other than the catalog price Price match, damaged goods sold at a discount, a mislabelled shelf
void_order Cancelling an entire sale in progress Customer walks away, card declines and they leave, sale rung on the wrong lane
no_sale Opening the drawer with no transaction Giving change, a safe drop, retrieving something

Each is logged whether or not it needed approval, so the log is a complete record rather than only the exceptions.

A reason is required, chosen from a fixed list so the log can be filtered and counted rather than read as free text. A free-text note can be added alongside it.

Code Use it for
damaged Goods are damaged and sold or written off accordingly
customer_changed_mind The customer decided against the item at the counter
entry_error The cashier rang the wrong thing — wrong item, wrong quantity, scanned twice
spoilage_comp Spoilage, or a goodwill gesture to the customer
price_match Matching a price the customer has evidence for
not_wanted The item is not wanted and goes back on the shelf
other Anything else — always add a note
  1. Decide who approves. Grant authorize_pos_override to supervisors and duty managers under Settings → Staff. Cashiers who hold it are approving themselves, which the log records as self-service.

  2. Each approver sets their own override PIN from their profile. It is a separate credential from their POS login PIN, so a cashier who watches a sign-in has not watched an approval.

  3. Brief the floor: an override is requested by the cashier and approved at the till by someone with the permission entering their override PIN. Nothing is approved by handing over a login.

  4. Review the log weekly. This is the step that makes the rest of it work.

Open Dashboard → POS → Override log. Filter by register, by action and by reason; the table is paginated.

Column Meaning
When Timestamp of the action
Action One of the four logged actions
Reason The reason code, with the cashier’s free-text note appended if there is one
Order The order the action applied to
Requested by The cashier who asked
Approved by The approver, or self-service when the cashier held the permission themselves
Amount delta How much money the action moved
Qty delta How many units it moved
  • One cashier, one reason, over and over. A cashier whose voids are always entry_error either needs training or is using the code as cover.
  • Voids late in a shift. Clusters in the last minutes before a close are worth checking against that shift’s variance.
  • No-sales on a low-cash lane. A lane that takes mostly card payments has little reason to keep opening its drawer.
  • Price overrides with no note on other. The code of last resort with no explanation is the entry to ask about first.
  • Self-service entries from people who should not be approving. A sign that authorize_pos_override is granted too widely.

Cross-reference what you find with Dashboard → POS → Shifts: an override pattern that lines up with a cash variance on the same register and shift is a much stronger signal than either alone.

Permission Needed for
use_pos Requesting a void, price override or no-sale
authorize_pos_override Approving an override, and setting an override PIN
view_reports Reading the override log
edit_users Granting authorize_pos_override to staff

Nobody can approve an override. No member of staff on the floor holds authorize_pos_override, or the person who does has not set an override PIN. Both are needed.

Everything in the log says self-service. authorize_pos_override has been granted to cashiers. Narrow it to supervisors if you want approval to be a real control.

The log is empty on a busy lane. Either the lane genuinely has not needed an override — possible on a small shop — or it is selling offline and has not synced yet. Check the register’s last-used time in the device panel.

A void does not show the order. Voiding a line on a sale that was then cancelled entirely leaves the line’s entry pointing at a cancelled order. Both entries will be in the log; read them together.

Override PIN and login PIN are confused. They are separate by design. The login PIN starts a cashier session; the override PIN authorises an exception. Anyone approving overrides needs both.

What is a no-sale? Opening the cash drawer without a transaction — to give change, to drop notes, or to look for something. It is recorded because an unexplained pattern of drawer opens is one of the clearest early signals of till loss.

Can a cashier approve their own override? Only if they personally hold authorize_pos_override. When they do, the log records the entry as self-service rather than leaving the approver blank, so it is visible as such. Where you want a second pair of eyes, do not grant that permission to cashiers.

Why is a reason code mandatory? Because the amount alone tells you nothing. “Three pounds off” is unreadable six weeks later; “price match, three pounds off, approved by the duty manager” is a decision you can audit.

What should I actually look at in the override log? Patterns, not individual entries. The same cashier always using entry_error, voids clustering in the last ten minutes of a shift, or no-sales on a lane that takes little cash are each worth a conversation. One void with a sensible reason is just retail.