August 2026 / My store
Draft run · not closedPrototype v0.2 · real August data, masked
For: store manager · J3
What does my store need to explain?
The store's own exceptions, laid out by day and shift so the people who were there can add context.
Decisions this view supportsAdd context to items · Agree a deposit routine · Whether staff need a keying refresher (inter-punches)
Exceptions in my store1,213waiting for context from the store
Inter-punch16rung under the wrong delivery app
Notes added0prototype: none yet
Exceptions by day and shift
When the items happened, so the store can recall what was going on. Evenings carry the most.
Day (06–15)Evening (15–22)Night (22–06)
Table view
| Day | Day (06–15) | Evening (15–22) | Night (22–06) |
|---|---|---|---|
| 01 | 11 | 15 | 26 |
| 02 | 12 | 19 | 13 |
| 03 | 11 | 13 | 6 |
| 04 | 8 | 19 | 7 |
| 05 | 9 | 14 | 8 |
| 06 | 5 | 8 | 8 |
| 07 | 12 | 10 | 8 |
| 08 | 15 | 17 | 16 |
| 09 | 7 | 22 | 8 |
| 10 | 5 | 13 | 4 |
| 11 | 7 | 9 | 4 |
| 12 | 11 | 19 | 7 |
| 13 | 14 | 19 | 9 |
| 14 | 12 | 23 | 21 |
| 15 | 6 | 22 | 13 |
| 16 | 9 | 24 | 11 |
| 17 | 9 | 26 | 7 |
| 18 | 9 | 16 | 11 |
| 19 | 7 | 12 | 5 |
| 20 | 8 | 19 | 11 |
| 21 | 16 | 10 | 13 |
| 22 | 6 | 18 | 8 |
| 23 | 11 | 16 | 11 |
| 24 | 10 | 13 | 6 |
| 25 | 6 | 10 | 6 |
| 26 | 9 | 18 | 10 |
| 27 | 12 | 16 | 11 |
| 28 | 10 | 23 | 23 |
| 29 | 21 | 29 | 20 |
| 30 | 20 | 40 | 17 |
| 31 | 9 | 29 | 7 |
Add context to an item
The store adds what happened; finance explains; the manager accepts.
e.g. Rider showed a Glovo order; tapped Uber by mistake
Add noteVisible to finance and the manager
Exceptions by register
By POS register, not by person.
Table view
| Register | Exceptions |
|---|---|
| Register 4 | 963 |
| Register 5 | 91 |
| Register 99 | 81 |
| Register 1 | 48 |
| Register 3 | 30 |
About peopleThe store sees items by POS register and shift, never by person. Unmatched does not mean someone did wrong (Employment Act s.19 needs wilful default). Only losses the finance manager confirms, with evidence, go to the admin's HR report, and HR decides what follows.
Built from the pipeline run of 10 Oct 2026 (Payments.xlsx + POS export). Customer details are masked and cashiers are shown as pseudonyms. Items tagged "assumed" rest on assumptions in the spec.