Retail SOP · Mugs

Two of a colour.
Per customer. Every branch.

Drop the daily POS export and see which branches sell over the limit, either on one invoice or by splitting it across many.

Brewing your report… Half Million · Mugs SOP Monitor
Drop the “Sales By Product” export or · .xlsx, .xls, .csv Read in your browser only. Nothing is uploaded. The last file is kept on this computer until you clear it.

How it works

Three checks, one daily file.

01

Direct violation

One invoice has more than two mugs of one colour, for example 6 × Al-Haram Beige.

02

Split-invoice run

The same colour rung on back-to-back invoices, each within the limit, adding up to more. Scored against the branch’s normal pace, so a busy Haram queue isn’t treated like a 1 AM burst.

03

Zero-quantity lines

Lines with 0 quantity or SAR 0, likely voids or returns, listed for review.

Reading a flag

A score that explains itself.

Every split run gets a 0–100 risk score. Open it to see why: how many invoices, how many mugs over the limit, how far above normal pace, and whether the baskets were identical.

  • Invoices in the runup to 30
  • Mugs over the limitup to 25
  • Burst vs normal paceup to 30
  • Identical basketsup to 15
  • High ≥ 60Medium 35–59Low < 35

My account


Change password

Admin

Users

People create their own account. Approve them here: choose Area manager and pick their name (they will only see their own branches), or make them an Admin (uploads data and sees everything).

Name / emailRoleArea managerStatusLast sign-in

Method

How the checks work

1. Rebuilding invoices

The export has no invoice number, so lines with the same branch + closing time (to the millisecond) count as one invoice. If a future export includes an invoice or receipt column, the app uses it automatically.

2. Direct violations

Any invoice with more than the limit of one item (or colour, depending on the setting).

3. Split-invoice runs

For each branch and colour, invoices are put in time order. Invoices no more than the max gap apart are chained into a run. A run is flagged when it has at least the minimum number of invoices, every invoice is within the limit, and the run total is over the limit.

4. Risk score (0–100)

Limits of this version

Without a card token, customer mobile or cashier ID in the export, a split run is likely, not proven. A real queue of different customers can look the same. Check High runs with the branch, POS logs and CCTV.