Sweethearting at the till: when the discount is the theft

Short answer: Sweethearting hides inside normal till functions: a manual price override, a staff discount applied to the wrong basket, an item passed around the scanner, a coupon accepted twice. No single transaction proves anything, because each function has a legitimate use. The pattern proves it: the same operator, the same small group of customers, the same override types, at values that never quite trigger a review threshold.

Why the daily total looks clean

A store can hit its sales target while sweethearting runs underneath it, because the goods leave through a recorded transaction. Stock and money both move, just at the wrong price. Shrink figures catch part of it weeks later as an unexplained category loss, by which time the till records are the only route back to a cause.

That delay is why till exception reporting exists. Overrides, voids after tender, discount percentage by operator, and no sale drawer openings are recorded at the moment they happen. A manager who reads exceptions weekly sees sweethearting forming. A manager who reads only the stocktake sees a number with no story.

Look for clustering, not size. One operator whose manual discounts run well above peers on the same shifts. Baskets where a high value line is discounted and everything else is full price. Regular timing, the same evening, the same customer paying by the same card. Any one of these can be innocent. Together they are a file worth opening.

The shapes worth a second look

Self discounting has its own shape: staff purchases rung by the purchaser, or by one consistent colleague, outside the store's rule for independent ringing. Most retailers already ban the practice on paper. The till data shows whether the ban is real.

Set override limits in the till system by role, require a supervisor code above a modest threshold, and make the reason code mandatory and reportable. Friction at the moment of the override deters more than a poster in the staff room, because the person sweethearting counts on the transaction being one of thousands nobody reconstructs.

Design the temptation out first

Rotate till assignments and break times where you can. Fixed pairings, one operator always serving one regular at one till, are the social structure sweethearting needs. Rotation is not an accusation. It is scheduling, and it quietly removes the arrangement.

When the pattern is strong, stop and preserve: till logs, exception reports, and relevant CCTV before routine overwriting deletes them. Stores lose winnable cases by challenging first and gathering later, when the recordings have already cycled out.

Confront with transactions, not character. Put the specific baskets, dates, and override records on the table and let the employee answer them. Vague accusations produce denials and grievances. A record produces a conversation with an end.

Handle the finding like evidence, not gossip

Keep reading: Self checkout shrink: reading the patterns instead of blaming the machines, Refund method switching: the quiet gap between sale and refund.

Frequently asked questions

What is the difference between sweethearting and a pricing error?

Frequency and benefit. A pricing error is random, benefits strangers, and stops when training or labelling is fixed. Sweethearting repeats, benefits a connected customer or the operator, and clusters on one operator's exception report.

What is the difference between sweethearting and a pricing error?

The operator exception report: manual overrides, discount value and percentage, voids, and no sale events compared across operators on similar shifts. Outliers there appear within a week, long before a stocktake would show anything.

What is the difference between sweethearting and a pricing error?

Most stores allow it with controls instead: independent ringing by another operator, discount applied per policy, and the transaction visible in reporting. A ban pushes purchases to a colleague's till with no record, which is worse.

What is the difference between sweethearting and a pricing error?

Rarely. Footage shows an item passing the till, not the price it was rung at. The proof is the combination of the transaction record showing the override and footage or timing that identifies the customer and operator.

See your own numbers.

A free bot-traffic audit shows the human-automated split in your live traffic - no code changes, no commitment.

Get a free bot-traffic audit