Cybex Retail AI
Sales Audit family

Loss Prevention Analytics

Every ticket line of the week, aggregated to store, day, terminal, cashier and exception, so the loss prevention manager sees who is outside the pattern and why before the next weekend. Built on the sales audit fact, not on a separate feed.

Cashier exception ratesAfter-hours returns & voidsNo-sale drawer opensOver/short by tillPrice overridesWeekly watch list
Loss Prevention Analytics: how the solution reads the governed dataset

The signals

Exception rate

Exception lines per hundred tickets by cashier, terminal and store, against the store and the chain.

After hours

Returns and voids rung before opening or after close, with the hour and the ticket.

Drawer opens

No-sale opens per hundred tickets by terminal, with the reason entered.

Over and short

Cash-out variances by store and terminal, net and gross, recounts flagged.

Price overrides

Override value by cashier and the average per line; tightening the permission where it is high.

Returns and discounts

The reason codes that carry most of the dollars, by cashier and store.

Cashier not seller

Lines rung by one person and attributed to another, combined with any other flag.

Web and stores apart

Web order sites in the totals, out of the rankings, because they carry no ticket count.

The weekly routine

  1. Sunday night

    The audit fact loads with the ETL; the week-scoped dataset resolves the last complete Sunday to Saturday week.

  2. Monday morning

    The exceptions page is generated: chain scorecard, store table, cashier watch list, day by day, seven finding lists with an action each.

  3. Review

    Review CCTV for the tickets, recount the drawer, coach the cashier, tighten the override permission, or no action, recorded against the finding.

  4. Next week

    Same brief, next week, so a coached cashier's rate is visible against the prior week.

What it is built on

The sales audit fact carries every line with its audit type: regular, price override, discount, return, void, no-sale, over/short. Exceptions are flags on the fact, so the loss prevention view, the sales audit view and the finance journal read the same rows.

  • No separate loss prevention feed
  • Cashier and salesperson codes, names joined where permitted
  • After-hours window configurable per store
  • Same dataset feeds the BI series and the dynamic insight
Sales Audit and Loss Prevention pilot

Every exception, every store, on one page by Monday morning.

Audit fact, exception flags, cash-out variances and the weekly loss prevention insight, in production within eight to twelve weeks.