Order-exception handling β Summary
Online Store Β· Online Store Coordinator Β· Runs daily100% complete
Nothing waiting for a decision.
Hands-on time per run
1.3h
β 313 h a year
Planned to free (accepted)
0m per run
β 0 hours a year back to the team once done
Still open (recommendations to review)
0m per run
0m planned + 0m open + 1.3h untouched = 1.3h per run
β 0 hours a year if all adopted. Accepted ones sit under Planned to free; nothing here counts more than its step costs
Already automated today
0 of 6 steps
0m of hands-on time is on partly systematised steps β honest baseline, not opportunity
Top friction points
Worst first β how much a step hurts, multiplied by how long it takes. So a long mildly annoying step can outrank a short painful one.
| Step | Who does it | Kind of pain | Hurts | Time | Why it hurts |
|---|---|---|---|---|---|
| Rank 1, step 6, Log the outcome in the daily exceptions sheet | Online Store Coordinator | β | a bit | 5m | Nobody reads the sheet but it's required |
Recommendations
No analysis yet β run βAnalyse workflowβ from the map.
Manual hand-offs between systems
- 3 β 4Data moves from Retail ERP to Ecommerce platform by hand here.
- 5 β 6Data moves from Ecommerce platform to Excel by hand here.
Worked out from the systems named on each step, so check it against how the work really goes. No time or cost is counted for these.